3. Design eHealth architecture
The third step in the SNOMED CT implementation process is to design your eHealth architecture incorporating SNOMED CT, based on the information collected in the previous steps.
Different implementation approaches can be used to implement SNOMED CT within different parts of a clinical system. Implementation approaches include using SNOMED CT as:
A code system to store clinical data in health records
An interface terminology on the user interface
An indexing system to retrieve clinical data from health records
A common terminology for data exchange or integration
A dictionary for data analytics, decision support or linking to clinical guidelines
A combination of any of the above
Each of these approaches can support different use case requirements, and influence the broader components of the eHealth architecture.
Design target eHealth architecture
Identify existing clinical systems and data formats
Plan shared electronic health records, clinical registries and terminology servers
Design information models and data flows
Define SNOMED CT specific requirements
Terminology content requirements, e.g. which SNOMED CT edition and versions will be used?
Requirements for the user interface, storage, and terminology services
Requirements for data analytics, decision support, and the implementation of smart clinical guidelines
Create a detailed implementation plan
A shared plan between the teams in charge of implementing new terminology services and updating existing applications
Suggested resources and services