Protocol enforcement for pain clinics

Your best MA just gave notice. Your documentation quality shouldn't leave with her.

PainFlow encodes your providers' controlled-substance and procedure rules into a structured rooming workflow any medical assistant can run on day one. It produces consistent, audit-defensible notes no matter who you hire.

PHI-free by design. No backend, no database, no BAA needed for the core product.

~$14,200
Typical cost to replace one departed medical assistant.
#1
MAs are the top turnover role in ambulatory practices.
Two pains, one workflow

Turnover and audits cost you the same thing: consistent documentation.

Turnover

The workflow shouldn't live in one person's head.

When a seasoned MA leaves, the rooming knowledge goes with her: which questions to ask, which counts to run, when to hold an injection. The next hire relearns it from scratch, and your notes get thinner while they do. PainFlow holds the protocol so the person running it can change without the quality dropping.

Replacing a departed MA runs roughly $14,200, and medical assistants are the #1 turnover role in ambulatory practices.

Audit defense

Incomplete charts are what a DEA audit cites.

The most common DEA audit findings are incomplete charts and refill documentation. Not fraud, just gaps: a pill count that never made it into the note, a refill date nobody computed, a screen that got skipped on a busy day. PainFlow makes the count, the math, and the screen part of rooming, so the record is complete before the provider ever opens the chart.

DEA audits most commonly cite incomplete charts and refill documentation.

See the product

The MA runs the gate. The note writes itself from the fields.

Structured input on the left. Deterministic output on the right. Every number in the note came from a field the MA filled, not from a language model.

HPI · paste-ready for athenaOne Copy

Established patient returns for chronic pain follow-up. Interval history reviewed with the patient during rooming.

Medications

Oxycodone 10 mg reported, 3 tablets remaining against an expected range of 2 to 5: within expected range. Next refill calculated for 07/19/2026 based on the reported directions.

Health changes

No new falls, hospitalizations, or medication reactions reported this interval.

Procedure screening

Right knee steroid injection requested. No signs of active infection at the site. Most recent A1c 9.1, above the clinic threshold for steroid injection. Likely requires provider review before proceeding.

To complete

Provider assessment · plan · injection decision

Synthetic data shown. Nothing in this note is generated by a language model. The counts, the ranges, the refill date, and the screen results are read straight from the fields the MA completed. For controlled-substance documentation, a made-up number is a liability, so PainFlow does not invent one.

See it move

A rooming, start to finish.

A staff rooming in the live demo.

How it works

Your providers write the rules. We encode them. The MA runs them.

PainFlow enforces the protocol your physicians already follow. It never makes a clinical decision, and it uses suggest-and-defer language throughout.

Room the patient

The MA walks a structured flow on the clinic's existing iPad: pill counts with expected-range math, patch tracking, refill-date math, health-change screens, UDT workflow, and injection-eligibility gates.

The gates enforce protocol

An active infection halts the injection. An out-of-range A1c flags a steroid injection for review. An off-range count surfaces. The rules are your providers'; PainFlow enforces them and defers the clinical call back to the provider.

Paste the note

PainFlow generates a complete, deterministic HPI from the fields and copies it to the clipboard. The provider pastes it straight into athenaOne. No EHR integration, no IT project, no BAA.

The obvious objection

Why not just use your EHR's built-in screeners and a free ambient scribe?

Because those capture data. PainFlow enforces protocol.

A scribe documents what is said in the exam room. It never sees the pill count, because the count happens in rooming, before the provider walks in and before anyone speaks. It never blocks an injection at an out-of-range A1c. It never computes a refill date. Built-in screeners collect answers; they do not gate a procedure or run the math.

PainFlow produces deterministic output from structured fields, not a probabilistic summary of a conversation. For controlled-substance documentation, a made-up number is a liability, so nothing in a PainFlow note is generated by a language model. This is not an AI scribe, and that is the point.

Capability PainFlow Scribe
Records the pill count with expected-range math
Halts an injection at an out-of-range A1c
Computes the next refill date
Output is deterministic, never model-generated
Data & privacy

