HL7 Electronic Health Record System Functional Model, Release 2.1.1
2.1.1 - International flag

HL7 Electronic Health Record System Functional Model, Release 2.1.1, published by HL7 International / Electronic Health Records. This guide is not an authorized publication; it is the continuous build for version 2.1.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/mvdzel/ehrsfm-fhir-r5/ and changes regularly. See the Directory of published versions

Requirements: CP.1.6 Manage Immunization List (Function)

Official URL: http://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-CP.1.6 Version: 2.1.1
Standards status: Normative Active as of 2025-10-31 Computable Name: CP_1_6_Manage_Immunization_List

Create and maintain patient-specific immunization lists.

Statement N:

Create and maintain patient-specific immunization lists.

Description I:

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.

Criteria N:
CP.1.6#01
SHOULD

The system SHOULD provide the ability to manage all immunizations associated with a patient.

Satisfied by:
  1. https://hl7.org/fhir/immunization.html
CP.1.6#02
 dependent
SHOULD

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.
CP.1.6#03
SHALL

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.
CP.1.6#04
 dependent
SHALL

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.
CP.1.6#05
SHALL

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).
CP.1.6#06
SHALL

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).