Defining the scope of the map
Prior to building the map, it’s important to define the scope, processes, and mapping rules to ensure consistency among all personnel involved. These should be documented clearly and updated frequently as required.
The scope of a map is tightly bound to the map's use case and purpose. Once the use case and purpose have been defined, the scope of the map's source and target code systems can be determined.
When defining the scope of the source and target code systems of the map, consider the following:
What is the scope of the source code system?
Does the whole source code system need to be mapped, or is a subset sufficient?
If it is a historical code system, is the subset of codes used in practice sufficient?
Is there a need to map historical or inactive terms?
Is there a need to exclude some terms if ambiguous, duplicates, or not within the required scope?
How is the source code system used in the implementation?
Is the source code system appropriate for the data model it was implemented in?
What is the meaning of the codes in the context of the data model?
How will the map targets be implemented?
Is the target source code system appropriate for the new data model?
What is the scope of the target source code system?
Is the whole target code system appropriate, or is a subset more appropriate?
Are the scopes of the source and target code systems compatible?
Do they match? Should they match?
Requirements for exclusions or specific rules about how the scopes will be translated.
Is there a need for contextual information (e.g. from the information model) to be included in the decision for what the map target should be?
For example, if mapping from the source code system's "Family History" field, then the code 'A123 Breast cancer', when recorded in this field, may need to target a pre-coordinated concept, such as 429740004 |Family history of malignant neoplasm of breast|.
At what level do the terms need to be mapped? Is equivalence the goal, or are we grouping things to a broader target? This will be determined by the use case.
Last updated