Skip to content

The AI-native infusion OS

The infusion OS built natively for both human and AI agents.

Clear the patient. Get the authorization. Book the chair. Restock the drug. Bill the claim. In nico each one is a task. Agents carry most of them and write down what they did and where they read it. People make the few calls that are theirs. Everyone works from the same record.

The nico shell in three panes. On the left, the task list grouped as Needs you, Agents working and Done today. In the middle, a Clearance thread in which the Intake agent has read a faxed transfer of care and asks, in an approval gate, whether to link it to a patient, with the keys A, E and N. On the right, the inspector showing the candidate patient, her coverage and her infusion series.

Nov 6 · 8:54 AM · A fax arrives. The Intake agent read four pages, found one likely chart, and asks one question before it files anything.

Everything is a task
The whole center is tasks, in six kinds and six states. No hundred screens to configure and staff.
Agents and people, together
Agents do the legwork: benefits, authorizations, scheduling, the visit record, claims, restocking. People decide what is theirs, in the same task.
Closes to the money
It runs through the claim and the remittance, because an infusion suite lives on what it gets paid.

How it works

Six kinds of task carry a patient from referral to remittance.

Four follow the patient, in order: clearance, scheduling, the visit, the claim. Two run alongside: replenishment and setup. Each has an agent that signs its work and a gate where a person decides. Infusion is a series, so before every dose the agents re-verify, re-authorize and re-book on their own.

CLR-214Clear Josefina Alvarez for infliximab 5 mg/kg, visit Nov 18

The Clearance thread, ready to send. A result card lists the packet: the request in units and visits, the site, the copies, the provider's signed letter tagged verified · signature, the channel and the route. Below it an approval gate titled Before I send this to the payer summarizes the prior authorization request and its packet and offers Approve and send with the key A, Edit packet with E and Decline with N.

Nov 7 · 9:38 AM · Ready to send

The agent
Reads the referral, verifies benefits, estimates the cost and finds assistance. Builds the authorization packet from the payer's checklist, then tracks the payer's clock once it is sent.
You
The coordinator approves the packet and the estimate. If the payer denies, the provider decides between an appeal and a change of site, in the same gate.

Seven tasks, one dose, paid in full.

By the end of the walkthrough every task is Done. There are seven, not six, because the denied claim became a second claim task of its own. Agents did the reading, checking, drafting, sending and posting, and wrote each action down with its source. People made the eight calls that were theirs, each in under a minute.

The closing page of the walkthrough. The headline reads Every unit of work is an issue, and agents resolve them with you. Three counters show 42 agent actions each with a source line, 8 decisions people made, and 9 entries in people's own words. A card lists the seven tasks of the story, from the Clearance to the Setup, each marked Done, above a card titled What it stands on with three statements: FHIR underneath, Security by construction, and State of the art AI, kept honest.

Walkthrough

See how nico works, from referral to remittance.

One patient, one infusion series, twenty-four scenes. A fax arrives on Nov 6 and the remittance posts on Dec 17. In between, agents clear her, get the authorization, book the chair, restock the drug, run the visit and bill the claim. People decide eight things. Everything else is in the thread, signed.

The first four scenes are open. Leave an email for the other twenty. The shell behaves like the real one: everything a button does, a key does too.

→←
next and previous scene
jk
move through the task list, Enter opens
⌘K
the command palette, anywhere
AEN
answer the open gate
t
switch theme

A scripted story. The practice, the people, the patient, the identifiers and the amounts are invented.

The cover of the walkthrough. The nico wordmark above the line See how nico works, from referral to remittance; a summary of the story that begins One patient, one infusion series, every issue agents resolved with you; the six issue states as badges; the three provenance tags; a Start with the fax button; and three cards: the people with their roles, What it stands on with its three statements, and the keyboard keys.

How it works · Supervision and audit

You supervise. The record keeps itself.

Screens in nico are for supervising agents, catching exceptions and correcting them. Not for typing data in. The thread is the record, and it is what clinical and billing work has to be able to show.

Triage in two panes. The task list is ordered under Needs you: an overdue claim denied for no authorization on file, today's clearance question, then two dashed grouped rows for an EMR connection that has been failing since the evening before and for two unrouted inbound messages, with a notice at the top of the list. In the thread, the Claims agent has posted the remittance, tagged verified · 835, and an approval gate proposes a reconsideration with the authorization attached, offering Send A, Edit E and the write-off as N.

