Integration Fabric — Developer Overview
Public-facing documentation, indexed for search — partners find this page directly rather than being onboarded manually. Content mirrors the Ecosystem Blueprint's Integration Fabric (Section 1.4) exactly; this page must never describe a capability the architecture doesn't back.
What You're Integrating With
Ensure Health sits at the center of a hub-and-spoke model. You integrate once, against one of our standard adapters — not against a custom contract per partnership.
Ensure Health is the company and Integration Fabric. WellBee is the patient mobile app — the only brand a member ever sees or downloads (getwellbee.com). Partner integrations reach members through WellBee; you do not need to build your own consumer app.
Supported Protocols (Phase 1)
| Category | Protocol | Direction |
|---|---|---|
| Real-time benefit/price | NCPDP D.0 | Bidirectional |
| Coverage confirmation | X12 270/271 | Ensure Health → Payer (via clearinghouse) |
| Claims remittance | X12 835 | Payer/TPA → Ensure Health |
| Employer eligibility | EDI 834 / HRIS API | Employer → Ensure Health |
| Clinical context | HL7 v2, FHIR R4, SMART on FHIR | Bidirectional, where the source system supports it |
Not supported in Phase 1: claims submission (X12 837), write-capable prior authorization (X12 278). Read-and-recommend only — see Security & Compliance for why.
Getting Started
- Spec review — request the versioned transaction spec for your integration category (contact partnerships@ensure.health)
- Sandbox credentials — issued after a signed BAA and integration agreement
- Sandbox testing — includes deliberately malformed and slow transactions, so your fallback behavior is proven before go-live
- Go-live — every transaction tagged with a shared correlation ID your team and ours can both see