9. Troubleshooting & FAQ

See also the Error guide, which explains individual validator messages by category.

Validation problems#

"minimum required = 1, but only found 0" on an identifier slice#

The profile expects a specific identifier (e.g. identifier:healthId) and could not find one. Almost always the system is wrong — a typo, https instead of http, or a trailing slash. Copy the exact system from Nepal-specific rules. Also check the type coding.

"This element does not match any known slice"#

Usually information only: an identifier or extension that the profile does not define. Extra identifiers (e.g. your hospital MRN) are allowed. If you meant it to be an NP Core identifier, fix its system/type.

"Unknown extension" or "extension … is not allowed here"#

Check the extension URL character by character and make sure the extension is used in the right place: the address extensions on Address, caste/ethnicity on Patient, Bikram Sambat on date/dateTime elements (inside _birthDate, not birthDate).

"The value provided is not in the value set" / "Unknown code"#

The code is not allowed by the bound value set. Check the binding in the Profiles browser. If the binding is required, you must map your local code to an allowed one. For extensible bindings you may use another code only if no suitable code exists in the value set.

Warnings about SNOMED CT, LOINC or ICD-11 codes that "could not be validated"#

The sandbox may not hold a full copy of large external terminologies. The warning means the code was not verified, not that it is wrong. Double-check codes with the official browsers.

"Wrong display"#

The display does not match the code system. Copy the official display or omit display.

My dates are valid but a scenario fails on dates#

You may be sending Bikram Sambat dates as Gregorian (e.g. 2081-01-15). Convert to AD; see Bikram Sambat dates.

"Unrecognised property" / "Element must have some content"#

FHIR is case-sensitive and does not allow empty values. "Gender" is not "gender"; "telecom": [], "" and null are not allowed — omit the element instead. Configure your JSON serializer to skip nulls and empty lists.

The validator used the wrong profile#

With Auto-detect the first NP Core profile in meta.profile is used, otherwise the general NP Core profile for the resource type. Choose the profile explicitly in the picker, or set meta.profile correctly — e.g. lab results should claim NP Core Laboratory Result Observation.

XML resources#

XML is accepted. Remember that in XML element order matters and the namespace must be http://hl7.org/fhir. Most teams find JSON easier.

Account & API problems#

401 Unauthorized#

The Authorization: Bearer npfs_… header is missing, the key is mistyped, or it was revoked. Create a new key on the API keys page.

403 Forbidden#

Your company is not (or no longer) approved, so API keys and the FHIR endpoint are unavailable. See the status banner on your dashboard.

429 Too Many Requests#

You exceeded the rate limit. Wait and retry with exponential back-off (see the CI script in CI integration). Pending companies have lower limits.

413 Payload Too Large#

The request body is too big. Split large Bundles into smaller ones.

Validation is slow or times out#

The first validation after a restart can take longer while the validator warms up. Use a client timeout of at least 60 seconds. Very large Bundles take longer — split them.

I did not receive the reset / invitation email#

Check spam folders. Ask a colleague who is an owner to re-invite you, or contact the sandbox team (see Getting help).

General questions#

Is a passing result a certification?#

No. Sandbox results are for self-assessment. The conformance report says "Sandbox result — not an official certification". MoHFS may use it as input to formal processes.

Can other companies see my test data?#

No. Each approved company has its own private FHIR test server, and runs are visible only to your company and to MoHFS reviewers.

Can I use real patient data?#

No. Use synthetic data only. Submitting real personal health information can lead to suspension.

Which FHIR version?#

FHIR R4 (4.0.1), NP Core 1.0.0.

Where is the official specification?#

https://hiecore.mohp.gov.np/ig/en/ — the IG is the authority. If the sandbox and the IG disagree, tell us (see Getting help).