Personal Health Records, published by HL7 International / Patient Empowerment. This guide is not an authorized publication; it is the continuous build for version 1.0.0-ballot2 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/personal-health-record-format-ig/ and changes regularly. See the Directory of published versions
| Page standards status: Informative |
The intention of the PHR FHIR Implementation Guide is to provide a standard mechanism for the communication of health records contained in a personal health record. FHIR provides a data model for health history with a pedigree of 30 years of industry experience and use in major EHRs, and is used here as the exchange and communication format.
Loosely speaking, this data model encompasses all data relevant to a patient's health, whether it be generated by clinicians in a hospital inpatient setting, by a specialist clinic or nursing home, or contributed by the patient via gym fitness apps, nutrition tracking apps, and so forth. The FHIR data model allows this flexibility, while still being informed by clinical learnings on how to code data with SNOMED, LOINC, ICD-10 and other vocabularies, how to organize data into resources, and how to apply region specific extensions and profiles.
When implementing a PHR that conforms to this IG, the following FHIR resources represent the surface area of what most EHRs, PHRs, and consumer medical devices will export. While it is not the minimal amount of data necessary (many systems will begin implementation with a single resource type), it represents the minimum implementation needed to reasonably parse an arbitrary EHR or PHR record that one might receive from an external system. Note that the FHIR specification itself contains some 120+ resources, many of which include clinical workflow, administrative, and public health functionality. By contrast, the following model of ~36 resources is scoped to what a patient may receive via patient portals, consumer medical devices, health information exchanges, and the like.
This guide concerns itself with record keeping — library science — meaning the faithful preservation and exchange of health records as they were written. It does not provide guidance on how sex and gender should be modeled. The demographic rows in the table below (sex assigned at birth, race, ethnicity, gender identity, sexual orientation) document element patterns that appear in records a PHR may receive from external systems and jurisdictions; a record keeper preserves such records as received, and may be legally obligated to do so (see Jurisdictional Variation).
Systems generating new data for the PHR should consult their regional jurisdiction's current guidance on the collection and representation of sex, race, and ethnicity, and should be aware that these requirements differ across jurisdictions and change over time.
| FHIR resource | Elements | Standard | Category | Argonaut R4 |
|---|---|---|---|---|
| Patient | Given Name Family Name Previous Name Middle Name Suffix Date of Birth Gender Preferred Language Current Address Previous Address Phone Number Email address |
International Patient Summary (Optional) US Core (Optional) |
Demographics | Yes |
| Patient | Sex (assigned at birth) Race Ethnicity |
US Core | Demographics Social Determinants of Health |
No |
| Patient | Gender Identity |
Gender Harmony | Demographics | No |
| Patient | Sexual Orientation |
Demographics | No | |
| AllergyIntolerance | Substance (Medication) Substance (Drug Class) Reaction |
US Core | Yes | |
| Appointment | Argonaut Scheduling | Yes | ||
| Binary | Yes | |||
| Bundle | Yes | |||
| BodyStructure | No | |||
| Condition | SDOH Problems Health Concerns Date of Diagnosis Date of Resolution |
US Core | Active Problems Social Determinants of Health |
Yes |
| Composition | Progress Notes History and Physicals Discharge Summaries Operative Notes Procedure Notes Consultation notes |
US Core C-CDA on FHIR |
Clinical Documentation | Yes |
| CarePlan | Yes | |||
| CareTeam | No | |||
| Claim | Insurance & Out-of-pocket Costs | CMS Bluebutton 2.0 | Financial Health | No |
| Communication | No | |||
| Consent | Medical Power oof Attorneys |
End of Life | No | |
| Contract | Medical Power oof Attorneys |
End of Life | No | |
| DiagnosticReport | Radiologist Report Pathologist Report Cardiologist Report Oncologist Report |
US Core Radiation Dose Summary Breast Radiology Reporting |
Diagnostic Imaging | Yes |
| Device | Yes | |||
| DocumentReference | Yes | |||
| FamilyMemberHistory | No | |||
| Goal | No | |||
| ImagingStudy | Diagnostic Radiology Interventional Radiology Mammography Ultrasound MRI/CT |
US Core Radiation Dose Summary Breast Radiology Reporting |
Diagnostic Imaging | No |
| Immunization | Immunizations Vaccinations |
US Core SMART Health Cards |
Yes | |
| MeasureReport | Patient Reported Outcomes (PRO) | Patient Generated Data | No | |
| Media | Yes | |||
| Medication | US Core | Active Medications | Yes | |
| MedicationStatement | Yes | |||
| MolecularSequence | Whole Genome Sequence | Genomics Reporting | Genomics | No |
| Observation | Smoking status Glucose Steps Walked Diastolic Blood Pressure Systolic Blood Pressure Body Height Body Weight Heart Rate Respiratory Rate Body Temperature Pulse Oximetry Inhaled O2 Concentration BMI Percentile Weight for length percentile Head Circumference percentile |
Vital Signs Physical Activity |
Symptoms Vital Signs Laboratory Results Remote Patient Monitoring Behavioral Observations Wearables Point of Care Testing |
Yes |
| Practitioner | Yes | |||
| Provenance | No | |||
| Procedure | Yes | |||
| Questionnaire | Migrant farm worker status Armed forces discharge Phone usage data |
Argonaut Questionnaire | Structured Data Capture Social Determinants of Health PRAPARE Survey Technology Usage |
Yes |
| QuestionnaireResponse | Argonaut Questionnaire | Yes | ||
| RelatedPerson | Yes | |||
| Specimen | No | |||
| Schedule | Argonaut Scheduling | Yes | ||
| Slot | Argonaut Scheduling | Yes | ||
| Task | Patient Request for Corrections | No |