Difference between revisions of "Category:201701 Medication Track"
| Line 48: | Line 48: | ||
Please sign up! | Please sign up! | ||
| − | If you're working on a server, please complete the [ | + | If you're working on a server, please complete the [https://docs.google.com/a/healthedatainc.com/spreadsheets/d/1WVL09ge7SXE-Og6k3oVqWH9dcRexq76uIpGjJOBO4rQ/edit?usp=sharing "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 [ | + | If you're working on a client, please complete the [https://docs.google.com/a/healthedatainc.com/spreadsheets/d/1WVL09ge7SXE-Og6k3oVqWH9dcRexq76uIpGjJOBO4rQ/edit?usp=sharing "clients" tab of the Sprint 4 Spreadsheet]. You'll also need to update the `status` flag to indicate whether you've begun work (or completed work). |
| − | |||
| − | |||
==Roles== | ==Roles== | ||
Revision as of 13:27, 26 October 2016
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 Sprint 4 Spreadsheet. You'll also need to update the `status` flag to indicate whether you've begun work (or completed work).
Roles
Please include information here regarding how much advance preparation will be required if creating a client and/or server.
Role 1 Name
Scenarios
Scenarios
1. Patient access to a medication
- Action: (Patient consumer) requests medications.
- Precondition: Patient does exist on the server previously with medications
- Success Criteria: Patient medication list returned.
- Bonus point: The medication list includes both MedicationStatement and MedicationRequest
TestScript(s)
This category currently contains no pages or media.
