# How fast patients and payers must get health data: HIPAA access, information blocking and CMS API deadlines compared

**In short:** A HIPAA covered entity has up to 30 days (plus one 30-day extension) to act on a patient's access request, while CMS requires Medicare Advantage organizations, state Medicaid and CHIP agencies and QHP issuers on individual market Federally-facilitated Exchanges to put claims and clinical data in the Patient Access API no later than one business day after a claim is processed or data are received. From January 1, 2027, Medicare Advantage organizations must also show prior authorization information within 1 business day and answer Provider Access and Payer-to-Payer API requests within 1 business day. Under the information blocking manner exception an actor that cannot use the requested manner must use an alternative one without unnecessary delay, with no number of days stated, while an actor declining a request as infeasible must say why in writing within ten business days.

Healthcare · Customer & Citizen Experience. Published November 14, 2026. Last reviewed November 14, 2026.

License: CC BY 4.0. Underlying government texts are public domain or under their own terms. <https://creativecommons.org/licenses/by/4.0/>. Attribution: "Moraph Insights", <https://insights.moraph.com/compare/patient-health-data-access-deadlines>.

## The table

Each cell ends with the number of its source in "Sources". Cells were checked on November 14, 2026 unless the cell gives another date. Data: <https://insights.moraph.com/compare/patient-health-data-access-deadlines.csv> (CSV), <https://insights.moraph.com/compare/patient-health-data-access-deadlines.json> (JSON).

| Duty | Rule | Who | Clock starts | Deadline | Applies from |
|---|---|---|---|---|---|
| Act on an individual's request to access protected health information [1] | 45 CFR 164.524(b)(2) [1] | HIPAA covered entities [1] | Receipt of the request [1] | No later than 30 days after receipt; one extension of no more than 30 days, with a written statement of the reasons for the delay and the completion date given within the first 30 days [1] | Not confirmed (see Method) |
| Fulfill a request to access, exchange, or use electronic health information in an alternative manner when the requested manner is not possible (manner exception) [2] | 45 CFR 171.301(b) [2] | Actors under the information blocking rules [2] | The actor cannot fulfill the request in the manner requested (technically unable, or no agreeable terms) [2] | Without unnecessary delay; no number of days is stated [2] | Not confirmed (see Method) |
| Tell the requestor in writing why a request is infeasible (infeasibility exception) [3] | 45 CFR 171.204(b) [3] | Actors under the information blocking rules [3] | Receipt of the request [3] | Within ten business days of receipt of the request [3] | Not confirmed (see Method) |
| Make claims and encounter data available through the Patient Access API [4] | 42 CFR 422.119(b)(1)(i) and (ii) [4] | Medicare Advantage organizations [4] | A claim is processed, or encounter data from capitated providers are received [4] | No later than one (1) business day after [4] | January 1, 2021, for data with a date of service on or after January 1, 2016 [4] |
| Make data in a 45 CFR 170.213 content standard (USCDI) available through the Patient Access API [4] | 42 CFR 422.119(b)(1)(iii) [4] | Medicare Advantage organizations [4] | The MA organization receives the data [4] | No later than 1 business day after [4] | January 1, 2021, for data with a date of service on or after January 1, 2016 [4] |
| Make prior authorization information (excluding drugs) available through the Patient Access API [4] | 42 CFR 422.119(b)(1)(iv) [4] | Medicare Advantage organizations [4] | Receipt of a prior authorization request, and each status change [4] | Accessible no later than 1 business day after the request is received; updated no later than 1 business day after any status change; kept accessible while the authorization is active and at least 1 year after its last status change [4] | January 1, 2027 [4] |
| Make claims, encounter, USCDI and covered outpatient drug information available through the Patient Access API; prior authorization information from 2027 [5] | 42 CFR 431.60 [5] | State Medicaid agencies [5] | A claim is processed, data are received, drug information takes effect, or a prior authorization request is received or changes status [5] | No later than one (1) business day after each trigger [5] | January 1, 2021, for data with a date of service on or after January 1, 2016; prior authorization information beginning January 1, 2027 [5] |
| Make claims, encounter, USCDI and covered outpatient drug information available through the Patient Access API; prior authorization information from 2027 [10] | 42 CFR 457.730 [10] | State CHIP agencies [10] | A claim is processed, data are received, drug information takes effect, or a prior authorization request is received or changes status [10] | No later than one (1) business day after each trigger [10] | January 1, 2021, for data with a date of service on or after January 1, 2016; prior authorization information beginning January 1, 2027 [10] |
| Run the Patient Access API required by 431.60 as if it applied directly to the plan [6] | 42 CFR 438.242(b)(5) and (b)(9) [6] | Medicaid MCOs, PIHPs and PAHPs [6] | As in 431.60 [6] | As in 431.60 (no later than one business day) [5] | By January 1, 2021, except 431.60(b)(5), (g) and (h); 431.60(b)(5) and (g) by the rating period beginning on or after January 1, 2026 [6] |
| Make claims, encounter and USCDI data available through the Patient Access API; prior authorization information from plan year 2027 [7] | 45 CFR 156.221 [7] | QHP issuers on an individual market Federally-facilitated Exchange, not including issuers offering only stand-alone dental plans; the Exchange may grant an exception [7] | A claim is processed, data are received, or a prior authorization request is received or changes status [7] | No later than one (1) business day after each trigger [7] | Plan years beginning on or after January 1, 2021, for data with a date of service on or after January 1, 2016; prior authorization information for plan years beginning on or after January 1, 2027 [7] |
| Share enrollee data with in-network providers through the Provider Access API [8] | 42 CFR 422.121(a) [8] | Medicare Advantage organizations [8] | A request from an in-network provider, when the listed conditions are met (among them, the provider's identity is authenticated and the enrollee is attributed to the provider) [8] | No later than 1 business day after receiving the request [8] | January 1, 2027 [8] |
| Send an enrollee's data to another payer through the Payer-to-Payer API [8] | 42 CFR 422.121(b) [8] | Medicare Advantage organizations [8] | A request from another payer, when the listed conditions are met (among them, the payer's identity is authenticated and it attests that the patient is enrolled with it) [8] | Within 1 business day of receiving the request [8] | January 1, 2027 [8] |
| Permission, not a duty: the laboratory may give patients access to completed test reports on request [9] | 42 CFR 493.1291(l) [9] | Laboratories under CLIA [9] | A request from the patient or personal representative [9] | None stated: the laboratory may provide access to completed test reports that, using its authentication process, can be identified as belonging to the patient [9] | Not confirmed (see Method) |

