US Core DiagnosticReport Profile for Report and Note Exchange (US Core 6.1.0)
US Core DiagnosticReport Profile for Report and Note Exchange is a US Core 6.1.0 profile on the FHIR R4 DiagnosticReport resource. It marks 12 elements as must-support; the rows below list each constrained element's cardinality and binding strength.
| Profile | us-core-diagnosticreport-note |
|---|---|
| Implementation Guide | US Core 6.1.0 |
| Base resource | DiagnosticReport |
| Canonical URL | http://hl7.org/fhir/us/core/StructureDefinition/us-core-diagnosticreport-note |
| Must-support elements | 12 |
| Constrained elements with bindings | 3 |
| DiagnosticReport.status | 1..1, must support, binding: required |
| DiagnosticReport.category | 1..* (base 0..*), must support, binding: example |
| DiagnosticReport.code | 1..1, must support, binding: extensible |
| DiagnosticReport.subject | 1..1 (base 0..1), must support |
| DiagnosticReport.encounter | 0..1, must support |
| DiagnosticReport.effective[x] | 0..1, must support |
| DiagnosticReport.issued | 0..1, must support |
| DiagnosticReport.performer | 0..*, must support |
| DiagnosticReport.result | 0..*, must support |
| DiagnosticReport.media | 0..*, must support |
| DiagnosticReport.media.link | 1..1, must support |
| DiagnosticReport.presentedForm | 0..*, must support |
Example
pidgeon data install fhir-us-core-6.0
pidgeon conform --endpoint https://your-fhir-base/fhir --ig us-core-6.0 --ciThe conform run walks the live endpoint and grades sampled resources against the installed US Core 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-us-core-6.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 us-core-6.0 --ciWire it into your AI agent:
claude mcp add pidgeon -- npx -y @pidgeonhealth/mcpDownload Post free to browse this reference with generation attached.