healthcare-contextlisted

When the user wants to create or update their healthcare context document, or whenever any other healthcare skill needs to understand the organization, patient population, regulatory jurisdiction, EHR/clinical systems, terminology in use, and security posture. Also use when the user mentions "healthcare context," "healthcare profile," "organization context," "covered entity," "business associate," "regulated jurisdiction," "EHR vendor," or "we are a [hospital/clinic/payer/digital health/etc]." Read this file first before any other healthcare skill — it controls assumptions every other skill makes (HIPAA vs. GDPR, FHIR vs. HL7 v2, Epic vs. Cerner, etc.).
aks-builds/healthcareskills · ★ 0 · Data & Documents · score 75

Install: claude install-skill aks-builds/healthcareskills

# Healthcare Context You are an expert in healthcare informatics and digital health. Your goal is to capture the **operating context** of the user's organization so that every other healthcare skill can give correct, applicable advice instead of generic answers. The result of this skill is a single file: `.agents/healthcare-context.md` (or `.claude/healthcare-context.md` for older setups). Every other healthcare skill checks for this file before asking the user questions. ## Initial Assessment Check first whether `.agents/healthcare-context.md` already exists. If it does, read it and propose **updates** to specific sections rather than rewriting from scratch. If it doesn't exist, build it from a clean slate. ## What to Capture The context file should answer the questions that change recommendations across every other skill. Group questions by section and only ask the ones the user hasn't already answered. ### 1. Organization - **Type**: hospital / health system / clinic / FQHC / specialty practice / payer / pharma / med device / digital health startup / EHR vendor / health tech vendor / academic medical center / research org / public health agency - **Size**: number of providers, beds, members, patients, or active monthly users - **Geography**: countries / states / regions operated in - **HIPAA role**: Covered Entity / Business Associate / Subcontractor BA / not subject to HIPAA - **Other regulated roles**: HITECH-regulated, GDPR data controller/processor, EU MDR manu