How it works

You send the card and the note. Vinci sends back a checked claim, ready for your physician.

No EHR integration to set up, and no retyping the insurance card into a billing screen. Vinci reads the card, the visit note and the device report, builds the claim, and shows the line in your documentation behind each code. Nothing is sent until a physician at your clinic approves it.

We sign a Business Associate Agreement (BAA) with every clinic. Your data is not used to train AI models.

Illustrative — sample data, not a real patient or claim.
Before Vinci

Most of a claim already exists. It's just scattered.

The insurance card is a photo on someone's phone. The note is in the EHR. The test report came off the device as a PDF. Someone retypes all of it, picks the codes, and finds out weeks later that a modifier was missing. Then someone chases the doctor for an addendum, weeks after the visit.

Vinci starts where your desk starts: with the documents, not a blank claim form.

Overview

One visit, from the front desk to the payer

A short walk-through of one visit: what the front desk sends, how the claim is built, what the physician approves, and what happens after it's sent.

80 seconds. Illustrative — sample data, not a real patient or claim. Narration is an AI-generated voice. Service descriptions are written by Vinci and are not official code descriptors. CPT is a registered trademark of the American Medical Association. Read the transcript.
How Vinci Billing turns a visit into a claim — transcript

Narration is an AI-generated voice. All screens are illustrative: sample data, not a real patient or claim. Service descriptions are written by Vinci and are not official code descriptors. CPT is a registered trademark of the American Medical Association.

[A billing desk in a small medical office. Papers out of focus, an empty chair.]
The patient left an hour ago. The claim hasn't started.

[Two monitors on the desk. On screen: "Retype. Reread. Chase."]
Someone retypes the card, rereads the note, chases the test report.

[Screen: an insurance card photo, a visit note and a device report arrive in a new visit. On screen: "Send what you already have" and "No EHR integration needed."]
Vinci starts with what the clinic already has: a photo of the insurance card, the visit note, the device report. No EHR integration needed.

[Screen: the member ID field is linked to its place on the card. "Coverage active on date of service."]
It reads each document, checks the patient's coverage with the payer, and shows where each detail came from.

[Screen: diagnoses I10 and E11.9 and the visit line 99214, each with a quote from the note and its page and section.]
Then it proposes the codes. Next to each one is the sentence from the note that supports it, with its page and section. No line goes on the claim without it.

[Screen: four checks pass. The ECG line, 93000, moves to "Not on this claim": the tracing is in the file, but the note has no interpretation of it.]
Vinci checks for overcoding and undercoding, against national coding edits and coverage rules. When the note doesn't support a code, it says why and leaves it off.

[Screen: "Ready for your approval." The physician approves. "Approved by A. Sample, MD."]
The physician sees one screen: each line, its evidence, what was left off. The physician approves, or returns it with a comment. Nothing is sent before that.

[Screen: status moves from Sent to Accepted. "Accepted means received for processing, not paid." Note: electronic submission starts once each payer confirms EDI enrollment.]
Vinci submits the claim and tracks whether it's accepted or rejected.

[Vinci Billing logo. "Get your free Checkup" — an AI look at the claims and payment reports you already have. vincibilling.ai]
Send what you already have. Get back a claim that's coded, checked, and backed by your documentation.

The steps

Four steps from the visit to the payer

Each step takes something in and hands something on. Device Hub links in-office test results to the visit, so the Claim Builder can cite them as evidence.

Diagram: Capture leads to Claim Builder, then Review, then Submission. Device Hub sits beside Capture and links test results to the visit for Claim Builder. A Denials block after Submission is marked coming soon.

Capture

Card, note and superbill in. Visit data out.

Claim Builder

Codes proposed with evidence, checked against payer rules.

Review

Your physician approves or returns the claim.

Submission

Sent electronically and tracked.

Device Hub

Test results from the device, linked to the visit.

Denials

Coming soon

1 · Capture

Send it the way you have it