## Method

Each section was read in the current eCFR text of titles 42 and 45 (versioner API, text up to date as of 2026-11-12) on 2026-11-14, and deadlines and dates were copied from it. Only duties with a stated clock, or a stated absence of one, are compared; content of the data, API standards, exceptions other than manner and infeasibility, enforcement, state law and the Medicaid, CHIP and QHP Provider Access and Payer-to-Payer sections are not compared. Applies-from dates are given only where the section states them.

## Omitted

- **Act on an individual's request to access protected health information · Applies from:** Section 164.524 does not state a compliance date.
- **Fulfill a request to access, exchange, or use electronic health information in an alternative manner when the requested manner is not possible (manner exception) · Applies from:** Section 171.301 does not state an applicability date.
- **Tell the requestor in writing why a request is infeasible (infeasibility exception) · Applies from:** Section 171.204 does not state an applicability date.
- **Permission, not a duty: the laboratory may give patients access to completed test reports on request · Applies from:** Section 493.1291 does not state an applicability date for paragraph (l).

## Sources

1. U.S. Department of Health and Human Services. 45 CFR 164.524, Access of individuals to protected health information. <https://www.ecfr.gov/current/title-45/section-164.524> Checked November 14, 2026.
2. U.S. Department of Health and Human Services. 45 CFR 171.301, Manner exception. <https://www.ecfr.gov/current/title-45/section-171.301> Checked November 14, 2026.
3. U.S. Department of Health and Human Services. 45 CFR 171.204, Infeasibility exception. <https://www.ecfr.gov/current/title-45/section-171.204> Checked November 14, 2026.
4. Centers for Medicare & Medicaid Services. 42 CFR 422.119, Access to and exchange of health data and plan information (Medicare Advantage). <https://www.ecfr.gov/current/title-42/section-422.119> Checked November 14, 2026.
5. Centers for Medicare & Medicaid Services. 42 CFR 431.60, Beneficiary access to and exchange of data (Medicaid). <https://www.ecfr.gov/current/title-42/section-431.60> Checked November 14, 2026.
6. Centers for Medicare & Medicaid Services. 42 CFR 438.242, Health information systems (Medicaid managed care). <https://www.ecfr.gov/current/title-42/section-438.242> Checked November 14, 2026.
7. Centers for Medicare & Medicaid Services. 45 CFR 156.221, Access to and exchange of health data and plan information (QHP issuers on Federally-facilitated Exchanges). <https://www.ecfr.gov/current/title-45/section-156.221> Checked November 14, 2026.
8. Centers for Medicare & Medicaid Services. 42 CFR 422.121, Access to and exchange of health data for providers and payers (Medicare Advantage). <https://www.ecfr.gov/current/title-42/section-422.121> Checked November 14, 2026.
9. Centers for Medicare & Medicaid Services. 42 CFR 493.1291, Standard: Test report (CLIA). <https://www.ecfr.gov/current/title-42/section-493.1291> Checked November 14, 2026.
10. Centers for Medicare & Medicaid Services. 42 CFR 457.730, Beneficiary access to and exchange of data (CHIP). <https://www.ecfr.gov/current/title-42/section-457.730> Checked November 14, 2026.

Last reviewed: November 14, 2026
Canonical URL: <https://insights.moraph.com/compare/patient-health-data-access-deadlines>
Publisher: Moraph Insights
