vertical-healthcare

Configure HIPAA-compliant healthcare memory with PHI handling and audit trails.

31|20|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/mycelium-hq/ai-brain-starter --skill vertical-healthcare
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vertical-healthcare
Source: https://github.com/mycelium-hq/ai-brain-starter/tree/main/skills/vertical-healthcare
Command: npx skills add https://github.com/mycelium-hq/ai-brain-starter --skill vertical-healthcare

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Healthcare organizations require a HIPAA-compliant memory substrate that safeguards PHI and provides auditable trails for compliant onboarding and cross-organization governance.

Core Features & Use Cases

  • Ships seven typed-memory categories: patient-scoped-fact, clinical-decision, phi-tagged-doc, baa-counterparty, retention-policy, hipaa-incident, breach-notification.
  • Connectors for Epic FHIR, Cerner FHIR, and Salesforce Health Cloud, with HIPAA retention defaults and per-state add-ons.
  • Decision-audit patterns enforce PHI handling and clinical-decision traceability across encounters.

Quick Start

Run /vertical-healthcare init to bootstrap the healthcare pack on your substrate.

Frequently Asked Questions about vertical-healthcare

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement a HIPAA-compliant memory substrate for AI that safeguards PHI?

HIPAA-compliant memory is configured by preconfiguring PHI handling, audit trails, and BAA tracking within your AI substrate to safeguard Protected Health Information. It provides auditable trails for compliant onboarding and cross-organization governance.

Does this healthcare memory pack support Epic FHIR, Cerner FHIR, and Salesforce Health Cloud?

Yes, the healthcare memory pack includes connectors for Epic FHIR, Cerner FHIR, and Salesforce Health Cloud. It applies HIPAA retention defaults and per-state add-ons across these connected health systems for covered entities and business associates.

What typed-memory categories do I need for PHI handling and clinical decision traceability?

PHI handling requires seven typed-memory categories: patient-scoped-fact, clinical-decision, phi-tagged-doc, baa-counterparty, retention-policy, hipaa-incident, and breach-notification. Decision-audit patterns enforce traceability across clinical encounters using these categories.

How do I set up BAA tracking and breach notification for a covered entity using AI memory?

Set up BAA tracking and breach notification by bootstrapping the healthcare memory pack with preconfigured typed-memory categories like baa-counterparty, hipaa-incident, and breach-notification. This enforces cross-tenant governance and HIPAA retention defaults for covered entities.

Can I apply per-state HIPAA retention defaults across multiple health system tenants?

Yes, you can apply per-state HIPAA retention add-ons across multiple health system tenants. The memory substrate supports cross-tenant governance and preconfigured retention policies to satisfy per-state compliance requirements for covered entities and business associates.

When do I need preconfigured decision-audit patterns for clinical encounters in healthcare AI?

You need decision-audit patterns when processing clinical encounters that require strict PHI handling and clinical-decision traceability. These patterns enforce auditable trails for compliant onboarding and cross-organization governance within healthcare memory substrates.