Last updated
Documentation of mapping methodology and decisions made is important:
to allow reproduction of the mapping process for updates
as evidence of the mapping process undertaken and the rules applied for compliance assessment
A map is not necessarily static; future versions of a map may require changes to decisions or rules, which will need to be clearly defined and consistently applied.
Clear documentation will allow the correct usage of the map and allow users to identify when the meaning of the results of the map has changed
Documentation should include:
identification of source and target code systems (include versioning)
the purpose and use case of the map
intended users of the map
the scope and rules of the map
pre-processing undertaken
processes undertaken to modify data
rules and reasons for changes
personnel involved
tools used
the mapping process used
issues resolution process
validation process
risk assessment
risk management process
Last updated