ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1
2.1.0 - local
ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1
2.1.0 - local
Publish Box goes here
| Active as of 2024-11-26 |
<Requirements xmlns="http://hl7.org/fhir">
<id value="EHRSFMR2.1-CP.1.6"/>
<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>Create and maintain patient-specific immunization lists.</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>Immunization lists are managed over time, whether over the course of a visit or stay, or the lifetime of a patient. Details of immunizations administered are captured as discrete data elements including date, type, manufacturer and lot number. The entire immunization history is viewable.</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.6#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 manage all immunizations associated with a patient.</p>
</div></span>
Satisfied by:<ol>
<li><a href="https://hl7.org/fhir/immunization.html">https://hl7.org/fhir/immunization.html</a></li>
</ol>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.1.6#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 to maintain immunization details, as discrete data, including:</p>
<ul>
<li>the immunization name/type, seqeunce number in the series & series identifier, strength and dose;</li>
<li>the date and time of administration;</li>
<li>manufacturer, lot number, expiration date,</li>
<li>route and site of administration;</li>
<li>administering provider;</li>
<li>observations, reactions and complications;</li>
<li>reason immunization not given, and/or immunization related activity not performed;
according to scope of practice, organizational policy, and/or jurisdictional law.</li>
</ul>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.1.6#03</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, as discrete elements, data associated with an immunization that was not given to a patient (e.g., due to a contraindication or a patient's refusal). Data associated with an immunization that was not given to a patient includes date-and-time, immunization type, series, exception reason, and immunization-withholding provider.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.1.6#04</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 render (e.g., print or transmit) a report of a patient's immunization history (e.g., for appropriate authorities such as schools, day-care centers or public health immunization registries) 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.6#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 the currently recommended date for a companion immunization (e.g., a subsequent or booster dose) with each immunization (if such a companion immunization is needed).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.1.6#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, maintain and render population-based immunization schedules from relevant public health immunization authorities (e.g., CDC for US realm).</p>
</div></span>
</td>
</tr>
</table>
</div>
</text>
<url value="http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CP.1.6"/>
<version value="2.1.0"/>
<name value="CP_1_6_Manage_Immunization_List"/>
<title value="CP.1.6 Manage Immunization List (Function)"/>
<status value="active"/>
<date value="2024-11-26T16:30:50+00:00"/>
<publisher value="EHR WG"/>
<contact>
<telecom>
<system value="url"/>
<value value="http://www.hl7.org/Special/committees/ehr"/>
</telecom>
</contact>
<description
value="Create and maintain patient-specific immunization lists."/>
<jurisdiction>
<coding>
<system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
<code value="001"/>
<display value="World"/>
</coding>
</jurisdiction>
<purpose
value="Immunization lists are managed over time, whether over the course of a visit or stay, or the lifetime of a patient. Details of immunizations administered are captured as discrete data elements including date, type, manufacturer and lot number. The entire immunization history is viewable."/>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.1.6-01"/>
<label value="CP.1.6#01"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to manage all immunizations associated with a patient."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.1.4.4#1"/>
<satisfiedBy value="https://hl7.org/fhir/immunization.html"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="true"/>
</extension>
<key value="EHRSFMR2.1-CP.1.6-02"/>
<label value="CP.1.6#02"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to maintain immunization details, as discrete data, including:
- the immunization name/type, seqeunce number in the series & series identifier, strength and dose;
- the date and time of administration;
- manufacturer, lot number, expiration date,
- route and site of administration;
- administering provider;
- observations, reactions and complications;
- reason immunization not given, and/or immunization related activity not performed;
according to scope of practice, organizational policy, and/or jurisdictional law."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.1.4.4#2"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.1.6-03"/>
<label value="CP.1.6#03"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to manage, as discrete elements, data associated with an immunization that was not given to a patient (e.g., due to a contraindication or a patient's refusal). Data associated with an immunization that was not given to a patient includes date-and-time, immunization type, series, exception reason, and immunization-withholding provider."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="true"/>
</extension>
<key value="EHRSFMR2.1-CP.1.6-04"/>
<label value="CP.1.6#04"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to render (e.g., print or transmit) a report of a patient's immunization history (e.g., for appropriate authorities such as schools, day-care centers or public health immunization registries) according to scope of practice, organizational policy, and/or jurisdictional law."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.1.4.4#3"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.1.6-05"/>
<label value="CP.1.6#05"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to capture the currently recommended date for a companion immunization (e.g., a subsequent or booster dose) with each immunization (if such a companion immunization is needed)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.1.6-06"/>
<label value="CP.1.6#06"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to capture, maintain and render population-based immunization schedules from relevant public health immunization authorities (e.g., CDC for US realm)."/>
</statement>
</Requirements>