| name | healthcare-orchestrator |
| description | Route a healthcare-software task to the right skill among four clinical specialists — PHI/PII privacy & access control, EMR/EHR encounter workflows, the CDSS safety engine (drug interactions, dose, NEWS2), and the patient-safety eval harness that gates deploys. USE WHEN building, reviewing, or shipping a clinical/health app but the specific concern (privacy vs. workflow vs. decision-support vs. release gate) hasn't been named. |
| cluster | healthcare |
| version | 1.0.0 |
Healthcare Orchestrator
The single entry skill for healthcare-software work. It locates the task on the lifecycle ×
concern map and delegates to one of four specialist spokes. The cross-cutting model every
clinical app shares — the three-layer data-protection contract (classify → control access →
audit), the patient-safety bias (alerts block, never silently pass), and the CRITICAL-vs-HIGH
gate thresholds — lives in healthcare-core; read it before designing data access, wiring a
CDSS alert, or configuring a deploy gate.
Cluster map
healthcare-phi-compliance — the data-protection implementation core: PHI/PII
classification, Row-Level Security, audit trails, encryption, and the common leak vectors
(logs, URLs, browser storage, service keys). Multi-jurisdiction: HIPAA (US), DISHA (India),
GDPR (EU).
healthcare-emr-patterns — EMR/EHR build patterns: the single-page encounter flow,
smart clinical templates, the locked-encounter + addendum model, prescription PDFs, and
accessibility-first medical UI.