Submitted By: Shelly Spiro / Pharmacy HIT Collaborative | |
---|---|
Data Element Information | |
Rationale for Separate Consideration | These foundational FHIR resources are part of a suite of resources and should all be under USCDI Medication as they are needed for eCare Plans, including but not limited to the Pharmacist eCare Plan. |
Use Case Description(s) | |
Use Case Description | These foundational FHIR resources are part of a suite of resources and should all be under USCDI Medication as they are needed for eCare Plans, including but not limited to the Pharmacist eCare Plan. |
Estimated number of stakeholders capturing, accessing using or exchanging | At least 21 pharmacy system vendors are FHIR enabled and are created millions of Pharmacist eCare Plans throughout the US. |
Healthcare Aims |
|
Maturity of Use and Technical Specifications for Data Element | |
Applicable Standard(s) | RxNorm and SNOMED CT |
Additional Specifications | https://www.hl7.org/fhir/medications-module.html |
Current Use | This data element has been used at scale between multiple different production environments to support the majority of anticipated stakeholders |
Supporting Artifacts |
https://www.ecareplaninitiative.com/ https://216b2f95-65cb-4e7e-bd94-a9b066b0a193.filesusr.com/ugd/b303f5_a66df3115abd40a58659bae8f51b4aad.pdf |
Number of organizations/individuals with which this data element has been electronically exchanged | 5 or more. This data element has been tested at scale between multiple different production environments to support the majority of anticipated stakeholders. |
Potential Challenges | |
Restrictions on Standardization (e.g. proprietary code) | MedicationKnowledge resource is draft |
Restrictions on Use (e.g. licensing, user fees) | None known. |
Privacy and Security Concerns | None known. |
Estimate of Overall Burden | Burden is on the EHR and pharmacy system vendors to implement. |
ONC Evaluation Details Each submitted Data Element has been evaluated based on the following 4 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 |
|
---|---|
Maturity – Standards/Technical Specifications | Level 1/2 - Must be represented by a vocabulary standard or an element of a published technical specification |
Maturity - Current Use | Level 2 - Used at scale in more than 2 different production environments |
Maturity - Current Exchange | Level 2 - Demonstrates exchange between 4 or more organizations with different EHR/HIT systems |
Breadth of Applicability - # Stakeholders Impacted | Level 2 - Used by a majority of patients, providers or events requiring its use |
Comment