Provider-authored request for the delivery of patient care services.

Usage notes: Orders convey a provider’s intent to have a service performed on or for a patient, or to give instructions on future care.

Data Element
Medication Order
Description (*Please confirm or update this field for the new USCDI version*)

Provider-authored request for the dispensing of a therapeutic agent.

Submitted By: Joel Andress / Centers for Medicare and Medicaid Services (CMS) Center for Clinical Standards and Quality (CCSQ)
Data Element Information
Data Element Description Order or a Service Request represents a request for a procedure, diagnostic service, intervention, laboratory test, follow-up care, or other planned service for a patient. This concept may be used to share relevant information required to support a referral or a transfer of care request from one practitioner or organization to another when a patient is required to be referred to another provider for a consultation /second opinion and/or for short term or longer-term management of one or more health issues or problems.
Rationale for Separate Consideration USCDIv1 includes medical services that are complete (procedures, labs) and Plan of Treatment, but not orders for services. Services not provided by the same organization where ordered requires a transfer of a patient with the relevant order information.
Use Case Description(s)
Use Case Description Orders (service requests) are used extensively by hospitals, clinicians and providers as part of the quality measurement. They are important for quality improvement, clinical decision support and measurement to understand the link between things ordered and then completed/administered. 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 services orders, and those completed.
Currently, CMS quality measures include the following order concepts. Orders for:
• Labs and diagnostic studies
• Interventions (i.e. hospice, comfort care, palliative care) and procedures
• Devices
• Follow-ups/referrals
Estimate the breadth of applicability of the use case(s) for this data element More than 4,00 hospitals and 1 million providers currently capture, access and exchange this order (service request) information. This information is currently electronically submitted by providers and hospitals to CMS for quality measurement.
eCQI resource center, includes measure specifications for CMS program eCQMs (i.e. CMS 125, CMS 71, CMS 645): https://ecqi.healthit.gov/ecqms
Link to use case project page https://ecqi.healthit.gov/ecqms
Use Case Description Each step in the chain of events between a clinician’s request for a service (order) and the completion of that service is critical for vigilance and surveillance of patient safety and appropriate care. It is important to have the capacity to evaluate the clinician’s intent, the actual completion across care settings and across time. Specifically, this concept allows for transfer of information of the order to be completed, if the service is not being provided by the same organization.
Estimate the breadth of applicability of the use case(s) for this data element All healthcare providers, laboratories, hospitals using EHR systems should have order information documented and accessible.
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) Orders reference services available in standardized terminology:
Intervention order (Comfort measures): SNOMEDCT
Device order: SNOMEDCT
Diagnostic study, laboratory test order: LOINC
Encounter/follow-up order: SNOMEDCT

https://vsac.nlm.nih.gov/valueset/expansions?pr=ecqm
Additional Specifications HL7 FHIR QI Core Implementation Guide STU4 based on FHIR R4, Service Request: http://hl7.org/fhir/us/qicore/StructureDefinition-qicore-servicerequest.html
CMS Quality Data Model (QDM) version 5.5 Guidance, orders (https://ecqi.healthit.gov/sites/default/files/QDM-v5.5-Guidance-Update-May-2020-508.pdf)
US CORE Implementation Guide: Service Request noted as a future potential profile: https://www.hl7.org/fhir/us/core/future-of-us-core.html
Current Use Extensively used in production environments
Supporting Artifacts Orders (service requests) are routinely captured in EHR systems used by hospitals and providers for the use in CMS quality reporting eCQMs across programs including IQR, QPP, and Promoting Interoperability programs. CMS requires the submission of order (service request) related data for quality measurement for eligible hospitals/CAHs and clinicians using ONC Certified Health Electronic Record Technology (CEHRT)—this includes order (service requests) for a procedure, diagnostic service, intervention, laboratory test, or other planned service for a patient.
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 Orders (service requests) 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. These orders (service requests data elements have been tested for reliability and validity of capture during the development of CMS eCQMs and can be feasibly exchanged. Ongoing testing for exchanging these data in FHIR standards via HL7 Connectathons.
https://ecqi.healthit.gov/qrda
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 element.
Estimate of Overall Burden Orders (Service requests) are regularly captured by a broad range of healthcare providers, and should not cause burden to implement. Some burden required to include a ServiceRequest profile as a US Core profile, though it is already noted as a potential addition for future iterations, and built out in QI Core.
Other Implementation Challenges N/A
ONC 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 portmi3 on

Commenter: Michael Porter, Mport Media Group, Inc. (Discharge Bridge — care-transition orchestration).

We support USCDI v7 Referral Order, Referral Note, and Reason for Referral for hospital → SNF / post-acute exchange. Please keep SNF / post-acute explicitly in examples and vocabulary guidance.

We support Medication Order and Medication Administration for transition medication safety, and recommend leveling Level 0 Discharge medications (and Medication List Type as applicable) so implementers can exchange a reconciled active list at handoff distinct from open orders vs administration.

We support Encounter Disposition, Appointment, Healthcare Agent, and Discharge Summary Note for operational handoff / decision-maker / disposition context, mapping to these existing elements before inventing new definitions.

(3) We recommend evaluating structured Prior Authorization Determination Status for inclusion or leveling (ONDEC or comment adjacent to Health Insurance Information / related coverage elements), because authorization fragmentation blocks timely acute→post-acute transitions and is relevant under CMS interoperability and prior-authorization directions that reference USCDI. Prefer placement under Health Insurance Information or Orders as ONC prefers — not a new data class.

(4) Prefer mapping operational handoff needs to existing USCDI elements — Encounter Disposition, Discharge Summary Note, Healthcare Agent, Facility Information — and leveling Level 0 Discharge medications — before inventing new definitions. ONDEC Post-acute Placement Disposition only if Encounter Disposition cannot close SNF acceptance/decline + destination + level of care + bed-ready timing.

This comment reflects an implementer perspective. It does not imply ONC endorsement and does not claim HIPAA or SOC 2 certification.

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