'hipaa' 검색 결과

미국 의료 소프트웨어의 HIPAA 대응을 검토할 때 환자 정보 처리, 외부 서비스 전송 조건, 최소한의 접근 범위와 감사 기록을 확인하는 스킬입니다.

• AI 진료 요약의 HIPAA 대응을 확인합니다
• 환자 정보의 분석 플랫폼 전송을 검토합니다
• 최소 접근 범위와 감사 기록을 설계합니다

This skill enables Claude to automatically check for HIPAA (Health Insurance Portability and Accountability Act) compliance issues in codebases, infrastructure configurations, and documentation. It leverages the hipaa-compliance-checker plugin to identify potential violations related to data privacy, security, and access controls. Use this skill when the user explicitly requests to "check HIPAA compliance", "scan for HIPAA violations", "assess HIPAA readiness", or similar phrases related to HIPAA audits and security best practices. It is useful for projects handling protected health information (PHI) and requiring adherence to HIPAA regulations.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Prepare medical device regulatory work for the US FDA. Compare submission routes, organize required documents, review quality management requirements, assess patient data safeguards under HIPAA, and plan device cybersecurity documentation and controls.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Compare 510(k), PMA, and De Novo submission routes
• Organize required 510(k) documents and submission milestones
• Review quality documentation against QMSR and ISO 13485:2016

Audit applications and infrastructure handling Protected Health Information against HIPAA — Security Rule (administrative, physical, technical safeguards), Privacy Rule, Breach Notification Rule, plus HITECH. Covers ePHI scoping, the 18 HIPAA identifiers, Business Associate Agreement (BAA) chain-of-liability, minimum-necessary standard, and breach notification timing. Use when the user mentions 'HIPAA,' 'HIPAA Security Rule,' 'HIPAA Privacy Rule,' 'PHI,' 'ePHI,' 'protected health information,' 'BAA,' 'business associate agreement,' 'covered entity,' 'business associate,' 'minimum necessary,' 'HIPAA breach,' 'HITECH,' 'healthcare compliance,' 'medical data,' 'patient data,' or audits any system that creates, receives, maintains, or transmits PHI.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert HIPAA compliance assistant for healthcare and software contexts. Use this skill whenever the user mentions HIPAA, PHI (Protected Health Information), ePHI, covered entities, business associates, healthcare data privacy, medical records, health information security, BAA (Business Associate Agreements), or any compliance review involving patient data. Also trigger for requests to draft privacy notices, HIPAA policies, consent forms, security risk assessments, or breach notification letters. Use for developers building healthcare software who need technical safeguard guidance (encryption, access controls, audit logs), compliance officers reviewing documents or procedures, and anyone asking "is this HIPAA compliant?" or "what does HIPAA require for X?". When in doubt about whether a healthcare or data privacy question falls under this skill — use it.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert HIPAA compliance assistant for healthcare and software contexts. Use this skill whenever the user mentions HIPAA, PHI (Protected Health Information), ePHI, covered entities, business associates, healthcare data privacy, medical records, health information security, BAA (Business Associate Agreements), or any compliance review involving patient data. Also trigger for requests to draft privacy notices, HIPAA policies, consent forms, security risk assessments, or breach notification letters. Use for developers building healthcare software who need technical safeguard guidance (encryption, access controls, audit logs), compliance officers reviewing documents or procedures, and anyone asking "is this HIPAA compliant?" or "what does HIPAA require for X?". When in doubt about whether a healthcare or data privacy question falls under this skill — use it.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Addresses HIPAA compliance for mobile health (mHealth) applications, wearable devices, and remote patient monitoring. Covers OCR guidance on mobile device PHI, FDA-regulated mobile medical applications, FTC Health Breach Notification Rule for non-HIPAA apps, BYOD policies, and encryption requirements for ePHI on mobile platforms. Keywords: mHealth, mobile health, HIPAA mobile, wearable, remote monitoring, BYOD, mobile device management, app privacy.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill when designing HIPAA-compliant workflow requirements for Health Cloud: minimum necessary access design, audit trail requirements mapping, access control patterns, and BAA dependency identification. NOT for org-level HIPAA architecture or Shield encryption configuration — use architect/hipaa-compliance-architecture. NOT for care team and SDOH process design — use admin/care-coordination-requirements.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review audit logs from agent federation, a system for connecting agents. Filter events by compliance mode, date, and severity, then summarize personal information detections, blocked threats, trust changes, and critical or error events.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review audit events for a compliance mode
• Investigate critical or error events
• Count personal information detections and blocked threats

Plan compliance work for SOC 2, GDPR, HIPAA, and PCI-DSS by connecting requirements to technical safeguards, responsible teams, policies, and audit evidence. Get practical guidance for ongoing operations and audit preparation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning a SOC 2 compliance program
• Designing personal data retention and deletion rules
• Organizing audit evidence and access reviews

