shift-handover-summarizer
Generate structured shift handover summaries from EHR records, highlighting critical events, vital sign changes, and pending tasks for incoming clinical staff.
Best use case
shift-handover-summarizer is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Generate structured shift handover summaries from EHR records, highlighting critical events, vital sign changes, and pending tasks for incoming clinical staff.
Teams using shift-handover-summarizer should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/shift-handover-summarizer/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How shift-handover-summarizer Compares
| Feature / Agent | shift-handover-summarizer | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Generate structured shift handover summaries from EHR records, highlighting critical events, vital sign changes, and pending tasks for incoming clinical staff.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
> **Source**: [https://github.com/aipoch/medical-research-skills](https://github.com/aipoch/medical-research-skills) # Shift Handover Summarizer Generate structured shift handover summaries from EHR updates, highlighting critical events that occurred during the shift. > **Clinical Disclaimer:** This tool generates summaries for handover support only. All clinical decisions must be verified by qualified medical staff. Patient data must comply with applicable data protection regulations (e.g., HIPAA). ## Quick Check ```bash python -m py_compile scripts/main.py python scripts/main.py --help ``` ## When to Use - Use this skill when generating a structured handover summary from EHR records at the end of a clinical shift. - Use this skill when prioritizing patients by event severity for incoming staff. - Do not use this skill as a substitute for direct clinical handover, real-time patient assessment, or emergency triage. ## Workflow 1. Confirm the patient records file, shift start/end times, and optional department filter. 2. Validate that the input records are within the declared shift time range. 3. **Timezone validation:** If `--shift-start` or `--shift-end` lacks a timezone offset (e.g., `2026-02-06T00:00:00` without `Z` or `+HH:MM`), emit a warning: "Shift times appear to lack a timezone offset. Assuming UTC. Specify timezone explicitly (e.g., `2026-02-06T00:00:00+08:00`) to avoid incorrect event filtering." 4. Run the summarizer script or apply the manual extraction path. 5. Return a structured summary with patients ranked by priority, key events, and pending tasks. 6. If inputs are incomplete, state exactly which fields are missing and request only the minimum additional information. ## Usage ```text python scripts/main.py \ --records data/shift_records.json \ --shift-start "2026-02-06T00:00:00Z" \ --shift-end "2026-02-06T08:00:00Z" \ --department "Cardiology" \ --output summary.json ``` ## Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `--records` | file path | Yes | JSON file of EHR records for the shift | | `--shift-start` | ISO 8601 | Yes | Shift start time | | `--shift-end` | ISO 8601 | Yes | Shift end time | | `--department` | string | No | Department filter | | `--output` | file path | No | Output file path (default: stdout) | | `--no-vitals` | flag | No | Exclude vital signs summary | ## Event Priority Levels | Priority | Event Type | |----------|-----------| | High | Resuscitation, deterioration, serious complications, abnormal vitals | | Medium | New symptoms, abnormal findings, medication adjustments, special procedures | | Low | Routine treatment, condition improvement, daily care | ## Output - Shift summary with total patients and critical patient count - Per-patient priority ranking, key events, vitals summary, medication summary, and pending tasks - Plain-text handover narrative ## Scope Boundaries - This skill processes structured EHR records; it does not access live hospital systems. - Event classification is based on preset thresholds and keywords; adjust thresholds for department-specific needs. - This skill does not replace direct verbal handover or physician sign-off. ## Stress-Case Rules For complex multi-constraint requests, always include these explicit blocks: 1. Assumptions 2. Shift Period and Inputs Used 3. Summary Output 4. Critical Flags 5. Risks and Manual Checks ## Error Handling - If required inputs are missing, state exactly which fields are missing and request only the minimum additional information. - If the task goes outside the documented scope, stop instead of guessing or silently widening the assignment. - If `scripts/main.py` fails, report the failure point, summarize what still can be completed safely, and provide a manual fallback. - Do not fabricate patient data, clinical events, or execution outcomes. ## Input Validation This skill accepts: a structured EHR records file with shift start and end times for handover summary generation. If the request does not involve shift handover summary generation from EHR records — for example, asking for real-time patient monitoring, clinical diagnosis, or direct treatment recommendations — do not proceed with the workflow. Instead respond: > "shift-handover-summarizer is designed to generate structured handover summaries from EHR records. Your request appears to be outside this scope. Please provide a records file and shift times, or use a more appropriate clinical tool." ## Response Template Use the following fixed structure for non-trivial requests: 1. Objective 2. Inputs Received 3. Assumptions 4. Workflow 5. Deliverable 6. Risks and Limits 7. Next Checks If the request is simple, you may compress the structure, but still keep assumptions and limits explicit when they affect correctness.
Related Skills
note-summarizer
Organize study notes into a structured knowledge-point outline and export to a .docx summary when you need a shareable, hierarchical document from Word/PPT/Text/Markdown inputs.
ib-summarizer
Summarize core safety information from Investigator's Brochures for clinical.
abstract-summarizer
Transform lengthy academic papers into concise, structured 250-word abstracts.
skill-auditor
A comprehensive auditor for any agent skill — including Manus, OpenClaw/ClawHub, Claude, LobeHub, or custom SKILL.md-based skills. Use this skill whenever a user wants to evaluate, audit, review, score, or quality-check an agent skill before publishing, updating, or deploying. Covers two hard veto gates (structural redlines + research integrity redlines), static quality scoring across 25 criteria (ISO 25010 + OpenSSF + Agent), dynamic test input generation, multi-mode execution testing, multi-layer output evaluation with five specialized category rubrics (Evidence Insight / Protocol Design / Data Analysis / Academic Writing / Other), a Research Veto that applies to all four research categories, human eval viewer generation, actionable P0/P1/P2 optimization recommendations, and automatic skill improvement that outputs a polished, production-ready SKILL.md. Also use whenever a user says "audit my skill", "evaluate my skill", "improve my skill", or wants a corrected version after evaluation.
two-sample-mr-research-planner
Generates complete two-sample Mendelian randomization (MR) research designs from a user-provided research direction. Use when users want to design, plan, or build a study using two-sample MR to test causal relationships. Triggers:"design a two-sample MR study", "build a publishable MR paper", "test whether this biomarker causally affects this disease", "generate Lite/Standard/Advanced MR plans", "screen multiple exposures with MR", "bidirectional MR design", "causal inference using GWAS summary statistics", or "I want to study X and Y using MR". Always outputs four workload configurations (Lite / Standard / Advanced / Publication+) with a recommended primary plan, step-by-step workflow, figure plan, validation strategy, minimal executable version, and publication upgrade path.
research-proposal-generator
Generates a comprehensive research proposal design based on input literature, including hypothesis, mechanism verification, and budget. Use when the user wants to design a research project from a paper.
research-grants
Write competitive research proposals for NSF, NIH, DOE, DARPA, and Taiwan's NSTC when you need agency-compliant narratives, budgets, and review-criteria alignment for a specific solicitation/FOA/BAA.
protocol-standardization
Standardize fragmented experimental steps into reproducible protocol documents when you need method organization, lab SOP drafting, or cross-operator reproducibility; missing parameters must be explicitly marked as "To be supplemented/Not provided".
prospero-registration-helper
Assists researchers in generating PROSPERO registration content for meta-analyses from a title and optional protocol. Use when the user wants to draft a PROSPERO registration form.
non-tumor-ml-research-planner
Generates complete non-tumor biomedical machine learning research designs from a user-provided research direction. Always use this skill when users want to plan bioinformatics + ML papers for non-cancer diseases (metabolic, cardiovascular, kidney, inflammatory, autoimmune, infectious, neurological, endocrine, wound healing, chronic multifactor), design diagnostic biomarker studies, combine GEO datasets with feature selection and ML modeling, or generate Lite/Standard/Advanced/Publication+ workload plans. Trigger for:"non-tumor ML study", "bioinformatics paper outside oncology", "key genes and diagnostic model for a disease", "pyroptosis/ferroptosis/senescence/autophagy + disease", "GEO datasets + machine learning", "RF + LASSO diagnostic model", "DEG + feature selection + validation", "immune infiltration + biomarker", "non-cancer biomarker paper". Trigger even for casual phrasings like "I want to study X using machine learning", "help me design a non-tumor bioinformatics paper", or "how do I build a diagnostic model for disease Y".
network-tox-docking-research-planner
Generates complete network toxicology + molecular docking research designs from a user-provided toxicant and disease/phenotype. Always use this skill when users want to investigate how an environmental toxicant, endocrine disruptor, heavy metal, food contaminant, pharmaceutical residue, or consumer product chemical may contribute to a disease through shared molecular targets, hub genes, pathways, and docking evidence. Trigger for:"network toxicology study", "toxicology mechanism paper", "target prediction + PPI + docking", "environmental pollutant and disease mechanism", "hub genes and docking for toxicant", "Lite/Standard/Advanced toxicology plan", "CTD + SwissTargetPrediction + GeneCards + STRING", "CB-Dock2 docking study", "triclosan/BPA/cadmium/PFAS + disease". Also triggers for Chinese phrasings:"网络毒理学研究设计"、"毒物机制论文"、"靶点预测+PPI+对接"、"环境污染物与疾病机制". Trigger even for casual phrasings like "I want to study how chemical X affects disease Y" or "help me design a toxicology paper". Always output four workload configurations (Lite / Standard / Advanced / Publication+) with a recommended primary plan, step-by-step workflow, figure plan, validation strategy, minimal executable version, and publication upgrade path.
meta-protocol-writer
Generates a PROSPERO-compliant Meta-analysis protocol based on Title and PICOS. Use when the user wants to write a protocol for a systematic review or meta-analysis.