affaan-m/ECC

hipaa-compliance

针对医疗隐私和安全工作的HIPAA特定入口点。当任务明确围绕HIPAA、PHI处理、受保实体、BAA、违规态势或美国医疗合规要求时使用。

61Collecting
See how to use itView GitHub source
npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/hipaa-compliance"
Automated source guide

Source checked Jul 28, 2026·Refresh due Oct 26, 2026

Reorganized from the pinned upstream SKILL.md

Turn hipaa-compliance's source instructions into a guide you can follow

According to the pinned SKILL.md from affaan-m/ECC: 当任务明确涉及美国医疗合规时,以此作为 HIPAA 专用入口。此技能刻意保持精简和规范:

npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/hipaa-compliance"
Check the pinned source

Best fit

  • 针对医疗隐私和安全工作的HIPAA特定入口点。当任务明确围绕HIPAA、PHI处理、受保实体、BAA、违规态势或美国医疗合规要求时使用。

Bring this context

  • A concrete task that matches the documented purpose of hipaa-compliance.
  • The files, examples, or context the task depends on.
  • Your constraints, target environment, and definition of done.

Expected outputs

  • A result that follows the pinned hipaa-compliance instructions.
  • A concise record of assumptions, inputs used, and unresolved questions.
  • A final check against the source workflow and relevant permission signals.

Key source sections

Read hipaa-compliance through these 5 source sections

Sections are extracted automatically from the pinned SKILL.md and link back to the source.

01

使用时机

请求明确提及 HIPAA、PHI、受保实体、业务伙伴或 BAA 构建或审查存储、处理、导出或传输 PHI 的美国医疗软件 评估日志记录、分析、LLM 提示、存储或支持工作流是否产生 HIPAA 暴露风险 设计面向患者或临床医生的系统时,需关注最小必要访问和可审计性

SKILL.md · 使用时机
请求明确提及 HIPAA、PHI、受保实体、业务伙伴或 BAA构建或审查存储、处理、导出或传输 PHI 的美国医疗软件评估日志记录、分析、LLM 提示、存储或支持工作流是否产生 HIPAA 暴露风险
02

工作原理

将 HIPAA 视为覆盖在更广泛的医疗隐私技能之上的叠加层:

SKILL.md · 工作原理
从 healthcare-phi-compliance 开始,获取具体的实施规则。应用 HIPAA 专用决策门:这些数据是否为 PHI?
03

HIPAA 专用防护栏

切勿将 PHI 置于日志、分析事件、崩溃报告、提示或客户端可见的错误字符串中。 切勿在 URL、浏览器存储、截图或复制的示例负载中暴露 PHI。 要求对 PHI 的读写操作进行认证访问、范围授权并保留审计追踪。 默认将第三方 SaaS、可观测性、支持工具和 LLM 提供商视为禁止状态,直至明确其 BAA 状态和数据边界。 遵循最小必要访问原则:正确的用户应仅看到完成任务所需的最小 PHI 片段。 优先使用不透明的内部 ID,而非姓名、病历号、电话号码、地址或其他标识符。

SKILL.md · HIPAA 专用防护栏
切勿将 PHI 置于日志、分析事件、崩溃报告、提示或客户端可见的错误字符串中。切勿在 URL、浏览器存储、截图或复制的示例负载中暴露 PHI。要求对 PHI 的读写操作进行认证访问、范围授权并保留审计追踪。
04

示例

为我们的临床医生仪表板添加 AI 生成的就诊摘要。我们服务美国诊所,需保持 HIPAA 合规。

SKILL.md · 示例
激活 hipaa-compliance使用 healthcare-phi-compliance 审查 PHI 流动、日志记录、存储和提示边界在发送任何 PHI 前,验证摘要生成提供商是否受 BAA 覆盖
05

示例 1:以 HIPAA 为框架的产品需求

为我们的临床医生仪表板添加 AI 生成的就诊摘要。我们服务美国诊所,需保持 HIPAA 合规。

SKILL.md · 示例 1:以 HIPAA 为框架的产品需求
激活 hipaa-compliance使用 healthcare-phi-compliance 审查 PHI 流动、日志记录、存储和提示边界在发送任何 PHI 前,验证摘要生成提供商是否受 BAA 覆盖

SkillSignal prompt templates

Provide the task, context, and acceptance criteria

These prompts were written by SkillSignal from the source structure; they are not upstream text.

Task-start prompt

Confirm source fit, inputs, and outputs before acting.

Use hipaa-compliance to help me with: [specific task]. Context: [files, data, or background]. Constraints: [environment, scope, and prohibited actions]. Before acting, check the pinned SKILL.md and explain which sections apply, what inputs are still missing, and what you will deliver.

Source-guided execution

Make the Agent explicitly follow the key extracted sections.

Apply the pinned hipaa-compliance source to [task]. Pay particular attention to these source sections: “使用时机”, “工作原理”, “HIPAA 专用防护栏”, “示例”, “示例 1:以 HIPAA 为框架的产品需求”. Preserve the important decision at each step. Mark facts not covered by the source as “needs confirmation” instead of inventing them. Then verify the result against my acceptance criteria: [criteria].

Result-review prompt

Check omissions, permissions, and source drift before delivery.

Review the current hipaa-compliance result: (1) does it satisfy the original task; (2) were any applicable steps or limits in the pinned SKILL.md missed; (3) did it perform any unauthorized file, command, network, or data action; and (4) which conclusions remain unverified? List issues first, then fix only what the source or user authorization supports.

Output checklist

Verify each item before delivery

The task matches the purpose documented in the SKILL.md.

The source section “使用时机” has been checked.

The source section “工作原理” has been checked.

The source section “HIPAA 专用防护栏” has been checked.

