Record of vaccine administration.

Data Element
Vaccination Administration Date
Description

The date the vaccination event occurred.
Submitted By: Nedra Garrett / Centers for Disease Control and Prevention
Data Element Information
Data Element Description The date the vaccination event occurred.
Use Case Description(s)
Use Case Description Date of vaccination is extremely important to various health care communities, especially to providers who routinely use this information to determine patient care. Providers use this information to determine if their patients were vaccinated according to schedule, if their patients need booster vaccinations, and when their patients will need to be vaccinated next. In turn, this provides patients information about their healthcare needs. 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 In addition to helping clinical care, date of vaccination administration helps inform decision making in public health. Date of vaccination is routinely used to determine if a vaccine preventable disease case was vaccinated properly. In fact, vaccination events missing date of administration may not be collected by providers, as providers are given guidance that only vaccinations with dates of administration are considered evidence of vaccination. Thus, some vaccinations may not be included in patient’s electronic medical records, and then sent to public health. Further, during analyses, public health practitioners often exclude vaccination administrations missing date information. By not including vaccination administrations missing date information, results from analyses could be inaccurate, depending on the number of administrations excluded. Inaccurate results could be harmful, as results help to inform communication, planning, and vaccine supply logistics.
Estimate the breadth of applicability of the use case(s) for this data element "There are mulitple stakeholders that would capture, access, use or exhange this data element or data class including:
• Electronic Health Records
• Immunization information systems and local and state departments of public health
• Vaccine Adverse Event Reporting System (VAERS)
• Providers
• Research and academic institutions, especially those running clinical trials "
Link to use case project page https://www.immregistries.org/ Immunization Action Coalition: https://www.immunize.org/
Use Case Description 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.
Healthcare Aims
  • Improving patient experience of care (quality and/or satisfaction)
  • Improving the health of populations
  • Reducing the cost of care
  • 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/

https://loinc.org/30952-6/
Additional Specifications "Yes, 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 This data element has been used at scale between multiple different production environments to support the majority of anticipated stakeholders
Supporting Artifacts "HL7 v2.5.1 Implementation Guide for Immunization Messaging
HL7 v2.8.2 Implementation Guide: Immunization Messaging
NNDSS MMGs for VPDs
Clinical Decision Support for Immunizations FHIR IG
AIRA Functional Standards Document
CDC Endorsed Data Elements "

"HL7 v2.5.1 and v2.8.2 IGs: https://www.cdc.gov/vaccines/programs/iis/technical-guidance/hl7.html
CDC NNDSS MMGs for VPDs: https://wwwn.cdc.gov/nndss/case-notification/message-mapping-guides.html
Clinical Decision Support of Immunizations FHIR IG: http://hl7.org/fhir/uv/immds/"


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) N/A
Restrictions on Use (e.g. licensing, user fees) None
Privacy and Security Concerns There are privacy concerns with the use and exchange of these data elements, mainly mother’s maiden name.
Estimate of Overall Burden There should be little burden to implement this data element, as all healthcare IT already stores and messages this information.
Other Implementation Challenges N/A
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 0 - Use cases apply to a limited number of care settings or specialties, or data element represents a specialization of other, more general data elements.
Evaluation Comment This data element represents a specific type of existing USCDI data element Performance Time in the Procedures data class.

Comment

Submitted by nedragarrett_CDC on

CDC's comment for proposed inclusion in USCDI v7

We propose the inclusion of the "Vaccination Administration Date" in USCDI v7 due to its critical role in enhancing healthcare data management and interoperability. This data element serves as a unique temporal identifier that, when combined with demographic information, aids in accurately matching and deduplicating patient records. This is particularly vital in cases where common names or birthdates may lead to record confusion.
The "Vaccination Administration Date" is essential for the effective coordination of immunization efforts, ensuring that individuals receive their vaccinations on schedule. It is routinely captured in electronic health record (EHR) systems, making it a key component for maintaining accurate immunization records.
Standardizing the "Vaccination Administration Date" with a consistent format (e.g., YYYY-MM-DD) will significantly enhance interoperability across various healthcare systems. This standardization will facilitate reliable health information exchanges among healthcare providers, public health organizations, educational institutions, and employers, particularly in sectors where health status is critical.
Moreover, this data element is pivotal for public health initiatives, supporting preventive care management and epidemic response. It is crucial for accurate public health surveillance and reporting, which are essential for compliance with international travel regulations, school admissions, and workforce readiness in healthcare settings. Its relevance spans all age groups, from pediatrics to geriatrics, highlighting its universal application throughout the continuum of care.
Incorporating the "Vaccination Administration Date" into USCDI v7 will not only promote interoperability but also enhance population health outcomes by enabling timely and coordinated vaccination strategies. Additionally, it supports health equity by identifying disparities in vaccination rates, facilitates integration with Health Information Exchanges, and enhances clinical decision support systems.
Furthermore, standardized vaccination data is essential for research and public health studies, aligns with national health initiatives, and bolsters emergency preparedness efforts. It also empowers patients by providing them with access to their vaccination history, encouraging active participation in their healthcare.
We strongly advocate for its inclusion and recommend the development of comprehensive conformance and implementation guidelines to ensure consistent capture and exchange of this vital data element across healthcare platforms.

