MANSOQ Knowledge
← Knowledge library

IT & integrations

Validate NPHIES FHIR messages and terminology

Understand structural validation, business checks and code-version checks before delivery.

Current source · source reviewed · 8 min read

Before you begin

1. Build the correct message profile

Current builders emit FHIR R4 message Bundles with MessageHeader first, stable identifiers, explicit profiles and resolvable references. Choose institutional, professional, pharmacy, oral or vision context as configured.

2. Run structural validation

Load the complete pinned canonical catalog, including extensions and datatype constraints. Canonical URLs are case-sensitive; do not repair mismatches by lowercasing identifiers.

3. Run business and arithmetic checks

Validate totals, line calculations, supporting information, balances and other configured business rules separately. A structural pass alone is insufficient.

4. Check terminology independently

Verify the coding release for each domain and the service date. A structurally valid payload can still carry an obsolete or inappropriate code system version.

5. Retain findings safely

Keep issue code, path, stage and package reference. Use protected transaction storage for clinical payloads and publish only synthetic examples in public support material.

FHIR scope boundary

This audit establishes NPHIES-specific FHIR R4 messaging and a terminology client. It does not establish a general clinical FHIR REST server, SMART-on-FHIR app authorization or arbitrary resource CRUD support.

Wire amount detail

The validator identifies Claim.item.net as the FHIR R4 line amount and Claim.total as the header total. It rejects assumptions about a nonexistent Claim.item.total path.

Troubleshooting

The local validator passes but the remote system rejects

Review the server business rule, coding version and environment package. Use the returned issue reference to update the supported rule source rather than treating sample payloads as a conformance oracle.

Source evidence

References are pinned to the private MANSOQ source repository. Repository access is required to open these links.