Skip to main content
promotional banner for can you prove your CC^ checklist
Build a Defensible Authorization Check for Third-Party App RequestsRegulatory Framework
5 min readFor Compliance Officers

Build a Defensible Authorization Check for Third-Party App Requests

The Problem: Why This Matters Now

On November 10, CHIME and 17 health systems sent a letter to HHS warning that the final HIPAA Privacy Rule update could "categorically prohibit" providers from independently confirming whether a patient authorized a third-party app to receive their Protected Health Information (PHI). The 2021 NPRM preserved Covered Entities' ability to use reasonable verification measures, but there's concern the final rule might change that.

The final text is still unknown, and OCR doesn't comment on pending rulemaking. This guide is not a reaction piece but a proactive playbook. Your work now will be useful regardless of the outcome and addresses a gap many organizations have: identity proofing, patient matching, and authorization verification often get collapsed into one step. CHIME's letter argues these are distinct functions. An IAL2 credential can establish identity but not the correct record match or the scope, duration, or validity of authorization.

Build these functions separately and document your reasoning. If the rule tightens, you'll be able to show which checks verify authority and which are unreasonable barriers.

What You Need Before Starting

  • Inventory of App-Initiated Request Paths: List all FHIR/API endpoints, patient portal connections, and intermediary aggregators that a third-party app can use to request PHI.
  • Current Policies Mapped to Regulations: Align your verification procedures with 45 CFR § 164.514(h) (Privacy Rule verification), 45 CFR § 164.308(a)(4) (information access management), and 45 CFR § 164.312(a)(1) (access control). These are the provisions that could create conflicting obligations if verification is restricted.
  • Your Information Blocking Analysis: Know which exceptions you rely on and who approves them.
  • Logging Capability: Ensure your authorization server and API gateway record request metadata, token claims, and disposition.
  • Legal and Privacy Official Availability: Assign a named owner for escalation decisions.
  • A Current Risk Analysis: Have an amendable risk analysis under the HIPAA Security Rule.

Step-by-Step Implementation

Step 1: Separate the Three Functions in Your Architecture Documents Create a diagram with three labeled stages:

  1. Identity proofing: Is this person who they claim to be? (An IAL2 credential, if used, applies here.)
  2. Patient matching: Does this verified identity map to exactly one record in your system? Document your matching attributes and handling of ambiguous matches.
  3. Authorization verification: Did this patient authorize this specific app, for what scope, and is that authorization still valid?

Ensure a passing result at stage 1 doesn't automatically satisfy stage 3. Make this explicit in code and policy.

Step 2: Define "Reasonable" in Writing Draft a two-column standard:

  • Reasonable: Confirming the app's registration and the patient's grant through your authorization server; checking scope against the data requested; validating token expiry and revocation status; automated, machine-speed checks.
  • Potentially Unreasonable: Requiring notarized forms, in-person visits, repeated re-authorization for unchanged grants, manual review queues that delay routine requests, or requests for information beyond what the check needs.

Have your Privacy Official and counsel approve and date the standard.

Step 3: Make Authorization Checks Automated and Scope-Aware Validate on every API request: token signature and expiry, the granted scopes against the resource requested, and the client ID against your registered-app list. Reject requests that exceed granted scope and log the decision. Automation ensures verification is fast and consistent, which helps counter claims that verification is a barrier.

Step 4: Build a Tiered Exception Path Create an escalation trigger for anomalies: mismatched demographics, requests for unusually broad scope, tokens from unregistered clients, or sudden volume spikes. Route these to a named reviewer with a defined response window, and document this window in policy to avoid open-ended delays.

Step 5: Add a Patient-Facing Confirmation Signal Where possible, notify the patient when a new app is granted access, with a one-step revoke link. This provides evidence of patient awareness without adding friction to the request.

Step 6: Update Your Risk Analysis and Policies Add a risk entry for fraudulent app-initiated disclosure and one for regulatory changes that restrict verification. Record the safeguards from Steps 2 through 5 as controls, mapped to the Security Rule access control requirements. Update your disclosure accounting and incident response procedures to evaluate unauthorized app disclosures under the Breach Notification Rule.

Step 7: Map the Post-HIPAA Exposure Once PHI reaches an app that isn't a Covered Entity or Business Associate, other regulations may apply, including Section 5 of the FTC Act, the FTC Health Breach Notification Rule, and state laws like Washington's My Health My Data Act and the California Consumer Privacy Act. Add a notice to your app registration terms and patient disclosures so patients understand protections may change after disclosure. Have counsel review the language.

Step 8: Prepare a Regulatory-Change Playbook Draft, but don't activate, two versions of your verification procedure: your current one and a fallback that removes independent authorization confirmation and relies on the upstream credential alone. Pre-identify what changes, who approves, and what residual risk you'd accept in writing. If the final rule arrives, you'll choose from prepared options instead of improvising.

Validation: How to Verify It Works

  • Replay Test: Send requests through a test harness with expired tokens, revoked grants, out-of-scope requests, and unregistered clients. All should be rejected and logged.
  • Separation Test: Confirm that a valid identity credential alone can't return PHI without a passing authorization check. If it can, Step 1 isn't implemented.
  • Matching Test: Run known duplicate and near-duplicate patient records through the pipeline and confirm ambiguous matches go to escalation instead of returning data.
  • Tabletop Exercise: Walk the Privacy Official, Security lead, and counsel through a fraudulent-request scenario, including breach risk assessment.
  • Evidence Package: Confirm you can produce, on request, the written standard, the logs, the risk analysis entry, and the approval record.

Maintenance: Ongoing Tasks

  • Review the "Reasonable" Standard whenever HHS releases the final rule, guidance, or OCR commentary. Revise the dated standard and keep prior versions.
  • Monitor the Comment Record: Track whether OCR reopens comment and consider submitting your operational experience.
  • Review Escalation Logs regularly for false positives and delay patterns. A slow review queue becomes an unreasonable barrier.
  • Re-test Annually and after changes to your authorization server, API gateway, or matching logic.
  • Track Related Legislation, including the Health Information Privacy Reform Act, which could authorize HHS to create a framework for health data outside HIPAA.
  • Reassess Your Risk Analysis whenever you add a new app category or intermediary.

The core discipline is simple: keep three functions separate, keep your definition of reasonable written down, and keep the evidence ready. Whatever OCR finalizes, you'll be able to show what you did and why.

Application Security Isn’t Optional Anymore.

You Might Also Like