The source section “示例” has been checked.

Inputs, constraints, and acceptance criteria are explicit.

Unverified facts, compatibility, and outcome claims are clearly marked.

Any file, command, network, or data action has been reviewed.

Choose a different workflow

When another Skill is the better fit

hipaa-compliance

HIPAA-specific entrypoint for healthcare privacy and security work. Use when a task is explicitly framed around HIPAA, PHI handling, covered entities, BAAs, breach posture, or US healthcare compliance requirements.

A separate implementation from affaan-m/ECC; compare its source, maintenance signals, and permission requirements.

Open source detail

ab-testing

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

A separate implementation from coreyhaines31/marketingskills; compare its source, maintenance signals, and permission requirements.

Open source detail

churn-prevention

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o

A separate implementation from coreyhaines31/marketingskills; compare its source, maintenance signals, and permission requirements.

Open source detail

FAQ

What does hipaa-compliance do?

当任务明确涉及美国医疗合规时,以此作为 HIPAA 专用入口。此技能刻意保持精简和规范:

How do I start using hipaa-compliance?

The catalog detected this source-specific install command: npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/hipaa-compliance". Inspect the command and pinned source before running it.

Which Agent platforms does it declare?

No dedicated Agent platform is declared in the pinned source record.

Repository stars
234,327
Repository forks
35,711
Quality
61/100
Source repository last pushed

Quality breakdown

Based on traceable docs and repository signals; stars are not treated as quality.

61/100
Documentation13/30
Specificity11/25
Maintenance20/20
Trust signals17/25

Compare before choosing

Related Agent Skills and source variants

These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.

hipaa-compliance by affaan-m

HIPAA-specific entrypoint for healthcare privacy and security work. Use when a task is explicitly framed around HIPAA, PHI handling, covered entities, BAAs, breach posture, or US healthcare compliance requirements.

ab-testing by coreyhaines31

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

churn-prevention by coreyhaines31

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o

design-intelligence by event4u-app

Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.

design-system-capture by event4u-app

Write and maintain DESIGN.md + PRODUCT.md — captures visual decisions and interaction patterns so design tasks stay consistent across sessions without re-scanning past work.

View original Skill.mdThis page is parsed directly from the repository SKILL.md without editorial rewriting. Collected: Jul 28, 2026 · about 1 min

HIPAA 合规

当任务明确涉及美国医疗合规时,以此作为 HIPAA 专用入口。此技能刻意保持精简和规范:

  • healthcare-phi-compliance 仍是处理 PHI/PII、数据分类、审计日志、加密和泄露防护的主要实施技能。
  • healthcare-reviewer 仍是当代码、架构或产品行为需要医疗感知的二次审查时的专业审核者。
  • security-review 仍适用于通用认证、输入处理、密钥、API 和部署加固。

使用时机

  • 请求明确提及 HIPAA、PHI、受保实体、业务伙伴或 BAA
  • 构建或审查存储、处理、导出或传输 PHI 的美国医疗软件
  • 评估日志记录、分析、LLM 提示、存储或支持工作流是否产生 HIPAA 暴露风险
  • 设计面向患者或临床医生的系统时,需关注最小必要访问和可审计性

工作原理

将 HIPAA 视为覆盖在更广泛的医疗隐私技能之上的叠加层:

  1. healthcare-phi-compliance 开始,获取具体的实施规则。
  2. 应用 HIPAA 专用决策门:
    • 这些数据是否为 PHI?
    • 该行为者是否为受保实体或业务伙伴?
    • 供应商或模型提供商在接触数据前是否需要 BAA?
    • 访问权限是否限制在最小必要范围内?
    • 读/写/导出事件是否可审计?
  3. 如果任务影响患者安全、临床工作流或受监管的生产架构,则升级至 healthcare-reviewer

HIPAA 专用防护栏

  • 切勿将 PHI 置于日志、分析事件、崩溃报告、提示或客户端可见的错误字符串中。
  • 切勿在 URL、浏览器存储、截图或复制的示例负载中暴露 PHI。
  • 要求对 PHI 的读写操作进行认证访问、范围授权并保留审计追踪。
  • 默认将第三方 SaaS、可观测性、支持工具和 LLM 提供商视为禁止状态,直至明确其 BAA 状态和数据边界。
  • 遵循最小必要访问原则:正确的用户应仅看到完成任务所需的最小 PHI 片段。
  • 优先使用不透明的内部 ID,而非姓名、病历号、电话号码、地址或其他标识符。

示例

示例 1:以 HIPAA 为框架的产品需求

用户请求:

为我们的临床医生仪表板添加 AI 生成的就诊摘要。我们服务美国诊所,需保持 HIPAA 合规。

响应模式:

  • 激活 hipaa-compliance
  • 使用 healthcare-phi-compliance 审查 PHI 流动、日志记录、存储和提示边界
  • 在发送任何 PHI 前,验证摘要生成提供商是否受 BAA 覆盖
  • 如果摘要影响临床决策,则升级至 healthcare-reviewer

示例 2:供应商/工具决策

用户请求:

我们可以将支持对话记录和患者消息发送到分析平台吗?

响应模式:

  • 假设这些消息可能包含 PHI
  • 除非分析供应商已获批准处理 HIPAA 约束的工作负载且数据路径已最小化,否则阻止该设计
  • 尽可能要求进行脱敏处理或采用非 PHI 事件模型

相关技能

  • healthcare-phi-compliance
  • healthcare-reviewer
  • healthcare-emr-patterns
  • healthcare-eval-harness
  • security-review
Source repo
affaan-m/ECC
Skill path
docs/zh-CN/skills/hipaa-compliance/SKILL.md
Commit SHA
4e973d3eaf92
Repository license
MIT
Data collected