HL7 Personal Health Record System Functional Model, Release 2
2.0.1-ballot - Normative Ballot
This page is part of the HL7 Personal Health Record System Functional Model, Release 2 (v2.0.1-ballot: Normative 1 Ballot 1) based on FHIR (HL7® FHIR® Standard) v5.0.0. No current official version has been published yet. For a full list of available versions, see the Directory of published versions
| Page standards status: Informative |
<Requirements xmlns="http://hl7.org/fhir">
<id value="PHRSFMR2-PH.6"/>
<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>Manage information for scheduling, preparation, and assimilation of knowledge gained by encounters with providers.</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>Each interaction with a provider, including office visits, virtual visits, hospitalizations, telephone conversations, or diagnostic procedures, comprise an encounter. Some encounters are non-discretionary such as emergent admission to a level 1 trauma center. Many encounters are initiated by providers in the course of care such as a scheduled chemotherapy treatment. Some encounters are initiated by the PHR Account Holder requiring additional steps facilitated by their PHR-S.</p>
<p>Example(s): The Account Holder makes a self-assessment that his or her chest pain warrants urgent evaluation and telephones an ambulance service. Access to the PHR Account Holder’s PHR information is provided to the ambulance crew and emergency room staff. The resulting assessments, updates to the current data set including problems, procedures, and medications, and new care plans from the hospital evaluation are then incorporated into the PHR Account Holder’s PHR-S during or shortly after the encounter concludes. The Primary Care Provider receives an alert to the changes.</p>
</div></span>
<span id="actors"><b>Actors:</b><br/> ehr</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-PH.6"/>
<version value="2.0.1-ballot"/>
<name value="PH_6_Manage_Encounters_with_Providers"/>
<title value="PH.6 Manage Encounters with Providers (Header)"/>
<status value="active"/>
<date value="2025-04-04T11:42:51+11:00"/>
<publisher value="EHR WG"/>
<contact>
<telecom>
<system value="url"/>
<value value="http://www.hl7.org/Special/committees/ehr"/>
</telecom>
</contact>
<description
value="Manage information for scheduling, preparation, and assimilation of knowledge gained by encounters with providers."/>
<purpose
value="Each interaction with a provider, including office visits, virtual visits, hospitalizations, telephone conversations, or diagnostic procedures, comprise an encounter. Some encounters are non-discretionary such as emergent admission to a level 1 trauma center. Many encounters are initiated by providers in the course of care such as a scheduled chemotherapy treatment. Some encounters are initiated by the PHR Account Holder requiring additional steps facilitated by their PHR-S.
Example(s): The Account Holder makes a self-assessment that his or her chest pain warrants urgent evaluation and telephones an ambulance service. Access to the PHR Account Holder’s PHR information is provided to the ambulance crew and emergency room staff. The resulting assessments, updates to the current data set including problems, procedures, and medications, and new care plans from the hospital evaluation are then incorporated into the PHR Account Holder’s PHR-S during or shortly after the encounter concludes. The Primary Care Provider receives an alert to the changes."/>
</Requirements>