How LocalScribe Works with SPRY
If you use SPRY, LocalScribe usually fits in as a rehab drafting step that starts with SOAP and then gets more customized as the workflow becomes more discipline-specific. SPRY centers structured SOAP documentation, AI-generated SOAP notes, customizable templates, macros, and specialty support across rehab settings. That makes it a hybrid platform. Built-in LocalScribe SOAP-style templates are a strong starting point for standard users, but many clinics will want a LocalScribe custom template for a closer match. (sprypt.com)
The main setup choice
If your clinic uses a straightforward SOAP workflow, start with a built-in LocalScribe SOAP-style template. If your team uses SPRY’s specialty-specific templates, macros, or a more customized documentation structure, the better setup is to mirror that structure in a LocalScribe custom template. That means using the same headers, the same order, and, when needed, the same nested subheaders your clinic already documents with. (sprypt.com)
Daily notes and SOAP notes
This is the clearest fit. SPRY strongly centers structured SOAP workflows across therapy disciplines, so a standard LocalScribe SOAP-style template is often a very good starting point. If the clinic’s daily-note structure is more specialized, build a matching LocalScribe custom template instead. (sprypt.com)
These custom-template examples show the section headers and the instructions you would give the model for each section.
A practical daily-note template in LocalScribe might use:
Subjective: Include the patient or caregiver report, current concerns, symptom change, and relevant carryover since the last visit.
Objective: Document interventions completed, measurable performance, observable responses, cueing level, and treatment data.
Assessment: Summarize clinical interpretation of the session, progress, barriers, and skilled reasoning.
Plan: State the next treatment focus, home program or carryover, and any needed follow-up.
Evaluations and assessments
This is where custom templates usually matter more. SPRY’s assessment content emphasizes PT-specific assessments, functional outcome measures, musculoskeletal assessment elements, and other discipline-specific clinical content. That makes evaluations and assessments a stronger LocalScribe custom-template category rather than something best forced into one generic format. (sprypt.com)
A practical evaluation or assessment template in LocalScribe might use:
Referral and reason for evaluation: State the referral concern, diagnosis context, and purpose of the evaluation.
Background and history: Include relevant medical, developmental, therapy, injury, and functional history.
Objective findings and measures: Document exam findings, test results, scores, severity, and other measurable clinical data.
Functional impact: Summarize strengths, deficits, participation limits, and real-world functional effect.
Clinical assessment: Interpret the findings, identify priority problems, and describe clinical significance.
Plan and recommendations: Document treatment recommendations, frequency, goals, and next steps.
Plan of care and progress reporting
This is another strong custom-template category. SPRY ties documentation closely to progress reporting, treatment tracking, recovery planning, and specialty-specific measurable metrics. If the clinic wants its usual structure preserved, it makes sense to create a LocalScribe custom template that mirrors that plan or progress workflow rather than relying on a broad generic note. (sprypt.com)
A practical plan or progress template in LocalScribe might use:
Problem areas: State the main deficits, impairments, or treatment targets.
Goals: Write clear, measurable goals in discipline-appropriate language.
Progress toward goals: Summarize measurable improvement, lack of progress, or barriers to change.
Interventions: Describe the skilled interventions and treatment approach being used.
Frequency and next steps: Document expected visit frequency, review timing, and next treatment focus.
PT, OT, and SLP variation
This matters more in SPRY than in many general EHRs because the documentation focus clearly shifts by discipline. OT documentation emphasizes functional skills and patient-centered goals, PT emphasizes measurable physical metrics and recovery planning, and SLP workflows emphasize speech-specific clinical elements and customizable assessment fields. That means discipline-specific LocalScribe templates matter here, but so do custom terminology and test-reference tools. In PT, OT, and SLP workflows, getting the template shape right is only part of the job. The draft also needs to reflect the right specialty language, outcome measures, and assessment terms for the discipline. When that is true, LocalScribe’s custom terminology and test-reference tools become especially useful, because they help the draft stay closer to the language and measure-based reasoning the clinician actually documents with.
What to put into LocalScribe
Use the same source material you would normally rely on while writing manually. That can include typed shorthand, pasted text, dictation, ambient or session recording, and attachments such as intake paperwork, prior evaluations, screeners, outcome measures, referrals, and other source documents, plus clinician observations not captured elsewhere. LocalScribe is built to turn that source material into a structured draft.
Bottom line
For SPRY, built-in LocalScribe SOAP-style templates are often a strong starting point. Evaluations, specialty-specific documentation, and structured progress or plan workflows are often better handled with a LocalScribe custom template that mirrors the clinic’s actual SPRY structure.
Subscribe for future posts
If you want new writing at the intersection of AI and psychology, ethics, and implementation of AI in clinical practice, subscribe on Substack.
The views expressed here are my own and do not necessarily reflect the views of any current or future employer, training site, academic institution, or affiliated organization.