Amendment request response period

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

Action means a decision plus required next steps

Current 45 CFR 164.526 directs an entity that grants a request to make the amendment and inform the individual. A denial requires a timely plain-language written notice with specified rights and complaint information. A status such as under review does not complete either path.

Start the clock from documented receipt under the entity's amendment process. Confirm identity and authority, the disputed PHI, the requested change, and any advance writing or reason requirement the entity has properly communicated. Search every affected designated record set and route questions about origin, accuracy, or completeness to qualified reviewers early in the 60-day period.

For an acceptance, identify the affected records and append or link the amendment, inform the individual, obtain relevant recipient identification and agreement, and make the required reasonable downstream efforts. For a denial, give the complete written notice and prepare to receive a statement of disagreement. The response period governs action on the request; implementation evidence shows that the selected path became real.

Part decisions need segmented tracking

A request can be accepted in part and denied in part. Record each disputed item, designated-record-set location, decision, basis, owner, individual notice, linkage, disagreement rights, and downstream work. Keep the request-level clock while showing each item's outcome.

Create an item table at intake instead of reconstructing one at the deadline. One request might challenge a diagnosis label, service date, contact detail, and billing code across several systems. Map each assertion to its affected records and reviewer. Mixed decisions should produce a notice that lets the individual see exactly what changed, what did not, and which rights apply to each denied item.

Clarification should preserve the original clock history. Record what was unclear, when clarification was requested, what the individual supplied, and whether the scope changed. A truly distinct later request may receive its own record, but routine follow-up should not silently reset receipt.

Control the extension as part of the same timeline

If the entity cannot act within 60 days, it may use one extension of no more than 30 days after giving a written reason and completion date within the original period. Keep the original receipt, first due date, notice date, reason, promised date, and final action together. System logic should prevent a second extension.

Use the additional time to close specific tasks. “Waiting for review” should name the reviewer, materials needed, escalation date, and decision deadline. Prepare acceptance linkage or denial-notice fields before the promised date. A timely extension followed by a missed promised date is still an overdue final outcome.

Example across request items

A request contains four disputed items. Two are accepted, one is denied with a complete notice, and one remains under review after day 60 without an extension. Item disposition is 3 of 4 items, while request-level timely completion is 0 of 1 request.

If a valid extension had been sent before day 60, the request could remain timely through the stated extended date while the fourth item stayed open. Once that item is decided, measure the accepted items' linkage and the denied item's notice separately. This prevents a dashboard from treating three correct decisions as a complete request or treating the final decision as proof of every follow-up action.

Response-period checklist

• Preserve receipt date, requester identity, authority, disputed PHI, and requested change.
• Map every disputed item to affected designated-record-set locations.
• Assign reviewers and collect evidence early in the 60-day period.
• Record acceptance, denial, or mixed outcomes at item and request levels.
• Use at most one qualifying extension after timely written notice.
• Complete the acceptance linkage or denial notice required for each item.
• Retain individual communication and delivery evidence.
• Report timeliness, item disposition, and path implementation separately.

Owner controls

Use a receipt event that staff cannot overwrite, deadline calculations, whole-or-part fields, a single-extension limit, and acceptance and denial checklists. The HHS Audit Protocol can guide evidence review. Report overdue requests even when most items are resolved.

Audit requests close to both deadlines, mixed outcomes, changed scope, and cases with vendor-held records. Track median age, extension use, overdue items, notice defects, linkage defects, and unresolved recipient work. A strong response-period record tells the complete story from receipt through the action that the rule requires.