Publish Box goes here

• Narrative Content
• XML
• JSON
• TTL

: Care Provision Support - XML Representation

Active as of 2024-11-26

Raw xml | Download

<Requirements xmlns="http://hl7.org/fhir">
  <id value="EHRSFMR2.1-CPS"/>
  <meta>
    <profile value="http://hl7.org/ehrs/StructureDefinition/FMSection"/>
  </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>The Care Provision Support Section focusses on functions required to support the provision of care to a specific patient to enable hands-on delivery of healthcare. This section is organized generally in alignment with Care Provision Section. For example, CP.4 (Manage Orders) is supported directly by CPS.4 (Support Orders). This alignment is designed to assist in finding related support functions related to care provision functions but is not expected to be 100% matched as some Care Provision Functions do not require matching Support functions or vice-versa.</p>
<p>All functions within the Care Provision Support Section have an identifier starting with “CPS”.</p>
</div></span>

    

    

    
    <table id="statements" class="grid dict">
        
    </table>
</div>
  </text>
  <url value="http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CPS"/>
  <version value="2.1.0"/>
  <name value="Care_Provision_Support"/>
  <title value="Care Provision Support"/>
  <status value="active"/>
  <date value="2024-11-26T16:30:50+00:00"/>
  <publisher value="EHR WG"/>
  <contact>
    <telecom>
      <system value="url"/>
      <value value="http://www.hl7.org/Special/committees/ehr"/>
    </telecom>
  </contact>
  <description
               value="The Care Provision Support Section focusses on functions required to support the provision of care to a specific patient to enable hands-on delivery of healthcare. This section is organized generally in alignment with Care Provision Section. For example, CP.4 (Manage Orders) is supported directly by CPS.4 (Support Orders). This alignment is designed to assist in finding related support functions related to care provision functions but is not expected to be 100% matched as some Care Provision Functions do not require matching Support functions or vice-versa.

All functions within the Care Provision Support Section have an identifier starting with “CPS”."/>
  <jurisdiction>
    <coding>
      <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
      <code value="001"/>
      <display value="World"/>
    </coding>
  </jurisdiction>
</Requirements>