Camilla Baek

It’s about time to improve health mapping quality and reduce manual mapping time

September 8, 2021

Manual mapping has had its era, and most healthcare organizations say it’s becoming a burden to maintain. It is about time for all healthcare organizations to acquire an IT system that supports mapping activities and improves the mapping quality.  

Why and how? Through semantic interoperability, we will shape the future of healthcare, and mapping is a key part of it.  

What is healthcare data mapping?  

Semantic interoperability is the ability for an information technology (IT) system to receive information from another IT system and reliably apply its business rules to the information received. To achieve semantic interoperability, the health system must adopt and implement consistent clinical messaging and data standards that provide a framework and language for communicating a shared meaning. This is where mapping comes into place. 

Standard vocabularies for representing clinical data have matured over the last few years and have been internationally adopted in many areas.  

For example, Logical Observation Identifiers Names and Codes (LOINC; Regenstrief Institute, Inc., Indianapolis, IN), provide universal identifiers for laboratory tests and other clinical observations, and Systematized Nomenclature of Medicine–Clinical Terms (SNOMED CT) provides universal identifiers for organisms, substances, diseases, and other findings that may be recorded in the medical records or identified in test results.  

Although clinical data standards are available, most hospitals, laboratories, and physicians continue to rely on local and idiosyncratic ways of identifying clinical observations (e.g. laboratory tests and clinical measurements).  

Therefore, to understand the local clinical data from a hospital, healthcare organizations must often translate data into standardized LOINC and SNOMED CT codes. This transformation process is known as mapping.  

Challenges of mapping local codes to international standardized codes  

Mapping local terms to standard vocabularies is complex and resource intensive. Identifying the correct concept from the standard vocabulary requires specific domain knowledge and knowledge of the target vocabulary standards. 

In addition, local laboratory test names often lack the information needed to appropriately identify the correct standard concept. For example, test names may lack an indication of the specimen type or whether the result returned is quantitative or ordinal. 

Similarly, the units of measure associated with a result may not be available during mapping. This missing information can increase the risk of having ambiguous test names, which makes the mapping process more challenging.  

Furthermore, data representation of the local clinical observations can vary as different people typically have been a part of developing the local vocabulary list. For example, the granularity and descriptive information for each entity in the same hospital can vary. This variation can make the concept identification more complex than normal as information needs to be gathered at different places. 

Tools to optimize the mapping process 

Rhapsody has many years of experience with different data structures both local code systems and international standards. Based on our research and client experience, the mapping should leverage as much source or local code system information as can be collected.  

Additional properties, values, and fields are needed because the local code descriptions are typically less granular compared to the international standards. Utilizing the full scope of the local content will increase the accuracy of the mapping. A lot of different tools are available to automatically map your local codes into a standard, both using simple algorithms or AI-based algorithms.  

However, each local code system is unique, and using one algorithm or a domain-optimized algorithm sometimes isn’t always enough to ensure high clinical quality mappings. The clinical domain is not so simple that algorithms used for auto-mapping can be one-size-fits-all.  

Incorporating the subject matter expert’s knowledge of both the local and standard code system is of paramount importance to achieve a successful automatic mapping. Rhapsody Semantic provides a mapping tool to configure your own algorithm(s) to ensure the needed clinical domain knowledge is included when mapping match suggestions are generated. 

Using tools to improve the mapping process does not (and perhaps should not) necessarily replace the expert human reviews, but it can reduce the time spent on the mapping process. We still suggest that expert reviews are needed to resolve the computer-generated suggested mappings as local and standard vocabularies evolve and the clinical understanding of ambiguity and use are difficult to replace. 

Furthermore, the burden of maintaining the manual mappings is significant, ongoing, and easily underestimated. Therefore, all healthcare organizations – whether data senders, receivers, or both – require people, processes, and tools to support mapping activities and improve the mapping quality. 

For further reading, check out these resources: 

Ready to discuss semantic terminology management for your healthcare organization? Let’s talk

Related Blogs

Rhapsody Health Solutions Team

Opening a digital front door that removes friction between patients, providers, and payers with trusted, actionable data

Geisinger shares they’re freeing up resources, boosting efficiency, and transforming how healthcare data is used throughout Pennsylvania with Rhapsody integration and identity solutions

Read more

Gevik Nalbandian

Why patients should own their data

It’s time to flip the script on healthcare data ownership and take a patient-centric approach.

Read more

Jamie Light

Chief Strategy Officer shares data interoperability expertise on US and UK health digitization debate

Drew Ivan discusses the constant need for interoperability following any health digitization with HIMSS CEO, Hal Wolf and Healthcare World’s Steve Gardner.

Read more