Therapy Note Sharing Controls
Design role-based access controls for therapy notes that separate patient-facing summaries from restricted clinical documentation.
The brief
Understand the problem
Background
Therapy records may include a shared care plan, progress summary, private psychotherapy notes, third-party information, and legally required disclosures. Treating every note as one document creates privacy and continuity risks.
User context
Dr. Chen is documenting a session for a patient who can access visit summaries. A family member is involved in care but may see only the agreed safety plan, not the full clinical note.
Product problem
Clinicians need precise sharing controls and a clear preview, while patients need to understand which records exist and how to request access or correction.
Objective
Create note classification, audience selection, disclosure preview, and access-request handling for behavioral health documentation.
What to design
Define the experience
Required experience
- Classify sections while writing a therapy note
- Choose audiences by section and purpose
- Preview each recipient's exact view
- Respond to a patient access or correction request
Screens and states
- Structured note editor
- Audience controls
- Recipient preview
- Access request case
Core user flow
Follow the critical path
- 01
Dr. Chen writes a shared progress summary and restricted clinical detail
- 02
She grants the family member access only to the safety plan
- 03
The preview reveals that one copied sentence would expose third-party information
- 04
She corrects the section and publishes with an audit record
Product rules
Requirements and constraints
Requirements
- Support section-level classification with safe defaults
- Explain legal and organizational access rules in context
- Preview the final patient, proxy, and care-team views
- Audit viewing, sharing, amendment, and disclosure events
Constraints
- Restricted-note rules vary by jurisdiction
- Copying text cannot silently inherit a broader audience
- Emergency disclosure needs a documented purpose and authorized path
Reality check
States worth considering
Finish line
What to deliver
- Four desktop-first screens with a section-level permission model
If you want more
Optional extensions
Optional direction
Visual resources
Use these as a starting constraint if you want one. They are not part of the required solution.
Libre Baskerville & Source Sans Pro
Clear interface writing gives people the confidence to understand what changed and decide what to do next.
Libre Baskerville & Source Sans Pro
Clear interface writing gives people the confidence to understand what changed and decide what to do next.