data fits to expectations/specification

preserve what you get

exactly what is specified, nothing else

allow for modifications of the data

taken by association

in an equivalent way

Data received is preserved by 1:1 mapping/translation to an internal value that is semantically equivalent, that preserves the temporal aspect of the translation.

Two concepts are semantically equivalent if they can substitute for each other in the defined use case with no loss of information used to define the concept.

Two concepts are clinically equivalent if they can substitute for each other in the defined use case with no impact on clinical interpretation by a trained clinician. This may include further refinements based on the specific domain, e.g., for Lab use case, this would require interpretation that includes the impact of differences in normal ranges.

Use referenced data based on stored pointer; stored data is displayed by linking to the corresponding stored value most often the case for data elements that are STORED EXACT by ASSOCIATION.

cut off remaining characters from the data thereby shortening the data

extends the expected data with more/own information, e.g. appartment if street is specified

provides the data with more granular details, e.g. house number for an address line

provide a null-flavor/absent reason

this value has no valid representation or meaning in the sending application, it is just added because it is required to be there

how to manage unexpected data (as sender or receiver)

replaces the expected data by something else

take vare of values that are coming but not described/specified. Allows for warnings