Neutrino
AccessHub · App

Intake AI

The front door of the hub.

Multi-channel intake that turns fax, portal, email, API, and EHR referrals into clean, structured cases — automatically.

Intake teamsHub operations
Problem

Why Patient Access teams need this

The realities we hear from operators — the ones that don't show up in product demos.

×
Every channel is different

Faxes, portals, EHR referrals, and emails arrive in every shape imaginable.

×
Agents do the typing

Most intake time is spent re-keying fields the system could have read.

×
Duplicates slip through

Patients and cases get created twice — triaged by different agents.

×
No confidence on extraction

If extraction fails silently, errors propagate downstream.

What this solves

Outcomes, not algorithms

We lead with the business outcome — the mechanism sits behind a stable interface.

Auto-extraction with confidence

OCR + LLM extract fields with explicit confidence scores.

Duplicate detection

Patient and case dedup catches repeats at ingestion.

Smart HITL queues

Only low-confidence items reach humans — with context attached.

Canonical case model

Every downstream app inherits a clean, consistent case.

How it works

A controlled view of the flow

We share the stages — not the internal logic, models, or scoring methods.

1Stage
Capture
Fax, portal, email, API, and EHR channels unified.
2Stage
Classify
Document type, program, and routing determined.
3Stage
Extract
Fields read with per-field confidence scores.
4Stage
Reconcile
Duplicate detection and canonical case creation.
High-level stages shown — internal logic, models, and scoring methods are intentionally abstracted.
Ecosystem fit

Where this sits in Patient Access

This capability isn't a silo — it plays with every actor across the journey.

Hub
Feeds all downstream AccessHub apps with clean cases.
Providers
Accepts fax and portal submissions without form changes.
EHRs
Consumes FHIR referral and order messages.
Value delivered

Measured against the metrics that matter

We publish outcome ranges, not point claims — every number is validated in-context.

Intake time
From case receipt to structured record — minutes, not hours.
Error rate
Lower downstream rework from clean intake data.
Agent capacity
Intake teams handle more volume with the same headcount.
Deployment

Fits the way you work

Embed inside your platform, run alongside it, or consume through API — your call.

Embedded
Surfaced directly inside your existing UX.
Sidecar
Runs alongside your platform without disrupting it.
API
Consume capabilities programmatically.
Ready when you are

See Intake AI in your environment.

A focused walkthrough against scenarios that mirror your hub or SP — no theoretical decks.