ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1
0.14.0 - CI Build
ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1
0.14.0 - CI Build
ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1 - Local Development build (v0.14.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Active as of 2024-06-01 |
<Requirements xmlns="http://hl7.org/fhir">
<id value="EHRSFMR2.1-TI.10.3"/>
<meta>
<profile value="http://hl7.org/ehrs/StructureDefinition/FMFunction"/>
</meta>
<text>
<status value="extensions"/>
<div xmlns="http://www.w3.org/1999/xhtml">
<span id="description"><b>Statement <a href="https://hl7.org/fhir/versions.html#std-process" title="Normative Content" class="normative-flag">N</a>:</b> <div><p>Map or translate one clinical model to another as needed by local, regional, national, or international interoperability requirements.</p>
</div></span>
<span id="purpose"><b>Description <a href="https://hl7.org/fhir/versions.html#std-process" title="Informative Content" class="informative-flag">I</a>:</b> <div><p>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.
Example:
Example: Within a healthcare organization there may be a need to map terminology concepts with the same semantic meaning to meet different purposes (e.g., between an EHRS and an external laboratory system, or between an EHRS and a billing system). Standard terminologies are evolving and maps will need to be adjusted to support this evolution and more sophisticated use of standard terminologies and maps over time.</p>
<p>Realm specific (including local, regional, national or international) interoperability requirements can also determine the need for clinical model mapping, and in many cases mapping services (internal or external) can be used to satisfy these requirements.</p>
<p>The interaction and mapping of clinical models may be called into question in a legal proceeding, when clinical decisions were documented or when semantic meaning could be misinterpreted. It is important to seek guidance, document and retain all mapping decisions for all types of clinical model mapping, and to recognize when mapping may not be possible from one clinical model to another. The quality of mapping is dependent upon the skills and interpretation of standard clinical models and clinical information by mapping experts.</p>
<p>Note: the mapping of one clinical model to another is mostly done on the level of data elements and value sets. The importance of data is changing over time and to prevent a trend break in research data is mapped to keep old data and use that data in the analysis.$EX$</p>
</div></span>
<span id="requirements"><b>Criteria <a href="https://hl7.org/fhir/versions.html#std-process" title="Normative Content" class="normative-flag">N</a>:</b></span>
<table id="statements" class="grid dict">
<tr>
<td style="padding-left: 4px;">
<span>TI.10.3#01</span>
</td>
<td style="padding-left: 4px;">
<span>SHALL</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHALL provide the ability to manage data using clinical model maps which may be provided by mapping services (internal or external).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>TI.10.3#02</span>
</td>
<td style="padding-left: 4px;">
<span>SHOULD</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHOULD provide the ability to update clinical model maps using standard clinical model services (internal or external).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>TI.10.3#03</span>
</td>
<td style="padding-left: 4px;">
<span>SHOULD</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>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.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>TI.10.3#04</span>
</td>
<td style="padding-left: 4px;">
<span>MAY</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>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.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>TI.10.3#05</span>
</td>
<td style="padding-left: 4px;">
<span>MAY</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>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.</p>
</div></span>
</td>
</tr>
</table>
</div>
</text>
<url value="http://hl7.org/ehrs/Requirements/EHRSFMR2.1-TI.10.3"/>
<version value="0.14.0"/>
<name value="TI_10_3_Clinical_Model_Mapping"/>
<title value="TI.10.3 Clinical Model Mapping (Function)"/>
<status value="active"/>
<date value="2024-06-01T08:34:10+00:00"/>
<publisher value="EHR WG"/>
<contact>
<telecom>
<system value="url"/>
<value value="http://www.hl7.org/Special/committees/ehr"/>
</telecom>
</contact>
<description
value="Map or translate one clinical model to another as needed by local, regional, national, or international interoperability requirements."/>
<purpose
value="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.
Example:
Example: Within a healthcare organization there may be a need to map terminology concepts with the same semantic meaning to meet different purposes (e.g., between an EHRS and an external laboratory system, or between an EHRS and a billing system). Standard terminologies are evolving and maps will need to be adjusted to support this evolution and more sophisticated use of standard terminologies and maps over time.
Realm specific (including local, regional, national or international) interoperability requirements can also determine the need for clinical model mapping, and in many cases mapping services (internal or external) can be used to satisfy these requirements.
The interaction and mapping of clinical models may be called into question in a legal proceeding, when clinical decisions were documented or when semantic meaning could be misinterpreted. It is important to seek guidance, document and retain all mapping decisions for all types of clinical model mapping, and to recognize when mapping may not be possible from one clinical model to another. The quality of mapping is dependent upon the skills and interpretation of standard clinical models and clinical information by mapping experts.
Note: the mapping of one clinical model to another is mostly done on the level of data elements and value sets. The importance of data is changing over time and to prevent a trend break in research data is mapped to keep old data and use that data in the analysis.$EX$"/>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-TI.10.3-01"/>
<label value="TI.10.3#01"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to manage data using clinical model maps which may be provided by mapping services (internal or external)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-TI.10.3-02"/>
<label value="TI.10.3#02"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to update clinical model maps using standard clinical model services (internal or external)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-TI.10.3-03"/>
<label value="TI.10.3#03"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="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."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-TI.10.3-04"/>
<label value="TI.10.3#04"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="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."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-TI.10.3-05"/>
<label value="TI.10.3#05"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="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.
"/>
</statement>
</Requirements>