Comparison tables

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

How fast patients and payers must get health data: HIPAA access, information blocking and CMS API deadlines compared Each number links to the cell's source. Cells checked unless the cell shows another date.
DutyRuleWhoClock startsDeadlineApplies from
Act on an individual's request to access protected health information1Rule45 CFR 164.524(b)(2)1WhoHIPAA covered entities1Clock startsReceipt of the request1DeadlineNo 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 days1Applies fromNot 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)2Rule45 CFR 171.301(b)2WhoActors under the information blocking rules2Clock startsThe actor cannot fulfill the request in the manner requested (technically unable, or no agreeable terms)2DeadlineWithout unnecessary delay; no number of days is stated2Applies fromNot confirmed (see Method)
Tell the requestor in writing why a request is infeasible (infeasibility exception)3Rule45 CFR 171.204(b)3WhoActors under the information blocking rules3Clock startsReceipt of the request3DeadlineWithin ten business days of receipt of the request3Applies fromNot confirmed (see Method)
Make claims and encounter data available through the Patient Access API4Rule42 CFR 422.119(b)(1)(i) and (ii)4WhoMedicare Advantage organizations4Clock startsA claim is processed, or encounter data from capitated providers are received4DeadlineNo later than one (1) business day after4Applies fromJanuary 1, 2021, for data with a date of service on or after January 1, 20164
Make data in a 45 CFR 170.213 content standard (USCDI) available through the Patient Access API4Rule42 CFR 422.119(b)(1)(iii)4WhoMedicare Advantage organizations4Clock startsThe MA organization receives the data4DeadlineNo later than 1 business day after4Applies fromJanuary 1, 2021, for data with a date of service on or after January 1, 20164
Make prior authorization information (excluding drugs) available through the Patient Access API4Rule42 CFR 422.119(b)(1)(iv)4WhoMedicare Advantage organizations4Clock startsReceipt of a prior authorization request, and each status change4DeadlineAccessible 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 change4Applies fromJanuary 1, 20274
Make claims, encounter, USCDI and covered outpatient drug information available through the Patient Access API; prior authorization information from 20275Rule42 CFR 431.605WhoState Medicaid agencies5Clock startsA claim is processed, data are received, drug information takes effect, or a prior authorization request is received or changes status5DeadlineNo later than one (1) business day after each trigger5Applies fromJanuary 1, 2021, for data with a date of service on or after January 1, 2016; prior authorization information beginning January 1, 20275
Make claims, encounter, USCDI and covered outpatient drug information available through the Patient Access API; prior authorization information from 202710Rule42 CFR 457.73010WhoState CHIP agencies10Clock startsA claim is processed, data are received, drug information takes effect, or a prior authorization request is received or changes status10DeadlineNo later than one (1) business day after each trigger10Applies fromJanuary 1, 2021, for data with a date of service on or after January 1, 2016; prior authorization information beginning January 1, 202710
Run the Patient Access API required by 431.60 as if it applied directly to the plan6Rule42 CFR 438.242(b)(5) and (b)(9)6WhoMedicaid MCOs, PIHPs and PAHPs6Clock startsAs in 431.606DeadlineAs in 431.60 (no later than one business day)5Applies fromBy 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, 20266
Make claims, encounter and USCDI data available through the Patient Access API; prior authorization information from plan year 20277Rule45 CFR 156.2217WhoQHP issuers on an individual market Federally-facilitated Exchange, not including issuers offering only stand-alone dental plans; the Exchange may grant an exception7Clock startsA claim is processed, data are received, or a prior authorization request is received or changes status7DeadlineNo later than one (1) business day after each trigger7Applies fromPlan 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, 20277
Share enrollee data with in-network providers through the Provider Access API8Rule42 CFR 422.121(a)8WhoMedicare Advantage organizations8Clock startsA 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)8DeadlineNo later than 1 business day after receiving the request8Applies fromJanuary 1, 20278
Send an enrollee's data to another payer through the Payer-to-Payer API8Rule42 CFR 422.121(b)8WhoMedicare Advantage organizations8Clock startsA 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)8DeadlineWithin 1 business day of receiving the request8Applies fromJanuary 1, 20278
Permission, not a duty: the laboratory may give patients access to completed test reports on request9Rule42 CFR 493.1291(l)9WhoLaboratories under CLIA9Clock startsA request from the patient or personal representative9DeadlineNone stated: the laboratory may provide access to completed test reports that, using its authentication process, can be identified as belonging to the patient9Applies fromNot confirmed (see Method)

Get the data: CSV · JSON

License: CC BY 4.0. Underlying government texts are public domain or under their own terms. Attribute "Moraph Insights" with a link to the page.

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

What was left out, and why.

  • 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. Checked .
  2. U.S. Department of Health and Human Services. 45 CFR 171.301, Manner exception. Checked .
  3. U.S. Department of Health and Human Services. 45 CFR 171.204, Infeasibility exception. Checked .
  4. Centers for Medicare & Medicaid Services. 42 CFR 422.119, Access to and exchange of health data and plan information (Medicare Advantage). Checked .
  5. Centers for Medicare & Medicaid Services. 42 CFR 431.60, Beneficiary access to and exchange of data (Medicaid). Checked .
  6. Centers for Medicare & Medicaid Services. 42 CFR 438.242, Health information systems (Medicaid managed care). Checked .
  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). Checked .
  8. Centers for Medicare & Medicaid Services. 42 CFR 422.121, Access to and exchange of health data for providers and payers (Medicare Advantage). Checked .
  9. Centers for Medicare & Medicaid Services. 42 CFR 493.1291, Standard: Test report (CLIA). Checked .
  10. Centers for Medicare & Medicaid Services. 42 CFR 457.730, Beneficiary access to and exchange of data (CHIP). Checked .

How we source and check every fact: Editorial standards · Corrections

Last reviewed .

Spotted an error? Tell us and we will check it and correct the table where needed.