The Challenge
The Department of Health and Human Services (HHS) has issued a final rule modifying the HIPAA Privacy Rule, significantly impacting your operations. The time frame for providing individuals with copies of their Protected Health Information (PHI) has been reduced from 30 days to 15 days. While a 30-day extension is still possible, the base period is now much shorter.
This single change in a 363-page rule is likely to reveal weaknesses in how your organization handles Designated Record Set requests. The challenge isn't just about speed; it's about working faster while adhering to new limits on fees, identity verification, and request channels, and accommodating requests to send Electronic Protected Health Information (ePHI) (ePHI) to personal health apps.
This case study analyzes the regulatory problem directly and explores the decisions a Privacy Official must make.
The Environment and Constraints
Several factors shape your response.
The clock is shorter, and clarification doesn't pause it. The response time remains unchanged even if you need to clarify a request with the individual. Your intake process must resolve ambiguity quickly, not use it as a delay tactic.
Barriers are prohibited. You can't limit requests to a patient portal or impose unreasonable identity verification measures. If your current process requires a notarized form or an in-person visit, it needs revision.
Fees are narrower. You can't charge for in-person inspection or access to ePHI through internet-based methods like patient portals. The new structure supersedes HHS's 2016 guidance, including the optional flat fee of up to $6.50 for electronic copies. Permitted fees include reasonable, cost-based charges for labor for copying, supplies for paper copies, postage, and a summary or explanation if the individual agrees. If you have a website, you must post a fee schedule there and make it available at the point of service.
App disclosures depend on capability. An individual can request that a copy of ePHI in a Designated Record Set be sent to their chosen personal health app, provided you can produce ePHI in that form or format. The right to direct ePHI to another designated person is limited to ePHI in an electronic health record (EHR) and a Designated Record Set.
Verification is your call, but the risk is real. CHIME and a coalition of healthcare organizations warned that identity proofing, patient matching, and confirming authorization are separate functions. You retain discretion to choose verification measures suited to your environment and aren't required to always use the least burdensome method. You may contact a patient directly if you question the designated recipient's authority, although the rule doesn't specifically confirm you may contact a patient to verify they requested a transfer to a specific app.
The Approach: A Decision Framework
Since the rule leaves real discretion with you, your approach involves a series of decisions. Here's how to sequence them.
1. Map the request lifecycle against a 15-day budget. Trace a request from receipt to delivery. Identify every handoff: front desk, Health Information Management (HIM), clinical review, billing, IT. Any step without a named owner and a time target is where the 15 days will leak. Treat the 30-day extension as an exception you document, not a planning assumption.
2. Open the intake channels. Audit every way a request can arrive. If your policy funnels requests through a single portal form, you need alternatives. The rule keeps the "clear, conspicuous, and specific" standard for third-party directives and lets you require those in writing, including by email. This provides a defensible, low-friction channel for third-party and app requests without accepting oral requests.
3. Separate three verification questions. Build your process around three distinct checks: Is this person who they claim to be? Is this the right record? Did this patient authorize this recipient? A single control rarely answers all three. Document which control addresses which question, and keep your selected measures proportionate so they don't act as an unreasonable barrier.
4. Treat app disclosures as a security and policy decision. The right applies where you can provide ePHI in the requested form or format, so inventory what you can actually produce. For each supported format, decide how you'll confirm the patient directed the transfer, and what you'll tell patients about the limits of your responsibility once data leaves your systems. Update your Notice of Privacy Practices language and staff scripts accordingly.
5. Rebuild the fee schedule. Remove flat fees that no longer fit. Confirm that portal and in-person access carry no charge. Publish the schedule on your website and at the point of service, listing every free access type plus standard fees for copies, electronic copies sent to a third party, and disclosures under a patient authorization. Consider a patient's finances when setting fees.
6. Update policies and train. The rule calls for updated policies and procedures and staff training. Sequence training by role: intake staff first, then HIM and release-of-information teams.
Results and Metrics
The measurable figures in the rule come from HHS's analysis. Eliminating the requirement that direct treatment providers make a good faith effort to obtain written acknowledgment of receipt of the Notice of Privacy Practices (and document and retain, for six years, why it wasn't obtained) is estimated to save around $798 million per year. This includes $483 million in policy and procedure change costs and $148 million in training costs. HHS expects this change to more than offset first-year costs, for a net first-year saving of around $14 million.
Treat these as HHS projections, not your outcomes. They highlight where the rule's burden relief sits: in documentation, not in access. Your access workload increases while your acknowledgment paperwork decreases. Set your own baseline now, such as average days to fulfill a request and the share of requests needing an extension, so you can measure the effect against the 15-day standard.
What You'd Do Differently
If you're starting from scratch, a few lessons stand out from how the rule evolved.
Don't design around dropped proposals. Several measures didn't make the final rule: the expanded right to photograph records during a visit, mandatory oral requests for third-party directives, required urgent-request prioritization, a 15-day extension, mandatory forwarding of requests to another Covered Entity (now voluntary), individualized fee estimates, and fee caps on third-party copies. Don't build workflows around them. OCR monitoring fees to keep your fee practices defensible.
Don't over-verify. The easiest mistake is stacking controls out of caution. Excessive friction invites scrutiny under the unreasonable-verification prohibition.
Don't wait on guidance. Since the rule doesn't resolve whether you may contact a patient to confirm an app request, document your reasoning for whatever approach you choose.
Takeaways for Your Team
- Plan to a 15-day clock, and log every extension with its reason.
- Keep multiple intake channels open; require writing only where the rule allows.
- Split identity, record matching, and authorization into separate, documented checks.
- Inventory the ePHI formats you can deliver before promising app transfers.
- Publish a compliant fee schedule on your website and at the point of service.
- Retire acknowledgment-of-receipt tracking for the Notice of Privacy Practices, and redirect that effort to access operations.
- Update policies and train staff by role.
The rule trades paperwork for responsiveness. Your job is to make that trade deliberately.





