HE
healthcare-ai-research-guardrails
Use this skill when researching, drafting, reviewing, or building healthcare, wellness, clinical, medical-device, patient-support, health-content, or health-data AI workflows that require source quality, privacy, non-diagnostic boundaries, human review, and regulated-domain guardrails.
Install
mkdir -p .claude/skills/healthcare-ai-research-guardrails && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13508" && unzip -o skill.zip -d .claude/skills/healthcare-ai-research-guardrails && rm skill.zipInstalls to .claude/skills/healthcare-ai-research-guardrails
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use this skill when researching, drafting, reviewing, or building healthcare, wellness, clinical, medical-device, patient-support, health-content, or health-data AI workflows that require source quality, privacy, non-diagnostic boundaries, human review, and regulated-domain guardrails.286 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
About this skill
Healthcare AI Research Guardrails
Support healthcare work with evidence handling and safety boundaries; do not act as a clinician or medical-device authority.
Workflow
- Classify the task: general health content, patient education, clinical workflow support, medical-device/software concern, privacy/data handling, or operational healthcare tooling.
- Identify the audience and risk level: consumer, patient, caregiver, clinician, admin staff, developer, regulator, or internal reviewer.
- Prefer primary and authoritative sources: official regulators, public-health bodies, clinical guidelines, peer-reviewed evidence, and product documentation.
- Separate facts, assumptions, uncertainty, and user-specific advice. Avoid diagnosis, treatment selection, medication changes, or emergency triage decisions.
- Check privacy boundaries before using any health data: minimum necessary data, consent, de-identification, retention, access controls, audit logs, and local policy.
- For AI workflows, define human review, escalation, fallback, disclaimers, model limitations, source citations, and post-deployment monitoring.
- For medical-device-adjacent functionality, flag that regulatory review may be required before claims, deployment, or user-facing decisions.
- Deliver a concise risk review with sources checked, unresolved evidence gaps, required human owner, and safe next step.
Checklist
- Include emergency and urgent-care escalation language when user harm could result from delay.
- Cite current sources for medical, regulatory, or public-health claims.
- Avoid personalized medical advice unless the user has explicitly provided clinician-approved context and the output remains drafting/support.
- Validate accessibility and plain-language readability for patient-facing content.
- Log neither PHI nor sensitive health details unless the system is explicitly designed and approved for that purpose.
- Treat model outputs as suggestions for qualified humans, not final clinical decisions.
Guardrails
- Do not diagnose, prescribe, interpret test results for a patient, or recommend changing treatment.
- Do not claim HIPAA, FDA, CE, or other compliance status without legal/regulatory evidence.
- Do not process or expose protected health information outside approved systems.
- Do not present AI-generated healthcare output as clinician-reviewed unless it actually was.