FHIR Resource Mapping

Within the Chorus platform, all system features, clinical activities, and workflows correspond directly to native FHIR R4 resource structures based on the US Core Implementation Guide.

No Adapters Required

Unlike legacy systems that translate proprietary schemas into FHIR at the integration layer, Chorus uses FHIR resources directly as its fundamental persistence model through the HAPI FHIR JPA server.

Core Clinical Mapping

The following table illustrates how platform capabilities are natively represented:

System Feature / Capability	FHIR Resource	Description / Attributes
Patient Demographics	Patient	Core identity, contact info, and demographics (US Core Patient Profile).
Physiological Readings	Observation	Individual vital signs (BP, SpO2, Weight) with LOINC codes and timestamps.
Hardware / Wearables	Device	MAC addresses, UDI, manufacturer, and model of connected health devices.
Device Assignments	DeviceUseStatement	Links a specific patient to an active cellular device.
Clinical Encounters	Encounter	Captures the context of a provider interacting with a patient's data.
Care Programs	CarePlan	Defines the specific RPM protocol and thresholds assigned to a patient.
Risk Stratifications	RiskAssessment	Machine learning outputs identifying probability of clinical deterioration.
Clinical Findings	DiagnosticReport	Aggregated weekly/monthly summaries of observations and interpretations.
Alerts & Interventions	Communication + Task	Clinician messaging, automated alerts, and pending workflow actions.
Billing & Time Tracking	ChargeItem	System-generated tracking of billable time against specific CPT codes.

This strict mapping ensures that all monitoring activities and clinical insights are immediately interoperable without loss of fidelity.