HL7 Electronic Health Record System Functional Model, Release 2.1.1
2.1.1-ballot - Normative Ballot

Publication Build: This will be filled in by the publication tooling

## Requirements: CP.6.2 Manage Immunization Administration (Function)

Page standards status: Informative

Statement N:

Capture and maintain discrete data concerning immunizations given to a patient including date administered, type, manufacturer, lot number, and any allergic or adverse reactions. Facilitate the interaction with an immunization registry to allow maintenance of a patient's immunization history.

Description I:

During an encounter, recommendations based on accepted immunization schedules are presented to the provider. Allergen and adverse reaction histories are checked prior to giving the immunization. If an immunization is administered, discrete data elements associated with the immunization including date, type, immunization expiration date, manufacturer and lot number are recorded. Any new adverse or allergic reactions are noted. If required, a report is made to the public health immunization registry or other organization (e.g., military unit commander, refugee program leadership). This function should include the ability to use GTIN barcode scanners to capture vaccine information (NDC, lot number, expiration date).

Actors:
ehr Criteria N:

CP.6.2#01 | dependent SHALL | The system SHALL provide the ability to capture immunization administration details as discrete data, including: the immunization name/type, series, strength and dose; 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.6.2#02 | dependent MAY | The system MAY auto-populate the immunization administration record as a by-product of verification of administering provider, patient, medication, dose, route and time according to scope of practice, organizational policy, and/or jurisdictional law.
CP.6.2#03 | SHALL | The system SHALL provide the ability to determine and render required immunizations, and when they are due, based on widely accepted immunization schedules, when rendering encounter information.
CP.6.2#04 | SHOULD | The system SHOULD provide the ability to capture, in a discrete field, an allergy/adverse reaction to a specific immunization.
CP.6.2#05 | SHALL | The system SHALL conform to function CP.3.2 (Manage Patient Clinical Measurements) to capture other clinical data pertinent to the immunization administration (e.g., vital signs).
CP.6.2#06 | SHOULD | The system SHOULD provide the ability to link standard codes (e.g., LOINC, SNOMED or other jurisdictionally-specific codes) with discrete data elements associated with an immunization.
CP.6.2#07 | SHALL | The system SHALL provide the ability to maintain a patient-specific immunization schedule.
CP.6.2#08 | SHALL | The system SHALL provide the ability to render a patient's immunization history upon request for appropriate authorities such as schools or day-care centers.
CP.6.2#09 | SHALL | The system SHALL conform to function CP.1.2 (Manage Allergy, Intolerance and Adverse Reaction List).
CP.6.2#10 | dependent SHOULD | The system SHOULD transmit required immunization administration information to a public health immunization registry according to scope of practice, organizational policy, and/or jurisdictional law.
CP.6.2#11 | dependent SHOULD | The system SHOULD exchange immunization histories with public health immunization registries or Immunization Information Systems according to scope of practice, organizational policy, and/or jurisdictional law.
CP.6.2#12 | dependent SHOULD | The system SHOULD harmonize Immunization histories with a public health immunization registry or Immunization information Systems according to scope of practice, organizational policy, and/or jurisdictional law.
CP.6.2#13 | SHOULD | The system SHOULD capture and render immunization histories from a public health immunization registry or Immunization Information Systems including immunization administration recommendations.
CP.6.2#14 | SHALL | The system SHALL conform to function CP.1.6 (Manage Immunization List).
CP.6.2#15 | SHOULD | The system SHOULD provide the ability to update immunization histories at the time of capturing an immunization administration.
CP.6.2#16 | SHALL | The system SHALL provide the ability to render an immunization order as written (e.g., exact clinician order language or as mandated - such as by a public health requirement), when rendering administration information.
CP.6.2#17 | dependent SHALL | The system SHALL provide the ability to determine due and overdue ordered immunizations including earliest through latest date ranges and render a notification according to organizational policy, and/or jurisdictional law.
CP.6.2#18 | SHALL | The system SHALL provide the ability to render a patient educational information regarding the administration (e.g., Vaccine Information Statement (VIS).
CP.6.2#19 | SHALL | The system SHALL provide the ability to capture that patient educational information (e.g., VIS) was provided at the time of immunization administration.
CP.6.2#20 | SHOULD | The system SHOULD provide the ability to capture that patient educational information (e.g., VIS) was provided at the time of the immunization including to whom the information was provided and the date/time that it was provided.
CP.6.2#21 | SHOULD | The system SHOULD provide the ability to capture and maintain immunization refusal reasons as discrete data.
CP.6.2#22 | SHOULD | The system SHOULD provide the ability to capture patient preferences regarding receipt of immunization (e.g., refusal of certain vaccines) at time of immunization administration.