5. Conformance scenarios
Validating single resources tells you whether your JSON is correct. Conformance scenarios go one step further: each scenario describes a real task your software performs — registering a patient, reporting a lab result, recording a vaccination — and checks that the resource your software produces for that task contains what NP Core and the Ministry expect.
The checklist#
Open Scenarios from the main menu. Scenarios are grouped (for example Foundation, Clinical, Laboratory) and ordered from simple to complex. Each one shows a status:
| Status | Meaning |
|---|---|
| Not started | Nothing submitted yet |
| Passed | Your latest submission passed every check |
| Failed | Your latest submission failed at least one check |
Only your latest submission per scenario counts for the conformance report.
Current scenarios#
| Group | Scenario | Resource | Target profile |
|---|---|---|---|
| Bundles | Transaction Bundle: patient, encounter and vitals | Bundle (or Bundle) | http://hl7.org/fhir/StructureDefinition/Bundle |
| Dates | Dates: Gregorian value with Bikram Sambat original | Patient | NP Core Patient |
| Documents | Clinical document (DocumentReference) | DocumentReference | NP Core Clinical Document Reference |
| Encounter & Clinical | Record an OPD encounter | Encounter | NP Core Encounter |
| Encounter & Clinical | Diagnosis coded in ICD-11 | Condition | NP Core Condition |
| Encounter & Clinical | Record an allergy | AllergyIntolerance | NP Core Allergy Intolerance |
| Encounter & Clinical | Record a procedure | Procedure | NP Core Procedure |
| Encounter & Clinical | Record an immunization (EPI) | Immunization | NP Core Immunization |
| Foundation | Register a patient | Patient | NP Core Patient |
| Foundation | Patient with coded Nepali address | Patient | NP Core Patient |
| Foundation | Record caste / ethnicity | Patient | NP Core Patient |
| Foundation | Register a practitioner | Practitioner | NP Core Practitioner |
| Foundation | Practitioner role at a facility | PractitionerRole | NP Core PractitionerRole |
| Foundation | Register a health facility | Organization | NP Core Health Facility |
| Foundation | Service location | Location | NP Core Location |
| Foundation | Healthcare service | HealthcareService | NP Core HealthcareService |
| Foundation | Related person / guardian | RelatedPerson | NP Core RelatedPerson |
| Identifiers | Identifier: Nepal National ID | Patient | NP Core Patient |
| Identifiers | Identifiers: Health ID and national documents | Patient | NP Core Patient |
| Identifiers | Identifier: NHFR facility code | Organization | NP Core Health Facility |
| Identifiers | Identifier: NHWR health-worker code | Practitioner | NP Core Practitioner |
| Identifiers | Identifier: professional council registration | Practitioner | NP Core Practitioner |
| Laboratory | Laboratory specimen | Specimen | NP Core Specimen |
| Laboratory | Laboratory result | Observation | NP Core Laboratory Result Observation |
| Laboratory | Laboratory panel | Observation | NP Core Laboratory Panel Observation |
| Laboratory | Laboratory report | DiagnosticReport | NP Core Laboratory Report |
| Medications | Medication definition | Medication | NP Core Medication |
| Medications | Prescription (MedicationRequest) | MedicationRequest | NP Core MedicationRequest |
| Medications | Pharmacy dispense | MedicationDispense | NP Core MedicationDispense |
| Radiology | Radiology report | DiagnosticReport | NP Core Radiology Report |
| Referral | Refer a patient to another facility | ServiceRequest | NP Core Referral Request |
| Vitals | Blood pressure | Observation | NP Core Blood Pressure Observation |
| Vitals | Heart rate | Observation | NP Core Heart Rate Observation |
| Vitals | Body weight | Observation | NP Core Body Weight Observation |
| Vitals | Body temperature | Observation | NP Core Body Temperature Observation |
| Vitals | Vital signs panel | Observation | NP Core Vital Signs Panel |
Anatomy of a scenario#
The scenario page shows:
- Description — the clinical or administrative task.
- Target profile — the NP Core profile the resource must conform to (with a link to the IG page).
- Checks — the list of things that will be tested. There are two kinds:
- Profile validation — the resource is validated against the target profile; there must be no errors.
- Content checks — additional rules written in FHIRPath, for example "the Patient has a Health ID", or "the lab result has a LOINC code". Each has its own explanation and fix hint.
- Hint and sample — guidance and, where available, an official example to start from.
Submitting#
- Make your software produce the resource for the task (use test data).
- Paste it into the scenario's editor, or upload the file.
- Press Submit. The result lists every check with pass/fail, the validation issues, and explanations.
Some scenarios accept a Bundle (for example a lab report together with its observations and patient); the scenario page says so.
You can also submit from code: POST /api/scenarios/{id}/submit with an API key. See
Machine testing via the API.
Produce, don't hand-edit
It is tempting to fix the JSON by hand until the scenario passes. That proves nothing about your software. Fix the export code, regenerate the resource, and submit what your software actually produces.
The conformance report#
When your company is approved, Conformance report summarises:
- the percentage of scenarios passed, per group and overall,
- the date and time of each latest submission,
- the NP Core version tested against.
Print it or save it as PDF from the browser. Every report carries the notice "Sandbox result — not an official certification": MoHFS may use it as evidence during formal assessments, but it is not itself a certificate.