Implements HIPAA de-identification methods under 45 CFR §164.514(a)-(b). Covers expert determination method and safe harbor method with 18 identifiers removal, re-identification risk assessment, limited dataset requirements, and data use agreements. Keywords: HIPAA de-identification, safe harbor, expert determination, 18 identifiers, limited dataset, PHI.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Conducts comprehensive inventory of protected health information across the enterprise per HIPAA Security Rule requirements at 45 CFR §164.308(a)(1)(ii)(A) and §164.310(d). Covers identification of all ePHI repositories, data flow mapping, classification of PHI by sensitivity, and integration with risk analysis. Keywords: PHI inventory, ePHI, data mapping, information asset, data flow, HIPAA risk analysis, designated record set.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Conducts HIPAA risk analysis per 45 CFR §164.308(a)(1) following OCR guidance methodology. Covers threat identification, vulnerability assessment, likelihood and impact determination, risk scoring, and mitigation planning for electronic protected health information. Keywords: HIPAA risk analysis, OCR guidance, threat assessment, vulnerability, risk management, ePHI.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Implements HIPAA breach notification requirements under 45 CFR §164.400-414. Covers individual notification within 60 days, HHS reporting thresholds (500+ immediate, under 500 annual), state attorney general notification, media notification for 500+ in a state, and breach risk assessment. Keywords: HIPAA breach notification, HHS reporting, OCR breach portal, individual notice, state attorney general.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Implements HIPAA minimum necessary standard under 45 CFR §164.502(b). Covers role-based access policies per workforce member category, routine vs non-routine disclosure protocols, reasonable reliance doctrine, documentation requirements, and HITECH amendments. Keywords: minimum necessary, role-based access, workforce, routine disclosure, HIPAA.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Implements HIPAA Privacy Rule requirements for research uses of protected health information under 45 CFR §164.512(i). Covers IRB and Privacy Board waivers of authorization, individual authorization for research, limited data set and data use agreements, preparatory to research provisions, and decedent research provisions. Keywords: HIPAA research, IRB waiver, Privacy Board, authorization, limited data set, preparatory research, de-identification, Common Rule.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Executes breach notification under HIPAA Breach Notification Rule (45 CFR 164.400-414). Covers 60-day individual notification, HHS/OCR reporting for breaches of 500+ individuals (immediate) and under 500 (annual log), state attorney general notification, media notification for 500+ in a single state, and breach risk assessment using the four-factor test. Keywords: HIPAA, breach notification, PHI, HHS, OCR, covered entity, business associate.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Implements HIPAA workforce training requirements under 45 CFR §164.530(b) (Privacy Rule) and 45 CFR §164.308(a)(5) (Security Rule). Covers initial onboarding training, periodic refresher cadence, role-based content differentiation, documentation of training completion, and sanction policy integration. Keywords: HIPAA training, workforce training, security awareness, privacy training, §164.530(b), §164.308(a)(5).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Manages HIPAA Business Associate Agreements under 45 CFR §164.502(e) and §164.504(e). Covers required BAA provisions, business associate vs subcontractor obligations, breach notification chain, downstream BA requirements, and termination remedies. Keywords: BAA, business associate, subcontractor, HIPAA compliance, PHI disclosure, termination.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Implements HIPAA Privacy Rule requirements under 45 CFR §164.500-534 for covered entities and business associates. Covers minimum necessary standard, treatment-payment-operations exceptions, directory opt-out, personal representative rules, and authorization requirements. Keywords: HIPAA Privacy Rule, PHI, minimum necessary, TPO, authorization, covered entity.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Implements HIPAA Security Rule technical safeguards under 45 CFR §164.312 for electronic protected health information. Covers access controls with unique user identification, emergency access procedures, automatic logoff, encryption, audit controls, integrity controls, and transmission security. Keywords: HIPAA Security Rule, ePHI, access controls, encryption, audit controls, technical safeguards.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Apply HIPAA-compliant security practices for Abridge clinical AI integrations. Use when securing PHI in transit/at rest, configuring access controls, implementing audit logging, or preparing for HIPAA security audits. Trigger: "abridge security", "abridge HIPAA", "abridge PHI protection", "abridge access control", "abridge audit logging".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

의료 앱의 환자·직원·재무 기밀 정보를 분류하고, 의료기관별 접근 제어와 감사 기록을 설계하며 로그·주소·브라우저 저장소의 정보 유출을 점검합니다.

• 환자 기록을 다루는 코드를 점검합니다
• 의료기관 간 접근 제어를 설계합니다
• 기밀 정보의 조회와 변경을 기록합니다

Checks application code, dependencies, and security controls to identify vulnerabilities and plan fixes. Includes Python scanners, reports, incident response workflows, and guidance for adding security checks to CI/CD, the automated build and deployment process.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking code for exposed secrets and injection risks
• Prioritizing fixes for known dependency vulnerabilities
• Adding security checks to CI/CD pipelines