Page History
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 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.
- Use advanced SNOMED CT features for analyzing clinical datasets coded with SNOMED CT:
- The Data Analytics with SNOMED CT guide provides information relevant to the implementation of 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.
...
Once you have defined your SNOMED CT roadmap, and selected your use case for SNOMED CT deployment, the SNOMED CT implementation process begins.
The first step in an implementation is to understand the details and constraints of the relevant eHealth environment and the high-level requirements of the use case. This information is needed to select an implementation approach for SNOMED CT and define an architecture for the planned system.
This architecture will form part of a detailed implementation plan, and the implementation team will work with this information to produce the SNOMED CT integration plan. The recommended software architecture for a SNOMED CT enabled system is to use a Terminology Server to provide effective access to the terminology content.
In order to get access to SNOMED CT releases and all future updates, implementations register as affiliates in local National Release Centers or directly with SNOMED International, obtaining credentials to access a SNOMED CT distribution service.
Many implementations also require the creation and maintenance of local SNOMED CT extensions, including SNOMED CT reference sets, maps, translations, and (in some cases) new content. These terminology artefacts will be managed by a terminology team to support the focus use cases, and made available to the deployment team to be included in the content on the terminology server.
| Info | ||
|---|---|---|
| ||
|
Next step: Implementation in progress
| Awesome Icon | ||
|---|---|---|
|
How do I implement SNOMED CT in this use case?
Once you have defined your SNOMED CT roadmap, and selected your use case for SNOMED CT deployment, the SNOMED CT implementation process begins.
The first step in an implementation is to understand the details and constraints of the relevant eHealth environment and the high-level requirements of the use case. This information is needed to select an implementation approach for SNOMED CT and define an architecture for the planned system.
This architecture will form part of a detailed implementation plan, and the implementation team will work with this information to produce the SNOMED CT integration plan. The recommended software architecture for a SNOMED CT enabled system is to use a Terminology Server to provide effective access to the terminology content.
In order to get access to SNOMED CT releases and all future updates, implementations register as affiliates in local National Release Centers or directly with SNOMED International, obtaining credentials to access a SNOMED CT distribution service.
Many implementations also require the creation and maintenance of local SNOEMD CT extensions, including SNOMED CT reference sets, maps, translations, and (in some cases) new content. These terminology artefacts will be managed by a terminology team to support the focus use cases, and made available to the deployment team to be included in the content on the terminology server.
| Info | ||
|---|---|---|
| ||
|
Next step: Implementation in progress
| Awesome Icon | ||
|---|---|---|
|
Overview
Content Tools
Apps
Feedback