Protected Health Information Handling

Enforce encryption, access control, and retention policies for Protected Health Information in software.

26|6|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/AminAlam/meddev-agent-skills --skill protected-health-information-handling
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Protected Health Information Handling
Source: https://github.com/AminAlam/meddev-agent-skills/tree/main/data/phi-handling
Command: npx skills add https://github.com/AminAlam/meddev-agent-skills --skill protected-health-information-handling

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the critical need to identify, protect, and manage Protected Health Information (PHI) within software systems, ensuring compliance with privacy regulations and minimizing data breach risks.

Core Features & Use Cases

  • PHI Identification & Classification: Automatically identify and tag data elements containing PHI.
  • Data Minimization: Enforce the "minimum necessary" principle for data collection, storage, and transmission.
  • Encryption & Access Control: Ensure PHI is encrypted at rest and in transit, with robust access controls and auditing.
  • Retention & Deletion: Implement policies for data retention and secure deletion or de-identification.
  • Use Case: When developing a new patient portal feature that stores medical history, this Skill ensures that only essential patient data is collected, encrypted, and accessible only by authorized personnel, with a clear policy for data deletion after a specified period.

Quick Start

Apply the PHI handling skill to ensure all patient data stored in the new user profile feature is encrypted and access-controlled.

Frequently Asked Questions about Protected Health Information Handling

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I ensure my patient portal feature is HIPAA compliant?

To ensure HIPAA compliance for a patient portal, identify Protected Health Information (PHI), enforce minimum necessary data collection, encrypt data in transit and at rest, and apply role-based access controls with retention policies.

What is the minimum necessary principle for data privacy in healthcare software?

The minimum necessary principle for healthcare data privacy requires collecting, storing, and transmitting only the essential patient data needed for a specific feature, limiting exposure across logs, telemetry, and backups.

How do I securely manage PHI in logs and analytics pipelines?

Securely manage PHI in logs and analytics by implementing log sanitization to strip sensitive patient data, ensuring that telemetry and analytics pipelines do not retain or transmit unencrypted Protected Health Information.

Does this approach support verified deletion and de-identification of medical records?

Yes, this PHI handling approach supports verified deletion and de-identification by enforcing data retention policies that require secure deletion or de-identification of medical records upon expiry.

What encryption standards are needed for transmitting Protected Health Information?

Transmitting Protected Health Information requires TLS 1.3 encryption in transit to secure the data, alongside robust encryption at rest, to meet strict data security and regulatory compliance requirements.

How do I implement role-based access control for sensitive patient data?

Implement role-based access control for sensitive patient data by restricting system access to authorized personnel only, ensuring that features storing or transmitting medical history enforce strict auditing and minimum necessary use policies.