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

Onelife Overview

The OneLife section of this Implementation Guide describes the FHIR R4 resources produced by One Medical's OneLife electronic health record system. These resources are synced to the Clinical Data Platform (CDP) and made available to downstream consumers including clinical decision support, quality reporting, the patient-facing app, and external health information exchanges.

Available Profiles

Profile	Resource Type	Description
OneLifeCondition	Condition	Patient conditions, problems, and diagnoses from the problem list. Coded in ICD-10-CM with SNOMED CT cross-maps.
OneLifeObservation	Observation	Clinical measurements and vital signs (e.g., heart rate, temperature, weight).
OneLifeBloodPressureObservation	Observation	Blood pressure readings with systolic and diastolic components.

Governance Tags

Every OneLife resource includes two governance tags in meta.tag that identify the data's provenance:

Tag	System	What it means
Source Type	http://onemedical.com/terminology/source-type	Who originated the data. OneLife resources use one-medical-collected (clinician-entered data).
Source System	http://onemedical.com/terminology/source-system	Which application wrote the data. OneLife resources use onelife.

These tags are required on every resource and are used by downstream consumers to filter and route data appropriately.

Getting Started

• Most commonly used: Start with OneLifeCondition for the patient problem list, and OneLifeObservation for vital signs and measurements.
• Each profile page includes a human-readable intro, a Key Fields table, and interpretation notes — read these before diving into the FHIR differential tables.
• Examples are provided for each profile showing realistic clinical scenarios with actual code systems and values.