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.1.3 Manage Health Care Provider Information (Function) - XML Representation

Page standards status: Informative

Raw xml | Download


<Requirements xmlns="http://hl7.org/fhir">
  <id value="PHRSFMR2-S.1.3"/>
  <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>Support the import or retrieval of data necessary to identify a healthcare provider.</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>This information will assist the PHR Account Holder in contacting a provider to schedule appointments and ask health-related questions. The provider roles include, but are not limited to, physician, nurse and physical therapist.</p>
</div></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>S.1.3#01</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 regarding a provider’s location or contact information regarding a facility.</p>
</div></span>
                
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
                
                <span>S.1.3#02</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 manage information regarding a provider's location, contact information, hours of operation, role as a member of the PHR Account Holder’s care team, and authorizations attributed to the provider.</p>
</div></span>
                
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
                
                <span>S.1.3#03</span>
                
            </td>
            <td style="padding-left: 4px;">
                
                <i>dependent</i>
                
                
                
                <span>MAY</span>
                
            </td>
            <td style="padding-left: 4px;" class="requirement">
                
                <span><div><p>The system MAY provide the ability for the PHR Account Holder to hide or mask selected elements of the provider’s identifying information according to the PHR Account Holder's authorization, organizational policy, and/or jurisdictional law. For example, the PHR Account Holder might desire to mask the physician's specialty as a drug counselor.</p>
</div></span>
                
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
                
                <span>S.1.3#04</span>
                
            </td>
            <td style="padding-left: 4px;">
                
                
                <i>conditional</i>
                
                
                <span>SHOULD</span>
                
            </td>
            <td style="padding-left: 4px;" class="requirement">
                
                <span><div><p>IF a directory service is available, THEN the system SHOULD update a provider’s current information via that directory service.</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-S.1.3"/>
  <version value="2.0.1-ballot"/>
  <name value="S_1_3_Manage_Health_Care_Provider_Information"/>
  <title value="S.1.3 Manage Health Care Provider Information (Function)"/>
  <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="Support the import or retrieval of data necessary to identify a healthcare provider."/>
  <purpose
           value="This information will assist the PHR Account Holder in contacting a provider to schedule appointments and ask health-related questions. The provider roles include, but are not limited to, physician, nurse and physical therapist."/>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="PHRSFMR2-S.1.3-01"/>
    <label value="S.1.3#01"/>
    <conformance value="SHOULD"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHOULD provide the ability to capture information regarding a provider’s location or contact information regarding a facility."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="PHRSFMR2-S.1.3-02"/>
    <label value="S.1.3#02"/>
    <conformance value="SHOULD"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHOULD provide the ability to manage information regarding a provider's location, contact information, hours of operation, role as a member of the PHR Account Holder’s care team, and authorizations attributed to the provider."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="true"/>
    </extension>
    <key value="PHRSFMR2-S.1.3-03"/>
    <label value="S.1.3#03"/>
    <conformance value="MAY"/>
    <conditionality value="false"/>
    <requirement
                 value="The system MAY provide the ability for the PHR Account Holder to hide or mask selected elements of the provider’s identifying information according to the PHR Account Holder's authorization, organizational policy, and/or jurisdictional law. For example, the PHR Account Holder might desire to mask the physician's specialty as a drug counselor."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="PHRSFMR2-S.1.3-04"/>
    <label value="S.1.3#04"/>
    <conformance value="SHOULD"/>
    <conditionality value="true"/>
    <requirement
                 value="IF a directory service is available, THEN the system SHOULD update a provider’s current information via that directory service."/>
  </statement>
</Requirements>