Skip to content

CRD Medication Request (Da Vinci CRD 2.1.0)

CRD Medication Request is a Da Vinci CRD 2.1.0 profile on the FHIR R4 MedicationRequest resource. It marks 23 elements as must-support; the rows below list each constrained element's cardinality and binding strength.

Profileprofile-medicationrequest
Implementation GuideDa Vinci CRD 2.1.0
Base resourceMedicationRequest
Canonical URLhttp://hl7.org/fhir/us/davinci-crd/StructureDefinition/profile-medicationrequest
Must-support elements23
Constrained elements with bindings7
MedicationRequest.identifier0..*, must support
MedicationRequest.status1..1, must support, binding: required
MedicationRequest.intent1..1, must support, binding: required
MedicationRequest.category0..*, must support, binding: example
MedicationRequest.reported[x]0..1, must support
MedicationRequest.medication[x]1..1, must support, binding: extensible
MedicationRequest.subject1..1, must support
MedicationRequest.encounter0..1, must support
MedicationRequest.authoredOn1..1 (base 0..1), must support
MedicationRequest.requester1..1 (base 0..1), must support
MedicationRequest.performer0..1, must support
MedicationRequest.reasonCode0..*, must support, binding: extensible
MedicationRequest.reasonReference0..*, must support
MedicationRequest.dosageInstruction0..*, must support
MedicationRequest.dosageInstruction.text0..1, must support
MedicationRequest.dosageInstruction.timing0..1, must support
MedicationRequest.dosageInstruction.doseAndRate0..*, must support
MedicationRequest.dosageInstruction.doseAndRate.dose[x]0..1, must support, binding: preferred
MedicationRequest.dispenseRequest0..1, must support
MedicationRequest.dispenseRequest.numberOfRepeatsAllowed0..1, must support
MedicationRequest.dispenseRequest.quantity0..1, must support
MedicationRequest.substitution0..1, must support
MedicationRequest.substitution.allowed[x]1..1, binding: example
MedicationRequest.priorPrescription0..1, must support

Example

pidgeon data install fhir-davinci-crd-2.1
pidgeon conform --endpoint https://your-fhir-base/fhir --ig davinci-crd-2.1 --ci

The 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 --ci

Wire it into your AI agent:

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

Download Post free to browse this reference with generation attached.

FHIR® R4 © Health Level Seven International. FHIR R4 specification content is used under its CC0 license; this page is a derivative work and is not endorsed by HL7 International.

HL7® and FHIR® are registered trademarks of Health Level Seven International.

Published by Pattern Engine LLC (Pidgeon Health).

Rendered from the same machine-readable definitions the Pidgeon engine validates against. Exported from the installed fhir-davinci-crd-2.1 package (2.1.0, CC0) through the Pidgeon engine's profile loader.