Device resource (FHIR R4)
Device is the FHIR R4 resource for a type of a manufactured item that is used in the provision of healthcare without being substantially changed through that activity.
| Resource | Device |
|---|---|
| FHIR version | R4 (4.0.1) |
| Canonical URL | http://hl7.org/fhir/StructureDefinition/Device |
| Required elements | none; every top-level element is optional (min 0) in base R4 |
| IG profiles in this catalog | 2 |
Example
{
"resourceType": "Device",
"id": "device-926e9bc385126a034489a8e757a5ec41",
"status": "active",
"manufacturer": "Acme Vitals",
"deviceName": [
{
"name": "Digital weight scale",
"type": "user-friendly-name"
}
],
"type": {
"text": "Digital weight scale"
},
"lotNumber": "LOT-34132",
"patient": {
"reference": "Patient/patient-L46A6EIB9J"
}
}Generated by the Pidgeon engine: pidgeon generate Device --seed 20260722.
Validation context
- strict pidgeon validate grades a Device instance against the base R4 structure definition: missing required elements raise REQUIRED_FIELD_MISSING and cardinality violations raise CARDINALITY_MIN or CARDINALITY_MAX.(REQUIRED_FIELD_MISSING)
- strict Profile validation grades the same instance against an installed IG profile: profile cardinality findings carry FHIR-PROFILE-CARDINALITY and terminology binding findings carry FHIR-PROFILE-BINDING.(FHIR-PROFILE-CARDINALITY)
This answer, in your terminal
pidgeon lookup DeviceWire it into your AI agent:
claude mcp add pidgeon -- npx -y @pidgeonhealth/mcpDownload Post free to browse this reference with generation attached.