physical-therapy-ops
Turns a small findings JSON (patient initials only — never full names, DOBs, or other PHI) into a formatted plan-of-care markdown template with Subjective, Objective, Goals, and Plan sections. Use when drafting PT plan-of-care notes from evaluation findings that still need licensed clinician review and signature.
$ skillbank install physical-therapy-ops@1.0.0 # pins exactly 1.0.0 · README + changelog included
Physical Therapy Ops
Overview
After an evaluation you have findings and you need a plan-of-care document with the standard Subjective / Objective / Goals / Plan shape. This skill renders one from a small JSON file: patient initials, diagnosis area, subjective and objective lists, measurable goals, and treatment frequency. Anything that isn't one of those known keys is rejected, so full names and other PHI can't slip into the template through an unexpected field.
The output is a draft markdown file. It is explicitly marked as requiring clinician review and signature before it becomes part of a medical record.
Installation
1. Copy the physical-therapy-ops/ directory anywhere convenient. 2. Make the script executable (Unix):
chmod +x scripts/poc.py
No pip install needed — standard library only.
Configuration
Findings live in a JSON file you point at with --findings. Accepted keys (and only these keys):
{
"initials": "R.K.",
"diagnosis_area": "right shoulder (rotator cuff)",
"subjective": ["4/10 aching pain with overhead reaching"],
"objective": ["AROM: shoulder flexion 120 deg"],
"goals": ["Reduce pain to 2/10 or less within 4 weeks"],
"frequency": "2x/week for 6 weeks"
}
initials, diagnosis_area, goals, and frequency are required; subjective and objective are optional. Never put names, dates of birth, MRNs, or any other PHI in this file.
Inputs
scripts/poc.py --findings FILE [--out PATH]
| Flag | Required | Description | |--------------|----------|----------------------------------------------| | --findings | yes | Path to the findings JSON file. | | --out | no | Write markdown to PATH; default prints to stdout. |
Worked example
$ ./scripts/poc.py --findings examples/sample-findings.json --out poc.md
wrote poc.md
# Plan of Care
**Patient initials:** R.K.
**Diagnosis area:** right shoulder (rotator cuff)
**Frequency:** 2x/week for 6 weeks
**Drafted:** 2026-09-27
## Subjective
- Reports 4/10 aching pain in right shoulder, worse with overhead reaching
- Pain onset 3 weeks ago after moving furniture; no prior shoulder injury
- Sleep disturbed when rolling onto right side
## Objective
- AROM: right shoulder flexion 120 deg, abduction 100 deg; left WNL
- Mild tenderness over supraspinatus insertion; no swelling
- Empty-can test reproduces pain; drop-arm test negative
## Goals
- Reduce shoulder pain to 2/10 or less within 4 weeks
- Restore overhead reaching for daily tasks within 6 weeks
- Return to sleeping on right side without waking within 6 weeks
## Plan
- Treatment frequency: 2x/week for 6 weeks
- Re-evaluation in 30 days or sooner if status changes.
- [ ] Clinician review and signature
Not medical advice
This skill formats documentation you provide; it does not evaluate patients, choose treatments, or set goals for you. The generated document is a draft template only — a licensed clinician must review, edit as needed, and sign it before it becomes part of a medical record.
Version history
Changelog
1.0.0 — 2026-09-27
- Initial release:
scripts/poc.pyrenders a plan-of-care markdown template
(Subjective / Objective / Goals / Plan) from a findings JSON file; patient initials only, unknown keys rejected to keep PHI out.