NPHIES Workflows¶
Overview¶
This document describes the standard workflows for NPHIES transactions including eligibility verification, prior authorization, claim submission, and payment reconciliation.
Core Workflows¶
1. Eligibility Verification¶
Purpose: Confirm patient insurance coverage before service.
sequenceDiagram
participant P as Provider
participant N as NPHIES
participant I as Insurer
P->>N: Eligibility Request
N->>I: Forward Request
I->>N: Eligibility Response
N->>P: Coverage Details Steps:
- Request Generation
- Patient identifier
- Date of service
-
Service type (optional)
-
NPHIES Processing
- Route to correct payer
-
Validate request
-
Payer Response
- Coverage status
- Benefit details
-
Copay/deductible
-
Provider Action
- Confirm coverage
- Inform patient of costs
- Proceed with service
Request Example:
{
"resourceType": "CoverageEligibilityRequest",
"status": "active",
"purpose": ["benefits"],
"patient": {
"reference": "Patient/123"
},
"servicedDate": "2024-01-15",
"insurer": {
"reference": "Organization/bupa"
}
}
Response Interpretation:
| Status | Meaning | Action |
|---|---|---|
| active | Coverage valid | Proceed |
| cancelled | Coverage terminated | Patient pay |
| entered-in-error | Invalid request | Correct and retry |
2. Prior Authorization¶
Purpose: Obtain approval for services before delivery.
sequenceDiagram
participant P as Provider
participant N as NPHIES
participant I as Insurer
P->>N: Authorization Request
N->>I: Forward Request
I->>N: Auth Decision
N->>P: Approval/Denial
alt Approved
P->>P: Provide Service
else Denied
P->>I: Appeal
end Steps:
- Request Submission
- Clinical justification
- Proposed services
-
Supporting documentation
-
Payer Review
- Medical necessity
- Policy coverage
-
Network status
-
Decision
- Approved
- Denied (with reason)
-
Pended (need more info)
-
Provider Action
- If approved: Schedule service
- If denied: Appeal or inform patient
- If pended: Provide additional info
Authorization Types:
| Type | Timeline | Examples |
|---|---|---|
| Standard | 48-72 hours | Elective surgery |
| Urgent | 24 hours | Semi-urgent procedures |
| Emergency | Retrospective 72h | Life-threatening |
| Concurrent | During stay | Extended admission |
3. Claim Submission¶
Purpose: Submit billing claims for adjudication.
sequenceDiagram
participant P as Provider
participant N as NPHIES
participant I as Insurer
P->>N: Submit Claim
N->>N: Validate
N->>I: Forward Claim
I->>I: Adjudicate
I->>N: ClaimResponse
N->>P: Result
alt Accepted
I->>P: Payment
else Rejected
P->>P: Correct & Resubmit
end Steps:
- Claim Generation
- Patient demographics
- Encounter details
- Diagnoses (ICD-10)
- Procedures (CPT/ACHI)
-
Charges
-
Validation
- FHIR compliance
- Business rules
-
Code validation
-
Adjudication
- Benefit determination
- Medical policy review
-
Payment calculation
-
Response Processing
- Accept/reject handling
- Remittance posting
- Denial management
Claim Types:
| Type | Code | Use Case |
|---|---|---|
| Institutional | institutional | Hospital/facility |
| Professional | professional | Physician services |
| Pharmacy | pharmacy | Medication claims |
| Vision | vision | Eye care |
| Dental | dental | Dental services |
4. Claim Status Inquiry¶
Purpose: Check status of submitted claims.
sequenceDiagram
participant P as Provider
participant N as NPHIES
participant I as Insurer
P->>N: Status Request
N->>I: Query
I->>N: Status Response
N->>P: Current Status Status Values:
| Status | Description |
|---|---|
| queued | Received, pending |
| active | Under review |
| cancelled | Cancelled by provider |
| draft | Not yet submitted |
| entered-in-error | Invalid |
5. Payment Reconciliation¶
Purpose: Match payments to claims.
sequenceDiagram
participant I as Insurer
participant N as NPHIES
participant P as Provider
I->>N: Payment Notification
N->>P: ERA/835
P->>P: Post Payment
P->>P: Reconcile Steps:
- Payment Notice
- Payment amount
- Claim references
-
Adjustment reasons
-
ERA Processing
- Parse payment details
- Match to claims
-
Post to accounts
-
Reconciliation
- Verify amounts
- Identify discrepancies
- Follow up on issues
Advanced Workflows¶
Pre-Determination¶
Purpose: Estimate coverage before service.
graph LR
A[Request] --> B[Payer Review]
B --> C[Estimate]
C --> D[Patient Decision] Claim Resubmission¶
Purpose: Correct and resubmit rejected claims.
graph LR
A[Rejection] --> B[Analyze]
B --> C[Correct]
C --> D[Resubmit]
D --> E{Accepted?}
E -->|No| B
E -->|Yes| F[Done] Appeal Process¶
Purpose: Challenge denied claims.
graph TD
A[Denial] --> B[Review Reason]
B --> C{Appealable?}
C -->|Yes| D[Gather Evidence]
C -->|No| E[Accept/Write-off]
D --> F[Submit Appeal]
F --> G{Decision}
G -->|Upheld| H[Escalate/Accept]
G -->|Overturned| I[Payment] Error Handling¶
Common Errors¶
| Error | Cause | Resolution |
|---|---|---|
| VALIDATION_ERROR | Invalid FHIR | Fix structure |
| AUTH_EXPIRED | Token expired | Refresh token |
| TIMEOUT | Network issue | Retry |
| DUPLICATE | Already submitted | Check status |
Retry Strategy¶
- Immediate retry - Network errors
- Delayed retry - Rate limiting
- Manual review - Business errors
Integration Timeline¶
Standard Processing Times¶
| Transaction | Expected | Maximum |
|---|---|---|
| Eligibility | 3 seconds | 30 seconds |
| Prior Auth | 72 hours | 14 days |
| Claim Submit | 2 seconds | 60 seconds |
| Adjudication | 5 days | 30 days |
Related Documents¶
Last updated: January 2025