Your front desk sends what it already has for the visit: a photo of the insurance card, front and back, and the visit note or superbill, as a PDF or a photo. Your team enters the patient and the date of service. Vinci reads each document and fills in the payer, member ID, subscriber and provider. Click any field to see the text in the document it was read from.

Then Vinci checks coverage with the payer for that date, so a wrong member ID shows up now, not as a rejection three steps later.

In
  • Insurance card photo
  • Visit note or superbill (PDF or photo)
  • Device report, when there is one
Out
A visit with patient, coverage and provider details, each field tied to its source, and the payer's eligibility response for the date of service.
Illustrative — sample data, not a real patient or claim.
2 · Claim Builder

Codes that match the note, with the note quoted

Vinci proposes the diagnosis and procedure codes the documentation supports, with modifiers where they apply, such as the professional and technical components of a test (26 and TC). Each code cites the sentence in your documentation that supports it, and that quote is checked word for word against the source document. The visit level is set by fixed rules from what the note documents: the problems addressed, the data reviewed and the risk of patient management.

Then the claim runs through the checks a biller does by hand: codes valid on the date of service, national bundling edits for code pairs, unit limits, diagnosis pointers, provider NPIs, place of service, and the coverage rule for each test. Charges come from your fee schedule.

It works in both directions. If the note supports a different visit level than the superbill shows, higher or lower, the claim carries the level the note supports, and you see the quote behind it. If the note doesn't support a line at all, the line comes off, and Vinci tells you what the documentation is missing. Vinci never suggests a diagnosis to justify a test.

In
  • Visit data from Capture
  • The documents themselves
  • Device results linked to the visit
  • Your fee schedule
Out
A proposed claim: each line with its code, its evidence and the checks it passed, plus a list of anything left off and why.

Illustrative — sample data, not a real patient or claim.

3 · Review

Your physician has the final word

The claim reaches your physician on one screen: each code next to the line from the note behind it, anything left off and the reason, and the coverage check. The physician approves it or returns it with a comment. Nothing is sent before that. The approval is recorded with the physician's name and the time, and if the claim changes after approval, it comes back for a new one.

If something is missing that only your clinic can provide, such as the ordering provider or a page of the note, Vinci asks your team for it before the claim reaches the physician.

In
  • The proposed claim, with its evidence and what was left off.
Out
A claim approved by a physician at your clinic, or returned with a comment.
Illustrative — sample data, not a real patient or claim.
4 · Submission

Sent, then tracked where you can see it

Once approved, Vinci submits the claim electronically and shows you each step: sent, accepted or rejected by the clearinghouse, and the payer's response when it arrives. If a claim is rejected, you see the reason. Vinci corrects what it got wrong and sends it again; any change to the claim goes back to your physician first.

At launch, Vinci submits primary claims. Secondary claims are coming soon.

For payers that require EDI enrollment, electronic submission starts once the payer confirms it. Vinci fills in the enrollment forms from your clinic profile, and each billing provider signs. Some payers confirm in a few days; others take a few weeks. EDI enrollment authorizes Vinci to send claims for your providers. It is not payer credentialing, and it does not change your contracts or where your payments go.

In
  • The approved claim.
Out
A submitted claim with its status, from sent to the payer's response.
Illustrative — sample data, not a real patient or claim.
Beside the path · Device Hub

Test results, straight from the device

Device Hub receives the file the device already produces and keeps the original unchanged. At launch it reads Biotracker files. Each measurement is listed with its unit and the reference range from the device file. Values outside that range are marked; that is a comparison with the file, not a clinical interpretation. Results are matched to the patient and suggested as evidence for that patient's visit on the same date. Once linked, they are evidence the Claim Builder can cite. A device reading never creates a visit, a diagnosis or a test order.

Your team also gets the results panel: each patient's history across tests, an export by period as CSV, with the device's original report when it produces one, and an alert when a device stops sending.

For clinics that use Biotracker, the uploader already at your clinic sends each new test to Vinci. There is nothing new to install. Biotracker is a device partner of Vinci Billing.

A test is coded only when it is on Vinci's launch list and the note documents the order and the interpretation.

Ask us for the current list of tests Vinci codes at launch.

