Record of vaccine administration.

Data Element
Vaccination Event Record Type
Description

Indicates whether the vaccination event is based on a historical record (e.g., second hand knowledge of the vaccination event) or was administered at the facility submitting the data.
Submitted By: Nedra Garrett / Centers for Disease Control and Prevention
Data Element Information
Data Element Description Indicates whether the vaccination event is based on a historical record (e.g., second hand knowledge of the vaccination event) or was administered at the facility submitting the data.
Use Case Description(s)
Use Case Description Knowing whether a vaccination was administered or was a historical record is helpful when providers are evaluating a patient’s immunization status to determine when the next vaccination in a series should be given. This information helps the IIS and other health IT systems identify, prevent, and resolve duplicate vaccination events using an automated process, thus ensuring that a patient is vaccinated according to the ACIP schedule. Additionally, this information could increase vaccination rates, a Healthy People 2030 goal, by ensuring patients are vaccinated on time.
Estimate the breadth of applicability of the use case(s) for this data element "There are multiple stakeholders that would capture, access, use or exchange this data element or data class including: • Electronic Health Records
• Immunization information systems and local and state departments of public health
• Providers
• Research and academic institutions, especially those running clinical trials "
Link to use case project page https://www.cdc.gov/vaccines/programs/iis/index.html
Use Case Description Additionally, determining whether a vaccination was administered or was a historical record is helpful when performing public health analyses. Vaccine efficacy analyses use this information to determine immunization population coverage. Statistical analyses help to identify underserved populations so that resources redirected appropriately and used efficiently.
Estimate the breadth of applicability of the use case(s) for this data element "There are multiple stakeholders that would capture, access, use or exchange this data element or data class including:
• Electronic Health Records
• Immunization information systems and local and state departments of public health
• Providers
• Research and academic institutions, especially those running clinical trials "

AIRA: https://www.immregistries.org/ Immunization Action Collition: https://www.immunize.org/
Link to use case project page https://www.immunize.org/
Healthcare Aims
  • Improving the health of populations
  • Improving provider experience of care
Maturity of Use and Technical Specifications for Data Element
Applicable Standard(s) LOINC:30952-6- Date and time of vaccination: https://loinc.org/30952-6/

PHINVAD Immunization Information Source
https://phinvads.cdc.gov/vads/ViewCodeSystem.action?id=2.16.840.1.114222.4.5.293
Additional Specifications This information is in various technical specifications including:
• The HL7 2.5.1 Implementation Guide for Immunization Messaging and the HL7 2.8.2 Implementation Guide: Immunization Messaging (see RXA-3)
• FHIR r4 (see immunization.occurrence)
• Clinical Decision Support for Immunizations FHIR IG
• CDC Nationally Notifiable Disease Surveillance System (NNDSS) Message Mapping Guides (MMGs) for Vaccine Preventable Diseases (VPDs)
Current Use In limited use in production environments
Supporting Artifacts Similar information has been collected in various artifacts including the HL7 v2.5.1 Implmentation Guide for Immunization Messaging, the HL7 2.8.2 Implementation Guide: Immunization Messaging, and various public heatlh reporting forms.

https://www.cdc.gov/vaccines/programs/iis/technical-guidance/hl7.html
Extent of exchange N/A
Potential Challenges
Restrictions on Standardization (e.g. proprietary code) None
Restrictions on Use (e.g. licensing, user fees) None
Privacy and Security Concerns None
Estimate of Overall Burden The overall burden to implement this data element is low, as most healthcare IT information systems most likely have this data element stored and messaged in their system already.
Other Implementation Challenges One possible challenge for implementation is ensuring that the correct information is captured, as depending on the timing of the administration, there could be confusion about whether the vaccination was administered or reported. For example, some EHRs would consider a vaccination event given on the same day by a provider outside of their EHR system a historical record, even though they were given on the same day, even within a matter of a few hours.
ASTP Evaluation Details
Each submitted Data Element has been evaluated based on the following criteria. The overall Level classification is a composite of the maturity based on these individual criteria. This information can be used to identify areas that require additional work to raise the overall classification level and consideration for inclusion in future versions of USCDI
Criterion #1
Maturity - Current Standards		 Level 2 - Data element is represented by a terminology standard or SDO-balloted technical specification or implementation guide.
Criterion #2
Maturity - Current Use 		Level 2 - Data element is captured, stored, or accessed in multiple production EHRs or other HIT modules from more than one developer.
Criterion #3
Maturity - Current Exchange		 Level 2 - Data element is electronically exchanged between more than two production EHRs or other HIT modules of different developers using available interoperability standards.
Criterion #4
Use Case(s) - Breadth of Applicability		 Level 2 - Use cases apply to most care settings or specialties.

Comment

Submitted by rdillaire on

CMS-CCSQ Support Vaccination Event Record Type for USCDI v6

