ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1
0.16.0 - CI Build
ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1
0.16.0 - CI Build
Publish Box goes here
| Active as of 2024-08-12 |
<Requirements xmlns="http://hl7.org/fhir">
<id value="EHRSFMR2.1-CP.1.1"/>
<meta>
<profile value="http://hl7.org/ehrs/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>Manage medical, procedural/surgical, mental health, substance use, social and family history. This includes pertinent positive and negative histories, patient-reported or externally available patient clinical 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 history of the current illness and patient historical data related to previous medical diagnoses, surgeries and other procedures performed on the patient, clinicians involved in procedures or in past consultations, and relevant health conditions of family members is captured through such methods as patient reporting (e.g., interview, medical alert band) or electronic or non-electronic historical data. This data may take the form of a pertinent positive such as "The patient/family member has had..." or a pertinent negative such as "The patient/family member has not had...". When first seen by a health care provider, patients typically bring with them clinical information from past encounters. This and similar information may supplement locally captured documentation and notes wherever appropriate. Information regarding the patient's living situations may be an important means for a provider to uniquely identify a patient or to identify illnesses that may occur within a given proximity. Information regarding past or present living situations or environmental factors related to the patient or the fetal death may include a description of the father's type of occupation and occupational demographic information (such as the name and location of the employment). For example, it may be important for the clinician to know that the patient works in an occupation where lead exposure is common. It may also be important for the clinician to know that the patient lives in a household where asbestos routinely appears on clothing.</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>CP.1.1#01</span>
</td>
<td style="padding-left: 4px;">
<span>SHALL</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHALL provide the ability to manage current patient history including pertinent positive and negative elements (e.g., diagnosis or ruled out diagnosis), and information on clinicians involved.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.1.1#02</span>
</td>
<td style="padding-left: 4px;">
<i>dependent</i>
<span>SHALL</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHALL provide the ability to manage the identity of clinicians involved in patient history elements according to scope of practice, organizational policy, and/or jurisdictional law.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.1.1#03</span>
</td>
<td style="padding-left: 4px;">
<span>SHOULD</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHOULD conform to function [[CPS.2.1]] (Support externally-sourced Clinical Documents) to capture, store and render previous external patient histories.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.1.1#04</span>
</td>
<td style="padding-left: 4px;">
<span>SHOULD</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHOULD conform to function [[CPS.2.2]] (Support externally-sourced Clinical Data) to capture, store and render previous external patient histories.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.1.1#05</span>
</td>
<td style="padding-left: 4px;">
<span>SHALL</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHALL provide the ability to capture family history.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.1.1#06</span>
</td>
<td style="padding-left: 4px;">
<span>SHALL</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHALL provide the ability to capture social history.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.1.1#07</span>
</td>
<td style="padding-left: 4px;">
<span>SHALL</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHALL provide the ability to capture as part of the patient history the patient's relationships (e.g., genealogic, living situation, other).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.1.1#08</span>
</td>
<td style="padding-left: 4px;">
<span>SHALL</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHALL provide the ability to capture structured data in the patient history (e.g., administrative, social, mental health, geographic location, and/or financial statuses, poverty, orphan, disability, incarceration, incompetence, or remote geographic location).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.1.1#09</span>
</td>
<td style="padding-left: 4px;">
<span>SHALL</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHALL maintain and render documentation made in a non-linear as well as linear temporal and non-temporal sequence.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.1.1#10</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 present multiple levels of data (log view versus readable view) versus not display at all.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.1.1#11</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 to capture patient history adhering to a standards-based form or template according to scope of practice, organizational policy, and/or jurisdictional law.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.1.1#12</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 an indication of the patient's receipt of social subsidies.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.1.1#13</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 Investigational Product (e.g., medication, device, immunization) exposure information including Start Date/time, End Date/Time, Dose Amount, Dose Unit, Study Treatment Name, Route, Formulation as discrete elements.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.1.1#14</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 to manage information regarding past or present living situations or environmental factors related to the patient (e.g., war, famine, poverty, political situation, or proximity to dangerous chemicals) according to scope of practice, organizational policy, and/or jurisdictional law.</p>
</div></span>
</td>
</tr>
</table>
</div>
</text>
<url value="http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CP.1.1"/>
<version value="0.16.0"/>
<name value="CP_1_1_Manage_Patient_History"/>
<title value="CP.1.1 Manage Patient History (Function)"/>
<status value="active"/>
<date value="2024-08-12T10:56:01+00:00"/>
<publisher value="EHR WG"/>
<contact>
<telecom>
<system value="url"/>
<value value="http://www.hl7.org/Special/committees/ehr"/>
</telecom>
</contact>
<description
value="Manage medical, procedural/surgical, mental health, substance use, social and family history. This includes pertinent positive and negative histories, patient-reported or externally available patient clinical history."/>
<purpose
value="The history of the current illness and patient historical data related to previous medical diagnoses, surgeries and other procedures performed on the patient, clinicians involved in procedures or in past consultations, and relevant health conditions of family members is captured through such methods as patient reporting (e.g., interview, medical alert band) or electronic or non-electronic historical data. This data may take the form of a pertinent positive such as "The patient/family member has had..." or a pertinent negative such as "The patient/family member has not had...". When first seen by a health care provider, patients typically bring with them clinical information from past encounters. This and similar information may supplement locally captured documentation and notes wherever appropriate. Information regarding the patient's living situations may be an important means for a provider to uniquely identify a patient or to identify illnesses that may occur within a given proximity. Information regarding past or present living situations or environmental factors related to the patient or the fetal death may include a description of the father's type of occupation and occupational demographic information (such as the name and location of the employment). For example, it may be important for the clinician to know that the patient works in an occupation where lead exposure is common. It may also be important for the clinician to know that the patient lives in a household where asbestos routinely appears on clothing."/>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.1.1-01"/>
<label value="CP.1.1#01"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to manage current patient history including pertinent positive and negative elements (e.g., diagnosis or ruled out diagnosis), and information on clinicians involved."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.1.2#1"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="true"/>
</extension>
<key value="EHRSFMR2.1-CP.1.1-02"/>
<label value="CP.1.1#02"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to manage the identity of clinicians involved in patient history elements according to scope of practice, organizational policy, and/or jurisdictional law."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.1.2#1"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.1.1-03"/>
<label value="CP.1.1#03"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD conform to function [[CPS.2.1]] (Support externally-sourced Clinical Documents) to capture, store and render previous external patient histories."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.1.2#2"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.1.1-04"/>
<label value="CP.1.1#04"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD conform to function [[CPS.2.2]] (Support externally-sourced Clinical Data) to capture, store and render previous external patient histories."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.1.1-05"/>
<label value="CP.1.1#05"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to capture family history."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.1.1-06"/>
<label value="CP.1.1#06"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to capture social history."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.1.1-07"/>
<label value="CP.1.1#07"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to capture as part of the patient history the patient's relationships (e.g., genealogic, living situation, other)."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.1.2#3"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.1.1-08"/>
<label value="CP.1.1#08"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to capture structured data in the patient history (e.g., administrative, social, mental health, geographic location, and/or financial statuses, poverty, orphan, disability, incarceration, incompetence, or remote geographic location)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.1.1-09"/>
<label value="CP.1.1#09"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL maintain and render documentation made in a non-linear as well as linear temporal and non-temporal sequence."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.1.1-10"/>
<label value="CP.1.1#10"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to present multiple levels of data (log view versus readable view) versus not display at all."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="true"/>
</extension>
<key value="EHRSFMR2.1-CP.1.1-11"/>
<label value="CP.1.1#11"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to capture patient history adhering to a standards-based form or template according to scope of practice, organizational policy, and/or jurisdictional law."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.1.1-12"/>
<label value="CP.1.1#12"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to capture an indication of the patient's receipt of social subsidies."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.1.1-13"/>
<label value="CP.1.1#13"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to capture Investigational Product (e.g., medication, device, immunization) exposure information including Start Date/time, End Date/Time, Dose Amount, Dose Unit, Study Treatment Name, Route, Formulation as discrete elements."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="true"/>
</extension>
<key value="EHRSFMR2.1-CP.1.1-14"/>
<label value="CP.1.1#14"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to manage information regarding past or present living situations or environmental factors related to the patient (e.g., war, famine, poverty, political situation, or proximity to dangerous chemicals) according to scope of practice, organizational policy, and/or jurisdictional law."/>
</statement>
</Requirements>