DTR Log Questionnaire Errors Input Parameters (Da Vinci DTR 2.0.1)
DTR Log Questionnaire Errors Input Parameters is a Da Vinci DTR 2.0.1 profile on the FHIR R4 Parameters resource. It marks 1 elements as must-support; the rows below list each constrained element's cardinality and binding strength.
| Profile | dtr-log-errors-input-parameters |
|---|---|
| Implementation Guide | Da Vinci DTR 2.0.1 |
| Base resource | Parameters |
| Canonical URL | http://hl7.org/fhir/us/davinci-dtr/StructureDefinition/dtr-log-errors-input-parameters |
| Must-support elements | 1 |
| Constrained elements with bindings | 0 |
| Parameters.parameter | 1..* (base 0..*), must support |
| Parameters.parameter.name | 1..1 |
Example
pidgeon data install fhir-davinci-dtr-2.0
pidgeon conform --endpoint https://your-fhir-base/fhir --ig davinci-dtr-2.0 --ciThe conform run walks the live endpoint and grades sampled resources against the installed Da Vinci DTR 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-dtr-2.0 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-dtr-2.0 --ciWire it into your AI agent:
claude mcp add pidgeon -- npx -y @pidgeonhealth/mcpDownload Post free to browse this reference with generation attached.