Start with the handoffs
Observe where patient details are copied, where a queue state becomes ambiguous, and where the next person has to ask for context again.
The first useful product boundary is a complete clinic day, not a long feature list.
Questions to review
- Who owns the patient match?
- Where is the current queue state written?
- What does the practitioner need before opening the encounter?
- How is the next step shared with the patient?
Name the exception states
A clinic workflow is not complete when the happy path works. Write down what happens when a patient is duplicated, a provider is unavailable, a payment is uncertain, or the connection drops.
Each exception needs a readable state, a safe preservation rule, and a next action.
Measure the baseline
Record time, re-entry, wait, failed messages, unsigned drafts, and handover defects before changing the workflow. A faster screen that loses record trust is not an improvement.
