Data Element
Submitted By: Joel Andress / CMS
Data Element Information
Data Element Description Indicates how much medication should be used by the patient, and how the medication should enter the body (route)
Rationale for Separate Consideration These additional medication details are critical to put context around a medication. These details allow for patients and clinicians to understand how the medication should be taken, and are details used in quality measurement.
Use Case Description(s)
Use Case Description Medication information, including medications administered with administration details, ordered, dispensed, at discharge, and negation rationale for not using a medication are key data elements currently used in CMS eCQMs across hospital and clinician reporting programs. These data are necessary to confirm appropriate and high quality of care is received for patients across different populations. It is clinically relevant from a care perspective and a quality measurement perspective to distinguish information about medication orders, medications dispensed, medications administered, and medications at discharge.
Additionally, negation rationale, or the reason a medication was not ordered/administered is important to accurately reflect quality of care in measurement, and avoid penalizing providers/hospitals (by a lower measure score). This information is also important for interoperability to ensure relevant clinical information about not taking a medication is clear.
Estimate the breadth of applicability of the use case(s) for this data element More than 4,000 hospitals and 1 million providers are currently capturing, accessing and exchanging this encounter level information. This information is currently electronically exchanged/submitted by providers and hospitals to CMS for quality measurement purposes.eCQI resource center, includes measure specifications for CMS program eCQMs, many of which (i.e. CMS 506, CMS 108, CMS 128) use these medication details.
Link to use case project page https://ecqi.healthit.gov/ecqms
Use Case Description Data exchange of medication information is also critical for clinical care. Each step in the chain of events between a clinician’s request for a medication and the complete administration of that medication is critical for vigilance and surveillance of patient safety. Assessment, improvement and accountability around quality measurement is a consistent and critical focus of human and financial resources throughout the healthcare system. It is important to have the capacity to evaluate the clinician’s intent, the actual administration, and ongoing provision of medications across care settings and across time. Clinician’s need to exchange information about each aspect, medication orders, active medications, and medications administered to guide new treatment decisions and identify near harm and actual harm events. The metadata associated with medications (route, dose) are also critical to clinical care.
Negation rationale provides important clinical information related to deviation of care from guidelines or supported pathways. Because clinicians might be included to implement guideline driven care regardless of the setting, it is important for them to communicate negation rationale for decisions to deviate from guidelines at previous encounters. Additionally, negation rationale can provide information about patient preference that is important to travel with the patient across settings and time to optimize their experience of care.
Medication information including medications administered, discharge medications, medication orders, and medication instructions can be exchanged via C-CDA for patient care coordination.
Estimate the breadth of applicability of the use case(s) for this data element All healthcare providers using certified electronic health record technology (CEHRT) should be capturing, accessing, using and exchanging these medication data elements. The capture of medication route and dose should also be common in EHR systems.
Link to use case project page http://www.hl7.org/implement/standards/product_brief.cfm?product_id=492
Healthcare Aims
  • Improving patient experience of care (quality and/or satisfaction)
  • Improving the health of populations
  • Improving provider experience of care
Maturity of Use and Technical Specifications for Data Element
Applicable Standard(s) Medications (including medications with dose): RxNORM
Medication Route: SNOMED (i.e. OID: 2.16.840.1.113883.3.117.1.7.1.222)
Negation Rationale (reason codes): SNOMED (i.e. OID: 2.16.840.1.113883.3.117.1.7.1.93)
https://vsac.nlm.nih.gov/valueset/expansions?pr=ecqm
Negation Rationale: https://www.hl7.org/fhir/valueset-reason-medication-not-given-codes.html , http://hl7.org/fhir/us/qicore/ValueSet-qicore-negation-reason.html

