NP Core Service Request

Sets minimum expectations for representing a clinical order or service request in Nepal. Intended as a base profile to be further specialised for specific request types such as referrals.

Open in IG ↗

Canonical URL: http://fhir.digitalhealth.gov.np/core/StructureDefinition/np-core-servicerequest
Resource / type: ServiceRequest
Based on: http://hl7.org/fhir/StructureDefinition/ServiceRequest
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
`ServiceRequest.status` draft \| active \| on-hold \| revoked \| completed \| entered-in-error \| unknown	1..1	Always
`ServiceRequest.intent` proposal \| plan \| directive \| order \| original-order \| reflex-order \| filler-order \| instance-order \| option	1..1	Always
`ServiceRequest.subject` Individual or Entity the service is ordered for	1..1	Always

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.

ServiceRequest.status
ServiceRequest.intent
ServiceRequest.category
ServiceRequest.subject
ServiceRequest.encounter
ServiceRequest.authoredOn
ServiceRequest.requester

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
`ServiceRequest.language`	preferred	http://hl7.org/fhir/ValueSet/languages
`ServiceRequest.status`	required	http://hl7.org/fhir/ValueSet/request-status
`ServiceRequest.intent`	required	http://hl7.org/fhir/ValueSet/request-intent
`ServiceRequest.category`	example	http://hl7.org/fhir/ValueSet/servicerequest-category
`ServiceRequest.priority`	required	http://hl7.org/fhir/ValueSet/request-priority
`ServiceRequest.code`	example	http://hl7.org/fhir/ValueSet/procedure-code
`ServiceRequest.orderDetail`	example	http://hl7.org/fhir/ValueSet/servicerequest-orderdetail
`ServiceRequest.asNeeded[x]`	example	http://hl7.org/fhir/ValueSet/medication-as-needed-reason
`ServiceRequest.performerType`	example	http://hl7.org/fhir/ValueSet/participant-role
`ServiceRequest.locationCode`	example	http://terminology.hl7.org/ValueSet/v3-ServiceDeliveryLocationRoleType
`ServiceRequest.reasonCode`	example	http://hl7.org/fhir/ValueSet/procedure-reason
`ServiceRequest.bodySite`	example	http://hl7.org/fhir/ValueSet/body-site

Official examples

ServiceRequest/ExampleNPCoreServiceRequest

View in IG ↗

{
  "resourceType": "ServiceRequest",
  "id": "ExampleNPCoreServiceRequest",
  "meta": {
    "profile": [
      "http://fhir.digitalhealth.gov.np/core/StructureDefinition/np-core-servicerequest"
    ]
  },
  "status": "active",
  "intent": "order",
  "category": [
    {
      "coding": [
        {
          "system": "http://snomed.info/sct",
          "code": "108252007",
          "display": "Laboratory procedure"
        }
      ]
    }
  ],
  "code": {
    "coding": [
      {
        "system": "http://loinc.org",
        "code": "24362-6",
        "display": "Renal function 2000 panel - Serum or Plasma"
      }
    ]
  },
  "subject": {
    "reference": "Patient/ExampleNPCorePatient"
  },
  "encounter": {
    "reference": "Encounter/ExampleNPCoreEncounter"
  },
  "authoredOn": "2026-05-10",
  "requester": {
    "reference": "Practitioner/ExampleNPCorePractitioner"
  }
}

Narrative (text) removed for readability.