Submitted by nedragarrett_CDC on

CDC's Comment for draft USCDI v6

The inclusion of the "Vaccination Administration Date" in USCDI v6 is strongly advocated, as it serves as a critical component for effective healthcare data management, particularly in matching and deduplication processes. This date acts as a unique temporal identifier that, when paired with demographic information, aids in distinguishing individuals who may share similar identifiers. The importance of this element is highlighted in the American Immunization Registry Association (AIRA)'s Modeling of Immunization Registry Operations Workgroup (MIROW) document titled "Consolidating Demographic Records and Vaccination Event Records." The need for specificity becomes especially apparent when common names or birthdates could lead to record discrepancies.

The Vaccination Administration Date is essential for coordinating immunization efforts effectively, ensuring that individuals receive their vaccines at the appropriate times. It is routinely documented across various Electronic Health Record (EHR) systems and plays a vital role in maintaining accurate immunization records.

By standardizing this data element and implementing a consistent date format (e.g., YYYY-MM-DD), interoperability can be significantly enhanced. Such standardization will enable more reliable health information exchanges among diverse entities, including healthcare providers, public health organizations, educational institutions, and employers where health status is critical.

Moreover, the "Vaccination Administration Date" is integral to public health initiatives ranging from preventive care management to epidemic response. It supports accurate public health surveillance and reporting—key components for compliance with international travel regulations, school admissions processes, and workforce readiness within healthcare settings. Its significance spans all age demographics—from pediatrics to geriatrics—highlighting its universal applicability throughout the continuum of care.

Incorporating this data element into USCDI v6 would not only foster interoperability but also substantially improve population health outcomes by enabling timely and coordinated vaccination strategies. Urgent consideration for its inclusion is recommended along with the development of comprehensive conformance and implementation guidelines to ensure consistent capture and exchange of this crucial data element across healthcare platform

Submitted by nedragarrett_CDC on

Vaccination Administration Date

The inclusion of the "Vaccination Administration Date" in the USCDI v6 is paramount, as it serves as an indispensable tool for matching and deduplication processes within healthcare data management. The vaccination administration date serves as a distinct temporal identifier, which, when combined with other demographic details, helps differentiate individuals with similar identifiers. This significance is emphasized in the American Immunization Registry Association (AIRA)'s Modeling of Immunization Registry Operations Workgroup (MIROW) document titled "Consolidating Demographic Records and Vaccination Event Records". Specificity is particularly important when common names or birthdates lead to potential record confusion. Vaccination Administration Date underpins the effective coordination of immunization efforts, ensuring that individuals receive vaccines at the appropriate times. The vaccination administration date is a key identifier routinely recorded in numerous EHR systems and is essential for maintaining accurate immunization records.

By standardizing this data element and adopting a consistent date format (e.g., YYYY-MM-DD), we can achieve greater interoperability. Such standardization will facilitate more reliable exchanges of health information across various entities, including healthcare providers, public health organizations, educational institutions, and employers in sectors where health status is crucial.

The "Vaccination Administration Date" plays a pivotal role in public health initiatives, from managing preventive care to responding to epidemics. It supports precise public health surveillance and reporting, which are vital for international travel compliance, school admissions procedures, and workforce readiness in healthcare environments. Its relevance spans all age groups—from pediatrics to geriatrics—underscoring its universal application throughout the continuum of care.

Incorporating this data element into USCDI v6 would not only promote interoperability but also significantly enhance population health outcomes by facilitating timely and well-coordinated vaccination strategies. CDC strongly support its inclusion and urge the development of comprehensive conformance and implementation guidelines that ensure this critical data element's consistent capture and exchange across healthcare platforms.

