Pre-authorizations
and claims, handled.

For Nigerian hospitals.

No API.  No new software.  Staff approve.

Works without an API

Runs in your HMS, portals, WhatsApp and email.

The one-hour clock, visible

Every request timed to the NHIA one-hour rule.

Nothing sent unapproved

Staff approve every submission. All logged.

The problem

The code comes before the care.

Getting an HMO code still means phone calls, WhatsApp messages and portal logins.

Pre-auth by hand

Calls, WhatsApp, email and portal logins for every insured patient.

A clock nobody sees

The NHIA one-hour window, tracked by hand on paper.

Claims that come back

Rejected, queried or unpaid. Each fix is more manual work.

~40

HMOs in Nigeria, each with its own forms and portals.

No API

In most hospital software, and most HMO systems.

Sh31bn

Kenyan claims under review (SHA, 30 April 2026).

The platform

One desk for every HMO.

AI agents that work in the systems you already use. Nothing to replace.

Ready for your approval
Claim · Harbor Health#CLM-20418

Funmi Adeyemi · Outpatient visit

  • Authorization code attached
  • Itemised charges · 6 lines
  • Lab report scan · low confidence
Approve & submitEditSend back
Appeal draft · Meridian Care

Reason: missing investigation report

Pre-auth · Crestline HMO

Adaeze Okafor · Appendectomy

Approval queue

You review. Agents do the legwork.

Approve, edit or send back what each agent prepared.

How it works
Pre-authorizations · today
PatientHMOChannelClock
Adaeze OkaforCrestline HMOPortal48:20
Tunde BakareHarbor HealthWhatsApp17:05
Chiamaka EzeMeridian CareEmail06:44
Ibrahim MusaNorthgate HMOPortalCode received
Pre-authorization board

Every request on one clock.

HMO, channel and time left on the one-hour window.

How it works
New workflow · recording
REC 02:145 steps captured
  1. 01Open Crestline HMO provider portal
  2. 02Search enrollee by ID
  3. 03Fill procedure and diagnosis
  4. 04Attach referral letter
  5. 05Submit and copy reference
Workflow recorder

Show it once. It runs from then on.

Record a task in the HMO’s portal. Review it. Let it run.

How it works

How it works

Record once. Venia learns it.

No integration project. If an HMO portal changes, the workflow stops and flags it.

Book a demo
provider.crestline-hmo.example · Pre-authorization
CRH-2231-0045
Abdominal ultrasound
referral_okafor.pdf
Submit request
Recording
  • Opened portal
  • Searched enrollee
  • Filled procedure
  • Attaching referral…

The agents

Five agents. One billing cycle.

Each one handles one administrative workflow. Start with one, add the next later.

01

Pre-authorization agent

Prepares each request in the HMO’s format and sends it through its channel.

  • Visible one-hour timer
  • Code attached to the visit
02

Claim preparation agent

Builds the claim file from documents, charges and authorization codes.

  • Checks for missing items
03

Submission agent

Submits each claim through the HMO’s portal or channel.

  • Logs what was sent, and when
04

Denial & appeal agent

Reads the rejection, classifies the reason and drafts the appeal.

  • Staff approve the resubmission
05

Reconciliation agent

Matches HMO payments against submitted claims.

  • Paid, short-paid, outstanding
Start with one

Most pilots start with pre-authorization.

Book a demo

1hr

NHIA window for an HMO to issue a code.

~40

HMOs in Nigeria, each with its own forms.

0

APIs needed, hospital side or HMO side.

5

Agents, from pre-auth to reconciliation.

The AI layer

Reads the paperwork. Drafts the appeal.

  • Document understanding

    Referral letters, lab results and scanned forms, even phone photos.

  • Code suggestions

    Each with a confidence score. Low scores go to a person.

  • Denial-reason classification

    Rejections sorted by reason, so patterns show across HMOs.

  • Appeal drafting

    A first draft from the claim file and the HMO’s stated reason.

Works where your team works

Nothing to integrate or replace.

Agents work in WhatsApp, email, Excel and HMO portals, just like your staff.

  • Sits on top of your hospital software
  • Uses each HMO’s own portal and channel
  • No API from the hospital or the HMO
Venia agents
Hospital softwareHMO portalsWhatsAppEmailExcelScanned formsPhone photos

Human control and audit trail

Your team signs off. Every time.

Venia prepares the work. Your staff decide what gets sent.

Book a demo

Approve before submit

Relax it per workflow and per HMO as trust grows.

Every action logged

Who did it, what was sent, what came back, and when.

Edge cases go to people

Low-confidence outputs are routed to a person.

Administrative only

Venia never decides if care is needed or covered.

Data and privacy

Designed with the NDPA in mind.

Health data is sensitive personal data under the NDPA. So it stays in the region.

In-region hosting

AWS Cape Town or Azure South Africa North.

Role-based access

Each person sees only what their role needs.

Full audit trail

Every action and approval, timestamped.

Who it’s for

For hospitals that run on HMOs.

Private hospitals and multi-site clinics in Nigeria first. Kenya is next.

For the

Head of billing

One queue for every HMO’s requests and claims.

For the

Revenue or finance lead

Paid, short-paid and outstanding, per HMO.

For the

Hospital administrator

A full record of what was sent, by whom, when.

FAQ

Questions hospitals ask.

Anything else, ask us on the call.

Book a demo
Do we need to replace our hospital software?

No. Venia works on top of the hospital software, HMO portals, WhatsApp, email and Excel you already use.

Do our HMOs need to give you API access?

No. Agents use the same portals, WhatsApp and email your staff use today. No API on either side.

Does Venia make clinical or coverage decisions?

No. Venia handles administrative workflows only. It never decides whether care is needed or covered.

Who approves what gets sent?

Your staff. At first every submission waits for approval. You can relax this per workflow and per HMO.

What if an HMO changes its portal or form?

The workflow stops and flags it instead of carrying on silently. Staff re-record the changed step.

Where is our data stored?

In the region: AWS Cape Town or Azure South Africa North, with role-based access and a full audit trail.

How does a pilot start?

We map your two or three busiest HMOs and your software, then pilot one workflow, usually pre-authorization.

How is Venia priced?

We walk through pricing on the demo call, once we understand your HMOs and volumes.

For developers

An API, when you want one.

Not needed to run Venia. Planned at api.veniahealth.app.

Placeholder. Endpoints and fields will change.

GET /v1/preauths/pa_8f2k
$ curl https://api.veniahealth.app/v1/preauths/pa_8f2k \
    -H "Authorization: Bearer $VENIA_KEY"

{
  "id": "pa_8f2k",
  "hmo": "Crestline HMO",
  "channel": "portal",
  "status": "code_received",
  "code": "CRH-PA-449120",
  "minutes_elapsed": 38,
  "approved_by": "billing.desk"
}

Book a demo

See it on your own HMOs.

A call built around your HMOs and how your billing desk works today.

Book a demo

Map your HMOs

Your two or three busiest HMOs, and your software.

Pick one workflow

Usually pre-authorization. It has a clock to measure.

Record, review, approve

Your team stays in control from day one.