PHI-free by design. HIPAA exposure engineered out.

PainFlow is built on one rule: protected health information never leaves your device. There is no server to breach and no database to lose, because none exists.

Nothing is stored

No patient names or identifiers. Answers live only in the active session on the iPad, in temporary memory. Sessions clear automatically: 20 minutes after copy, or after 10 minutes of inactivity.

Nothing is transmitted

The app runs entirely in the browser on your device. There is no backend and no PainFlow account system. The note reaches athenaOne by clipboard paste on the same iPad, not across the internet.

No IT project

Runs as a web app on the iPads you already have. Deployable without EHR integration, without an IT integration, and without a BAA for the core product. Your compliance officer is welcome to review the architecture with us directly.

No third parties

No analytics, no advertising, no crash reporting, no tracking on any screen where patient information appears. There is nothing to leak because there is nothing collected.

Where the line sits: because PainFlow never creates, receives, maintains, or transmits PHI on our side, our working position is that no business associate agreement is needed for the core product. Your compliance officer should confirm that conclusion for your practice. Device passcodes, screen safeguards, and staff training stay on your side, exactly as they do today.

The model

A service, not licensed software.

We encode your providers' protocols and maintain them as the rules and regulations change. The tool is how the service is delivered; it is never sold on its own.

Protocol encoding
$5,000 – $15,000
one-time, fixed fee

A fixed-fee engagement to encode your clinic's controlled-substance and procedure protocols into the rooming workflow. The range depends on protocol depth: more gates, more procedures, more medication logic.

Maintenance retainer
$2,000 – $4,000
flat, per month

A flat monthly retainer covering protocol updates, regulatory changes, and new-MA support. When the rules change or you hire, the workflow stays current without a new project.

Typical engagement ranges shown.
Never revenue share Never per-seat Never licensed standalone
Where this goes

Roadmap

Honest about what is here today and what is next.

Next

Deeper compliance modules

Controlled-substance agreement tracking with renewal dates, and UDT cadence by risk tier: the documentation spots incumbents leave unproductized.

In research

Direct EHR field insertion

Writing structured fields straight into the EHR instead of a clipboard paste. Under research; clipboard paste is the supported path today.

Second vertical

Addiction medicine

The same controlled-substance gates, counts, and UDT cadence port directly to office-based addiction medicine, the designated next vertical.

Questions

Straight answers

Is this an AI scribe?
No. An AI scribe listens to the exam-room conversation and summarizes it. PainFlow is a structured rooming workflow the MA runs before the provider walks in, and it generates the note deterministically from the fields, not from audio and not from a language model. That matters because the pill count, the refill math, and the injection gates happen in rooming and are never spoken, so a scribe structurally cannot capture them. And for controlled-substance documentation, a deterministic note has no room for an invented number.
Where does patient data go?
Nowhere. PainFlow is PHI-free by design: no patient names or identifiers, no backend, no database, nothing leaves the iPad. Session data lives in temporary memory and clears itself automatically, 20 minutes after the note is copied or after 10 minutes of inactivity. There is no server to breach because none exists.
Do we have to change our EHR?
No. PainFlow runs as a web app on the iPads you already have, alongside whatever EHR you use. It works with athenaOne today by copying the finished note to the clipboard for a paste. There is no EHR integration, no IT integration, and no BAA required for the core product.
Who writes the clinical rules?
Your providers. The protocols are provider-authored: your clinic's own physician rules get encoded, and PainFlow enforces them. It never makes a clinical decision. Throughout, it uses suggest-and-defer language ("likely qualifies," "review needed") and routes the actual call back to the licensed provider.
What happens if we cancel?
The encoded workflow stops being maintained: protocol updates, regulatory changes, and new-MA support end with the retainer. There is no data lock-in, because there is no data stored anywhere to hold. You are not trapped by a database you cannot get out of; you simply stop receiving maintenance of the encoded rules.
See it running

Watch the gate hold and the note write itself.

The live demo runs on synthetic data only. Room a patient, hit a gate, and read the deterministic note it produces.