Data Element: Vaccination Event Record Type (Level 2)

  1. Recommendation: Add the Vaccination Event Record Type data element to Final USCDI v6.
  2. Rationale: The Vaccination Event Record Type data element provides critical information about whether a vaccination has ever been administered, planned, or reported. The current Immunizations data element is insufficient to identify whether the vaccination is based on the historical record or was administered at the facility submitting the vaccination record. By adding Vaccination Event Record Type for immunizations, ASTP/ONC can also ensure data elements necessary to determine whether vaccinations are current, and whether any vaccinations need to be administered. Since this information helps improve accuracy of vaccine reporting, it can benefit many existing CMS vaccination quality measures. It can already be exchanged via HL7 v2.5.1 and 2.8.2 IGs.

Submitted by BLampkins_CSTE on

CSTE Comment - v5

CSTE agrees with CDC and continues to strongly recommends that Vaccine Administration Date and Vaccination Event Record Type be included in USCDI v5. Both elements are required for immunization exchange and always have been. Each year, IIS respond to CDC’s annual report (IISAR). At the end of calendar year 2019, IIS records contained vaccine administration date 99.9% of the time with only 1 IIS reporting less than 100%. With these lacking from USCDI v5 draft, it would be possible to list only the immunization code a patient received, but not the date the patient received the dose or if the vaccination event originated in the source system. Vaccine Administration Date enables accurate record evaluation (e.g., were doses given at the proper age and at a proper interval) while Vaccination Event Record Type enable accurate inventory decrementing by public health and aids in vaccine matching/deduplication.

Submitted by yale-coredQMRoadmap on

CDC and CMS-CCSQ Joint Support for Vaccination Event Record Type

Thank you for opportunity to comment on this data element. The Centers for Medicare and Medicaid Services (CMS) and the Centers for Disease Control and Prevention (CDC) emphasize the importance of patient safety being reflected in the USCDI standards. Identification of whether vaccinations are current and whether any vaccinations need to be administered using the Vaccination Event Record Type and Immunization Status data elements are vital to patient safety outcomes. CMS and CDC strongly recommend the Vaccination Event Record Type (Level 2) data element in the Immunization data class be added to USCDI. This addition would promote patient safety.

Submitted by CDC_DSMH_WG on

CDC's comment for USCDI Draft v5

CDC would like to underscore the importance of the "Vaccination Event Record Type" as a data element for v5 of USCDI, aiming to standardize vaccine event categorization across healthcare systems. This element facilitates accurate scheduling of subsequent vaccinations, addresses duplicate record issues, and supports real-time monitoring of vaccination trends, particularly beneficial during mass vaccination campaigns like those for influenza or COVID-19. Its inclusion is advocated for its potential to elevate care standards, improve data accuracy, and empower effective public health surveillance and response.

Submitted by CDC_DSMH_WG on

CDC's comment on behalf of NACCHO for USCDI v5

Support - The standardization of this data element will enhance LHDs ability to use and analyze this data. It will reduce the data preparation burden and thus enable more LHDs to use this type of data to inform decision-making.

Submitted by CDC_DSMH_WG on

CDC's comment on behalf of CSTE for USCDI v5

CSTE agrees with CDC and continues to strongly recommends that Vaccine Administration Date and Vaccination Event Record Type be included in USCDI v5. Both elements are required for immunization exchange and always have been. Each year, IIS respond to CDC’s annual report (IISAR). At the end of calendar year 2019, IIS records contained vaccine administration date 99.9% of the time with only 1 IIS reporting less than 100%. With these lacking from USCDI v4 it would be possible to list only the immunization code a patient received, but not the date the patient received the dose or if the vaccination event originated in the source system. Vaccine Administration Date enables accurate record evaluation (e.g., were doses given at the proper age and at a proper interval) while Vaccination Event Record Type enable accurate inventory decrementing by public health and aids in vaccine matching/deduplication.

Submitted by CDC_DSMH_WG on