https://vsac.nlm.nih.gov/valueset/expansions?pr=ecqm
Additional Specifications HL7 FHIR US Core Implementation Guide STU3 based on FHIR R4, MedicationRequest. (https://www.hl7.org/fhir/us/core/StructureDefinition-us-core-medicationrequest.html ) This profile supports specification of dose/route, intent (order, plan), status (active), status reason (for not done) and category (discharge)
HL7 FHIR QI Core Implementation Guide STU4 based on FHIR R4, specifies MedicationAdministration, MedicationDispense profiles (http://hl7.org/fhir/us/qicore/StructureDefinition-qicore-medicationdispense.html ; http://hl7.org/fhir/us/qicore/StructureDefinition-qicore-medicationadministration.html )
HL7 FHIR QI Core Implementation Guide STU4 based on FHIR R4, MedicationAdministration, MedicationDispense, MedicationRequest, NotDone profiles, for negation rationale: http://hl7.org/fhir/us/qicore/profiles.html
CMS Quality Data Model (QDM) version 5.5 Guidance (https://ecqi.healthit.gov/sites/default/files/QDM-v5.5-Guidance-Update-May-2020-508.pdf)
HL7 C-CDA Release 2.0 (http://www.hl7.org/implement/standards/product_brief.cfm?product_id=492)
ePrescribing NCPDP SCRIPT Standard Implementation Guide Version 2017071
Current Use Extensively used in production environments
Supporting Artifacts Medication data is routinely captured in EHR systems used by hospitals, providers, and other healthcare stakeholders including pharmacies. Medication data used in CMS program eCQMs across IQR, QPP, and Promoting Interoperability and therefore are widely stored in production environments.
Widely available in EHR systems. Medication orders and instructions are most commonly available in FHIR standards:
https://open.epic.com/Interface/FHIR
https://mydata.athenahealth.com/fhirapidoc
https://fhir.cerner.com/millennium/r4/medications/medication-request/
https://developer.allscripts.com/FHIR?PageTitle=Resources
https://www.cms.gov/Medicare/Quality-Initiatives-Patient-Assessment-Instruments/MMS/Quality-Programs
https://ecqi.healthit.gov/ecqms

https://www.cms.gov/Medicare/Quality-Initiatives-Patient-Assessment-Instruments/MMS/Quality-Programs
Extent of exchange 5 or more. This data element has been tested at scale between multiple different production environments to support the majority of anticipated stakeholders.
Supporting Artifacts Medication data for quality measurement is electronically exchanged from organization’s EHR systems to CMS for reporting and payment quality measurement programs, via QRDA files and other architectures. Negation rationale for medications is particularly relevant in quality measurement and has been used at scale in measurement. Ongoing testing for exchanging these data in FHIR standards via HL7 Connectathons.
Medication data is also routinely electronically exchanges with external organizations via C-CDA, as part of ONC’s CEHRT criteria, and a part of data exchange for electronic prescribing to support the continuum of care, particularly with prescribers, dispensers, intermediaries, and post-acute care settings.
https://ecqi.healthit.gov/qrda
http://www.hl7.org/implement/standards/product_brief.cfm?product_id=7
https://www.healthit.gov/isa/section/electronic-prescribing
https://confluence.hl7.org/display/FHIR/2020-09+Clinical+Reasoning

https://ecqi.healthit.gov/qrda
Potential Challenges
Restrictions on Standardization (e.g. proprietary code) No challenges anticipated. This data is available in standard terminology that can be publicly access via the VSAC and HL7.
Restrictions on Use (e.g. licensing, user fees) We are not aware of any restrictions.
Privacy and Security Concerns This data, like any patient data should be exchanged securely. Current processes exist, governed by CMS and ONC, to securely transfer this data.
Estimate of Overall Burden Medication data is regularly captured as part of EHR systems. Most hospitals, including critical access hospitals, and providers are already capturing and exchanging these medication data for quality measurement to CMS. Some additional efforts may be necessary to specify negation rationale, for those stakeholders not using for measurement, but the information is clinically relevant for a variety of use cases.
Many Medication FHIR profiles also required by the US Core Capability Statement and therefore will be stood up by those stakeholders complying with the ONC requirement for the Standardized API for patient and population services—some additional efforts to add in profiles to clarify medication administration and dispensing.
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 2 - Use cases apply to most care settings or specialties.

Comment

Submitted by nedragarrett_CDC on

CDC-CMS Joint Priority Data Element

Both CDC and CMS support this date element and details were included in the joint cover letter.

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