Therapy Documentation Platform

A system-driven experience that still feels comfortable, built so the rules stop the slips that cause errors later.

Role
Solo designer
Effort
A few days per delivery
Platform
Web and tablet
Domain
US therapy, Medicare

Under NDA, so names and screens here are re-created.

  • 3structures

    Explored for plan templates before choosing one

  • 1thread

    Every record ties back to the one before it

In therapy documentation every record has to connect. The evaluation justifies the plan of care, the plan justifies each session, and each note shows progress. Clinicians call this the golden thread.

When a link is missing, the record can be rejected at audit, long after the session happened. Clinicians document between patients and can't be expected to hold every rule in their heads.

  • Medicare documentation rules are not negotiable.
  • Clinicians have minutes, not hours, per note.
  • Extend the product's existing design system instead of adding one-off patterns.

Across several modules, the same few decisions kept coming back. In summary.

01 Let the system carry the rules

The order of records is a property of the product, not something a clinician must remember. A later record opens only when the earlier ones are complete.

02 Guide, don't just block

For plan templates I explored three structures before choosing a guided flow. When something is missing, the screen says what, why it matters, and how to fix it, next to where the clinician is working.

03 Keep distinct records distinct

Records that look alike but mean different things at audit never share a form. It costs a little duplication and removes a whole class of mix-ups.

04 Comfortable by default

Compliance stays strict underneath. On the surface the work is short steps, plain language and nothing to configure every session.

Try to start a daily note from New document. The screen stops you, says why, and shows the next step.

app.strandhealth.example/patients/arthur-bell/pt
PatientsArthur BellPT case Share
AB

Arthur Bell Active

78 · Male · Room 214 · Admitted 3 March

  1. Initial evaluationSigned

    M. Chen, PT · 3 impairments, 3 long-term goals

  2. Plan of care Needs physician certification Sent to Dr. A. Rahman Certified

    3× a week for 4 weeks · 12 visits · until 1 April

    Dr. A. Rahman hasn't certified this plan yet.
  3. Daily notesLockedLockedOpen

    Opens when the plan of care is certified, so every note ties back to a signed plan.

    Waiting on certification.

    12 visits planned. Start today's note from New document.

  4. Progress note

Re-created for this page. It shows the pattern, with sample data.

The states I check on work like this, because nobody asks for them until they break.

  • Unsigned noteWork saved but not yet signed
  • Certification expiredThe plan has lapsed
  • Review dueA periodic re-certification is coming up
  • Co-signature pendingWaiting on a second clinician
  • Missing linkA record with nothing to tie back to
  • Out-of-order records are designed out. The product won't let them be created.
  • Three template structures were explored and compared before one was chosen.
  • Features were released with written release notes for the clinical teams.

These results weren't tracked on this project. With access, these are the numbers I'd watch.

  • Notes rejected at audit
  • Time to complete a note
  • Unsigned notes past their deadline

Next: Bring the same guard-and-guide pattern to the remaining modules, and measure where clinicians still slow down.

Next case Clinical Copilot Overlay