This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Category:201701 Medication Track"
Jump to navigation
Jump to search
Bamarquard (talk | contribs) |
Bamarquard (talk | contribs) |
||
| Line 28: | Line 28: | ||
==Scenarios== | ==Scenarios== | ||
<!-- What will be the actions performed by participants? --> | <!-- What will be the actions performed by participants? --> | ||
| − | === 1. Patient access to a medication | + | === 1. Patient access to a medication === |
| − | :Action: (Patient consumer) requests | + | :Action: (Patient consumer) requests medications. |
:Precondition: Patient does exist on the server previously with medications | :Precondition: Patient does exist on the server previously with medications | ||
:Success Criteria: Patient medication list returned. | :Success Criteria: Patient medication list returned. | ||
Revision as of 18:53, 24 October 2016
Return to January 2017 Proposals
Medication Track
Submitting WG/Project/Implementer Group
Justification
Proposed Track Lead
See Connectathon_Track_Lead_Responsibilities
Expected participants
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.
