HL7 Electronic Health Record System Functional Model, Release 2.1.1, published by HL7 International / Electronic Health Records. This guide is not an authorized publication; it is the continuous build for version 2.1.1-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/ehrsfm-ig/ and changes regularly. See the Directory of published versions

• Narrative Content
• XML
• JSON
• TTL

: CPS.1 Record Management (Header) - XML Representation

Page standards status: Informative

Raw xml | Download

<Requirements xmlns="http://hl7.org/fhir">
  <id value="EHRSFMR2-CPS.1"/>
  <meta>
    <profile
             value="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/FMHeader"/>
  </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>Manage the patient record including all patient demographics, identifiers and other information to support the provision of care.</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>Management of the patient record includes creation through quick registration or through a captured referral request as well as managing the patient encounter information linked to the appropriate patient record. It is also critical to manage the patient's relationships through genealogy, insurance, living situation or other means. This section also includes support for the management of patient and family preferences including patient advance directives, consents and authorizations linked to the unique patient record. For those functions related to data capture, data should be captured using standardized code sets or nomenclature, depending on the nature of the data, or captured as unstructured data. Care-setting dependent data are entered by a variety of caregivers. Data may also be captured from devices or other tele-health applications.</p>
</div></span>
    

    
    
    

    
    <table id="statements" class="grid dict">
        
    </table>
</div>
  </text>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="ehr"/>
  </extension>
  <url value="http://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-CPS.1"/>
  <version value="2.1.1-ballot"/>
  <name value="CPS_1_Record_Management"/>
  <title value="CPS.1 Record Management (Header)"/>
  <status value="active"/>
  <date value="2025-08-29T14:03:55+00:00"/>
  <publisher value="HL7 International / Electronic Health Records"/>
  <contact>
    <telecom>
      <system value="url"/>
      <value value="http://www.hl7.org/Special/committees/ehr"/>
    </telecom>
  </contact>
  <description
               value="Manage the patient record including all patient demographics, identifiers and other information to support the provision of care."/>
  <jurisdiction>
    <coding>
      <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
      <code value="001"/>
      <display value="World"/>
    </coding>
  </jurisdiction>
  <purpose
           value="Management of the patient record includes creation through quick registration or through a captured referral request as well as managing the patient encounter information linked to the appropriate patient record. It is also critical to manage the patient's relationships through genealogy, insurance, living situation or other means. This section also includes support for the management of patient and family preferences including patient advance directives, consents and authorizations linked to the unique patient record. For those functions related to data capture, data should be captured using standardized code sets or nomenclature, depending on the nature of the data, or captured as unstructured data. Care-setting dependent data are entered by a variety of caregivers. Data may also be captured from devices or other tele-health applications."/>
</Requirements>