NP Core Laboratory Report

Sets minimum expectations for representing a laboratory diagnostic report in Nepal.

Canonical URL: http://fhir.digitalhealth.gov.np/core/StructureDefinition/np-core-lab-report
Resource / type: DiagnosticReport
Based on: http://hl7.org/fhir/StructureDefinition/DiagnosticReport
Claim conformance: Put the canonical URL in meta.profile of each instance.

Required elements

“Always” means the element must be present in every instance. Otherwise it is required only when its parent element is present.

Element	Card.	When
`DiagnosticReport.status` registered \| partial \| preliminary \| final +	1..1	Always
`DiagnosticReport.category` Service category	1..*	Always
`DiagnosticReport.category:lab` Service category	1..1	Always
`DiagnosticReport.code` Name/Code for this diagnostic report	1..1	Always
`DiagnosticReport.subject` The subject of the report - usually, but not always, the patient	1..1	Always
`DiagnosticReport.encounter` Health care event when test ordered	1..1	Always
`DiagnosticReport.issued` DateTime this version was made	1..1	Always
`DiagnosticReport.performer` Responsible Diagnostic Service	1..*	Always
`DiagnosticReport.result` Observations	1..*	Always
`DiagnosticReport.media.link` Reference to the image source	1..1	If parent present

Must-support elements

If your system has this data it SHALL send it, and receivers SHALL process it. Must-support does not by itself make an element mandatory.

DiagnosticReport.status
DiagnosticReport.category
DiagnosticReport.category:lab
DiagnosticReport.code
DiagnosticReport.subject
DiagnosticReport.encounter
DiagnosticReport.issued
DiagnosticReport.performer
DiagnosticReport.specimen
DiagnosticReport.result
DiagnosticReport.conclusion

Fixed and pattern values

Element	Value
`DiagnosticReport.category:lab`	{ "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/v2-0074", "code": "LAB", "display": "Laboratory" } ] }

Terminology bindings

required: codes SHALL come from the value set · extensible: use the value set if a suitable code exists · preferred / example: guidance only.

Element	Strength	Value set
`DiagnosticReport.language`	preferred	http://hl7.org/fhir/ValueSet/languages
`DiagnosticReport.status`	required	http://hl7.org/fhir/ValueSet/diagnostic-report-status
`DiagnosticReport.category`	example	http://hl7.org/fhir/ValueSet/diagnostic-service-sections
`DiagnosticReport.category:lab`	example	http://hl7.org/fhir/ValueSet/diagnostic-service-sections
`DiagnosticReport.code`	extensible	http://hl7.org/fhir/ValueSet/report-codes
`DiagnosticReport.conclusionCode`	example	http://hl7.org/fhir/ValueSet/clinical-findings

Official examples

DiagnosticReport/ExampleNPCoreLabReport

View in IG ↗

{
  "resourceType": "DiagnosticReport",
  "id": "ExampleNPCoreLabReport",
  "meta": {
    "profile": [
      "http://fhir.digitalhealth.gov.np/core/StructureDefinition/np-core-lab-report"
    ]
  },
  "status": "final",
  "category": [
    {
      "coding": [
        {
          "system": "http://terminology.hl7.org/CodeSystem/v2-0074",
          "code": "LAB",
          "display": "Laboratory"
        }
      ]
    }
  ],
  "code": {
    "coding": [
      {
        "system": "http://loinc.org",
        "code": "11502-2",
        "display": "Laboratory report"
      }
    ]
  },
  "subject": {
    "reference": "Patient/ExampleNPCorePatient"
  },
  "encounter": {
    "reference": "Encounter/ExampleNPCoreEncounter"
  },
  "issued": "2026-05-10T13:00:00+05:45",
  "performer": [
    {
      "reference": "Organization/ExampleNPCoreOrganization"
    }
  ],
  "result": [
    {
      "reference": "Observation/ExampleNPCoreLabPanelObservation"
    }
  ],
  "conclusion": "Renal function within normal limits."
}

Narrative (text) removed for readability.