Implement US Core Implantable Device profile to record and query implanted devices such as pacemakers, with UDI parsing and must-support field compliance
domain: hl7.org/fhir/us/core · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create a Device resource conforming to US Core Implantable Device; populate udiCarrier.deviceIdentifier with the device identifier portion of the FDA UDI string
Populate type with a SNOMED CT code representing the device type and set patient to reference the patient — both are MustSupport
Parse the full UDI string to extract the lot number, manufacture date, and expiration date and populate the corresponding Device fields
Search for patient implants with GET /Device?patient={id}&type={snomed-code} and confirm results are filtered to the correct device type
Validate the resource against the US Core Implantable Device profile URL using $validate to confirm all MustSupport obligations are met
Known gotchas
The UDI deviceIdentifier is only the DI (Device Identifier) portion of the full UDI string; the full UDI including production identifiers must go in udiCarrier.carrierHRF, not deviceIdentifier
US Core Implantable Device excludes non-implanted devices (software, non-implantable equipment); using this profile for a blood pressure cuff is a conformance error
Device.status must be active for active implants; a removed or explanted device should have status set to inactive, not be deleted, to preserve longitudinal history
Give your agent this knowledge — and 6,400+ more routes
One MCP install gives any agent live access to the full route map across 2,100+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp