All insights
Architecture

The money isn’t lost in the visit. It’s lost in the account

No healthcare provider loses money by treating patients badly. It loses money in the account that is settled by hand, the invoice that does not match the regulatory report, and the payer objection that almost never gets paid.

Engineering team· · 7 min read
The money isn’t lost in the visit. It’s lost in the account

No clinic director wakes up worried about interoperability. They worry about the waiting room, the staff, the equipment. And yet the money a healthcare provider loses rarely leaks from bad medicine. It leaks from what happens after the medicine: between the visit and the payment, where nobody is watching because nobody thinks that is where the problem lives.

Three leaks that never show up on a dashboard

They are not dramatic. They are routine, which is exactly why they survive:

  • The account is settled by hand against a payer contract that changed six months ago and that nobody re-entered into the billing sheet.
  • The invoice and the regulatory report disagree because one was built from the clinical note and the other from what the biller remembered, and nothing forces them to match.
  • The payer objects, and the reply —if there is one— arrives without the supporting document that would have settled the argument, because nobody kept it where anyone could find it in time.

Each leak on its own looks small enough to live with. Add them up across a year of visits and they explain more of a provider’s margin than any negotiation with a payer ever will.

A provider does not lose money treating patients. It loses money doing paperwork about the patients it already treated well.

What changes when the data is born clinical

The usual fix is hiring more people to reconcile what should never have needed reconciling. The alternative is making the charge, the invoice and the report come out of the same clinical act, automatically, instead of being rebuilt from it by three different people later.

That only works if the clinical note itself is structured data from the moment it is written, not free text that somebody re-reads and re-types downstream. A doctor who dictates the visit and reviews an AI-drafted note —never signs anything they haven’t reviewed— produces a record that can feed billing, the regulatory report and an interoperable clinical summary in the same instant it is closed, because the diagnosis and the procedure were already coded, not guessed at afterwards by someone reading a paragraph.

Reviewing the account before it is sent, not after it is rejected

Payer objections are expensive for a reason that has nothing to do with the visit itself: fixing an objection after the fact means finding a document, a signature or an authorisation that was filed somewhere and forgotten, under time pressure and often after the window to appeal has already started closing.

The alternative is checking the account against the contract, the authorisation and the stored supporting documents before it ever leaves the building —and if a payer objects anyway, answering with the evidence already assembled instead of starting the search from zero.

A requirement that stopped being optional

Every market Bitsideas operates in is moving the same direction: electronic health records that must be interoperable, not just digital. In Colombia, for instance, a provider now has to generate the RIPS in JSON, obtain the CUV from the Ministry of Health and send the Digital Care Summary to the IHCE, under Resolution 2275 of 2023 and Resolution 1888 of 2025. That is one configuration among several a system has to support —not a rule that applies everywhere the same way— but the direction is the same in every one of them: what used to be a compliance checkbox is now a live feed a system either produces automatically or someone assembles by hand, every time, under deadline.

What to check in your provider today

  • If a payer contract changes, does the billing side find out the same day, or the same quarter?
  • Can you produce the exact document that supports a specific charge in under a minute, or does that mean calling three people?
  • Does your invoice come from the same data as your clinical note, or from someone’s memory of it?
  • If the regulator changed the required report tomorrow, would your system produce it, or would it become a project?

None of those questions is about how well the doctor treats the patient. All of them decide whether the provider gets paid for having done it.

Keep reading