MyHealtheVet PHR FHIR API
0.3.9-current - ci-build
MyHealtheVet PHR FHIR API
0.3.9-current - ci-build
MyHealtheVet PHR FHIR API, published by VA Digital Services. This guide is not an authorized publication; it is the continuous build for version 0.3.9-current built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/department-of-veterans-affairs/mhv-fhir-phr-mapping/ and changes regularly. See the Directory of published versions
| Official URL: https://department-of-veterans-affairs.github.io/mhv-fhir-phr-mapping/ImplementationGuide/va.mhv.fhir.phr | Version: 0.3.9-current | |||
| IG Standards status: Trial-use | Maturity Level: 1 | Computable Name: VAMHVFHIRPHR | ||
This Implementation Guide includes the FHIR profiles and test plan for how MHV exposes the PHR. MHV is providing a FHIR Server API. This publication and github repository are managed by the department of veterans affairs. It is a publication, not a software product. As a publication it is publicly published (not private repository, private publication, or internal). It contains examples of reasonable medical data as would be found in Vista and the FHIR translations of that Vista data. These examples are not identifiable patient data, using test patient names. Some of the practitioner identities are madeup test users, some are test engineers who entered the data, and some historic data does have identifiers of historic clinicians from the VA.
This includes the test plan, profiles of how MHV makes PHR available, examples that match those profiles, and examples that are good FHIR Resources that MHV should handle well.
This is work as part of My Health Medical Records Product where business requirements can be found.
The main sections of this IG are:
All MHV profiles are based on HL7 FHIR US-Core implementation guide, which provides guidance to the USA marketplace that VHA participates within. Deeper explanation is provided in the US-Core specification.
Changes are noted in GitHub, and a human readable summary is in the Github Readme