DeviceRequest resource (FHIR R4)

DeviceRequest is the FHIR R4 resource for represents a request for a patient to employ a medical device.

Resource	DeviceRequest
FHIR version	R4 (4.0.1)
Canonical URL	http://hl7.org/fhir/StructureDefinition/DeviceRequest
Required elements	intent (1..1), code[x] (1..1), subject (1..1)
IG profiles in this catalog	2

Example

{
  "resourceType": "DeviceRequest",
  "id": "devicerequest-2d59fb43acb268b84a9c19950de48b4f",
  "status": "active",
  "intent": "order",
  "priority": "routine",
  "codeCodeableConcept": {
    "text": "Continuous positive airway pressure (CPAP) unit"
  },
  "subject": {
    "reference": "Patient/patient-L46A6EIB9J"
  },
  "authoredOn": "2026-07-01T12:00:00Z",
  "requester": {
    "display": "Dr. Ordering Physician"
  },
  "reasonCode": [
    {
      "text": "Ongoing home monitoring of a chronic condition"
    }
  ]
}

Generated by the Pidgeon engine: pidgeon generate DeviceRequest --seed 20260722.

Validation context

strict pidgeon validate grades a DeviceRequest 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 DeviceRequest

Wire it into your AI agent:

claude mcp add pidgeon -- npx -y @pidgeonhealth/mcp

Download Post free to browse this reference with generation attached.