Skill 詳細
healthcare-ops
Healthcare software operations and clinical workflow review.
使用前に確認
自動レビューは関連性のみを確認し、安全性や推奨を保証しません。使用前に出典の説明を読んでください。
SKILL.md
これはレビュー時に保存された抜粋です。完全で最新の内容は外部ソースを確認してください。
--- name: healthcare-ops description: "Review healthcare software for operational efficiency: appointment scheduling and resource allocation, clinical workflow burden (order entry clicks, documentation templates, alert fatigue), EHR/LIS/pharmacy/PACS integrations (HL7v2, FHIR, NCPDP SCRIPT, EDI 837/835), patient flow (ADT, bed management, wait times, throughput), quality reporting (CMS, HEDIS, MIPS), staff credentialing and workload balancing, and revenue cycle optimization. Use when auditing hospital, clinic, or health system software for operational bottlenecks and integration reliability." version: "2.0.0" category: review platforms: - CLAUDE_CODE --- You are in AUTONOMOUS MODE. Do NOT ask questions. Review the entire codebase from a healthcare operations perspective, identifying bottlenecks and optimization opportunities. TARGET: $ARGUMENTS If no arguments provided, review the entire project in the current working directory for operational efficiency. If a specific area is named (e.g., "scheduling", "patient flow", "integrations"), focus there but still note cross-cutting issues. ============================================================ PHASE 0: SYSTEM AND OPERATIONS CONTEXT ============================================================ Characterize the system from an operations standpoint: 1. Detect the tech stack and architecture. 2. Identify the operational domain: - Inpatient (hospital) vs outpatient (clinic) vs both - Single facility vs multi-facility - Specialty-specific or general 3. Map operational modules in the codebase: - Scheduling / appointments - Registration / check-in - Clinical workflow / order entry - Billing / revenue cycle - Reporting / analytics - Staff management / credentialing - Inventory / supply chain - Communication / messaging 4. Identify integration points with external systems: - EHR systems (Epic, Cerner, Meditech, etc.) - Lab information systems (LIS) - Pharmacy systems - Radiology (PACS/RIS) - Billing / claims clearinghouses - State registries (immunization, disease reporting) ============================================================ PHASE 1: SCHEDULING AND RESOURCE ALLOCATION ============================================================ Review scheduling implementation for operational efficiency: APPOINTMENT SCHEDULING: - Check appointment data model: does it capture provider, location, type, duration, status, patient, reason, recurring flag? - Verify scheduling constraints: provider availability, room availability, equipment availability, patient preferences. - Check for overbooking support (configurable overbooking rules by provider/type). - Verify wait-list management implementation. - Check for no-show tracking and predictive no-show modeling. - Verify cancellation and rescheduling workflows. RESOURCE ALLOCATION: - Check for room/bed assignment logic. - Verify equipment scheduling (shared resources across providers/departments). - Check for provider template management (recurring availability patterns). - Verify block scheduling support (surgical blocks, procedure rooms). - Check for resource conflict detection and resolution. CAPACITY PLANNING: - Check for capacity utilization tracking. - Verify appointment type duration analytics (actual vs scheduled). - Check for demand forecasting features (seasonal patterns, growth). - Verify bottleneck identification capabilities. OPTIMIZATION OPPORTUNITIES: - Flag scheduling logic that is purely FIFO without optimization. - Check for batch scheduling capabilities (multiple related appointments). - Verify support for multi-resource scheduling (provider + room + equipment). - Check for travel time consideration in multi-location practices. ============================================================ PHASE 2: CLINICAL WORKFLOW EFFICIENCY ============================================================ Review clinical workflows for documentation burden and throughput: ORDER ENTRYGitHub で全文を読む (外部ページ)