201701 Medication Track
Return to January 2017 Proposals
Medication Track
Coordinated with other related Connectathon tracks
- US-Core IG
Submitting WG/Project/Implementer Group
Pharmacy FHIR Profiles Project
Justification
This project is intended to support the Pharmacy WG in moving the Pharmacy FHIR resources to a higher maturity level based on feedback from the Argonaut Project, HL7 work groups and industry implementers. The key objective for this project is to use implement and test the following FHIR Medication related resources and the corresponding US-Core medication Profiles:
In addition to implementing the existing US-Core medication Profiles this tract will examine and support the development of new proposed US-Realm profiles for MedicationAdministration and MedicationDispense.
Proposed Track Lead
See Connectathon_Track_Lead_Responsibilities
Expected participants
Please sign up!
If you're working on a server, please complete the "servers" tab of the Signup Spreadsheet **This time around you'll need to update the `status` flag to indicate whether you've begun work (or completed work), so clients will know when to start testing.** You'll also share details about how a developer can obtain OAuth client credentials (`client_id` for public apps, or a `client_id` and `client_secret` for confidential apps) as well as user login credentials. You might consider simply sharing a set of fixed credentials in this spreadsheet, or else directing users to a web page where they can complete self-service registration. If absolutely necessary, you can ask developers to e-mail you directly.
If you're working on a client, please complete the "clients" tab of the Spreadsheet. You'll also need to update the `status` flag to indicate whether you've begun work (or completed work).
Roles
(reproduced from Argonaut Project implementation-program Resprint)
Server/EHR
If you're working on a server, please complete the "servers" tab of the Sprints Spreadsheet (see above). You'll need to update the status flag to indicate whether you've begun work (or completed work), so clients will know when to start testing. You'll also share details about how a developer can obtain OAuth client credentials (client_id for public apps, or a client_id and client_secret for confidential apps) as well as **user login credentials. The preferred approach is to direct users to a web page where they can complete self-service registration. (If absolutely necessary, you can ask developers to e-mail you directly.) Work on your OAuth implementation
The expectation is that servers will follow Argonaut’s best-practice approach by implementing the OAuth2-based SMART on FHIR authorization specification. To make this more approachable for new implementers, you can think about handling security in four parts:
- open server. Before you get OAuth working, and even once you have an OAuth-secured server, it can be helpful to host sample data at a totally unprotected https endpoint. This facilitates testing, debugging, and exploration
- Standalone launch. Following SMART’s “standalone launch” flow means that the user (patient, or clinician) can begin by launching an app, and from there can engage in a “connect to my EHR” workflow. This approach is suitable for MU3 patient API access.
- EHR launch. Following SMART’s “EHR launch” flow means that the user (patient, or clinician) can begin from the EHR or potal, and launch an app from there, ensuring that the app learns the context about the surrounding EHR or portal environment. This approach is suitable for embedding apps in an EHR or portal.
- Single Sign-on. Using the OAuth2-based OpenID Connect framework for single sign-on, your authorization server can “vouch for” a user’s identity. This helps ensure that users don’t need to create a new account, with new credentials, for every app they use. This approach to SSO can be used with either of SMART’s launch flows.
Client
If you're working on a client, please complete the "clients" tab of the Sprints Spreadsheet (see above) . You'll also need to update the status flag to indicate whether you've begun work (or completed work).
Scenarios
Dedicated Zulip chat stream for this Track.
Use cases:
- Patient and Provider access to a patient’s active and historical medication list
- Patient and Provider updates to a patient’s active and historical medication list
- Create new outpatient prescription
1. Patient and Provider access to a patient’s active and historical medication list
Action: (Patient consumer or Provider) requests active medications or historical medication list.
Using
`GET /MedicationStatement?patient={id}&status=active`
for active medications or
`GET /MedicationStatement?patient={id}&status=active,completed,stopped,on-hold`
for historical medications
This scenario is similar to the Argonaut use case Sprint 4. Refer to the Argonaut Medications IG for Success Criteria. (Note although this references DSTU2, our focus is on STU3.)
Examples:
http://fhir3.healthintersections.com.au/open/MedicationStatement/?pat=1&status=active
Preconditions:
- Patient does exist on the server previously with medications.
- Server Conforms to the US-Core CapabilityStatement-daf-query-responder for Medication, MedicationStatement, MedicationRequest, and Patient profiles
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
- Ambulatory setting. Over multiple encounters
- Inpatient setting. For the duration of an entire hospitalization.
Success Criteria:Server returns a Bundle containing entries for:
- all the patient's active medications
- all the patient's current and past medications
Bonus point:The medication list includes MedicationRequest, MedicationAdministration and MedcicationDispense resources
With Server Conforming to Pharmacy FHIR Maturity Project MedicationAdministration Profile and MedicationDispense Profile
Using
`GET /MedicationRequest?patient={id}&status=active`
`GET /MedicationDispense?patient={id}&status=active`
`GET /MedicationAdministration?patient={id}&status=in-progress`
for active medications or
`GET /MedicationRequest?patient={id}&status=active,completed,stopped,on-hold`
`GET /MedicationDispense?patient={id}&status=active,completed,stopped,on-hold`
`GET /MedicationAdministration?patient={id}&status=in-progress,completed,stopped,on-hold`
for historical medications
Issues and Questions (GitHub issues link)
2. Patient or Provider adding new medication to patient’s (“active”) medication
Action: (Patient consumer or Provider) requests active medications or historical medication list.
Using
`POST/PUT...
for active medications or
``POST/PUT...
for historical medications
Examples:
Preconditions:
- Patient does exist on the server previously with medications.
- Server Conforms to the US-Core CapabilityStatement-daf-query-responder for Medication, MedicationStatement, MedicationRequest, and Patient profiles
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
- Ambulatory setting. Over multiple encounters
- Inpatient setting. For the duration of an entire hospitalization.
Success Criteria:
Bonus point:The medication list includes MedicationRequest, MedicationAdministration and MedcicationDispense resources
With Server Conforming to Pharmacy FHIR Maturity Project MedicationAdministration Profile and MedicationDispense Profile
`POST/PUT... for active medications or
``POST/PUT...
for historical medications
Issues and Questions (GitHub issues link)
3. Dispense medication from Pharmacy
This scenario should be considered for future use since current vendors haven't prioritized the resources to support.
4. Create new outpatient Prescription
This scenario should be considered for future use since current vendors haven't prioritized the resources to support.
TestScript(s)
tbd
