EvidenceGate Project OS

Integration

MarkdownUse # headings, - lists, and plain text. Every save creates a revision.

# Integration Blueprint for Hospital, TPA, and NHCX

## Integration principle
EvidenceGate is an overlay, not a system of record. Every connector maps partner identifiers to EvidenceGate case and evidence contracts without erasing source provenance.

## Pilot interfaces
### Portal upload
Authenticated operator creates a case, selects insurer and procedure context, uploads files, and receives the quality packet.

### Case API
Create case, attach document version, request processing, read run status, retrieve packet, submit human action, and request evidence.

### Events
case.created, document.accepted, extraction.completed, quality_gate.completed, packet.ready, review.updated, evidence.requested.

## Adapter roadmap
- Hospital information and revenue-cycle systems.
- TPA and insurer case platforms.
- Document-management systems.
- Secure email intake where API access is unavailable.
- NHCX exchange flows.

## NHCX and FHIR mapping
Use NHCX and FHIR-aligned resources where they improve interoperability. Keep EvidenceGate evidence IDs and source hashes as extensions or linked metadata so conversion never breaks the path back to the submitted page.

Candidate mappings include patient, coverage, claim or pre-authorization request, encounter, diagnosis or condition, procedure, document reference, practitioner, organization, and supporting information.

## Connector controls
- Signed requests and rotating credentials.
- Idempotency keys.
- Tenant and partner rate limits.
- Schema validation and quarantine.
- Retry with dead-letter handling.
- Reconciliation report for source and destination case counts.
- No silent field truncation.

## Out of scope for the pilot
EvidenceGate will not replace the hospital system, become an NHCX gateway, or write a final insurer disposition. The pilot proves evidence quality and review readiness through a portal and a narrow API.