Defining use case and purpose
The method of creating a map, the rules and processes associated are tightly bound to the map's purpose, use case and requirements.
It is important that the map's use case and purpose are well defined prior to beginning map development and documented clearly for reference during development and for implementations. The map's use case and purpose have flow on effects through the maps lifecycle.
When thinking about this, consider:
What is the main purpose of this map?
Who is the intended audience?
What is the scope of content (source and target)?
Who is responsible for developing and maintaining the map?
How will the map be implemented?
Use case and purpose
A map must have a defined and specific purpose
Provides context to the map
Influences decisions/rules made when mapping and how to map when there is discrepancies between the source and target code systems
Example: the purpose of this map is to allow for Emergency Department SNOMED CT principal diagnosis codes to be mapped to the national Emergency Department National Minimum Data Set for funding.
Beware when reusing maps or repurposing mapped data, as even though the source and target code systems may appear the same and the healthcare setting may be the same, the purpose (and hence the rules used to build the map) may differ and can give unexpected and/or unwanted results!
Examples include:
coding for a clinical purpose vs a financial/funding purpose
two different funding maps
Example use cases, purposes, and considerations
Last updated