Patient Generated Health Data Implementation Guide
0.1.0 - ci-build

Patient Generated Health Data Implementation Guide - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Artifacts Summary

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

Structures: Resource Profiles

These define constraints on FHIR resources for systems conforming to this implementation guide.

AllergyIntolerance_Patient

Representation of the base AllergyIntolerance profile for the patient

AuditEventDataAccess

Representatione Profile for recording clinical and research data access as seen in mobile interfaces

Condition_Patient

Representation of the clinical condition using the Condition profile

Consent_Patient

Representation of the Consent profile for informed consent to the processing of health data.

Device_Audit

Represents the software origin of the log (e.g., Mobile App or Web Portal).

FamilyMemberHistory_Patient

Representation of the patient's family medical history using the FamilyMemberHistory profile

MedicationStatement_Patient

Representation of a list of Medicines/Supplements for a specific patient via MedicationStatement profile

Medication_Patient

Representation of a medicine or supplement that can be used by the patient via the Medication profile

Observation_LifeStyle

Representation of the patient's lifestyle observations via the Observation profile

Observation_Symptoms

Representation of the patient's symptom observations via the Observation profile

Observation_VitalSign

Representation of the patient's vital signs observations via the Observation profile

Organization_PGHD

Represents organizations or entities with data access context

PGHD_Patient

Representation of the patient using the Patient profile in the context of Patient-Generated Health Data (PGHD)

Practitioner_Patient

Representation of the Practitioner's basic profile

RiskAssessment_Patient

Representation of the risk assessment profile derived from medical history data and clinical predictive models based on artificial intelligence

Structures: Extension Definitions

These define constraints on FHIR data types for systems conforming to this implementation guide.

Context Access extension

Specifies whether the data access is regulated for example Regional-level and etc

Level of confidence in clinical information

Indicates the type and level of reliability of the information

Terminology: Value Sets

These define sets of codes used by systems conforming to this implementation guide.

Allergy Category Code VS

ValueSet containing the list of codes to be used for allergies/intolerances (e.g. food, medication)

ConfidenceLevel VS

ValueSet indicating the origin and confidence assigned to clinical information

Context Access Vs

ValueSet for Context Access

Dosage VS

ValueSet for patient medication dosing

Dosage direction VS

ValueSet used to specify the different routes of drug administration

Lifestyle observations

ValueSet for lifestyle observations

Observation Category VS

ValueSet for category type

Patient Symptoms VS

ValueSet for patient symptoms

VitalSignsObservations VS

ValueSet for vital signs observations

Terminology: Code Systems

These define new code systems used by systems conforming to this implementation guide.

CS Confidence Level

CodeSystem defining the levels of clinical confidence attributed to the origin of information, to indicate the reliability and certification of the source

CS AccessContext

CodeSystem for Context Access.

Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.

ASL-Napoli-1

Example of a regional-level organization (ASL Napoli 1)

Allergy_Penicillin G

Example of allergy to Penicillin G according to the AllergyIntolerance_Patient profile

AppMobileUser

Example of a generic audit device (Mobile App)

AuditExample

Example of an AuditEvent recording a data access for healthcare purposes at a regional level.

Body-Height-Patient-001

Example of body height observation for a patient

Condition-Patient-001

Example of clinical condition - Type 2 diabetes mellitus

Condition-Patient-002

Example of clinical condition - Essential (primary) hypertension

Consent Local Care - ASL

Consent for treatment at regional/local level (ASL)

Dr. Mario Rossi

Example of a physician

FamilyMemberHistory-Patient-001

Example of a family history of cancer

Hospital-Central

Example of a local-level organization

Medication-Patient-001

Example of a drug for the treatment of diabetes

Medication-Patient-002

Example of a drug for the treatment of hypertension

Medication-Statement-Patient-001

Instructions for taking medication by the patient (diabetes medication)

Medication-Statement-patient-002

Instructions for taking medication by the patient (hypertension medication)

Ministry-of-Health

Example of a national-level organization

Observation-Patient-HeartRate-001

Example of heart rate observation for a patient

Patient Smoking Status

Example of smoking status observation for a patient

Patient-PGHD-001

Example of Patient 001

Patient-PGHD-002

Example of Patient 002

Patient-PGHD-003

Example of Patient 003

Project-Research-XYZ

Example of a specific research project organization

Symptom observation: abdominal pain

Example of patient pain observation

Symptom observation: fever

Example of patient observation