Treatment Plans
Skill Verifiziert AktivGenerate concise (3-4 page), focused medical treatment plans in LaTeX/PDF format for all clinical specialties. Supports general medical treatment, rehabilitation therapy, mental health care, chronic disease management, perioperative care, and pain management. Includes SMART goal frameworks, evidence-based interventions with minimal text citations, regulatory compliance (HIPAA), and professional formatting. Prioritizes brevity and clinical actionability.
To streamline the creation of accurate, compliant, and professionally formatted medical treatment plans for healthcare professionals.
Funktionen
- Generates 7 types of treatment plan templates (LaTeX)
- Provides validation scripts for quality and completeness
- Includes detailed reference guides on standards, goals, and regulations
- Supports AI-powered schematic generation for visual enhancements
- Promotes evidence-based and patient-centered care principles
Anwendungsfälle
- Creating individualized patient treatment plans
- Ensuring regulatory compliance (HIPAA) in documentation
- Standardizing medical documentation across specialties
- Improving clarity and actionability of patient care strategies
Nicht-Ziele
- Providing medical advice or diagnosis
- Replacing professional clinical judgment
- Automating patient interaction or care delivery
Workflow
- Select template type (interactive or direct)
- Generate template file
- Customize template with patient data and goals
- Compile to PDF using LaTeX
- Run validation scripts for quality check
- Review and finalize plan
- Implement plan and document progress
Praktiken
- Clinical documentation standards
- Evidence-based practice
- Patient-centered care
- Regulatory compliance
Voraussetzungen
- LaTeX distribution (e.g., TeX Live) for PDF compilation
- Python 3.8+ environment
- OpenRouter API key for AI schematic generation
- Optional: matplotlib for visual timeline generation
Code Execution
- info:LoggingThe scripts have verbose logging options but do not appear to implement a persistent audit log for actions performed.
Compliance
- info:GDPRWhile the script handles personal data (API key), it does not explicitly operate on patient treatment plan data itself. The user is responsible for HIPAA compliance of the generated plans.
Execution
- info:Pinned dependenciesThe scripts depend on requests and optionally matplotlib, but explicit pinning or lockfiles are not managed within the skill's bundle.
Installation
npx skills add K-Dense-AI/claude-scientific-skillsFührt das Vercel skills CLI (skills.sh) via npx aus — benötigt Node.js lokal und mindestens einen installierten skills-kompatiblen Agent (Claude Code, Cursor, Codex, …). Setzt voraus, dass das Repo dem agentskills.io-Format folgt.
Qualitätspunktzahl
VerifiziertVertrauenssignale
Ähnliche Erweiterungen
Prepare Inspection Readiness
100Prepare an organisation for regulatory inspection by assessing readiness against agency-specific focus areas (FDA, EMA, MHRA). Covers warning letter and 483 theme analysis, mock inspection protocols, document bundle preparation, inspection logistics, and response template creation. Use when a regulatory inspection has been announced or is anticipated, when a periodic self-assessment is due, when new systems have been implemented since the last inspection, or after a significant audit finding that may attract regulatory attention.
Master Claude for Legal
100Master-Skill für Rechtsteams, die Claude verwenden. Lädt die richtige Referenz für die Benutzerfrage (Konfiguration von Privilegien, MCP-Härtung, Verifizierung, lange Dokumente, Muster für Fachbereiche, Skill-Erstellung) und leitet an spezialisierte Starter-Skills weiter (NDA-Triage, Versionsvergleich, Besprechungszusammenfassung, Zitationsverifizierung, Status-Synthese). Wird automatisch aufgerufen, wenn der Benutzer juristische Arbeit, Verträge, Redlines, NDAs, Privilegien, Anwaltsgeheimnis, Gerichtsakten, Vernehmungen, regulatorische Compliance erwähnt oder fragt, wie Claude für eine Anwaltskanzlei oder ein internes Rechtsteam eingerichtet wird.
Perform Csv Assessment
99Perform a Computer Systems Validation (CSV) assessment following GAMP 5 methodology. Covers user requirements, risk assessment, IQ/OQ/PQ planning, traceability matrix creation, and validation summary reporting. Use when a new computerized system is being introduced in a GxP environment, when an existing validated system is undergoing significant change, when periodic revalidation is required, or when a regulatory inspection demands a validation gap analysis.
Manage Change Control
99Manage change control for validated computerized systems. Covers change request triage (emergency, standard, minor), impact assessment on validated state, revalidation scope determination, approval workflows, implementation tracking, and post-change verification. Use when a validated system requires a software upgrade, patch, or configuration change; when infrastructure changes affect validated systems; when a CAPA requires system modification; or when emergency changes need expedited approval and retrospective documentation.
Monitor Data Integrity
100Design and operate a data integrity monitoring programme based on ALCOA+ principles. Covers detective controls, audit trail review schedules, anomaly detection patterns (off-hours activity, sequential modifications, bulk changes), metrics dashboards, investigation triggers, and escalation matrix definition. Use when establishing a data integrity monitoring programme for GxP systems, preparing for inspections where data integrity is a focus area, after a data integrity incident requiring enhanced monitoring, or when implementing MHRA, WHO, or PIC/S guidance.
Investigate Capa Root Cause
100Investigate root causes and manage CAPAs (Corrective and Preventive Actions) for compliance deviations. Covers investigation method selection (5-Why, fishbone, fault tree), structured root cause analysis, corrective vs preventive action design, effectiveness verification, and trend analysis. Use when an audit finding requires a CAPA, when a deviation or incident occurs in a validated system, when a regulatory observation needs a formal response, when a data integrity anomaly requires investigation, or when recurring issues suggest a systemic root cause.