This document presents a set of high-level examples of categories and requirements that could be considered when procuring a SNOMED CT enabled EMR or EHR system. These requirements remain relatively generic in order to be broadly applicable across Member countries and territories. 

Goals and Objectives

The intent of this document is to spark thinking within each Member’s National Release Center (NRC) in terms of the categories and types of requirements they may want to consider (and build on) in their local procurements. This document will also provide vendors with example SNOMED CT requirements that might be requested of products being procured.

Disclaimer:

• Please note that the exact SNOMED CT requirements that should be included in an EMR or EHR procurement depend upon the specific use case.

Target Audience

The target audience for this Example Guide includes:

• People from various disciplines who may be involved at any point in the procurement of an EMR/EHR system that includes SNOMED CT – from initial planning, analysis and clinical content definition and implementation through to use of the resulting clinical information. This spans people involved with planning and deciding to proceed and resource a SNOMED CT implementation, people involved in reference set development, terminology management, clinical subject matter experts, technical implementation and all aspects of deployment and use. It also includes people involved in clinical information retrieval, analyses, decision support and other aspects of knowledge representation.
• Vendors that may be interested in responding to procurement opportunities that include requirements for EMR/EHR systems containing SNOMED CT. The intent is to provide vendors with an understanding of generic or baseline requirements for provisioning a SNOMED CT – enabled system. 

Topics

The topics covered in this SNOMED CT Example EMR/EHR Requirements Guide include:

• Edition, Language and Content
• User Interface
• Analytics and Reporting
• Maintenance
• Storage
• Interoperability
• Additional Resources