Difference between revisions of "201805 Clinical Notes Track"
Bamarquard (talk | contribs) (Created page with "[http://wiki.hl7.org/index.php?title=Category:201805_FHIR_Connectathon_Track_Proposals Return to May 2018 Proposals] Category:201805_FHIR_Connectathon_Track_Proposals|May 20...") |
Bamarquard (talk | contribs) |
||
| Line 51: | Line 51: | ||
<!-- What will be the actions performed by participants? --> | <!-- What will be the actions performed by participants? --> | ||
| − | See the Argonaut | + | See the Argonaut Clinical Notes Build Use Cases: |
| − | + | <!-- | |
* '''[https://argonautproject.github.io/scheduling/patient-scheduling.html Patient based Scheduling Use Cases]''' | * '''[https://argonautproject.github.io/scheduling/patient-scheduling.html Patient based Scheduling Use Cases]''' | ||
** Use Case 1: Patient Portal Scheduling for existing patients | ** Use Case 1: Patient Portal Scheduling for existing patients | ||
| Line 68: | Line 68: | ||
* Cancels or cancel/reschedules | * Cancels or cancel/reschedules | ||
* Prefetching and updating Slots | * Prefetching and updating Slots | ||
| + | --> | ||
==TestScript(s)== | ==TestScript(s)== | ||
Revision as of 15:24, 27 February 2018
Zulip Chat stream for this Track is here and issues can be posted here
Background For Clinical Notes
This track is based upon Argonaut Clinical Notes Profile. It is based upon the FHIR 3.0.1 Standard.
For additional background, review the DocumentReference resource.
Submitting WG/Project/Implementer Group
Justification
The Argonaut Clinical Notes Profile is a vendor agnostic specification providing FHIR RESTful APIs and guidance for access to Clinical Notes by both patient and practitioner end users. This specification is based on FHIR Version 3.0.1 and specifically the DocumentReference resource.
The US ONC released a draft U.S. Core Data for Interoperability which proposed support for Clinical Notes access.
Proposed Track Lead
Coordinator: Brett Marquard
Expected participants
Servers: Epic, Cerner. Plan to contact Argonaut organizations for additional participants.
Clients: TBD
Roles
Provider or 3rd Party consumer application (Client)
An application that should be used by an end user (e.g., patient or practitioner) to support search for and retrieval of Clinical Notes.
FHIR Server (EHR)
A Server that contains Clinical Data.
If creating a client application, this track should require minimal work in advance of the connectathon, though at least a bit of playing is recommended. If creating a server, advanced preparation will be required.
Scenarios
See the Argonaut Clinical Notes Build Use Cases:
TestScript(s)
The supporting TestScripts and corresponding fixtures have been committed to the FHIR documents Github repository at: TBD
Please note that the available TestScripts test the TBD
Security and Privacy Considerations
- What Authentication/Authorization will be used (e.g. SMART on FHIR (OAuth), HEART (UMA/OAuth), IHE IUA (OAuth), generic OAuth, generic SAML, mutual-Auth-TLS), is out of scope and left to implementations. Expectation is many systems will use SMART on FHIR (OAuth)
