Nigerian healthcare deserves infrastructure that reflects how it actually works.

Mission

Take the friction out of the Nigerian claims lifecycle — for everyone in it.

HMO claims teams spend their days chasing paper. Providers wait months to be paid for care already rendered. Enrollees can't get care they're entitled to because eligibility can't be verified in real time. Regulators can't see what's really happening in the system they oversee. All of that is fixable — but only if you model the domain properly, from day one.

Compliance

Built to the NHIA spec — not adapted for it after the fact.

Sonecare's data model encodes the rules the regulator writes: 1-hour preauth SLAs, 60-day settlement windows, HCFA 12-diagnosis claims, immutable tariff and benefit snapshots, and the 7 NHIA-aligned denial categories. Every mutation is logged. Every decision is versioned. If a claim gets appealed, the original snapshot is still there — nothing gets rewritten silently.

Security

Faction-aware data isolation, every audit path served natively.

A single platform serves HMOs, providers, employers, and regulators — but each faction only ever sees the slice of data it's entitled to. Providers see their own claims. Employers see their own workforce. HMOs see their own book of business. Regulators see their jurisdiction. The isolation is enforced at the query layer, not in the UI — so it can't be bypassed by a curious frontend.

Where we are

HMO features are production-ready. Provider features are shipping in stages.

The HMO side of the platform — enrollment, preauth, encounter verification, per-line adjudication, denial catalogues, and analytics — is production-ready. The provider/EHR side is shipping in stages: encounter creation, preauth codes, claim visibility, and medical history are live; claim submission, remittance viewing, appeals, and document management are on the near-term roadmap. We're being explicit about the split because pretending otherwise doesn't help anyone.