MyHealtheVet use of PGHD
0.2.10-beta - ci-build
MyHealtheVet use of PGHD
0.2.10-beta - ci-build
MyHealtheVet use of PGHD - Local Development build (v0.2.10-beta) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Page standards status: Informative |
Overall test plan leverages the Profiles, and Examples shown on the Artifacts Summary. The Profiles listed are describing the constraints that MHV uses when publishing (Create) into PGHD. Thus any Resources that are known to have been published by MHV MUST be conformant to these profiles.
The Examples listed in Example Instances are example instances that are conformant to the MHV profiles.
The Examples listed in Other are examples that either assist with the structure of the examples (e.g. Patient and Encounter) or are examples that MHV should be able to handle in various ways.
See the Test Plan for each Profile to understand the specific expectations for each good, odd, and bad example.
The following Actions are defined for use in the Cucumber scripts
SUT - System Under Test – this is the MyHealtheVet application – aka MHV
PGHD - Patient Generated Health Data service – this is the FHIR Server that MyHealtheVet uses – aka PGD
Test-Patient - a FHIR Patient resource within the PGHD that is used for testing purposes and is tied to a test login to MHV
Test-Bench - a FHIR application (likely built with HAPI) that is used with PGHD for testing of the MHV
Preconditions
PGHD is operational and has no known defects that would affect the test.
Test-Patient is created or known to have no data that would affect the test.
This action is used to initialize a test, it is not expected to fail. So a failure is a fundamental failure, not an indication of the system-under-test.
GIVEN FHIR Resource X from this Implementation Guide
ACTION: