This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

201901 vhdir

From HL7Wiki
Revision as of 12:58, 26 September 2018 by Nagesh bashyam (talk | contribs)
Jump to navigation Jump to search


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.

Technical Considerations: The Connectathon should identify the technical APIs that are most meaningful, the specific search parameters that are most meaningful.

Policy Considerations: The Connectathon should identify what kind of validations should be performed on the data before consuming the data.

Clinical input requested

Yes, need to determine the commonly used search parameters in workflows for making the directory information useful.

Related tracks

Transitions of Care.

Proposed Track Lead

See Connectathon_Track_Lead_Responsibilities

Daniel Chaput, Alex Kontur.

Expected participants

FHA ONC


Roles

Please include information here regarding how much advance preparation will be required if creating a client and/or server.

VhDir Server

The VhDir Server provides the validated health care directory content to all the local environments. The VhDir has to preload a set of validated healthcare directory information.


TestScript(s)

Security and Privacy Considerations