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

: PH.2.5 Manage Historical and Current State Data (Function) - XML Representation

Page standards status: Informative

Raw xml | Download


<Requirements xmlns="http://hl7.org/fhir">
  <id value="PHRSFMR2-PH.2.5"/>
  <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>Maintain the summary lists depicting the PHR Account Holder’s current medical state and history.</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 current state data set is a data model of the PHR Account Holder that is useful to the PHR Account Holder, but is particularly useful to any healthcare provider who is asked by the PHR Account Holder for help. These data characterize the PHR Account Holder in current time and is useful in the evaluation of new conditions and predictive of how they might respond to treatments and/or therapies. Receiving these data in the PHR in an electronic and automated fashion may obviate having to recreate the data manually with every new encounter. For many of these elements, the PHR Account Holder is the primary authority. The following data elements are examples of information that is managed over time, across encounters with providers, and for particular health conditions:</p>
<ul>
<li>Problems (including Diagnoses)</li>
<li>Medications</li>
<li>Test Results</li>
<li>Allergies and intolerances</li>
<li>Medical history</li>
<li>Surgical history</li>
<li>Immunizations</li>
<li>Family history</li>
<li>Genetic information</li>
<li>Social history, including family relationship and work information.</li>
<li>Providers' notes</li>
</ul>
<p>Work information could be defined using the Occupational Data for Health (ODH) data elements:</p>
<ul>
<li>Current employment status (e.g., employed for wages);</li>
<li>Current job data: job employment type (e.g., self-employed), occupation and industry with the start and end dates, employer name and location, job duties, work schedule;</li>
<li>Usual, or longest-held, occupation and industry, with duration and start date.</li>
</ul>
<p>Specific complaints, history of present illness, review of systems, and the physical examination are more episodic and encounter specific.</p>
<p>Example(s): Current Problems, Medications taken, allergies, immunizations, past medical illnesses, surgeries, family history, and social history including habits along with recent diagnostic studies provide data useful for directing care.</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>PH.2.5#01</span>
                
            </td>
            <td style="padding-left: 4px;">
                
                <i>dependent</i>
                
                
                
                <span>SHOULD</span>
                
            </td>
            <td style="padding-left: 4px;" class="requirement">
                
                <span><div><p>The system SHOULD provide the ability for the PHR Account Holder and other Authorized PHR Users to render information about the PHR Account Holder's health conditions according to user role, organizational policy, and/or jurisdictional law.</p>
</div></span>
                
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
                
                <span>PH.2.5#02</span>
                
            </td>
            <td style="padding-left: 4px;">
                
                <i>dependent</i>
                
                
                
                <span>SHOULD</span>
                
            </td>
            <td style="padding-left: 4px;" class="requirement">
                
                <span><div><p>The system SHOULD provide the ability for the PHR Account Holder to manage user-configuration parameters regarding their preferences for rendering PHR Account Holder information according to organizational policy and/or jurisdictional law.</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-PH.2.5"/>
  <version value="2.0.1-ballot"/>
  <name value="PH_2_5_Manage_Historical_and_Current_State_Data"/>
  <title value="PH.2.5 Manage Historical and Current State Data (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="Maintain the summary lists depicting the PHR Account Holder’s current medical state and history."/>
  <purpose
           value="The current state data set is a data model of the PHR Account Holder that is useful to the PHR Account Holder, but is particularly useful to any healthcare provider who is asked by the PHR Account Holder for help. These data characterize the PHR Account Holder in current time and is useful in the evaluation of new conditions and predictive of how they might respond to treatments and/or therapies. Receiving these data in the PHR in an electronic and automated fashion may obviate having to recreate the data manually with every new encounter. For many of these elements, the PHR Account Holder is the primary authority. The following data elements are examples of information that is managed over time, across encounters with providers, and for particular health conditions:

- Problems (including Diagnoses)
- Medications
- Test Results 
- Allergies and intolerances
- Medical history
- Surgical history
- Immunizations
- Family history
- Genetic information
- Social history, including family relationship and work information.
- Providers' notes

Work information could be defined using the Occupational Data for Health (ODH) data elements:
- Current employment status (e.g., employed for wages); 
- Current job data: job employment type (e.g., self-employed), occupation and industry with the start and end dates, employer name and location, job duties, work schedule; 
- Usual, or longest-held, occupation and industry, with duration and start date.

Specific complaints, history of present illness, review of systems, and the physical examination are more episodic and encounter specific.

Example(s): Current Problems, Medications taken, allergies, immunizations, past medical illnesses, surgeries, family history, and social history including habits along with recent diagnostic studies provide data useful for directing care."/>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="true"/>
    </extension>
    <key value="PHRSFMR2-PH.2.5-01"/>
    <label value="PH.2.5#01"/>
    <conformance value="SHOULD"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHOULD provide the ability for the PHR Account Holder and other Authorized PHR Users to render information about the PHR Account Holder's health conditions according to user role, organizational policy, and/or jurisdictional law."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="true"/>
    </extension>
    <key value="PHRSFMR2-PH.2.5-02"/>
    <label value="PH.2.5#02"/>
    <conformance value="SHOULD"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHOULD provide the ability for the PHR Account Holder to manage user-configuration parameters regarding their preferences for rendering PHR Account Holder information according to organizational policy and/or jurisdictional law."/>
  </statement>
</Requirements>