Clinical documentation software with signed, versioned notes

How template versioning keeps a signed note reproducible

Clinical documentation is worth what it can withstand in a review two years later, and that durability comes from how the record is structured rather than from how it is written.

An organization enrolls in a template pack. Templates within a pack are immutable per version: a change publishes a new version and never rewrites the old one. A note pins its template version at creation. That single decision is what makes a signed note reproducible, because rendering a 2026 note through a 2028 template is how documentation quietly stops matching what the clinician actually saw and signed.

Signing is enforced where it cannot be worked around

Most systems enforce a signed note in the interface: the fields go read-only and the save button disappears. That holds until something reaches the record by another route.

Here the rule lives in the database. Signing snapshots the content as an immutable version and sets the note locked in one transaction. From then on a trigger raises on any change to the note’s content or to its signature fields, and the error it returns says what to do instead: add an addendum. Addenda can be inserted and read; they cannot be deleted, and the permission to delete them is not granted to any application role. The practical test is simple, and worth running during a trial: sign a note, then try to change it.

What a co-signature is, and what it is not

A co-signature is an attestation by a supervisor that the documentation is acceptable. It requires the co-sign permission, and it requires the author’s signature to already exist, so the sequence cannot be inverted.

It deliberately does not change the rendering provider on the encounter. For technician-delivered services many payers want the claim under the supervising clinician’s NPI, and both providers are stored on the encounter so a payer rule decides which one prints. That is a billing decision made from configuration, not a side effect of who happened to click co-sign, and it is per payer because the rules differ per payer.

Whether a co-signature is required at all comes from the template, matched against the author’s role, rather than from a global setting. Supervision rules differ by state, board and payer, which is why the rule is configured in the template you use rather than encoded by us.

Documentation that traces back to a goal

Notes and treatment plans are linked, so a note can be read against the goal it was meant to serve. The plan hierarchy is one structure serving two vocabularies: goal into objective for behavioral health, program into target for behavior analysis. Phase events sit on the plan item, which is what makes a phase line on a graph the same fact as the phase change recorded in the plan.

For behavior-analytic practices this is the same chain the data collection surface feeds: targets run during the session arrive in the note, the note is signed and co-signed, and the charge line comes from the encounter that produced both. An audit that starts at any one of the three ends at the same session.

Why there is no AI scribe here

Most clinical documentation software now leads with AI note generation, and the omission here is deliberate rather than pending.

A generated note is a plausible account of a session, assembled from a transcript or a prompt. It then has to be read carefully against what actually happened, because the clinician signing it is attesting to its accuracy and carries that attestation into any audit. The time saved writing is partly spent checking, and the part that is not checked is the part that creates exposure.

Pre-fill solves the same problem from the other end. The session times, the targets run and their totals are already recorded as structured data during the session, so they are placed in the note as facts rather than predictions. Nothing is inferred, the note cannot disagree with the data behind it, and what remains for the clinician to write is the clinical reasoning — the part a person should be writing.

Practices that specifically want dictation or an AI scribe should weigh that against this trade-off honestly: those tools are genuinely faster for narrative-heavy documentation, and if a narrative note is most of your documentation burden, they will save you more time than pre-fill does.

Current limits of the documentation module

Only the ABA template pack ships today. This is template-driven documentation with an ABA pack rather than a general note-template library, so practices needing SOAP, DAP or BIRP formats should wait for the behavioral-health pack.

Nothing here renders a finished document yet. The progress-report template is structured data you can complete, not a PDF you can send, so a re-authorization packet still leaves the system as data. No part of the module drafts, dictates or transcribes clinical content.