CRD Device Request (Da Vinci CRD 2.1.0)
CRD Device Request is a Da Vinci CRD 2.1.0 profile on the FHIR R4 DeviceRequest resource. It marks 12 elements as must-support; the rows below list each constrained element's cardinality and binding strength.
| Profile | profile-devicerequest |
|---|---|
| Implementation Guide | Da Vinci CRD 2.1.0 |
| Base resource | DeviceRequest |
| Canonical URL | http://hl7.org/fhir/us/davinci-crd/StructureDefinition/profile-devicerequest |
| Must-support elements | 12 |
| Constrained elements with bindings | 4 |
| DeviceRequest.identifier | 0..*, must support |
| DeviceRequest.basedOn | 0..*, must support |
| DeviceRequest.status | 1..1 (base 0..1), must support, binding: required |
| DeviceRequest.intent | 1..1, binding: required |
| DeviceRequest.code[x] | 1..1, must support, binding: extensible |
| DeviceRequest.parameter | 0..*, must support |
| DeviceRequest.subject | 1..1, must support |
| DeviceRequest.occurrence[x] | 0..1, must support |
| DeviceRequest.authoredOn | 1..1 (base 0..1), must support |
| DeviceRequest.requester | 1..1 (base 0..1), must support |
| DeviceRequest.performer | 0..1, must support |
| DeviceRequest.reasonCode | 0..*, must support, binding: example |
| DeviceRequest.reasonReference | 0..*, must support |
Example
pidgeon data install fhir-davinci-crd-2.1
pidgeon conform --endpoint https://your-fhir-base/fhir --ig davinci-crd-2.1 --ciThe conform run walks the live endpoint and grades sampled resources against the installed Da Vinci CRD profiles. A failed report exits non-zero; --ci also fails the run on must-support gaps (MUSTSUPPORT-*) and stub-profile fallbacks (CONFORM_STUB_PROFILE).
Validation context
- strict Profile validation grades an instance against this profile's snapshot: cardinality findings carry FHIR-PROFILE-CARDINALITY and terminology binding findings carry FHIR-PROFILE-BINDING.(FHIR-PROFILE-CARDINALITY)
- strict Under pidgeon conform --ci, a sampled resource missing one of this profile's must-support elements fails the run with a MUSTSUPPORT-<element> rule id.
- strict If the fhir-davinci-crd-2.1 package is not installed, validation falls back to an embedded subset stub and the report is flagged CONFORM_STUB_PROFILE; under --ci that warning fails the run.(CONFORM_STUB_PROFILE)
This answer, in your terminal
pidgeon conform --endpoint https://your-fhir-base/fhir --ig davinci-crd-2.1 --ciWire it into your AI agent:
claude mcp add pidgeon -- npx -y @pidgeonhealth/mcpDownload Post free to browse this reference with generation attached.