| Submitted By: Shelly Spiro / Pharmacy HIT Collaborative | |
|---|---|
| Data Element Information | |
| Use Case Description(s) | |
| Use Case Description | For the Pharmacist eCare Plan to help prepare for value-based payment |
| Estimated number of stakeholders capturing, accessing using or exchanging | 19 System Vendor https://www.ecareplaninitiative.com/software-solutions; CPESN network (https://www.cpesn.com) which includes over 2600 pharmacies; and anyone that adopts the Pharmacist eCare Plan implementation guide. |
| Link to use case project page | https://www.ecareplaninitiative.com/ |
| Healthcare Aims |
|
| Maturity of Use and Technical Specifications for Data Element | |
| Applicable Standard(s) | HL7 FHIR http://hl7.org/fhir/us/core/StructureDefinition-us-core-goal-definitions.html#Goal |
| Additional Specifications | http://hl7.org/fhir/us/core/StructureDefinition-us-core-goal-definitions.html#Goal |
| Current Use | Not currently captured or accessed with an organization |
| Number of organizations/individuals with which this data element has been electronically exchanged | 1 |
| Supporting Artifacts |
Omnisys as a vendor is capturing goals.outcome data |
| Potential Challenges | |
| Restrictions on Standardization (e.g. proprietary code) | None |
| Restrictions on Use (e.g. licensing, user fees) | SNOMED CT UMLS license |
| Privacy and Security Concerns | Unknown |
| Estimate of Overall Burden | Unknown |
Desired state to be achieved by a patient.
Data Element |
Information from the submission form |
|---|---|
| Outcome Code |
Description
Identifies the change (or lack of change) at the point when the status of the goal is assessed
|
Comment