Quill
Stop Charting After Dinner
Quill listens to the consultation with the patient's consent and drafts a structured note in your own format. You review it, edit what needs editing, and sign. Nothing enters the record until you put your name on it.

The consultation is already the documentation
Most of what belongs in a clinical note is said out loud during the visit. The work is not deciding what to write, it is typing it a second time, hours later, from memory and a few scribbled prompts.
Quill removes that second pass. Speech is converted to text, and the model identifies symptoms, diagnoses, medications, examination findings and the treatment plan, then assembles them into the note structure you already use.
What arrives on your screen is a draft, not a record. You are the one who reviews, corrects and signs, and the signed note is what everything downstream, including Tally's coding recommendations, actually reads.
Capabilities
What's included
The note is drafted by the time the visit ends
Your format, not a template
Notes are assembled into the structure each provider already uses, and the preferences are held per clinician rather than per practice.
Structured, not narrative
Symptoms, diagnoses, medications, findings and plan are identified as discrete elements, which is what makes the note usable downstream.
Consent handled properly
Capture runs through a consent workflow, and audio is handled under the same HIPAA safeguards as every other piece of PHI we touch.
Feeds the rest of the platform
The signed note is the input for coding recommendations, chart intelligence, risk and quality review, and the documentation behind any later appeal.
Why it matters
The outcomes practices actually measure
We are evaluated on the numbers that change in your operation, not on features shipped or tickets closed.
- Time back for clinicians
- The main benefit is straightforward: less manual note-writing after each visit, which is the single largest source of unpaid clinical admin.
- Documentation that supports the claim
- Because the note is structured at the point of creation, the specificity coding needs is present from the start rather than chased afterwards.
- The provider stays in control
- Nothing reaches the record unsigned. The AI drafts, the clinician decides, and that boundary does not move.
- Consistency across a group
- Note structure stays consistent across providers and locations without forcing everyone onto one template.
How it works
What working with us looks like
- 1
Start the session
The provider starts documentation before or during the consultation. Capture is explicit, never ambient-by-default.
- 2
Capture with consent
The conversation is captured under your consent workflow, with the audio handled under the safeguards described in our HIPAA notice.
- 3
Structure the content
Speech is converted to text, and symptoms, diagnoses, medications, examination findings and treatment plans are identified and placed into your note format.
- 4
Review and sign
The provider reviews and edits the draft and signs it. Only a signed note becomes part of the official record.
Frequently paired with
FAQ
Quill, frequently asked questions questions
- Does the provider still have to review the note?
- Yes, always. Quill produces a draft. A clinician reviews, edits and signs it, and only the signed note becomes part of the record. There is no configuration that removes that step.
- What happens to the audio?
- Audio is captured under your consent workflow and handled under the HIPAA safeguards described in our HIPAA compliance notice: encrypted in transit and at rest, access-controlled and audit-logged.
- Does it work for my specialty?
- Note structure is configured per specialty and then per provider, because a behavioural health note and an orthopaedic note have almost nothing structurally in common.
- What does Quill connect to?
- It runs inside SpeedCare natively. Against a third-party EHR it connects through our interoperability services, so the signed note lands in your existing record.
We're here to help
Ready to see what your revenue cycle could be doing?
Start wherever makes sense: a demo, a free assessment, or a straight conversation with someone who does this every day.