Nov 13 · 8:30 AM · Triage. An overdue claim first, then today's question, then two queues that are not tasks. A answers the gate and moves to the next row.

  • Triage is the day.

    Needs you is ordered by who is waiting, then what is due, then what is at stake. j and k move. Enter opens. A answers the gate and moves to the next row. Queues that are not tasks, like unrouted faxes or a connection outage, get one grouped row each.

  • One place for decisions.

    Anything consequential stops at a gate: an identity, a cost, a packet, a signature, a reconsideration, a route. The gate shows its basis, recommends an answer, and takes A, E or N. The decision is logged with who, in what role, and when.

  • Every entry is signed.

    Agents sign as themselves. People write in their own words, unedited. Corrections get appended. Nothing is edited in place. The thread is the audit trail, and a payer could read it.

  • Provenance on every fact.

    A fact from a rail is verified. A fact read out of a document or the chart is extracted. A fact the agent worked out is inferred until a person confirms it. Every tag says its word, never only a color. Done is quiet.

    verified · 271extracted · EMRinferred

  • Standing approvals, scoped.

    The one sanctioned way around a gate: a standing approval scoped to a payer, capped, and expiring. Every action under it is logged with its number. A clean claim to a known payer goes out on its own. A denial comes back to a person.

  • Writeback you can read back.

    A note sent to the EMR is inferred until the agent reads the chart back. Then it is verified. The visit closes only then, so a document drop that silently failed never looks like a filed note.

The Claim thread after the remittance. The tail of the posted 835 shows the payer's remark, claim information inconsistent with authorization, and the trace number. An approval gate titled Before I appeal the payer's denial proposes a reconsideration for the claim, denied CO-197 against an authorization the agent had verified, lists the basis, and offers Send the reconsideration with the key A, Edit with E and Hold for a call with N.

Dec 3 · 5:42 AM · A denial is a fact with a source. The agent wrote nothing off and drafted the reconsideration; the biller decides.

The Visit thread after the visit, marked Done. The tail of the Sent to card names the standing approval the document drop ran under. The Visit agent writes that it read the note back from the chart with the same hash and that the visit is done, and its result card, tagged verified · EMR read-back, lists the document found, the matching patient and hash, the time of the read and the one-hour window met.

Nov 18 · 2:41 PM · Sent to is inferred until Read back from makes it verified. The visit closes only then.

What it stands on

What it stands on. No hand-waving.

FHIR underneath.
Clinical data is stored as FHIR, one store per center, checked against nico’s own rules on every write. We read your EMR over its certified FHIR API. Every copy carries the time it was read, and every write back is proved by reading the chart again.
Security by construction.
The clinical store has one client, nico, on a private network. Agents act as named principals with short-lived, scoped credentials, on behalf of a person. Every read of a record is audited. Anything clinical or financial passes a gate. A kill switch stops any agent at its next step. A patient’s full identifiers appear in one place.
State of the art AI, kept honest.
The best available models read the faxes and letters. Every fact they extract carries its page and its confidence. Nothing inferred reaches a payer or a chart without a person, and no model decides treatment or money. The payer-policy knowledge base learns from outcomes.

Pricing

Software that does not take a cut of every infusion.

An infusion center runs on thin margins. Drugs are bought up front. Payers pay late. Chairs have to stay full. If your software bill is a line per infusion, it grows with every patient you treat and penalizes you for growing your own business, while the work still lands on your staff.

Adding an AI tool on top of practice software means two bills and two systems to keep in step. nico is one system, built for agents and people from the first line, and one fee. Our terms are a commitment, not a quote.

One flat monthly fee. Never per infusion.
You pay for the software, monthly. That is the whole price. Treating more patients never raises the bill, and no part of the fee is tied to a dose.
Monthly contracts only.
No annual lock-in. You stay because the software works for you. You can leave the month it stops.
You deal with the founders.
The team is small and technical, and we plan to keep it that way. No salespeople to get through. The people you talk to are the people who build it.

Design partners pay nothing while we build it, and are offered equity.

Design partners

Built with a few infusion centers first.

Design partners are owners of smaller infusion suites who want a say in what nico becomes. They use each part as soon as it is safe to use, pay nothing while it is built, and are offered equity. nico is lean and self-funded: no VC, no PE, and nobody pushing us to raise the price.

Become a design partner

FAQ

Plainly, where this stands.

Short answers to what a coordinator, a biller or a practice owner asks first.