treatment-plans
Category: clinical-and-health · License: MIT · Version: 2.2 · Includes scripts
Tags: treatment plans, clinical documentation, medicine, healthcare
When to use it
Format and structurally validate local treatment-plan documentation after clinical decisions have already been supplied and verified by authorized licensed professionals. Use for source traceability, clinician-authored intervention records, goals and checkpoints, shared-decision records, reconciliation handoffs, and release gates—not for clinical decision-making.Example requests
Ask your agent in plain language, for example:- “I have a synthetic treatment-plan package from our QA team. Can you run the structural validator on it and tell me what’s blocking release?”
- “I’m building a de-identified research handoff for our oncology pathway study. I have ./pkg/transition_reconciliation.json and ./pkg/goals_checkpoints.json. The validator is complaining about ‘unknown field’ and ‘duplicate key’ errors, and the checkpoint dates aren’t being scheduled. Can you help me fix the files so the derived schedule comes out right?”
- “Our clinic wants a consistent, traceable record of what the clinicians already decided for each patient’s plan: who authored each intervention, who verified it, the source version, the shared-decision discussion and who takes over at discharge. How should I structure that as local files?”
Install
/plugin marketplace add KalarisLabs/research-agent-skills and install the whole clinical-and-health category with /plugin install clinical-and-health@research-agent-skills.