EHRS-FM IG

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

: AS.3 Manage Personal Health Record Interaction (Header) - XML Representation

Active as of 2024-06-01

Raw xml | Download



<Requirements xmlns="http://hl7.org/fhir">
  <id value="EHRSFMR2.1-AS.3"/>
  <meta>
    <profile value="http://hl7.org/ehrs/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>Provide the system support in managing the interaction with a patient's PHR.</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 system can support interaction with the patient's PHR. It can also manage documentation related to the PHR-S consent and access directives.</p>
</div></span>
    

    

    
    <table id="statements" class="grid dict">
        
    </table>
</div>
  </text>
  <url value="http://hl7.org/ehrs/Requirements/EHRSFMR2.1-AS.3"/>
  <version value="0.14.0"/>
  <name value="AS_3_Manage_Personal_Health_Record_Interaction"/>
  <title value="AS.3 Manage Personal Health Record Interaction (Header)"/>
  <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="Provide the system support in managing the interaction with a patient's PHR."/>
  <purpose
           value="The system can support interaction with the patient's PHR. It can also manage documentation related to the PHR-S consent and access directives."/>
</Requirements>