The 3-Minute HEP Workflow: Eliminating After-Hours Charting

Why does home-program documentation end up in your evening?

Because building one requires leaving the clinical work to do a stretch of document assembly — and assembly is the first thing that gets pushed past the end of the day. The clinical decision takes seconds; a therapist finishing a session already knows what the child should be doing at home. What takes time is everything after that decision: locating an image that matches the exercise, pulling it out of a handout or PDF, rewriting the instructions in language a parent will actually follow, and formatting the result into something you can hand over or email.

In our interviews with pediatric clinicians, this came up more than any other operational complaint. One described the current process exactly: “Right now I’m screenshotting parts of PDFs, putting them into a Word document, and it’s taking forever.”

None of that is clinical reasoning. It is document production, and it lands in the evening because there is no room for it between back-to-back sessions. The programs that do get built under that pressure tend to be the generic ones — whatever was fastest to assemble — which is its own quiet cost.

What does a three-minute HEP actually look like?

Three steps, all of them inside the session rather than after it. Being precise about the claim: three minutes is the window this workflow is designed to fit into — the tail end of a visit, while the family is still in the room. It is a design target describing the shape of the work, not a stopwatch average we have measured and published. When we have timing data from clinics running it, we’ll publish that as our data and say so.

1. Start from a library, not a blank page. The single biggest time sink is creating content that already exists. Beginning from a pediatric exercise library means the therapist is editing rather than authoring.
2. Dictate the changes. Adjusting a protocol by speaking is faster than typing it, and it happens while you’re still facing the patient. As one clinician put it to us: “I just love that you can actually talk and your words just look pretty. You just speak, and that’s what we’re all hoping for: less typing.”
3. Send before they leave. A program delivered while the family is still present gets explained, demonstrated, and confirmed. One sent that evening arrives without any of that context.

The structural point underneath all three: anything deferred to after hours is the thing that gets deferred again. A workflow that depends on the therapist finding time later is a workflow that degrades under a full caseload, which is precisely when the home program matters most.

How do you keep the program custom without rebuilding it each time?

Start from something and change it — the opposite of both a blank page and a fixed protocol. The two common failures sit at opposite ends. A blank page means every program is authored from scratch, so it takes too long and consistency depends on who built it. A rigid template means every child gets the same six exercises regardless of presentation, which therapists correctly refuse to use.

The workable middle is a library that is specific enough to start from and editable enough to make genuinely individual. In pediatrics that specificity has to be developmental, not just anatomical — the exercise for a toddler with torticollis and the exercise for an eight-year-old post-op are not the same instruction with a different rep count. A pediatric PT put the mismatch this way: “I’m telling a six-year-old to do an exercise that a grandma is doing. It’s the same exercise, but it’s not translating nicely for patient buy-in.”

This is also why adapted adult content underperforms even when the biomechanics are right. The movement is correct; the delivery isn’t aimed at the person doing it or the parent supervising it.

Where does the data go — and why do silos form?

A home program sent as a PDF is a one-way message: the moment it leaves your hands, you stop learning anything from it. That’s the silo. You can’t tell whether it was opened, whether the child attempted it, which exercises were skipped, or whether something hurt. The next session opens with the same question every time — how did it go? — answered from memory by a parent recalling the whole interval at once.

Closing that loop doesn’t require asking families to do more. It requires making the return signal trivial: effort, pain, and completion logged in seconds from the app or straight from a text message, so the data comes back as a byproduct of doing the exercises rather than as separate homework.

What that changes clinically is the start of the next visit. Instead of reconstructing the interval, the adherence pattern is already there and flagged where it matters — which is the difference between opening the visit gathering history and opening it treating. Clinicians ask for this directly. One told us they wanted patients to be able to respond to an exercise: “like, ‘hey, this was really hard for me’ — so then I kind of just assist them a little bit more.” That is a feedback channel, and a PDF cannot carry it.

How does this connect to RTM billing?

It’s the same data — but be careful which minutes you count, because this is where clinics create denials. The adherence signal that makes your next session better is also the signal Remote Therapeutic Monitoring pays for. Once a family is logging, those qualifying days accumulate toward the device-supply code, and your between-visit review time accumulates toward treatment management.

The trap is the part clinics get wrong. Time spent building the home program during a visit is visit time. It belongs to the billable encounter, and it cannot also be counted toward RTM’s 20-minute treatment-management threshold — the same no-double-dipping rule that applies when an in-person conversation serves as RTM’s required interactive communication. Counting the same minutes twice is among the more predictable ways to lose a claim on audit.

What legitimately counts toward RTM is the work that happens between visits: reviewing incoming data, adjusting the program in response to what it shows, and the live check-in with the family. In other words, the workflow described above doesn’t manufacture RTM minutes — it produces the data that makes the between-visit review worth doing, and that review is the billable part. For the full picture of which code each month’s data earns, see the RTM guide, the code-by-code breakdown, or the launch playbook if you’re building the program from scratch.

What this workflow doesn’t fix

Worth being straight about the limits.

• It doesn’t make a family engaged. It removes friction for families who are willing. A caregiver with no capacity this month is a clinical and social problem, not a software one.
• It doesn’t replace clinical judgment. The library is a starting point. What the child should actually be doing is the therapist’s call, and it should stay that way.
• It doesn’t generate billable time on its own. RTM pays for between-visit review, not for faster documentation during a visit.
• It doesn’t come with an adherence guarantee. Anyone quoting you a specific improvement figure for your caseload is quoting someone else’s clinic.

The honest version of the claim is narrower and more defensible: a home program that gets built in the room, delivered before the family leaves, and logged in seconds gives you something a PDF never does — a picture of the week that’s waiting for you before the next session starts. What that’s worth is best answered by a pilot in your own clinic. If you’d like to run one, talk to us.