Product tour

From signing up to the folder an auditor asks for.

Every screen you’d touch, in the order you’d touch them — the account, the agreement, the roster, an EVV export going in, the five checks running, what the engine says it is worth, the text to the caregiver, the week after when it re-checks what it flagged and closes what came back fixed, and the one page you hand an auditor.

Captions included. The film itself doesn’t download until you press play.

Chapters

Picking one starts the film there.

Transcript

The narration of the whole thing (4:38), with timestamps. It follows the length you picked above.

0:00Every visit your caregivers make has to match a record in the state's EVV system.
0:05When it doesn't match, the claim doesn't get paid. And nothing tells you which visit it was.
0:12Oncu reads the export you already produce, and tells you before you bill. Real screens, real engine, a fictional agency.
0:21It starts with an account. Agency name, your email, a password. No sales call, no implementation project.
0:30Notice what it doesn't ask for. No license key, no contract, no card. The account exists the moment you submit it.
0:39Your email gets verified, because in a moment this account is going to hold protected health information.
0:46Which is why the authenticator comes here, not at the front door. At the point where real data begins.
0:54Then the Business Associate Agreement. You read it, you accept it in the app, and the acceptance is written to the audit log with your name and the timestamp.
1:04Until that is done, the system will not take a single row of your data. It isn't a checkbox. It's a lock.
1:12Then your roster. Caregivers, their mobile numbers, and the date each one consented to text messages.
1:20Three of these twenty haven't consented. Oncu will not message them, and it says so, rather than quietly dropping them. Clients come in the same way. Recipient IDs only.
1:33Now the part you'll actually do every week. Export the visits from your EVV system, and drop the file in.
1:42Before anything is committed, you see what the parser read. Three hundred and twelve rows, three hundred and three visits, nine exact duplicates collapsed. Counted, not deleted.
1:55Your file is never modified. The original is kept, byte for byte.
2:01Commit it, and five checks run on every visit. Missing clock-out. Missing clock-in. Missing service code. A recipient ID that isn't one of yours. A caregiver who isn't on your roster.
2:15Those are the five ways a claim dies.
2:18Seventy-two of those three hundred and three visits have something wrong with them.
2:24Worth how much? Oncu already knows which codes your visits used. You tell it what they pay.
2:31Published rates for your programme are here as a starting point. Only a starting point: which one applies depends on your program and provider type, so you confirm it against your own fee schedule.
2:44A little over two thousand seven hundred dollars at risk. One week, one agency, twenty caregivers.
2:51And it tells you what it cannot price. Thirteen visits have no service code at all, so there is no rate to apply.
2:59Each exception names the visit, the caregiver, and exactly what is missing.
3:05You fix it where the record actually lives, in your EVV system. Oncu never edits your source data.
3:13For the ones that need a person, Oncu texts the caregiver. This was recorded against a test instance, so nothing actually went out. But the body is exactly what the engine composes.
3:25No client name. No address. No diagnosis. Nothing in there would be a breach if it reached the wrong number.
3:34Replies come back into one thread. And outside the hours you set, it waits rather than sends.
3:41Then next week, you upload again. The engine recognises the visits it flagged, re-checks them, and closes them itself. Thirty-eight of them, worth one thousand two hundred and ninety-six dollars. You never mark your own homework.
3:57And when you need one page to hand to somebody, the baseline audit assembles it. Ninety days of visits, where the exceptions concentrate, and the three fixes that would move the number most.
4:10When an auditor asks for paperwork, it is already in one place. The consent form your caregivers signed, your BAA, the messaging terms. And underneath all of it, an append-only record of who did what, enforced by the database itself. Not even we can edit it.
4:27That's Oncu, end to end. Make an account, upload one export, and look at your own numbers.
4:34oncu.us

What you are watching, in full.

Northline Home Care does not exist. The agency, its twenty caregivers, its clients and every visit in the file are invented. No real patient, caregiver, agency or protected health information appears in any frame.

Every figure on screen is the engine’s. The row counts, the exception breakdown, the dollars at risk and the recovery in week two are unmodified output of the same rules engine your own export would run through — run on that invented input. Nobody typed a number to make the film look better. The service rates typed on camera are invented inputs too, so the dollar figures are not derived from published Ohio rates and are not a quote.

It was recorded on a local test instance. The email and SMS providers were mocked, so nothing was sent to anyone; the message bodies on screen are the ones the engine composes, and the app’s own “SMS mocked” badge is visible in that scene. The email-verification step was switched on in the database for filming, because a mocked mail provider never triggers it.

One thing in it is not demonstrated. Quiet hours were widened to a 24-hour window for filming, because it was shot at night. So when the narration says reminders wait outside the hours you set, you are hearing a description of the product and not watching it happen. The shipped default holds reminders to 8am–9pm in your agency’s timezone.

Its figures are not comparable with the ones elsewhere on this site. The film runs fixture weeks 38 and 39. The counters on the home page come from a separate generated run of the same invented agency, so the two sets of numbers are unrelated — not two weeks of one history.

One thing the film says that is worth repeating here, because it is the part people assume works the other way: Oncu never edits your source data. A flagged visit gets fixed where the record actually lives, in your EVV system. On your next upload the engine re-checks it and closes it itself.

Or skip the film and put your own export through the engine instead.

Start free or call +1 (888) 505-3275

Captions and a transcript of the narration are provided. There is no audio description, and the transcript describes what is said rather than what is on screen, so the film meets neither WCAG 1.2.3 (Level A) nor 1.2.5 (Level AA). If that is a barrier, ask us for a walkthrough and someone will take you through the same screens on a call — or open the live sample, which is the product itself with writing switched off.

Stop chasing exceptions

See what your last export is hiding.

Upload the EVV file you already produce and watch Oncu surface every visit putting a claim at risk — in minutes, on your own data.

Start free Or get a free Snapshot

or call +1 (888) 505-3275

Agreement first · readout within 48 hours · your file deleted after, certified