This page is part of the US-Medication FHIR IG (v0.0.1: STU 1 Ballot 1) based on FHIR v1.8.0. The current version which supercedes this version is 1.2.0. For a full list of available versions, see the Directory of published versions

1. Patient and Provider access to a patient’s active and historical medication list

1. This use case adopts the Use cases for the Argonaut Project specifically within the scope of accessing medication lists as prescribed in Meaningful Use 2015 §?170.302(d). Maintain active medication list. Enable a user to record, change, and access a patient’s active medication list as well as medication history: (i) Ambulatory setting. Over multiple encounters; or (ii) Inpatient setting. For the duration of an entire hospitalization.
2. Definitions:
   • Active Medication List – A list of medications that a given patient is currently taking.
   • Medication history - include a record of prior modifications to a patient’s medications
   • Question for group: do we want to add proposed medications to create a third option of “all medication” = past present and future?
3. Data Access and Retrieval which is documented in the US-Core Profiles for MedicationStatement and MedicationRequest
4. Record and change Medications: Patient or Provider adding new medication to patient’s (“active”) medication list.
   • Requires write access to patient’s data
5. Actors: Providers/Patient/EHR (See Use cases for the Argonaut Project)
6. FHIR Resources
   • MedicationStatement (Most common)
   • MedicationRequest (Nee MedicationOrder)
   • Medication
   • MedicationAdministration ( less common - context: inpatient)
   • MedicationDispense (least common - is not widely adopted)
7. Terminology
   • RxNorm

2. Create new outpatient Prescription

1. Actors: Providers/EHR (See Use cases for the Argonaut Project)
2. Workflow Description: See a general discussion of FHIR workflow here. - Question for group: Do we want to focus on a single or few patterns? (http://hl7.org/fhir/2017Jan/workflow.html#commpatterns).
3. FHIR Resources
   • MedicationRequest (Nee MedicationOrder)
   • Medication
   • Task for Workflow
4. Terminology
   • RxNorm

3. Dispense medication from Pharmacy

1. Background:
   • Not supported by community pharmacies since they are mandated to use NCPDP Script
   • Currently in hospital pharmacies using HL7 V2 RXD messaging.
   • Potential use for “secondary” recording of data.
     • For example: script history, real time benefit checking or Prescription Drug Monitoring
2. Actors: TBD
3. FHIR Resources
   • MedicationDispense
4. Terminology
   • RxNorm