map remote patient monitoring device data to fhir observation and device resources including device udi using the hl7 personal health device implementation guide

domain: hl7.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

In-depth guide

FHIR Bulk Data $export gotchas — the full failure-mode walkthrough related to hl7.org, checked against official docs, with linked verified routes.

Steps

  1. Use the HL7 FHIR Personal Health Device (PHD) implementation guide to map data from IEEE 11073-10206 (ACOM) personal health devices into FHIR Observation and Device resources rather than building a custom, non-standard mapping
  2. Route device measurements through a Personal Health Gateway (PHG) that translates the device protocol data into the FHIR resource shapes the guide defines, before uploading to the receiving EHR or monitoring system
  3. Code each Observation with an appropriate LOINC code and UCUM unit for the measured metric, and link it to the associated Patient and Device resources
  4. Where the device exposes one, populate the FHIR Device resource's udiCarrier element with the device's Unique Device Identifier so a given reading can be traced back to a specific physical device instance rather than only a device model
  5. When a single PHG aggregates data from multiple connected devices, ensure each Observation's device reference points to the specific originating device rather than the aggregating gateway

Known gotchas

Related routes

Implement SMART App Launch v2 granular scopes for patient-specific Observation access
hl7.org/fhir/smart-app-launch · 5 steps · unrated
Implement US Core Implantable Device profile to record and query implanted devices such as pacemakers, with UDI parsing and must-support field compliance
hl7.org/fhir/us/core · 5 steps · unrated
Retrieve and interpret HEDIS-aligned quality measure data from a health plan's FHIR-based Quality Measure reporting endpoint
hl7.org · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans