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

## : TI.10.1 Standard or Preferred Clinical Models (Function) - XML Representation

Page standards status: Informative

Raw xml | Download

    <Requirements xmlns="http://hl7.org/fhir">
      <id value="PHRSFMR2-TI.10.1"/>
      <meta>
        <profile
                 value="http://hl7.org/ehrs/uv/phrsfmr2/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>Employ approved standard or Preferred Clinical Models to ensure structured data correctness and to enable semantic interoperability (both within an enterprise and externally). Support a standard or Preferred Clinical Models model.</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>Healthcare is shifting from supply-oriented care to more demand / patient-oriented integrated care. The focus is the patient and the integrated care he needs executed by one or more healthcare provider(s) in one or more organizations. Information on the patient must be shared by these healthcare providers and organizations. The PHR system must be focused on a problem-oriented recording in an integrated PHR system. This recording should take place in the care process and seamlessly fit in the workflow of the healthcare professional. When the information is properly recorded in the PHR, these information can be reused: by other healthcare providers, for deriving quality information, financial information and for research. For this purposes the use of widely accepted international standards is necessary.</p>
    <p>Clinical Models are used to capture functional, semantic (non-technical) agreements for the standardization of information used in the care process. The purpose of the standardization is that this information from the care process is reused for other purposes such as quality registration, transfer or patient-related research. A Clinical Model is an information model in which a care-based concept is described in terms of the data elements from which that concept exists, the data types of those data elements, the binding to a (standard) terminology, etc.
    Clinical models are information models of minimal clinical concepts, each containing multiple data with agreed content, structure and mutual relationship.</p>
    <p>The binding to a terminology provides semantic and computable identity to its concepts. Examples of terminologies that a PHR-S may support include: LOINC, SNOMED, ICD-9, ICD-10, and CPT-4. See also Function TI.4 Standard Terminology and Terminology Services.</p>
    <p>The key is that the standard be approved by all stakeholders. For example, a standard Clinical Model for 'Problem'. The information that is recorded in the PHR according to the Clinical Model can be reused for other purposes as quality registration, transfer or patient-related research.</p>
    </div></span>

        <span id="actors"><b>Actors:</b><br/> ehr</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.1#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 exchange data with other systems (internal or external to the PHR-S) using approved standard or preferred clinical models or compositions of clinical models (e.g patient summary, follow-up message).</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>TI.10.1#02</span>

                </td>
                <td style="padding-left: 4px;">

                    <span>SHALL</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>The system SHALL determine that clinical terms and coded clinical data exist in an approved Clinical Model.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>TI.10.1#03</span>

                </td>
                <td style="padding-left: 4px;">

                    <i>dependent</i>

                    <span>SHOULD</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>The system SHOULD provide the ability to receive and transmit healthcare data using formal standard information models and approved standard or preferred clinical models according to scope of practice, organizational policy, and/or jurisdictional law.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>TI.10.1#04</span>

                </td>
                <td style="padding-left: 4px;">

                    <i>dependent</i>

                    <span>SHOULD</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>The system SHOULD provide the ability to manage data using a standard or preferred clinical model according to scope of practice, organizational policy, and/or jurisdictional law.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>TI.10.1#05</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 clical model assets and supporting tools (internal or external to the PHR-S).</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>TI.10.1#06</span>

                </td>
                <td style="padding-left: 4px;">

                    <i>conditional</i>

                    <span>MAY</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>IF there is no recognized-standard or preferred clinical model available, THEN the system MAY provide the ability to manage data using a locally-defined clinical model.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>TI.10.1#07</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 capture information into structured data formats using approved standard or preferred clinical models without the user requiring knowledge of the clinical models used.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>TI.10.1#08</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 enter data using content that is common to the user, and allow for collection and presentation of text form data to meet the pre-determined purposes of others. Text forms should exclude cryptic or uncommon abbreviations.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>TI.10.1#09</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 present the terms used in standard or preferred clinical models in a language which is appropriate for the user.</p>
    </div></span>

                </td>
            </tr>

        </table>
    </div>
      </text>
      <extension
                 url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
        <valueCode value="ehr"/>
      </extension>
      <url value="http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-TI.10.1"/>
      <version value="2.0.1-ballot"/>
      <name value="TI_10_1_Standard_or_Preferred_Clinical_Models"/>
      <title value="TI.10.1 Standard or Preferred Clinical Models (Function)"/>
      <status value="active"/>
      <date value="2025-04-04T11:42:51+11:00"/>
      <publisher value="EHR WG"/>
      <contact>
        <telecom>
          <system value="url"/>
          <value value="http://www.hl7.org/Special/committees/ehr"/>
        </telecom>
      </contact>
      <description
                   value="Employ approved standard or Preferred Clinical Models to ensure structured data correctness and to enable semantic interoperability (both within an enterprise and externally). Support a standard or Preferred Clinical Models model."/>
      <purpose
               value="Healthcare is shifting from supply-oriented care to more demand / patient-oriented integrated care. The focus is the patient and the integrated care he needs executed by one or more healthcare provider(s) in one or more organizations. Information on the patient must be shared by these healthcare providers and organizations. The PHR system must be focused on a problem-oriented recording in an integrated PHR system. This recording should take place in the care process and seamlessly fit in the workflow of the healthcare professional. When the information is properly recorded in the PHR, these information can be reused: by other healthcare providers, for deriving quality information, financial information and for research. For this purposes the use of widely accepted international standards is necessary.

    Clinical Models are used to capture functional, semantic (non-technical) agreements for the standardization of information used in the care process. The purpose of the standardization is that this information from the care process is reused for other purposes such as quality registration, transfer or patient-related research. A Clinical Model is an information model in which a care-based concept is described in terms of the data elements from which that concept exists, the data types of those data elements, the binding to a (standard) terminology, etc.
    Clinical models are information models of minimal clinical concepts, each containing multiple data with agreed content, structure and mutual relationship.

    The binding to a terminology provides semantic and computable identity to its concepts. Examples of terminologies that a PHR-S may support include: LOINC, SNOMED, ICD-9, ICD-10, and CPT-4. See also Function TI.4 Standard Terminology and Terminology Services.

    The key is that the standard be approved by all stakeholders. For example, a standard Clinical Model for 'Problem'. The information that is recorded in the PHR according to the Clinical Model can be reused for other purposes as quality registration, transfer or patient-related research."/>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="PHRSFMR2-TI.10.1-01"/>
        <label value="TI.10.1#01"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to exchange data with other systems (internal or external to the PHR-S) using approved standard or preferred clinical models or compositions of clinical models (e.g patient summary, follow-up message)."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="PHRSFMR2-TI.10.1-02"/>
        <label value="TI.10.1#02"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL determine that clinical terms and coded clinical data exist in an approved Clinical Model."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="true"/>
        </extension>
        <key value="PHRSFMR2-TI.10.1-03"/>
        <label value="TI.10.1#03"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to receive and transmit healthcare data using formal standard information models and approved standard or preferred clinical models according to scope of practice, organizational policy, and/or jurisdictional law."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="true"/>
        </extension>
        <key value="PHRSFMR2-TI.10.1-04"/>
        <label value="TI.10.1#04"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to manage data using a standard or preferred clinical model according to scope of practice, organizational policy, and/or jurisdictional law."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="PHRSFMR2-TI.10.1-05"/>
        <label value="TI.10.1#05"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to manage clical model assets and supporting tools (internal or external to the PHR-S)."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="PHRSFMR2-TI.10.1-06"/>
        <label value="TI.10.1#06"/>
        <conformance value="MAY"/>
        <conditionality value="true"/>
        <requirement
                     value="IF there is no recognized-standard or preferred clinical model available, THEN the system MAY provide the ability to manage data using a locally-defined clinical model."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="PHRSFMR2-TI.10.1-07"/>
        <label value="TI.10.1#07"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to capture information into structured data formats using approved standard or preferred clinical models without the user requiring knowledge of the clinical models used."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="PHRSFMR2-TI.10.1-08"/>
        <label value="TI.10.1#08"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to enter data using content that is common to the user, and allow for collection and presentation of text form data to meet the pre-determined purposes of others. Text forms should exclude cryptic or uncommon abbreviations."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="PHRSFMR2-TI.10.1-09"/>
        <label value="TI.10.1#09"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to present the terms used in standard or preferred clinical models in a language which is appropriate for the user."/>
      </statement>
    </Requirements>