For interoperability, it would be ideal for all systems in the healthcare ecosystem to implement the same terminology in the same way with the same information model. However, this is not realistic, as there are many systems with historical proprietary clinical systems already in existence.
In these situations, maps can be useful in different ways.
- Maps can be useful to allow systems that have implemented different terminologies or code sets to communicate temporarily while the systems migrate to the same terminology. These maps will not alter the UI for data entry but can be implemented alongside the data entry to allow users to see the term that is mapped to their entry term, or implemented in the back end when the information is being sent, received or retrieved and reported.
- Maps can also be used to help migrate legacy code systems to standard code systems like SNOMED, by providing a way to translate historical terms to the new standard; this would be a one-time one-step migration strategy
- Maps may be required to allow systems with legacy code or proprietary code systems work with knowledge resources which uses standards like SNOMED CT to allow decision support.
Feedback
Overview
Content Tools
Apps