How do I implement SNOMED CT in this use case?

A SNOMED CT can be implemented using different user interfaces and techniques, selecting which one depends on the user requirements, for example:

• Use SNOMED CT as the interface and reference vocabulary for the problems list data entry on an Electronic Medical Records application.
  • The user will interact with SNOMED through text search, examples and guidance on these implementations are available in this section of the DOCSEARCH.
  • A translation might be required in order to provide native language terms to the user, the Translations space contains additional information about the requirements and process for translating SNOMED CT content
  • The content allowed for the problems list data entry home page can be constrained to a subset of SNOMED CT. The ECL guide and the Reference Sets Guide cover the most common techniques for constraining data entry.
• Use SNOMED CT for structured data entry on an electronic form:
  • The Data entry section of the DOCSEARCH provides insights on the implementation of these form-based user interfaces.
  • The information on the ECL guide and the Reference Sets Guide also apply to this use case.
• Etc.

Image Removed

implementation starts by understanding all the details and constraints of the eHealth environment, and all the details of the use case.

This information will be used to decide the implementation approach for SNOMED CT and define an architecture for the desired system. 

This architecture will be represented in a detailed implementation plan, and software

developers will work with this information in producing the SNOMED CT integration. In the most common scenario, SNOMED will be incorporated into the software application using a Terminology Service.

In parallel, many implementations require the creation and maintenance of SNOMED CT content, new concepts, translations, maps or reference sets. These terminology artifacts will support the focus use cases, will be managed by a terminology team, and made available to the software developers to be included in the content of the terminology services.

Image Added