[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72Y3T43HB8C1QGVMBMP9WA8":3,"skill-same:01M72Y3T43HB8C1QGVMBMP9WA8":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M72Y3T43HB8C1QGVMBMP9WA8","healthcare-phi-compliance",null,"医疗应用中受保护健康信息（PHI）和个人身份信息（PII）的合规模式。涵盖数据分类、访问控制、审计追踪、加密及常见泄露途径。","SriramGandhiS\u002FSkills","SriramGandhiS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F211849986?v=4","01M72WQCW12BYX71C6WN584TTA","Sriram S","01M72WQCWTJ2RD0ET1X31AF1RC",1,"MIT","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Feverything-claude-code\u002Fdocs\u002Fzh-CN\u002Fskills\u002Fhealthcare-phi-compliance\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: healthcare-phi-compliance\ndescription: 医疗应用中受保护健康信息（PHI）和个人身份信息（PII）的合规模式。涵盖数据分类、访问控制、审计追踪、加密及常见泄露途径。\norigin: Health1 Super Speciality Hospitals — contributed by Dr. Keyur Patel\nversion: \"1.0.0\"\n---\n\n# 医疗 PHI\u002FPII 合规模式\n\n用于保护医疗应用中患者数据、临床医生数据和财务数据的模式。适用于 HIPAA（美国）、DISHA（印度）、GDPR（欧盟）以及通用医疗数据保护。\n\n## 何时使用\n\n* 构建任何涉及患者记录的功能\n* 为临床系统实施访问控制或身份验证\n* 设计医疗数据的数据库模式\n* 构建返回患者或临床医生数据的 API\n* 实施审计追踪或日志记录\n* 审查代码中的数据泄露漏洞\n* 为多租户医疗系统设置行级安全（RLS）\n\n## 工作原理\n\n医疗数据保护在三个层面运作：**分类**（什么是敏感数据）、**访问控制**（谁能查看）和**审计**（谁查看了数据）。\n\n### 数据分类\n\n**PHI（受保护健康信息）** — 任何能够识别患者身份且与其健康相关的数据：患者姓名、出生日期、地址、电话、电子邮件、国家身份证号码（SSN、Aadhaar、NHS 号码）、病历号、诊断、药物、化验结果、影像资料、保险单和理赔详情、预约和入院记录，或上述任意组合。\n\n**医疗系统中的 PII（非患者敏感数据）**：临床医生\u002F员工个人详细信息、医生收费结构和支付金额、员工薪资和银行信息、供应商付款信息。\n\n### 访问控制：行级安全\n\n```sql\nALTER TABLE patients ENABLE ROW LEVEL SECURITY;\n\n-- Scope access by facility\nCREATE POLICY \"staff_read_own_facility\"\n  ON patients FOR SELECT TO authenticated\n  USING (facility_id IN (\n    SELECT facility_id FROM staff_assignments\n    WHERE user_id = auth.uid() AND role IN ('doctor','nurse','lab_tech','admin')\n  ));\n\n-- Audit log: insert-only (tamper-proof)\nCREATE POLICY \"audit_insert_only\" ON audit_log FOR INSERT\n  TO authenticated WITH CHECK (user_id = auth.uid());\nCREATE POLICY \"audit_no_modify\" ON audit_log FOR UPDATE USING (false);\nCREATE POLICY \"audit_no_delete\" ON audit_log FOR DELETE USING (false);\n```\n\n### 审计追踪\n\n每次 PHI 访问或修改都必须记录：\n\n```typescript\ninterface AuditEntry {\n  timestamp: string;\n  user_id: string;\n  patient_id: string;\n  action: 'create' | 'read' | 'update' | 'delete' | 'print' | 'export';\n  resource_type: string;\n  resource_id: string;\n  changes?: { before: object; after: object };\n  ip_address: string;\n  session_id: string;\n}\n```\n\n### 常见泄露途径\n\n**错误消息：** 切勿在发送给客户端的错误消息中包含患者身份识别数据。仅在服务器端记录详细信息。\n\n**控制台输出：** 切勿记录完整的患者对象。使用不透明的内部记录 ID（UUID）——而不是病历号、国家身份证号或姓名。\n\n**URL 参数：** 切勿在可能出现在日志或浏览器历史记录中的查询字符串或路径段中包含患者身份识别数据。仅使用不透明的 UUID。\n\n**浏览器存储：** 切勿在 localStorage 或 sessionStorage 中存储 PHI。仅在内存中保留 PHI，按需获取。\n\n**服务角色密钥：** 切勿在客户端代码中使用 service\\_role 密钥。始终使用匿名\u002F可发布密钥，并让 RLS 强制执行访问控制。\n\n**日志和监控：** 切勿记录完整的患者记录。仅使用不透明的记录 ID（而不是病历号）。在发送到错误跟踪服务之前，清理堆栈跟踪。\n\n### 数据库模式标记\n\n在模式级别标记 PHI\u002FPII 列：\n\n```sql\nCOMMENT ON COLUMN patients.name IS 'PHI: patient_name';\nCOMMENT ON COLUMN patients.dob IS 'PHI: date_of_birth';\nCOMMENT ON COLUMN patients.aadhaar IS 'PHI: national_id';\nCOMMENT ON COLUMN doctor_payouts.amount IS 'PII: financial';\n```\n\n### 部署检查清单\n\n每次部署前：\n\n* 错误消息或堆栈跟踪中无 PHI\n* console.log\u002Fconsole.error 中无 PHI\n* URL 参数中无 PHI\n* 浏览器存储中无 PHI\n* 客户端代码中无 service\\_role 密钥\n* 所有 PHI\u002FPII 表已启用 RLS\n* 所有数据修改均有审计追踪\n* 已配置会话超时\n* 所有 PHI 端点均需 API 身份验证\n* 已验证跨机构数据隔离\n\n## 示例\n\n### 示例 1：安全与不安全的错误处理\n\n```typescript\n\u002F\u002F BAD — leaks PHI in error\nthrow new Error(`Patient ${patient.name} not found in ${patient.facility}`);\n\n\u002F\u002F GOOD — generic error, details logged server-side with opaque IDs only\nlogger.error('Patient lookup failed', { recordId: patient.id, facilityId });\nthrow new Error('Record not found');\n```\n\n### 示例 2：多机构隔离的 RLS 策略\n\n```sql\n-- Doctor at Facility A cannot see Facility B patients\nCREATE POLICY \"facility_isolation\"\n  ON patients FOR SELECT TO authenticated\n  USING (facility_id IN (\n    SELECT facility_id FROM staff_assignments WHERE user_id = auth.uid()\n  ));\n\n-- Test: login as doctor-facility-a, query facility-b patients\n-- Expected: 0 rows returned\n```\n\n### 示例 3：安全日志记录\n\n```typescript\n\u002F\u002F BAD — logs identifiable patient data\nconsole.log('Processing patient:', patient);\n\n\u002F\u002F GOOD — logs only opaque internal record ID\nconsole.log('Processing record:', patient.id);\n\u002F\u002F Note: even patient.id should be an opaque UUID, not a medical record number\n```\n","# 医疗 PHI\u002FPII 合规模式\n\n用于保护医疗应用中患者数据、临床医生数据和财务数据的模式。适用于 HIPAA（美国）、DISHA（印度）、GDPR（欧盟）以及通用医疗数据保护。\n\n## 何时使用\n\n* 构建任何涉及患者记录的功能\n* 为临床系统实施访问控制或身份验证\n* 设计医疗数据的数据库模式\n* 构建返回患者或临床医生数据的 API\n* 实施审计追踪或日志记录\n* 审查代码中的数据泄露漏洞\n* 为多租户医疗系统设置行级安全（RLS）\n\n## 工作原理\n\n医疗数据保护在三个层面运作：**分类**（什么是敏感数据）、**访问控制**（谁能查看）和**审计**（谁查看了数据）。\n\n### 数据分类\n\n**PHI（受保护健康信息）** — 任何能够识别患者身份且与其健康相关的数据：患者姓名、出生日期、地址、电话、电子邮件、国家身份证号码（SSN、Aadhaar、NHS 号码）、病历号、诊断、药物、化验结果、影像资料、保险单和理赔详情、预约和入院记录，或上述任意组合。\n\n**医疗系统中的 PII（非患者敏感数据）**：临床医生\u002F员工个人详细信息、医生收费结构和支付金额、员工薪资和银行信息、供应商付款信息。\n\n### 访问控制：行级安全\n\n```sql\nALTER TABLE patients ENABLE ROW LEVEL SECURITY;\n\n-- Scope access by facility\nCREATE POLICY \"staff_read_own_facility\"\n  ON patients FOR SELECT TO authenticated\n  USING (facility_id IN (\n    SELECT facility_id FROM staff_assignments\n    WHERE user_id = auth.uid() AND role IN ('doctor','nurse','lab_tech','admin')\n  ));\n\n-- Audit log: insert-only (tamper-proof)\nCREATE POLICY \"audit_insert_only\" ON audit_log FOR INSERT\n  TO authenticated WITH CHECK (user_id = auth.uid());\nCREATE POLICY \"audit_no_modify\" ON audit_log FOR UPDATE USING (false);\nCREATE POLICY \"audit_no_delete\" ON audit_log FOR DELETE USING (false);\n```\n\n### 审计追踪\n\n每次 PHI 访问或修改都必须记录：\n\n```typescript\ninterface AuditEntry {\n  timestamp: string;\n  user_id: string;\n  patient_id: string;\n  action: 'create' | 'read' | 'update' | 'delete' | 'print' | 'export';\n  resource_type: string;\n  resource_id: string;\n  changes?: { before: object; after: object };\n  ip_address: string;\n  session_id: string;\n}\n```\n\n### 常见泄露途径\n\n**错误消息：** 切勿在发送给客户端的错误消息中包含患者身份识别数据。仅在服务器端记录详细信息。\n\n**控制台输出：** 切勿记录完整的患者对象。使用不透明的内部记录 ID（UUID）——而不是病历号、国家身份证号或姓名。\n\n**URL 参数：** 切勿在可能出现在日志或浏览器历史记录中的查询字符串或路径段中包含患者身份识别数据。仅使用不透明的 UUID。\n\n**浏览器存储：** 切勿在 localStorage 或 sessionStorage 中存储 PHI。仅在内存中保留 PHI，按需获取。\n\n**服务角色密钥：** 切勿在客户端代码中使用 service\\_role 密钥。始终使用匿名\u002F可发布密钥，并让 RLS 强制执行访问控制。\n\n**日志和监控：** 切勿记录完整的患者记录。仅使用不透明的记录 ID（而不是病历号）。在发送到错误跟踪服务之前，清理堆栈跟踪。\n\n### 数据库模式标记\n\n在模式级别标记 PHI\u002FPII 列：\n\n```sql\nCOMMENT ON COLUMN patients.name IS 'PHI: patient_name';\nCOMMENT ON COLUMN patients.dob IS 'PHI: date_of_birth';\nCOMMENT ON COLUMN patients.aadhaar IS 'PHI: national_id';\nCOMMENT ON COLUMN doctor_payouts.amount IS 'PII: financial';\n```\n\n### 部署检查清单\n\n每次部署前：\n\n* 错误消息或堆栈跟踪中无 PHI\n* console.log\u002Fconsole.error 中无 PHI\n* URL 参数中无 PHI\n* 浏览器存储中无 PHI\n* 客户端代码中无 service\\_role 密钥\n* 所有 PHI\u002FPII 表已启用 RLS\n* 所有数据修改均有审计追踪\n* 已配置会话超时\n* 所有 PHI 端点均需 API 身份验证\n* 已验证跨机构数据隔离\n\n## 示例\n\n### 示例 1：安全与不安全的错误处理\n\n```typescript\n\u002F\u002F BAD — leaks PHI in error\nthrow new Error(`Patient ${patient.name} not found in ${patient.facility}`);\n\n\u002F\u002F GOOD — generic error, details logged server-side with opaque IDs only\nlogger.error('Patient lookup failed', { recordId: patient.id, facilityId });\nthrow new Error('Record not found');\n```\n\n### 示例 2：多机构隔离的 RLS 策略\n\n```sql\n-- Doctor at Facility A cannot see Facility B patients\nCREATE POLICY \"facility_isolation\"\n  ON patients FOR SELECT TO authenticated\n  USING (facility_id IN (\n    SELECT facility_id FROM staff_assignments WHERE user_id = auth.uid()\n  ));\n\n-- Test: login as doctor-facility-a, query facility-b patients\n-- Expected: 0 rows returned\n```\n\n### 示例 3：安全日志记录\n\n```typescript\n\u002F\u002F BAD — logs identifiable patient data\nconsole.log('Processing patient:', patient);\n\n\u002F\u002F GOOD — logs only opaque internal record ID\nconsole.log('Processing record:', patient.id);\n\u002F\u002F Note: even patient.id should be an opaque UUID, not a medical record number\n```\n",{"name":5,"origin":24,"version":25,"description":7},"Health1 Super Speciality Hospitals — contributed by Dr. Keyur Patel","1.0.0","master","d6ca01da0f24a3b0e26e4a8b7b66cbd25d429f5d","everything-claude-code\u002Fdocs\u002Fzh-CN\u002Fskills\u002Fhealthcare-phi-compliance",0,"https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills","https:\u002F\u002Fgithub.com\u002FSriramGandhiS","https:\u002F\u002Fsriram.website\u002F","Curious guy who keeps tinkering until something works","2026-05-20 16:21:34",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add SriramGandhiS\u002FSkills --skill healthcare-phi-compliance",{"tool":41,"command":42},"bunx","bunx skills add SriramGandhiS\u002FSkills --skill healthcare-phi-compliance",{"tool":44,"command":45},"pnpm","pnpm dlx skills add SriramGandhiS\u002FSkills --skill healthcare-phi-compliance","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Feverything-claude-code\u002Fdocs\u002Fzh-CN\u002Fskills\u002Fhealthcare-phi-compliance\u002FSKILL.md",true,[],[50,58,63,69,76,83],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":57},"01M732609EPJWV13PVTX3GT4TM","webgpu-threejs-tsl","Comprehensive guide for developing WebGPU-enabled Three.js applications using TSL (Three.js Shading Language). Covers WebGPU renderer setup, TSL syntax and node materials, compute shaders, post-processing effects, and WGSL integration. Use this skill when working with Three.js WebGPU, TSL shaders, node materials, or GPU compute in Three.js.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fwebgpu-threejs-tsl\u002Fskills\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":59,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":57},"01M7325XM47AGWB6K6C4VXKE6B","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":57},"01M7325WP6DES69JKC840VMFEP","verification-loop","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":57},"01M7325TFQF1DZTQ6J3WGQQ1VR","tdd-workflow","Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Ftdd-workflow\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":57},"01M7325RGV9AY9PK92D2V8KKPW","strategic-compact","Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fstrategic-compact\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":57},"01M7325MZC28SE86E7NMCNEFS4","security-review","Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment\u002Fsensitive features. Provides comprehensive security checklist and patterns.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fsecurity-review\u002FSKILL.md",[],[]]