Seventeen healthcare organizations are urging the US Department of Health and Human Services (HHS) to preserve healthcare providers' ability to verify patient authorization before sharing protected health information (PHI) with third-party applications.
What happened
According to a report by Information Security Media Group (ISMG), published by Government InfoSecurity, 17 healthcare organizations, led by the College of Healthcare Information Management Executives (CHIME), have raised concerns about potential changes to the Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule.
In a November 10, 2026, letter to HHS Secretary Robert F. Kennedy Jr., the organizations urged the US Department of Health and Human Services (HHS) to preserve healthcare providers' ability to verify patient authorization before sharing protected health information (PHI) with third-party applications. The letter comes as HHS's Office for Civil Rights (OCR), which oversees HIPAA enforcement, prepares to finalize proposed updates to the HIPAA Privacy Rule. However, the healthcare groups are concerned that the final rule could introduce additional restrictions that were not included in the original proposal. In particular, they warn that limiting providers' ability to verify patient authorization could increase the risk of unauthorized disclosures and expose healthcare organizations to regulatory scrutiny and legal liability.
The organizations are asking HHS to preserve reasonable verification procedures and provide clearer guidance on which identity verification practices are considered unnecessary barriers and which are legitimate safeguards.
The backstory
The proposed changes stem from a broader effort by the US Department of Health and Human Services (HHS) to modernize the HIPAA Privacy Rule and address regulatory requirements that could hinder healthcare delivery. On January 21, 2021, HHS's Office for Civil Rights (OCR) published a Notice of Proposed Rulemaking (NPRM) titled Proposed Modifications to the HIPAA Privacy Rule to Support, and Remove Barriers to, Coordinated Care and Individual Engagement. The proposal was developed partly in response to feedback received through a 2018 Request for Information (RFI), which sought public input on how HIPAA requirements affected care coordination and information sharing across the healthcare sector.
The proposed amendments focused on several areas:
- Improving patient access to health information: Strengthening individuals' rights to access their medical records, including electronic protected health information (ePHI), and reducing the time healthcare organizations have to respond to access requests from 30 to 15 calendar days.
- Supporting care coordination: Clarifying when healthcare providers and health plans can share PHI for care coordination and case management, including certain disclosures without requiring additional patient authorization.
- Increasing family and caregiver involvement: Giving healthcare providers greater flexibility to share relevant health information with family members and caregivers involved in a patient's care, particularly during emergencies or health crises.
- Reducing administrative requirements: Revising certain Notice of Privacy Practices requirements, simplifying identity verification procedures for patients requesting their records, and adjusting provisions governing fees for accessing health information.
HHS argued that these changes could improve information sharing, reduce unnecessary compliance burdens, and support a transition towards value-based healthcare while maintaining protections for patients' privacy. However, the proposal also raised concerns about how reducing verification requirements could affect the protection of sensitive health information. This is particularly relevant to the current dispute, as some healthcare organizations believe that making it easier for third-party applications to access patient records should not prevent providers from confirming that patients have genuinely authorized those disclosures.
Going deeper
The main concern is the potential treatment of Identity Assurance Level 2 (IAL2) credentials as sufficient verification for third-party applications requesting patient information. IAL2 is a digital identity assurance standard designed to establish confidence in an individual's identity. However, CHIME and the other healthcare organizations argue that verifying someone's identity does not necessarily establish that they have been matched to the correct patient record or that a third-party application has valid permission to access the requested information.
The organizations distinguish between three separate processes:
- Identity proofing: Establishing that an individual is who they claim to be.
- Patient matching: Confirming that the individual's identity corresponds to the correct medical record.
- Authorization verification: Establishing that the individual has given the third-party application permission to access their health information, including the scope and validity of that permission.
The groups argue that these processes should not be treated as interchangeable. Even when an individual has successfully completed identity verification, healthcare providers may still need to establish whether the application has legitimate authorization to receive the patient's information. The organizations also raised concerns about the legal implications of the proposed changes. They argue that prohibiting providers from carrying out reasonable authorization checks could conflict with the original 2021 proposal, which sought to eliminate unreasonable verification barriers rather than remove legitimate safeguards.
Under the Administrative Procedure Act (APA), federal agencies must provide adequate notice of proposed regulatory changes and an opportunity for affected parties to submit comments. The healthcare groups argue that a final rule introducing restrictions that were not clearly outlined in the original proposal could violate these requirements. They have therefore asked OCR to introduce another notice-and-comment period if the final rule substantially differs from the 2021 proposal.
What was said
In comments reported by Government InfoSecurity, CHIME emphasized that improving patient access to health information should not undermine healthcare organizations' ability to protect sensitive information. “Providers need to retain the ability to take reasonable steps to confirm that a patient has actually authorized an application to receive their sensitive health information,” said Chelsea Arnone, CHIME's senior director of federal affairs.
She added that treating identity proofing, patient matching, and authorization verification as a single credentialing process could introduce privacy and security risks. Arnone also questioned the potential liability implications for healthcare providers if the government restricts the safeguards they can use when disclosing patient information. “If the federal government is going to limit the safeguards healthcare providers can use when releasing patient information, it cannot simultaneously leave those same providers holding the regulatory liability when something goes wrong,” she said.
Privacy attorney Iliana Peters of Polsinelli also pointed out the risks associated with third-party requests for patient information. “From my personal experience, many of these types of requests by third parties to PHI are, in fact, fraudulent and/or unknown to the individual who is the subject of the PHI,” Peters said.
Privacy attorney Kirk Nahra of WilmerHale also questioned whether the original proposal adequately reflects the current healthcare environment. He noted that the proposal had been pending for several years, during which the healthcare landscape and patient access issues had evolved. “I think both patients and healthcare businesses would benefit from another real round of proposals before a final rule is developed," Nahra said.
Meanwhile, an HHS OCR spokesperson told Information Security Media Group (ISMG) that the agency does not comment on pending rulemaking.
Why it matters
Changes to HIPAA's Privacy Rule could affect how healthcare organizations manage requests from third-party applications seeking access to patient information. While improving patient access to health records is important, restricting reasonable verification procedures could increase the risk of fraudulent requests and unauthorized disclosures of protected health information.
The bottomline
Healthcare providers need clear guidance on how to balance patient access rights with their responsibility to protect sensitive health information.
See also: HIPAA Compliant Email: The Definitive Guide (2026 Update)
FAQS
What is a third-party health application?
A third-party health application is a digital tool developed by an organization outside a patient's healthcare provider or health plan. These applications may allow patients to access, manage, or share their medical records, including information from electronic health record systems.
What is Identity Assurance Level 2 (IAL2)?
Identity Assurance Level 2 (IAL2) is a digital identity verification standard that provides a higher level of confidence that an individual is who they claim to be. However, healthcare organizations argue that verifying an individual's identity does not necessarily confirm that they have been matched to the correct patient record or that an application has valid authorization to access their PHI.
What is the difference between identity verification and patient authorization?
Identity verification establishes that an individual is who they claim to be, while patient authorization confirms that the individual has permitted a third party to access their health information. Both processes serve different purposes and may be necessary to prevent unauthorized disclosures.
