Difference between revisions of "201901 vhdir"
(Created page with "{{subst::Template for FHIR Connectathon Track Proposals}}") |
|||
| Line 3: | Line 3: | ||
__NOTOC__ | __NOTOC__ | ||
=Track Name= | =Track Name= | ||
| + | VhDir | ||
==Submitting WG/Project/Implementer Group== | ==Submitting WG/Project/Implementer Group== | ||
| − | + | FHIR-I / Federal Health Architecture / Office of the National Coordinator | |
==Justification== | ==Justification== | ||
<!--Why is this an important track to include in the connectathon - include implementer need, impact on ballot, FMM readiness of the resources, etc. --> | <!--Why is this an important track to include in the connectathon - include implementer need, impact on ballot, FMM readiness of the resources, etc. --> | ||
| + | VhDir IG describes the architectural considerations for attesting to, validating, and exchanging data from a central source of validated provider data (i.e. a Validated Healthcare Directory or VHDir), as well as a RESTful FHIR API for accessing data from a VHDir. | ||
| + | Many of the clinical workflows require the provider data such as their location details, their electronic address to send information, their specialty, their insurance preferences etc. All of this data gets curated in a healthcare directory which is then accessed in clinical workflows to perform the necessary actions. | ||
==Clinical input requested== | ==Clinical input requested== | ||
Revision as of 12:11, 26 September 2018
Track Name
VhDir
Submitting WG/Project/Implementer Group
FHIR-I / Federal Health Architecture / Office of the National Coordinator
Justification
VhDir IG describes the architectural considerations for attesting to, validating, and exchanging data from a central source of validated provider data (i.e. a Validated Healthcare Directory or VHDir), as well as a RESTful FHIR API for accessing data from a VHDir.
Many of the clinical workflows require the provider data such as their location details, their electronic address to send information, their specialty, their insurance preferences etc. All of this data gets curated in a healthcare directory which is then accessed in clinical workflows to perform the necessary actions.
Clinical input requested
Related tracks
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
Scenario Step 1 Name
- Action:
- Precondition:
- Success Criteria:
- Bonus point:
