A claim asserts a service. An attestation proves it.

A claim is an assertion that something was done, to a named patient, on a named date, by a named clinician. Almost every system will let that assertion be created from an appointment, a template, or a batch job, and will let it be edited afterwards without leaving a mark. When the assertion is later challenged — by a payer, by defense counsel, or by a regulator — the burden is to show that the service happened, and a record that can be quietly rewritten cannot carry that burden.

The gate

A billable charge is not something the system creates and then looks for evidence to support. It is the last step, and it is refused until four things are true:

1. The service exists as a discrete event with a performing location, a date and time, and a rendering clinician — not as a line item inferred from a schedule.
2. The diagnostic record that the service produced or consumed is attached to it. For a laboratory charge that is the requisition and the issued report; for a professional component it is the signed interpretation.
3. The rendering clinician's identity is verified at the moment of signing, against credentials held for that clinician, not against a shared account.
4. That clinician signs. The signature is bound to the specific version of the record in front of them.

Until all four hold, the charge exists only as an unbilled draft. It cannot be submitted, it cannot be assigned to a lien, and it does not appear in the receivable. The point is not to slow billing down. It is that a charge which cannot be evidenced is a liability rather than an asset, and it is cheaper to find that out before submission than during a deposition.

What the signature actually covers

A signature that means everything means nothing, so the attestation is narrow and its text is stored with it rather than referenced from a policy that can change later. The clinician is attesting that the service described was performed, on the date recorded, by them or under their supervision at the level stated, and that the attached record is the record of it.

They are not attesting to the codes. Coding is a separate act by a separate party, it is recorded separately, and a coder's later change to a code does not silently inherit a clinician's signature. If a change to the record is material enough to alter what was attested, the attestation is invalidated and has to be given again against the new version.

The audit record

Every event above is written to an append-only log. Entries are not updated and not deleted. A correction is a new entry that references the one it corrects, so the sequence a reader sees is what happened, including the parts nobody is proud of.

The log is not a debugging aid that happens to be retained. It is the artifact that answers the question the whole page is about, so it is retained on the schedule the underlying record is retained on and it survives the deletion of the working copy.

Transparency, scoped like everything else

An audit record that only the vendor can read is not transparency. The attestation and its history are disclosable, and who sees how much of it follows the same release model as the clinical data rather than a separate set of rules invented for billing.

Patient

That a service was recorded, attested, and by whom, alongside the record itself. A person is entitled to know who says they treated them.

Attorney of record

The attested statement, the signature metadata, and the correction history for the charges on the matter, under the authorisation in force. This is usually the point of the exercise: a charge on a lien that arrives with its attestation attached is one fewer thing to litigate.

Payer and utilization review

The attestation supporting the specific claim in question, bounded by minimum necessary. A request to audit one claim is not a request for the log.

Rendering clinician and the practice

Their own signatures and everything recorded against them, including charges released under their name that they did not sign.

The last one is deliberate. A clinician being able to see what has been billed in their name is a control, and it is the one most often missing.

What this does not do

It does not establish that a service was medically necessary, which is a different argument on different evidence. It does not prevent a determined party from attesting to something untrue — nothing does — it makes the statement specific, attributable to a verified identity, timestamped, and impossible to revise quietly afterwards. And it is not a substitute for the signature requirements a given payer imposes, which vary and which remain the biller's obligation to meet.

Revenue integrityThe release model