One Medical FHIR Implementation Guide
0.1.0 - ci-build
One Medical FHIR Implementation Guide - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.
| OneLife FHIR Server Capability Statement |
Describes the FHIR R4 capabilities of the OneLife Clinical Data Platform. |
These define constraints on FHIR resources for systems conforming to this implementation guide.
| OneLife Blood Pressure Observation |
Represents a blood pressure measurement recorded for a One Medical patient, containing systolic and diastolic values as separate components. Blood pressure is always captured as a paired reading with both systolic and diastolic values in mmHg. Blood pressure readings are typically taken by a clinician during a visit using a manual or automated cuff, or self-reported by patients using a connected home blood pressure monitor. The overall observation is coded with LOINC 85354-9 (Blood pressure systolic & diastolic), and each component carries its own LOINC code (e.g., 8480-6 for systolic, 8462-4 for diastolic). This profile uses US Core Vital Signs as its parent since blood pressure is always categorized as a vital sign and the translator populates all required US Core fields. |
| OneLife Condition |
Represents a patient's clinical conditions, problems, and diagnoses as documented by One Medical clinicians. Conditions are recorded on the patient's problem list during clinical encounters and coded using ICD-10-CM, with SNOMED CT cross-maps included when available. Each record tracks clinical status (active, resolved, or inactive) and verification status (confirmed, unconfirmed, provisional, refuted, or entered-in-error) reflecting the clinician's certainty about the diagnosis. Sensitive conditions (e.g., behavioral health, HIV, substance abuse) carry security labels in meta.security indicating confidentiality level and information sensitivity category. Conditions hidden from the patient portal are tagged with the NOPAT act code. Consumers should note that clinicalStatus may be absent for unconfirmed, suspected, or rejected conditions — these represent diagnostic uncertainty rather than a known clinical state. The code field always includes an ICD-10-CM coding and may also include a SNOMED CT coding for the same diagnosis. |
| OneLife Observation |
Represents a clinical measurement recorded for a One Medical patient, including vital signs (e.g., heart rate, temperature, weight, BMI), laboratory results (e.g., glucose, cholesterol), and patient-reported survey responses. Measurements are captured during clinical encounters by clinicians, self-reported by patients via connected devices, or received from external laboratories. The observation category determines the US Core profile this resource conforms to: vital signs use the US Core Vital Signs profile, laboratory results use the US Core Observation Lab profile, and survey responses have no additional US Core profile. Values may be numeric (with UCUM units) or string-based depending on the measurement type and available unit mappings. Note: This profile uses base FHIR Observation as its parent because the translator dynamically selects between US Core Vital Signs and US Core Observation Lab profiles at runtime based on the measurement category. Both conformance claims appear in meta.profile on the output resource. |
| PPVAllergyIntolerance |
A OM PPV AllergyIntolerance |
| PPVCommunication |
A OM PPV Communication. |
| PPVComposition |
A OM PPV Composition |
| PPVCondition |
A OM PPV Condition |
| PPVEncounter |
A OM PPV encounter |
| PPVMedicationRequest |
A OM PPV Medication Request |
| PPVMessageHeader |
A OM PPV visit message header. |
| PPVPatient |
A OM PPV Patient |
| PPVProcedure |
A OM PPV Procedure |
| PPVVisitBundle |
A bundle sent representing a PPV visit. |
| VBCBundle |
A bundle sent by VBC. |
| VBCCondition |
A OM VBC Condition |
| VBCMessageHeader |
A VBC message header. |
These define sets of codes used by systems conforming to this implementation guide.
| PPV Condition Category Value Set |
A subset of values accepted for condition.category.coding |
These define new code systems used by systems conforming to this implementation guide.
| One Medical Scheduling Type |
Types of scheduling |
| One Medical Source System |
Identifies the source system of a resource |
| One Medical Source Type |
Identifies the source type of a resource |
| One Medical Terminology |
General One Medical terminology codes |
| One Medical Virtual Encounter Service |
Virtual encounter service types |
| One Medical Virtual Encounter Type |
Types of virtual encounters |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
| OneLife Blood Pressure Example — Normal In-Office Reading |
A normal blood pressure reading (120/78 mmHg) taken by a clinician during a routine office visit. Demonstrates the multi-component structure with systolic and diastolic values. |
| OneLife Condition Example — Active Hypertension |
An active, confirmed diagnosis of essential hypertension with both SNOMED CT and ICD-10-CM codings. Represents a typical problem list entry documented by a clinician during a routine visit. |
| OneLife Condition Example — Resolved Ankle Sprain |
A resolved condition showing abatementString with the resolution text. When a clinician resolves a problem, the resolution field or last-updated date appears as abatementString. |
| OneLife Condition Example — Sensitive Condition with Security Labels |
A behavioral health condition (generalized anxiety disorder) with security labels showing the confidentiality level (R=restricted) and sensitivity category (BH=behavioral health). Demonstrates how sensitive conditions are tagged for access control. |
| OneLife Condition Example — Unconfirmed Celiac Disease |
An unconfirmed condition with no clinicalStatus. Unconfirmed, suspected, and rejected conditions lack a clinical status because the diagnosis itself is uncertain. |
| OneLife Observation Example — Fasting Glucose (Laboratory) |
A fasting glucose lab result received from an external laboratory. Demonstrates a laboratory observation with numeric value, UCUM units, reference range, and the laboratory category. |
| OneLife Observation Example — Heart Rate (Vital Sign) |
A heart rate measurement taken by a clinician during a routine visit. Demonstrates a vital sign observation with LOINC coding, UCUM units, and the vital-signs category. |
| OneLife Observation Example — PHQ-9 Score (Survey) |
A PHQ-9 depression screening score from a patient survey. Demonstrates a survey observation with a string value and the survey category. |
| OneLife Patient Example |
A fictional One Medical patient used as a reference target in other examples. |
| OneLife Practitioner Example |
A fictional One Medical clinician used as a reference target in other examples. |
These are resources that are used within this implementation guide that do not fit into one of the other categories.