For developers

Remote patient monitoring with FHIR: blood pressure, heart rate and symptoms from the patient's own devices

How to build remote patient monitoring on a FHIR record without extra hardware: readings from the phone, the watch or a blood pressure monitor arrive as FHIR Observations under the patient's consent, your app gets a webhook, the clinic reads the series. What Anpheros provides and what stays yours.

by Published 3 min read

Remote patient monitoring usually means a kit: a device shipped to the patient, a vendor cloud, a dashboard, and an integration project to get the numbers into the record. Most of the readings a clinic wants in 2026 already exist on the patient's phone and watch. What is missing is a record they flow into, consent to read it, and a way to be told when something new arrives. That is what Anpheros Platform provides. The device, the thresholds and the clinical workflow stay yours.

Where the readings come from

Anpheros Daily, the patient app, writes vital signs as FHIR Observation resources with LOINC codes: blood pressure (85354-9 panel, with 8480-6 systolic and 8462-4 diastolic), heart rate (8867-4), body weight (29463-7), body temperature, glucose, SpO₂ (59408-5), steps (41950-7), sleep duration (93832-4), resting heart rate (40443-4) and HRV (80404-7). They arrive from:

  • the phone, typed by the person after a reading;
  • the watch or band, through Apple Health on iPhone and Health Connect on Android, as daily summaries and series;
  • a connected blood pressure monitor or scale that writes to those same health stores.

Every Observation carries its provenance (author_type device, patient or import, and the source), so a clinic can tell a watch reading from a typed one. Your own app can write Observations too, through /fhir/R4 or /v1, with the same codes.

How the clinic gets access

The person grants the clinic's application access through OAuth, with scopes (for example observations only, vital signs category) and a duration of 30, 90, 180 or 365 days. The grant appears in the person's "Connections"; they can revoke it at any time, and every read is logged. For a programme the clinic runs, the project can also create the patient itself and see what it created without a grant.

How your app learns something arrived

Register a webhook for resource.created and resource.updated. Deliveries are thin, ids and versions only, signed with HMAC-SHA256 and retried for up to 24 hours. Read the resource, apply your thresholds, alert your nurse. Events fire for writes by other projects into records you have access to, which is exactly the case of a patient app writing into a record a clinic monitors.

curl -X POST $BASE/v1/webhooks -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \
  -d '{"url": "https://your.app/anpheros/hook", "events": ["resource.created", "resource.updated"]}'

Reading the series

For a chart or a rule, GET /v1/patients/{id}/series?code=… returns a measurement over time; GET /v1/patients/{id}/timeline interleaves readings, symptoms and medications. Over FHIR:

GET /fhir/R4/Observation?patient={id}&code=http://loinc.org|85354-9&date=ge2026-09-01&_sort=-date

Symptoms sit next to the numbers: the person logs them as Observations coded in ICD-10 chapter R with intensity, so a rising blood pressure and a week of headaches are visible together.

What the platform does not do

It does not set thresholds, raise clinical alerts or decide who needs a call. Those are clinical decisions and belong in your product, under your clinical governance. The platform stores, labels and shares; the pattern engine can show what changed and what recurs, with evidence, but it does not diagnose.

Frequently asked questions

Do patients need a special device?

No. The phone, the watch they already own, or a consumer blood pressure monitor that syncs to Apple Health or Health Connect is enough. A dedicated device can still be used if it writes to those stores or if your app writes its readings to the record directly.

How often do readings arrive?

As often as the device and the person produce them. Watch summaries arrive daily; a typed blood pressure arrives when typed. Webhooks fire on each write.

Can the clinic write back, for example a target range?

Yes, as its own resources: a CarePlan or Goal in FHIR, or a note. It cannot alter what the patient or the device wrote; every writer owns its own resources.

Is this a certified medical device?

No. Anpheros Platform is a record and an API. If your monitoring product makes clinical decisions, the medical-device obligations are yours.

Where do I start?

The free sandbox has 30 synthetic patients with six months of vital signs. Register a webhook, read a series, and build your rules against real-looking data: developers.anpheros.com/guides/first-hour.

This guide is for information and does not replace medical advice. For decisions about your health, talk to your doctor. In an emergency, call 112.
About the author
Adrian Kereky

Founder of Anpheros. An electronics engineer, he spent six years in autonomous driving, on automotive projects run in partnership with Samsung and NVIDIA, designing the architecture of driver-assistance and AI systems that run on NVIDIA chips with CUDA. He then built Anpheros: the patient-controlled medical record and the HL7 FHIR R4 platform it runs on.

More about Anpheros and the author →

Keep your medical record with you

Anpheros Daily keeps symptoms, lab results, medications and documents in one place, in a standard format, under your control. The Basic plan is free.

Get Anpheros Daily