Individual skill

hipaa-security-rule

Not available

skills/perplexity/hipaa-security-rule/SKILL.md

Read pinned source

Source commit a991acae1b74d338ca89ec2245eaa13ad680dc8f

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 11, 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.

Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.

Repository context

Repository stars (not skill ratings)
39
Repository last updated
Jul 8, 2026
License
Apache-2.0

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

Declared tags are partial or unavailable.

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
<!-- AUTO-GENERATED by export-skills.py — DO NOT EDIT -->
---
name: hipaa-security-rule
description: HIPAA Security Rule safeguard requirements for protecting electronic protected health information (ePHI) across administrative, physical, and technical controls
tags: [compliance, security]
---

# HIPAA Security Rule Safeguards

## Overview

The HIPAA Security Rule (45 CFR Part 160 and Subparts A and C of Part 164) establishes national standards for protecting electronic protected health information (ePHI). It requires covered entities and business associates to implement administrative, physical, and technical safeguards that ensure the confidentiality, integrity, and availability of ePHI.

The rule organizes requirements into three safeguard categories, each containing standards with implementation specifications. Specifications are classified as either **Required (R)** -- must be implemented exactly as described -- or **Addressable (A)** -- the entity must assess whether the specification is reasonable and appropriate, and if not, document why and implement an equivalent alternative.
Back to top