HL7 Personal Health Record System Functional Model, Release 2
2.0.1-ballot - Normative Ballot

Publication Build: This will be filled in by the publication tooling

## Requirements: TI.10.3 Clinical Model Mapping (Function)

Page standards status: Informative

Statement N:

Map or translate one clinical model to another as needed by local, regional, national, or international interoperability requirements.

Description I:

The ability to map or translate one clinical model to another is fundamental to an organization in an environment where several clinical models are in play to meet different purposes. It is a common occurrence that data is captured using one clinical model, but is shared using another clinical model.

Actors:
ehr Criteria N:

TI.10.3#01 | SHALL | The system SHALL provide the ability to manage data using clinical model maps which may be provided by mapping services (internal or external).
TI.10.3#02 | SHOULD | The system SHOULD provide the ability to update clinical model maps using standard clinical model services (internal or external).
TI.10.3#03 | SHOULD | The system SHOULD provide the ability to render data quality and technical quality reports for a user to determine the validity of clinical model mappings using approved mapping techniques.
TI.10.3#04 | MAY | The system MAY provide the ability for a user to maintain custom clinical model maps using approved mapping techniques where formal standard clinical model maps are unavailable.
TI.10.3#05 | MAY | The system MAY provide the ability for a user to maintain custom clinical model maps to formal standard clinical model maps in order to support historical data use.