What is the HIPAA Privacy Rule?

The HIPAA Privacy Rule sets the national standards for when covered entities and business associates may use and disclose protected health information, and gives patients rights over their own records, including the right to get a copy. It applies to PHI in any form, not only electronic data.

The Privacy Rule starts from a simple position in 45 CFR 164.502: a covered entity or business associate may use or disclose PHI only as the rule permits or requires. Business associates are further limited to what their contract with the covered entity allows. Everything else in the rule defines those permissions and the patient's rights.

Permitted uses and disclosures

  • Treatment, payment, and health care operations: a covered entity may use or disclose PHI for its own treatment, payment, or operations without the patient's authorization (164.506).
  • Authorization: uses outside the permitted categories need the patient's written authorization under 164.508, and a general consent form cannot stand in for it.
  • Minimum necessary: most uses and disclosures must be limited to the minimum needed for the purpose, with exceptions such as disclosures for treatment.

The right of access

Under 45 CFR 164.524, patients may inspect and get a copy of their PHI in a designated record set. The covered entity has 30 days to act on a request, with one extension of up to 30 more days if it explains the delay in writing before the first deadline. If the records are electronic and the patient asks for a specific electronic format, the entity must provide it if it is readily producible. A patient can direct the entity to send the copy to another person, through a written, signed request that clearly identifies the recipient. Fees are limited to cost: labor, supplies, and postage.

What it means for software

Many Privacy Rule questions show up as product decisions. Before patient data goes anywhere new, the team has to know which permission covers it: treatment, payment, operations, a business associate contract, or the patient's authorization. A records download feature is how a portal meets the right of access at scale, and the formats it offers decide whether it can honor a request for a specific electronic format. Role design and outbound data feeds are where minimum necessary gets enforced.

Example

A health system adds a "send my records to another app" option to its patient portal. To fit 164.524, the flow captures the patient's signed request, names the recipient explicitly, and records the request date so staff can see the 30-day clock. The export uses a standard electronic format the receiving app can read.