Submitted by BLampkins_CSTE on

CSTE Comment - v6

CSTE supports inclusion of this data element in USCDI V6. Please see previously submitted CSTE comments for additional recommendations.

Submitted by Riki Merrick on

APHL supports inclusion of this data element

APHL supports inclusion of this discrete data element until the design of USCDI accomodates a mechanism for each use case to define further constraints around generic data elements, as otherwise the clinical context and signifcance of when to collect this element cannot be sufficently described.
In FHIR the immunization resource is it's own resource, separate from medication administration, so should be kept separate here, too; in the base the respective element is immunization.occurence, which is 1..1 (i.e. required!!) - it has a choice of date/time or text to accomodate less precise dating, so it is already also required in US Core because of that (see 13.134.1.1 under "Each Immunization Must Have" item #4 = https://hl7.org/fhir/us/core/StructureDefinition-us-core-immunization.html#mandatory-and-must-support-data-elements)
As per CDC comment on USCDIV5 draft content: "Vaccination Administration Date" is crucial for effective immunization management across healthcare settings. It facilitates accurate tracking of vaccination schedules, aligning with established terminology and date formats to enhance interoperability and streamline processes. Its broad relevance in public health reporting, international travel, and healthcare employment underscores the necessity for its inclusion, with strong advocacy for conformance and implementation guides to ensure consistent and accurate utilization across systems.
It is unjustified to have this element in level 0, as it meets all level 2 requirements:
Represented by a terminology standard or SDO-balloted technical specification or implementation guide = in V2 = and the CDC Implementation guide called out in https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-D/part-170/subpart-B/section-170.205#p-170.205(e)(4)) , in CDA = , in FHIR = 
Data element is captured, stored, or accessed in multiple production EHRs or other HIT modules from more than one developer. (immunization reporting has been in certification requirements since MU 1 and many immunization reports are being exchanged nation wide)
Data element is electronically exchanged between more than two production EHRs or other HIT modules of different developers using available interoperability standards.(immunization reporting has been in certification requirements since MU 1 and many immunization reports are being exchanged nation wide)
Use cases apply to most care settings or specialties. It applies to ALL patients at some point or another (unless they refuse all vaccines)

USCoreMustSupportElements.pdf

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 nedragarrett_CDC on

CDC's comment for USCDI Draft v5

CDC would like to reemphasize "Vaccination Administration Date" for inclusion in USCDI v5. "Vaccination Administration Date" is crucial for effective immunization management across healthcare settings. It facilitates accurate tracking of vaccination schedules, aligning with established terminology and date formats to enhance interoperability and streamline processes. Its broad relevance in public health reporting, international travel, and healthcare employment underscores the necessity for its inclusion, with strong advocacy for conformance and implementation guides to ensure consistent and accurate utilization across systems.

Submitted by nedragarrett_CDC 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 nedragarrett_CDC 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 nedragarrett_CDC on

CDC's Consolidated Comment for USCDI v5

  • The "Vaccination Administration Date" is a critical data element proposed for inclusion in the USCDI v5, serving as a cornerstone for effective immunization management across various healthcare settings. This data point is integral to facilitating accurate tracking and coordination of vaccination schedules, thereby playing a vital role in ensuring timely and appropriate vaccine administration. This data element is widely captured within numerous EHR systems, making it a key component of patient care and central to immunization registry reporting. Standardizing the "Vaccination Administration Date," potentially aligned with established terminology such as HL7 or CVX codes, and specifying the date format (e.g., YYYY-MM-DD) will enhance semantic interoperability and consistency across systems. Its inclusion in USCDI v5 is poised to significantly streamline healthcare processes, supporting unified, secure, and reliable information exchange among healthcare stakeholders, including providers, public health agencies, and schools. As vaccines are pivotal in preventive health and public health responses, including epidemic control, a standardized "Vaccination Administration Date" is essential for accurate public health reporting, international travel, school enrollment, and employment in health-sensitive areas. Its broad applicability is evident as it is relevant in pediatric, adult, and geriatric care, reflecting its universality across the healthcare continuum. The inclusion of this data element in the USCDI v5 would not only ensure interoperability but also contribute to improving population health outcomes by aiding in the delivery of timely and coordinated care. We strongly advocate for its inclusion and recommend developing conformance and implementation guides that address the consistent and accurate capture and sharing of this pivotal data element across healthcare systems.


 

  • ** 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.

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