Overview and Practical Implementation Guidelines
Executive Overview of National NPHIES Integration
The NPHIES implementation guide describes electronic claims-information exchanges between healthcare providers and insurers, including eligibility checks, prior authorizations, claims and responses. The guide’s technical exchanges use HL7 FHIR R4.0.1. The linked public guide identifies itself as a local development build and is not a definitive source for production fields or response times. Confirm the guide, profiles and onboarding requirements currently applicable to the facility’s role through the official system-vendor qualification pathway before implementation.
An integration designed against the current guide can help keep exchanged data consistent, but it cannot guarantee that every claim will be accepted or prevent revenue loss. Review the implementation guide and the Council of Health Insurance vendor-certification reference, and confirm the supplier’s current certification status and scope directly with CHI when selecting a system.
NPHIES Integration Review Points
- FHIR exchange: The published NPHIES guide specifies HL7 FHIR R4.0.1 for the exchange workflows it covers. Check the profiles and fields in the public guide alongside the applicable current onboarding requirements for each transaction type instead of assuming one format applies to every data item.
- Eligibility checking: The eligibility workflow uses a real-time exchange to check coverage status and the information returned in the response. Review errors and returned benefits; this response is not prior authorization for every service. See the official eligibility workflow.
- Prior-authorization tracking: A response may arrive in the same session when automatic adjudication is possible, or the request may enter a queue for manual review with partial results and a later final response. Responses can contain approval, denial, requests for information or errors; receipt is not approval. See the official authorization workflow.
- Transport security and certificates: The guide describes mutually authenticated HTTPS exchanges using nphies-issued X.509 certificates, renewal or replacement at expiry, and protection of certificates and patient information. Confirm the applicable certificate and security requirements; see message transport and security.
FHIR Resources in Example Workflows
The table gives examples of resources and data to verify in each transaction’s applicable current profile, not a universal field list or service-level agreement. Check the claims guidance and current onboarding requirements. A receipt acknowledgment confirms message receipt and may precede payer adjudication; it does not establish approval or payment.
| FHIR Resource | Clinical and Financial Function | Example Data to Verify in the Applicable Profile | Exchange and Response Tracking |
|---|---|---|---|
| CoverageEligibilityRequest | Check coverage status and benefits returned in the eligibility response. | Patient, coverage and provider identifiers according to the applicable profile. | Real-time exchange; an unavailable payer or invalid request can return an error. |
| Claim (Prior-Authorization) | Request payer authorization for services that require prior authorization. | Diagnosis and service codes from current applicable code sets, and supporting clinical information when required. | Same-session response or queued manual review, with partial or final results later. |
| Claim (Billing / Submission) | Submit a claim for delivered services for assessment under the insurance policy. | Service and invoice details, prices and tax where applicable; prior-authorization references when applicable. | Single or batch submission; receipt acknowledgment may precede payer adjudication. |
| ClaimResponse | Response containing processing status, payer adjudication details or errors where present. | Processing status, adjudication details, amounts, and rejection reasons or errors as provided in the response. | Same-session or later response; review processing status and decision details. |
| CommunicationRequest | Information inquiry initiated by payer requesting supplementary diagnostic evidence. | Transaction reference and requested information or attachments according to the request and applicable profile. | Follow the information request and response workflow; track outstanding requests. |
2. Integration Checks and Response Handling
Test data checks and response tracking in the proposed integration to support detection and reduction of avoidable billing errors. Claim acceptance depends on case information, policy coverage and the payer’s decision:
- Pre-submission checks: Validate required data and applicable code-set rules, and flag discrepancies for review before submission.
- Response handling: Separate technical errors and pending requests from payer denials, and route corrections, additional information or resubmissions to the responsible team under the applicable workflow.
- Supporting information: Submit clinical attachments when the claim or authorization workflow requires them, using file formats and limits in the applicable current implementation guidance.
- Transaction records: Maintain appropriate, secure request and response records according to facility policies and applicable data-protection and retention requirements.
Checking Applicable Clinical and Service Code Sets
Service codes and clinical claim data should match the code sets and validation rules applicable to the transaction. Incomplete or inconsistent information can lead to a rejection or a request for supporting information; a single rejection rate does not apply to all claims. Check the official claims guidance and applicable current validation rules.
3. Reviewing a Proposed Moon LIS and Moon HIS Integration
GNSCO can discuss whether Moon LIS and Moon HIS fit an organisation’s integration requirements. The following points should be checked in the proposal and technical demonstration; they do not establish that a particular product implements them. Before contracting, verify technical compatibility and the supplier’s current certification status and scope directly with the Council of Health Insurance.
- Reception eligibility workflow: Request a demonstration of query submission and display of responses, benefits and errors to the responsible team, and verify that the proposed system supports this workflow.
- Prior-authorization workflow: When discussing Moon LIS, test request preparation, review and submission where authorization is required, then track queued, partial and final responses under payer rules. Do not assume approval will arrive before sample collection.
- Billing reconciliation: Test matching of service details, invoice identifiers and payer responses. Assess applicable tax and electronic-invoicing requirements separately within the project scope.
Need to apply this to your facility?
Share the activity, city and current stage, and we can help define an appropriate work scope.
Explore healthcare IT solutions