0.4.4 - ci-build

StandardPatientHealthRecordIG - Local Development build (v0.4.4). See the Directory of published versions

Conformance Recommendations

This implementation guide was developed through meta-analysis of dozens of other guides, journal liturature, and an environment surveys of the PHR market. Implementators may find the following implementation guides of particular interest.

In this specification, the key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” are to be interpreted as described in RFC2119.

Implementation Guide Specialty Resources APIs
Bulk Data Export Medical Records NOT APPLICABLE MUST
PHR-S Functional Model   SHOULD MAY
Argonaut Data Query Internal Medicine SHOULD SHOULD
Argonaut Scheduling Primary Care SHOULD MAY
Argonaut Clinical Notes Primary Care SHOULD MAY
Argonaut Questionnaire   SHOULD MAY
Patient Request for Corrections   SHOULD MAY
International Patient Summary   SHOULD MAY
US CORE   SHOULD MAY
SMART on FHIR - App Launch   NOT APPLICABLE SHOULD
C-CDA on FHIR   MAY MAY
PACIO - Advanced Directives   SHOULD MAY
PACIO - Cognitive Status Neurology MAY MAY
PACIO - Functional Status Physical Therapy MAY MAY
SMART Health Cards - Vaccine & Testing Epidemiology SHOULD MAY
mCode Oncology SHOULD MAY
Gravity - Social Determinates of Health Social Work SHOULD MAY
Dental Data Exchange Dental MAY MAY
Genomics Reporting Genetics MAY MAY
Radiation Dose Summary Radiology MAY MAY
Breast Radiology Reporting Radiology MAY MAY
mCODE   MAY MAY
Allergy Intolerance Immunology SHOULD MAY
Vital Signs Intensive Care SHOULD MAY
UDAP Security   NOT APPLICABLE SHOULD
SNOMED Terminology Server   SHOULD MAY
CARIN Digital Insurance Card   SHOULD MAY
Physical Activity   SHOULD MAY
Mobile Access to Health Documents   MAY MAY
Patient Reported Outcomes   MAY MAY
Patient Health Devices   MAY MAY
Da Vinci - Prior Authorization   MAY MAY
Vital Records - Birth and Fetal Death Reporting   MAY MAY