Chronic disease management
Chronic Disease Management on FHIR
Chronic-condition programs combine ongoing monitoring with periodic review and a multi-disciplinary care team. The FHIR-native pattern is CarePlan with Goals, Observation streams from devices and lab work, Task-driven follow-ups, and a CareTeam-scoped access model that includes everyone who supports the patient.
What you can build
- Per-patient goals as Goal resources
Targets (HbA1c, weight, blood pressure) are Goals with target values and timeframes. Progress is computed against the underlying Observations.
- Multi-disciplinary CareTeam access
Physicians, nurses, dietitians, pharmacists, and patient navigators each have appropriate access through CareTeam membership.
- Long-running data series
Years of Observations queryable through the same FHIR API. No archival migration when a patient's history grows.
What you get out of the box
Who this is for
Care management teams, ACO informatics leads, and product teams building chronic-care platforms for diabetes, hypertension, heart failure, COPD, asthma, and similar conditions.
Clinical applicability
A diabetes care program follows 1,200 patients with type 2 diabetes. CarePlans capture each patient's goals (HbA1c target, weight, activity); Observations land from glucose meters and lab results; care team members coordinate through Tasks and Communications.
Modeling the program
A chronic-care program is a CarePlan with periodic review activities and ongoing monitoring activities. PlanDefinitions can capture standard program structures (the diabetes program, the heart failure program) and CarePlans instantiate them per patient.
Goals attached to the CarePlan capture the per-patient targets. Progress against goals is computed from the relevant Observations rather than stored as duplicate state. The Goal's target stays stable; the patient's actual values move.
Multi-disciplinary access
The care team for a chronic-condition patient typically includes the primary physician, a care management nurse, sometimes a dietitian or pharmacist, and patient navigators or community health workers. Each member has different needs.
CareTeam membership and role-specific rules express this. A nurse role has full access to the active patients on their team; a dietitian role sees nutrition-related Observations and Goals but not the full chart; a community health worker role sees scheduled outreach Tasks but not detailed clinical data unless the patient consents.
Long-running data and retention
A chronic-disease patient generates years of data. The FHIR resource model handles this naturally: Observations accumulate, the patient's history is queryable, and the access scope follows the CareTeam relationships rather than the time of the data.
Retention is a deployment decision driven by the operator's policy. Soft-delete patterns or archival storage tiers fit the chronic-disease pattern where the data has long-term clinical value but the access patterns shift over time.
Related docs
FAQ
How do I integrate with lab systems?
Lab interfaces typically write Observations to the FHIR backend through a service identity. The shape is the same as device-driven Observations; the source is the lab provider Device.
Can patients see their own goals and progress?
Yes. The Patient role reads their CarePlan, Goals, and Observations through the PatientCompartment validator. The patient app can compute progress from the same data the clinician sees.
What about quality measure reporting?
Standard quality measures (HEDIS, CMS) compute against FHIR resources directly. The reporting service can read the relevant resources through a research role with property filters appropriate to the measure.
How are program transitions handled?
A patient moving between programs (chronic care to active treatment, for example) gets a new CarePlan. The previous CarePlan moves to a completed status. The resource history captures the transition.
