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
|
Referral Orders
Description
Provider-authored request to another provider, specialist, or organization for care services.
Examples include referral orders to a wound specialist or podiatrist.
|
Submitted By: Grace Glennon, on behalf of NCQA
/ NCQA
|
Data Element Information |
Use Case Description(s) |
Use Case Description |
Referral orders represent another important type of order to support care coordination. Not all necessary medical services can be provided by a single provider, making referrals a necessary data point. Like other orders, referral orders are routinely captured and exchanged across care settings for routine care. These orders can be captured and exchanged via standard vocabulary (SNOMED).
In addition to being collected and exchanged as part of routine care for patients, quality measures currently utilize referral order information to assess appropriate care. NCQA continues to add follow-up components to many new and existing measures to assess for appropriate care following a significant medical finding; referral orders are one component to appropriate follow-up. |
Estimate the breadth of applicability of the use case(s) for this data element
|
(Level 2) – Use cases apply to most care settings or specialties.
Referral orders are documented, utilized and exchanged across care settings including primary care, outpatient and acute care settings, and a necessary process step to receive certain types of care. |
ONC Priority |
- Address behavioral health integration with primary care and other physical care
- Mitigate health and health care inequities and disparities
- Address the needs of underserved communities
- Address public health interoperability needs of reporting, investigation, and emergency response
|
Maturity of Use and Technical Specifications for Data Element |
Applicable Standard(s) |
SNOMED CT
|
Additional Specifications |
FHIR US Core (6.1.0, 7.0.0) ServiceRequest- must have a code defining what is being requested |
Current Use |
(Level 2) Captured, stored, or accessed in multiple production EHRs or other HIT modules from more than one developer |
Extent of exchange
|
(Level 2) Between more than two production EHRs or other HIT modules using available interoperability standards |
Supporting Artifacts |
Referrals are used in quality measures today, and used as part of routine care across almost all provider types.
|
Potential Challenges |
Restrictions on Standardization (e.g. proprietary code) |
No restrictions. |
Restrictions on Use (e.g. licensing, user fees) |
No restrictions. |
Privacy and Security Concerns |
Exchange of patient health information should follow HIPPA Privacy Rules. |
Estimate of Overall Burden |
Given that USCDI already includes other orders elements, exchanged via the same structure as this orders element, implementation burden should be low. |
Other Implementation Challenges |
No other known implementation challenges. |
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 1
- Use cases apply to several care settings or specialties.
|
|