Practice tools that sound like the people using them.

Each practice had its own rules, templates and way of communicating. The tools had to carry that context into everyday drafting while leaving clinicians in charge of approval. I built them to HIPAA requirements.

The useful design question was often simple: what is missing from this request? If the answer mattered, the tool paused and asked for clarification.

I built around the practices’ working context. In the intake and reply tools, policies, past messages and communication preferences guide the draft. Missing details and policy conflicts prompt clarification before writing. The clinician reviews and approves the result.

When a request is ambiguous or conflicts with a policy, the assistant stops to clarify before writing. That pause is part of the tool’s design.

The intake and reply tools support one clinician’s daily correspondence in the practice’s own voice, with clarification for incomplete requests and approval before anything is sent.

One clinician learned to maintain and extend the tools, so updates can happen close to the work as the practice changes.

The tools follow the practice's working rules, with review built into the drafting process.

1. Bring the working context. The practice's rules, templates and communication preferences give the tool a starting point.
2. Clarify what is missing. When a request lacks an essential detail or conflicts with a policy, the tool asks before writing.
3. Prepare a draft. The response follows the task and the practice's voice, ready for the clinician to review.
4. Review and approve. The clinician checks the result and decides what is ready to use or send.

I built around how each clinician already worked, then trained one clinician to maintain and extend the tools. That makes the handoff part of the project.

For a client with recurring correspondence or internal guidance, I start by understanding the examples, rules and decisions people use. Together, we can identify a useful first task and where a person should review the result.

If the same requests keep turning into another document or reply, bring an example of that work. We can explore what a useful drafting tool would need to know.