How do I implement SNOMED CT in this use case?

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 Search and Data Entry Guide.
  • 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 Search and Data Entry Guide 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.

The implementation process should always start from a detailed analysis of the user requirements, including the data architecture, the available tools, language requirements, and the need to maintain compatibility with legacy vocabularies or classifications. With all that information it's possible to create a project plan, that needs to be executed with some involvement of end-users and that should include a deployment and training plan.

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.