Official Website of the Office of the National Coordinator for Health Information Technology
Pharmacologic agents used in the diagnosis, cure, mitigation, treatment, or prevention of disease.
Data Element |
|---|
|
Medication Administration
|
Submitted by CDC_DSMH_WG on
CDC-CMS Joint Priority Data Element.
See letter here (submitted on 1/29/2024): https://www.healthit.gov/isa/sites/isa/files/2024-02/FINAL_CDC%20and%20CMS-CCSQ%20Joint%20USCDI%20v5%20submission%20letter_012924.pdf
Submitted by erjones on
Vizient recommends adding the Medication Administration data element to USCDI v5 as this element allows for further insight and analyses of which medications were administered within visits.
Submitted by gsgordon on
Posting as a member of the FDA USCDI Working Group: we are re-iterating the multiple requests to add support for distinction of medical records of the Administration of Medications to patients. US Core, as an approximate representation of USCDI in HL7 FHIR, currently has made "must support" requirements for use of MedicationRequest (for records of requests/prescriptions of medications) and MedicationDispense (for pharmacy dispensing of a medication). It is still surprising that USCDI continually omits the final ubiquitous type of record for patient medications, one which when it exists is the most definitive proof that a person has a medication in their body.
Please refer to my previous comment in strong support with a range of justifications of this in 2022: https://www.healthit.gov/isa/comment/11701 .
Further, over the past four years in addition to FDA, repeated support for inclusion of this in USCDI has come in comments to this request from multiple agencies (CDC, CMS) and public health organizations (CSTE, NACCHO), and FHIR developers. (see multiple comments here: https://www.healthit.gov/isa/uscdi-data/medication-administration )
As part of the Vulcan FHIR Accelerator work on real world data (RWD) use in clinical research, it was found that the requirement of consistent standardized use of FHIR for Medication Requests, Dispensation, Administration, and Statements was critical to assess how clearly one can determine the medication status of a patient (currently using, periodic use, previously used, etc). The Vulcan RWD FHIR Implementation Guide for this work ( https://build.fhir.org/ig/HL7/vulcan-rwd/index.html ) was published in May 2023. During IG testing at FHIR connectathons a participant data providers even found the transformation of Medication Administration Records from legacy or proprietary standards to be relatively non-burdensome, demonstrating the feasibility of this inclusion in USCDI for EHRs.
Cerner also appears to be supporting this in their implementations: https://fhir.cerner.com/millennium/r4/clinical/medications/medication-administration/ suggesting this will be a low level of effort for adoption.
Please consider this inclusion in support of healthcare and public health with downstream benefits for clinical research and pharmaceutical development
Submitted by yale-coredQMRoadmap on
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. As an integral aspect of patient safety, medication management is critical to patient care and coordination between providers, and related quality and public health enterprises. Medication administration, specifically, is a critical concept for CMS and CDC programs that support quality improvement and public health surveillance. We continue to emphasize the need for greater specificity in the USCDI Medications data class. The medications data class in USCDI is currently inadequate to support patient safety, quality improvement, or public health. The medication data elements do not differentiate among medications that are active, ordered, and administered/prescribed to the patient. Given these complexities, more clarity and structure are necessary in this data class to accurately evaluate and provide clinical care and promote patient safety. CMS and CDC strongly recommend the Medication Administration (Level 2)/Medication Administered Code (Level 0) in the Medications data class be added to USCDI.
Submitted by Lantana_Consul… on
Lantana Consulting Group supports the CDC/CMS-CCSQ recommendation and emphasizes the important role these data elements play in supporting patient safety.
Submitted by CDC_DSMH_WG on
Submitted by erjones on
Vizient recommends adding the Medication Administration data element to USCDI v4 as this element allows for further insight and analyses of which medications were administered within visits.
Submitted by yale-coredQMRoadmap on
We continue to urge adding more specificity to the USCDI Medications Data Class. These medication data elements are necessary for understanding adverse drug events, opioid use and misuse, and medication access. Medication administration, along with medications prescribed, discharge medications, medication administration route, medication administration dose, and medication administration date and time serve the ONC USCDI v4 stated priorities related to mitigating health inequities and disparities, addressing needs of underserved populations, and addressing public health reporting needs.
Submitted by yale-coredQMRoadmap on
We continue to urge adding more specificity to the USCDI Medications Data Class. These medication data elements are necessary for understanding adverse drug events, opioid use and misuse, and medication access. serve the ONC USCDI v4 stated priorities related to mitigating health inequities and disparities, addressing needs of underserved populations, and addressing public health reporting needs.
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.
To specify which data class your comment addresses:
To specify which data element your comment addresses:
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.
Fig 1 The "Data Class" and "Data Element" dropdown menus allow users to specify the exact content they wish to comment on.
If you cannot find the appropriate data class or element for your comment:
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.
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.
If you need to comment on multiple data classes or elements:
Fig 3 The "Comment on another data element" link enables users to create multiple comments addressing different elements within a single submission.
The platform allows you to upload supporting documentation to enhance 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.
Fig 4 The "File Upload" section permits users to attach supporting documentation that supplements their written comments.
If you need to pause your work and return to complete your comment later:
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.
Once you have completed your comment:
Fig 6 The review screen allows users to verify comment content and make any necessary modifications before final submission.
Submitted by BLampkins_CSTE on
CSTE Comment - v5
Medication data is critical for exchange with public health and is included in eCR standards. It is especially important for STI programs, HIV and TB surveillance as well as for public health response and surveillance for antimicrobial resistant pathogen infections. CSTE also strongly agrees that the ability to exchange data on prescribing of opioid medications in particular is of great importance to public health programs which aim to reduce opioid overdoses and deaths.