← Onceentered

Onceentered for healthcare intake

One patient. Intake, then the referral, then the prior auth. The same demographics, three times.

The front desk this is about

A new patient is registered. Name, date of birth, address, phone, insurer, member ID, group number, subscriber, the referring provider. It goes into the practice system once — and then it goes somewhere else.

The payer portal for eligibility. The specialist's referral form. The prior-authorisation request, which asks for the same member ID in a box labelled nothing like the last one did. Every one of them re-asks for a patient who is already fully entered on the screen behind it.

This is the work that makes an intake coordinator's afternoon disappear, and it is the work where a transposed member ID becomes a denied claim three weeks later.

Where this work goes

Named as examples of where the retyping goes, not as integrations. Onceentered has no per-site templates and nothing to configure — it reads whatever form is on the screen, which is why it still works on the small plan nobody builds connectors for.

The part your compliance officer will ask about first

We never receive the patient's information

Everything entered stays in the browser on the machine at the desk. We operate no server that could receive it, and the extension contains no code capable of sending it. Nothing is copied to a Google account, because Chrome's synchronised storage is never used. On the free plan the extension makes no network request at all; on a paid licence the single request it makes carries a licence key and opaque licence-instance identifiers — never a profile, field value, or computer name.

Stated plainly and without overreach: because nothing leaves the device, there is no copy of patient information in our hands to protect, disclose, or lose. That does not transfer any of your own obligations to us, and it is not legal advice — your privacy officer should review any tool that touches patient data, and this one is deliberately easy to review. The privacy policy is short, and every claim in it is enforced by an executable check that fails the build.

Two more facts they will want: the extension requests no host permissions, so it has no standing access to any website and cannot run in the background; and it never fills hidden fields.

The fields that actually break autofill

Browser autofill stores the identity of the person sitting at the keyboard. At a front desk, that is never the person being registered.

It never submits

It fills the form, shows what it filled and what it left alone with the reason for each, and stops. A person reads the screen and a person submits. That is a permanent boundary rather than a feature waiting to be added — software that submits a medical form on someone's behalf owns the error and never the consequence.

Screenshot — the same patient filling a payer portal

What it costs

Free: one patient profile, unlimited fills — enough to carry one real registration through to a payer portal today.

$28 per month, or $280 per year — two months free

If a subscription lapses, extra profiles lock rather than delete. Nothing entered is ever destroyed.

Get it

Coming to the Chrome Web Store

Tell me which portals your front desk retypes into and you will get the link the day it goes live, at the founding price held for as long as you keep the subscription.

Email me the link at launch

A plain email to hello@zrventures.co. No form, no tracker, no list to escape from later.