CDC's Consolidated Comment for USCDI v5

  • The "Vaccination Event Record Type" is a proposed essential data element for inclusion in the v5 USCDI, designed to enhance the quality and consistency of immunization data management across healthcare systems. This data element allows for the standardized categorization of vaccine events, significantly contributing to data interoperability across disparate health information systems. DefiningDefining a consistent framework for categorizing vaccination events enables healthcare professionals to accurately determine when subsequent vaccinations should be administered, thereby promoting adherence to recommended vaccination schedules and improving patient care. This element is critical for resolving duplicate vaccination records, a common issue that can lead to patient safety concerns and administrative burdens. The "Vaccination Event Record Type" is also pivotal for public health management, enabling efficient, real-time tracking and monitoring of vaccination trends at a population level. This facilitates timely and informed responses to emerging vaccination patterns, vaccine uptake rates, and potential adverse events following immunization. For instance, in mass vaccination campaigns, such as those for influenza or COVID-19, having a standardized record type can streamline reporting, minimize errors, and ensure that vaccines are effectively distributed and administered based on actual need. Moreover, this data element can play a crucial role in research, supporting robust and high-quality data sets for vaccine effectiveness and safety analysis. Therefore, we strongly advocate for including the "Vaccination Event Record Type" in the USCDI v5 due to its potential to significantly elevate the standard of care, improve data accuracy and reliability, and empower robust public health surveillance and response mechanisms.

 

  • ** ADD THIS USE CASE TO SUBMISSION **
  1. "Immunizations HPV": HPV is estimated to cause 70% of oropharyngeal cancers in the United States, although it is unclear if having HPV alone is enough to cause oropharyngeal cancers, or if other factors interact with HPV to cause these cancers. Because the HPV vaccine protects against the types of HPV that can cause oropharyngeal cancers, it may also prevent oropharyngeal cancers. The United States is struggling to achieve HPV vaccination goals because HPV vaccination policies vary greatly nationwide, making it hard to implement sustainable programs. Surveillance of HPV vaccination and risk factors can help to establish associations, identify at-risk populations, and better inform clinical decision-making guidelines and interventions. These activities can increase vaccination acceptance rates and may lower HPV-associated oropharyngeal cancer prevalence and incidence.

Submitted by yale-coredQMRoadmap on

CMS-CCSQ/CDC Joint USCDIv4 Priority Vacc. Event Record Type

The immunization data element provides critical information about whether a vaccination has ever been administered, planned or reported. The current immunization data element is insufficient to identify whether the vaccination is based on the historical record or was administered at the facility submitting the vaccine. By adding vaccine event record type for immunizations, ONC can also ensure data elements necessary to determine whether vaccinations are current, and whether any vaccinations need to be administered.

Submitted by Svellanky on

CMS-CCSQ Support for Vaccination Event Record Type: USCDI v4

The immunization data element provides critical information about whether a vaccination has ever been administered, planned or reported. The current immunization data element is insufficient to identify whether the vaccination is based on the historical record or was administered at the facility submitting the vaccine. By adding vaccine event record type for immunizations, ONC can also ensure data elements necessary to determine whether vaccinations are current, and whether any vaccinations need to be administered. Vaccine efficacy analyses use this information to determine immunization population coverage. Statistical analyses help to identify underserved populations so that resources are redirected appropriately and used efficiently. This should not add any substantial burden on vendors or implementers, as this metadata should already be routinely captured. As this information helps improve accuracy of vaccine reporting, it can benefit many existing CMS vaccination quality measures.

Maturity: This data element is classified as Level 2 by ONC and continues to have strong standardization and be in wide use.

Current uses, exchange, and use cases: The vaccination event record type data element provides information that is currently lacking in the USCDI on timing of the immunizations that can improve accuracy of measurement. Immunization information may not directly provide disparity information, but it is needed together with other disparity-related data (e.g., race, ethnicity, location) to identify vaccine breakthroughs or problems with vaccination access/coverage which may also speak to broader health disparities related to general access to medical care and services. This data is particularly important for COVID-19 reporting. This data element also allows CDC to see where immunizations may be lacking and can support future CMS quality measure reporting.

Submitted by CDC_DSMH_WG on

CDC's Consolidated Comment for USCDI v4

CDC continues to recommend inclusion of this high priority data element in USCDI v4

CSTE Comment:

  • CSTE agrees with CDC and continues to strongly recommends that Vaccine Administration Date and Vaccination Event Record Type be included in USCDI v4. Both elements are required for immunization exchange and always have been. Each year, IIS respond to CDC’s annual report (IISAR). At the end of calendar year 2019, IIS records contained vaccine administration date 99.9% of the time with only 1 IIS reporting less than 100%. With these lacking from USCDI v4 it would be possible to list only the immunization code a patient received, but not the date the patient received the dose or if the vaccination event originated in the source system. Vaccine Administration Date enables accurate record evaluation (e.g., were doses given at the proper age and at a proper interval) while Vaccination Event Record Type enable accurate inventory decrementing by public health and aids in vaccine matching/deduplication.

Log in or register to post comments

FormGuide

Help

1. Optional: Background Text / Cover Letter

The "Optional Background Text / Cover Letter" field provides space for additional context or introductory information related to your comment.

If you wish to provide context, explanation, or an introduction to your comment, enter this information in the field labeled "Optional Background Text / Cover Letter." This is entirely optional and is most useful when submitting multiple related comments or when additional background would help reviewers understand your feedback.

If you are only commenting on a single data class or element, you may leave this field blank.

2. Select the Data Class

