Menu

Individual skill

hipaa-safeguards

0upvotes

Map HIPAA Security Rule safeguards and run a risk analysis for systems handling PHI. Use when asked to become HIPAA-compliant, assess HIPAA safeguards, prepare for handling PHI/ePHI, or scope a BAA. Produces a HIPAA assessment — the administrative/physical/technical safeguards with required-vs-addressable status, a risk analysis, BAA scope, and a prioritised remediation plan.

skills/hipaa-safeguards/SKILL.md

Read pinned source

Source commit e0009a385c480fb0b5687e7412df67c7c64f7cee

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 12, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,541
Repository last updated
Nov 11, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# HIPAA Safeguards Skill

HIPAA's Security Rule is a list of safeguards for electronic protected health information (ePHI), split
into administrative, physical, and technical — some **required**, some **addressable** (you must do them
*or* document why an equivalent is reasonable). This skill maps your controls to that list, runs the
risk analysis HIPAA mandates, and flags where you're exposed — so handling PHI is defensible, not hopeful.

## Required Inputs

Ask for these only if they aren't already provided:

- **Your role** — covered entity, or business associate (a vendor handling PHI for one). Both owe Security Rule safeguards.
- **The ePHI flow** — where PHI is created, received, stored, transmitted, and who can access it.
- **Current safeguards** — what's in place for access control, encryption, audit logging, backups, training.
Back to top