HL7 Personal Health Record System Functional Model, Release 2
2.0.1-ballot - Normative Ballot

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

: S.3 Administration Management (Header) - XML Representation

Page standards status: Informative

Raw xml | Download


<Requirements xmlns="http://hl7.org/fhir">
  <id value="PHRSFMR2-S.3"/>
  <meta>
    <profile
             value="http://hl7.org/ehrs/uv/phrsfmr2/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>The purpose of this section is to provide the system support in managing the PHR-S and the interaction with other PHR and EHR systems. It also serves as a set of functions to manage documentation related to the PHR-S as well as legal documents that affect or may affect the PHR Account Holder.</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 PHR Account Holder (or the PHR Account Holder's Proxy) may desire to share certain demographic information with other stakeholders. The PHR Account Holder may also desire to review and comply with the PHR system manufacturer's conditions-of-use of the PHR system and associated informational artifacts. Additionally, the PHR system could benefit the PHR Account Holder by managing copies of certain health-related documents such as End-Of-Life Care statements, Advance Directives, Consents, Authorizations, and PHR information disclosure-control statements. The PHR Account Holder may also desire to import and/or export certain PHR information.</p>
<p>Example(s):
The PHR Account Holder may desire to restrict the sharing of Advance Directive information to only that of immediate family members.
The PHR Account Holder may desire to name a certain family relative as the PHR Account Holder's authorized designee.</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/phrsfmr2/Requirements/PHRSFMR2-S.3"/>
  <version value="2.0.1-ballot"/>
  <name value="S_3_Administration_Management"/>
  <title value="S.3 Administration Management (Header)"/>
  <status value="active"/>
  <date value="2025-08-29T14:03:44+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 purpose of this section is to provide the system support in managing the PHR-S and the interaction with other PHR and EHR systems. It also serves as a set of functions to manage documentation related to the PHR-S as well as legal documents that affect or may affect the PHR Account Holder."/>
  <purpose
           value="The PHR Account Holder (or the PHR Account Holder's Proxy) may desire to share certain demographic information with other stakeholders. The PHR Account Holder may also desire to review and comply with the PHR system manufacturer's conditions-of-use of the PHR system and associated informational artifacts. Additionally, the PHR system could benefit the PHR Account Holder by managing copies of certain health-related documents such as End-Of-Life Care statements, Advance Directives, Consents, Authorizations, and PHR information disclosure-control statements. The PHR Account Holder may also desire to import and/or export certain PHR information.

Example(s):
The PHR Account Holder may desire to restrict the sharing of Advance Directive information to only that of immediate family members.
The PHR Account Holder may desire to name a certain family relative as the PHR Account Holder's authorized designee."/>
</Requirements>