To specify which data class your comment addresses:

  1. In the "Data Class" drop-down menu, select the appropriate data class you want to comment on.
  2. If you are providing a general comment that is not specific to a data element, select "General" from the options. Comments with this designation will be displayed on the USCDI landing page.
  3. Note that the Data Class field will automatically populate based on your current location in the platform:
    1. If you are on a data class page, the field will be set to that specific data class
    2. If you are on a data element page, the corresponding data class will be pre-selected
       

3. Select the Data Element

To specify which data element your comment addresses:

  1. In the "Data Element" drop-down menu, select the specific data element you want to comment on.
  2. The drop-down menu will display only the elements available under the data class you selected in the previous step.
  3. You can use the search function within the drop-down to quickly locate a specific data element.
  4. If you are commenting on the data class itself rather than a specific element, you may leave this field blank.

Note: Comments on a specific data element will appear on the respective data element page, while comments on a data class (without a specific element selected) will appear on the landing page for that data class.
 

Data Class and Data Element

Fig 1 The "Data Class" and "Data Element" dropdown menus allow users to specify the exact content they wish to comment on.

4. Optional: Propose New Data Class or Element

If you cannot find the appropriate data class or element for your comment:

  1. Instead of clicking the "Comment On An Existing Data Class Or Element" button, click the adjacent button labeled "Propose a New Data Class or Data Element."
  2. This will redirect you to the ONDEC (ONC New Data Element and Class) Submission System.
  3. In the ONDEC system, follow the provided instructions to submit your proposal for a new data class or element.
  4. Once your proposal is submitted through ONDEC, it will be reviewed separately from the commenting process.
Propose New Data Class or Element

Fig 2 The "Propose a New Data Class or Data Element" button redirects users to the ONDEC Submission System for proposing new data elements not currently available in the system.

5. Complete the Comment Form

Fill out the required fields in the comment form:

Subject: Enter a brief, descriptive title that summarizes your comment. This helps reviewers quickly understand the nature of your feedback.

Comment: In this field, provide the full details of your comment or feedback. Be as clear and specific as possible about your suggestions, concerns, or observations. Include any relevant details that support your position.

6. Optional: Add Additional Comments

If you need to comment on multiple data classes or elements:

  1. After completing your first comment, click the link labeled "Comment on another data element" at the bottom of the form.
  2. A new comment section will appear, allowing you to enter details for your additional comment.
  3. For each additional comment, you must select the appropriate data class and data element from the drop-down menus.
  4. Complete the Subject and Comment fields for your additional comment.
  5. Repeat this process for each additional comment you wish to submit.

Fig 3 The "Comment on another data element" link enables users to create multiple comments addressing different elements within a single submission.

7. Optional: Upload Supporting Files

The platform allows you to upload supporting documentation to enhance your comment:

  • Locate the "File Upload" section at the bottom of the comment form.
  • Click to upload any files (such as PDFs or documents) that provide additional context, evidence, or clarification for your comment.

Important: If you have already entered your comments using the form fields, there is no need to upload duplicate content in PDF format. The file upload feature is intended for supplementary materials only. Please avoid uploading files that contain the same information already provided in your comment text.

Upload Supporting Files

Fig 4 The "File Upload" section permits users to attach supporting documentation that supplements their written comments.

8. Optional: Save and Exit

If you need to pause your work and return to complete your comment later:

  1. Click the "Save and Exit" button at the bottom of the form.
  2. Your comment will be saved as a draft that you can access and complete later.
  3. When you return to the platform, you will see a red triangle with an exclamation mark next to the “Return to saved Comment” button, indicating that you have saved comments in draft status.
  4. Click this button to continue working on your draft.
  5. You will be taken to a review page where you can:
    1. Select "Submit Comment" to officially submit your feedback.
    2. Click "Edit" to return to the comment form and make changes
    3. Select "Discard Draft" to delete the saved draft and start fresh

Fig 5 A red triangle with exclamation mark indicator appears next to the “Return to saved Comment” button when draft comments are saved in the system.

9. Review and Submit

Once you have completed your comment:

  1. Click the "Review and Submit" button at the bottom of the form.
  2. This will take you to a review screen displaying your comment(s) in full.
  3. Review all information for accuracy and completeness.
  4. On this review screen, you have three options: 
    1. Click "Submit Comment" to officially submit your feedback
    2. Click "Edit" to return to the comment form and make changes
    3. Click "Discard Draft" to delete the comment and start fresh
  5. The review screen also includes a "Print" button that allows you to create a printed copy of your comments for your records. 
  6. If you choose to submit, your comment will be recorded in the system and made available for review by the appropriate stakeholders.
Review and Submit

Fig 6 The review screen allows users to verify comment content and make any necessary modifications before final submission.

USCDI Comments

Close

Add a New Comment

Review comment and Submit

Edit
Comment #1
PDF, Doc, Docx
Max Size : 10 MB