DiagnosticReport resource (FHIR R4)

DiagnosticReport is a FHIR R4 resource. The Pidgeon engine generates synthetic DiagnosticReport instances and validates them against the R4 structure definitions.

Example

{
  "resourceType": "DiagnosticReport",
  "id": "diagnosticreport-9456fce1f076ea43b25a94096f61b7eb",
  "status": "final",
  "category": [
    {
      "coding": [
        {
          "system": "http://terminology.hl7.org/CodeSystem/v2-0074",
          "code": "LAB",
          "display": "Laboratory"
        }
      ]
    }
  ],
  "code": {
    "coding": [
      {
        "system": "http://loinc.org",
        "code": "omitted",
        "display": "LOINC code omitted from this published example"
      }
    ],
    "text": "Urinalysis complete"
  },
  "subject": {
    "reference": "Patient/patient-L46A6EIB9J"
  },
  "effectiveDateTime": "2026-06-29T09:00:00Z",
  "issued": "2026-07-01T12:00:00Z",
  "conclusion": "All values within normal limits."
}

Generated by the Pidgeon engine: pidgeon generate DiagnosticReport --seed 20260722. Codes from licensed terminologies (LOINC, SNOMED CT, CPT, RxNorm) are omitted from published examples.

Validation context

• strict pidgeon validate grades a DiagnosticReport instance against the base R4 structure definition: missing required elements raise REQUIRED_FIELD_MISSING and cardinality violations raise CARDINALITY_MIN or CARDINALITY_MAX.(REQUIRED_FIELD_MISSING)
• strict Profile validation grades the same instance against an installed IG profile: profile cardinality findings carry FHIR-PROFILE-CARDINALITY and terminology binding findings carry FHIR-PROFILE-BINDING.(FHIR-PROFILE-CARDINALITY)