Device Hub reads Biotracker files today. Make another device? Talk to us about your device

In
  • The file from the device.
Out
Organized results with units and reference ranges, the original file kept, and the test linked to the visit.
Illustrative — sample data, not a real patient or claim.
Next

Denials

Coming soon

A block for denied claims: the reason in plain language, the correction, the appeal and the resubmission. Rejections, when the clearinghouse or payer won't accept a claim for processing, are already handled in Submission.

One sample visit

How a claim is built

Vinci proposes the codes and cites the evidence for each one. It checks them against payer rules. Your physician approves.

  1. The visit: 99214. The note documents one chronic illness not at goal, a second one stable, and a prescription change. The evidence is quoted from the note: Increase lisinopril from 10 mg to 20 mg daily. Recheck BP in 4 weeks. Visit note, page 2, Plan.

  2. The ECG: left off. The tracing is in the file, but the note has no interpretation of it. If the physician interpreted the tracing at this visit, a dated, signed addendum can document it, and the line is checked again. Otherwise the code stays off the claim.

  3. The Biotracker test: linked, not billed. The results arrived from the device and were matched to this visit. In this sample the test is not billed. It would be coded only if it were on Vinci's launch list and the note documented the order and the interpretation.

  4. The physician: one screen. Approve and send, or return with a comment.

Illustrative — sample data, not a real patient or claim. Codes and quotes are examples. Service descriptions are written by Vinci and are not official code descriptors. CPT is a registered trademark of the American Medical Association.

Who does what

Two jobs at your clinic, and neither one is retyping

What your front desk does

  • Creates the visit: patient and date of service.
  • Uploads the card and the note or superbill. A phone photo works.
  • Answers when Vinci asks for something the claim needs.
  • Follows each claim's status in one list.

What it stops doing: retyping the card, looking up modifiers, and learning about a missing interpretation after the claim comes back.

What your physician sees

  • One screen per claim.
  • Each code next to the sentence from their own note that supports it.
  • Anything left off, and what the documentation is missing.
  • Two buttons: Approve and send, or Return with a comment.

Nothing is sent without the physician's approval, and the physician can return any claim with a comment.

Each claim shows where it is:

  • In preparation
  • We need some information
  • Ready for your approval
  • Sent
  • Accepted
  • Rejected
  • Not billable as documented

Questions billers ask

Do we need to connect our EHR?

No. Vinci works from the documents. If your EHR can print or export the visit note as a PDF, that's all Vinci needs from it.

Does AI decide the codes?

AI reads your documents and proposes the codes. The visit level is calculated by fixed rules from what the note documents, each quote is checked word for word against the source document, and the claim runs through coding edits. Anything that doesn't pass is left off and shown to you with the reason. Nothing goes out without your physician's approval.

Who is responsible for the claim?

Your practice, as the billing provider, is responsible for its claims. That's true with any billing service, and with Vinci. Vinci is responsible for sending exactly what your physician approved, showing the documentation behind every code, correcting and resending anything we got wrong, and protecting your data under the BAA.

Will this change what we get paid?

It can, in either direction. Vinci bills what the documentation supports, no more and no less. If the note doesn't support a code, the code comes off the claim, and you see why before anything is sent.

What about denials?

Handling denials, when a payer processes a claim and decides not to pay it, is coming soon in a Denials block. Rejections are handled today: when the clearinghouse or the payer won't accept a claim for processing, you see the reason in Submission. Vinci corrects what it got wrong and resends it, and if the fix needs something from your clinic, Vinci asks for it.

Where does our data go?

We sign a Business Associate Agreement (BAA) with every clinic, and your data is not used to train AI models. The details are on the Security page.

Starting in mid-December 2026 with Biotracker partner clinics.

Talk to us about pricing for a practice your size.

Pricing depends on the size of your practice. Not ready to talk? Start with a free Checkup: Vinci analyzes the claims and payment reports you already have and shows you where claims are being denied and why.

The Checkup is statistical. It does not review charts, and it cannot tell whether a specific visit supported a higher or lower code.