Skip to content

CRD Vision Prescription (Da Vinci CRD 2.1.0)

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

Profileprofile-visionprescription
Implementation GuideDa Vinci CRD 2.1.0
Base resourceVisionPrescription
Canonical URLhttp://hl7.org/fhir/us/davinci-crd/StructureDefinition/profile-visionprescription
Must-support elements21
Constrained elements with bindings4
VisionPrescription.identifier0..*, must support
VisionPrescription.status1..1, must support, binding: required
VisionPrescription.created1..1, must support
VisionPrescription.patient1..1, must support
VisionPrescription.encounter0..1, must support
VisionPrescription.dateWritten1..1, must support
VisionPrescription.prescriber1..1, must support
VisionPrescription.lensSpecification1..*, must support
VisionPrescription.lensSpecification.product1..1, must support, binding: example
VisionPrescription.lensSpecification.eye1..1, must support, binding: required
VisionPrescription.lensSpecification.sphere0..1, must support
VisionPrescription.lensSpecification.cylinder0..1, must support
VisionPrescription.lensSpecification.axis0..1, must support
VisionPrescription.lensSpecification.prism0..*, must support
VisionPrescription.lensSpecification.prism.amount1..1, must support
VisionPrescription.lensSpecification.prism.base1..1, must support, binding: required
VisionPrescription.lensSpecification.add0..1, must support
VisionPrescription.lensSpecification.power0..1, must support
VisionPrescription.lensSpecification.backCurve0..1, must support
VisionPrescription.lensSpecification.diameter0..1, must support
VisionPrescription.lensSpecification.duration0..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.