ABA Record Accuracy, Correction and Amendment Request Tracker for Families

Use one copy for one record or closely related set of entries. Quote only the wording needed to identify the issue. Preserve the original record separately and unchanged.

This ABA record correction request tracker for families is a family-owned preparation and follow-up tool. It is not a formal amendment request, legal complaint, grievance, payer appeal, billing adjustment, clinical opinion or replacement health record.

Families and Caregivers / Progress, Quality, Rights and Ethical Care.

What this tracker can and cannot establish

The tracker can preserve which record the family reviewed, what appears inaccurate or incomplete to the family, the requested correction or clarification, supporting context, the office or person contacted, and each dated response. It can also distinguish an accepted change, an addendum, a denial and an unresolved disagreement.

Important boundary: This tracker cannot alter a source record or declare information false, incomplete, fraudulent or unlawful. It cannot decide whether HIPAA or another law applies; identify a designated record set; determine an amendment right, deadline, required outcome, legal representative, wrongdoing, clinical appropriateness or payer liability; or replace a provider, plan, privacy, records, grievance, billing or legal process.

The BACB Ethics Code for Behavior Analysts addresses documentation, confidentiality, informed consent, communication and applicable requirements within its professional scope. A family tracker cannot determine code compliance or resolve a factual or clinical disagreement.

Identify the source record before describing the concern

Source-record fieldEntryRecord title or typeLearner or account identifier used by the holderService, claim or event dateDate the record was created or receivedAuthor, office or record holder, if knownPage, section, line or transaction referenceFamily copy locationResponsible correction or amendment route to confirm

Identify the exact record rather than describing a general disagreement. Note whether the family is looking at a portal display, exported copy, invoice, explanation of benefits or another source. Those documents may have different owners and correction routes.

Retain the original version. Record its date. Do not edit a downloaded copy in a way that makes it look like the source record changed.

Describe the questioned entry with attribution

Questioned-entry fieldFamily entryExact wording or data element at issueWhy the family believes review is neededFamily observation or alternate accountSupporting document or source, if anyRequested correction, clarification or addendumInformation the family does not know

Use precise language such as “the family reports” or “the portal copy shows.” Avoid stating that an author lied, committed fraud or violated a rule. A difference between recollections is not resolved by this worksheet.

Separate a factual entry from a professional opinion. A family may ask how either was documented. The responsible record holder decides how its process addresses the request.

Keep correction routes distinct

Possible routeWhat it may addressResponsible source to confirmReference or statusInformal clarificationMeaning or source of an entryProvider addendum or correctionProvider-owned record processFormal HIPAA amendment request, if applicableCovered record and applicable rightStatement of disagreement, if applicableResponse to a denied amendmentBilling or claim correctionCharge, code, claim or payment recordPayer dispute or appealPlan decision or noticeGrievance or complaintSeparate concern processSchool or other record processRecord held outside the ABA provider

One concern may involve more than one record holder. Do not assume that an ABA provider can change a payer, school or outside clinician's record. Route each question to the responsible source.

An acknowledgement is not a correction. A corrected family note is not a provider amendment. A billing adjustment does not necessarily change a clinical entry.

Prepare a bounded request

Request fieldEntryRecord or entry identifiedAction requestedReason stated in the family's wordsSupporting material includedRecipient and roleRequired form or channel confirmedDate sentCopy and delivery evidence retained

Ask the responsible organization whether it requires a specific form, signed request, reason or delivery channel. Do not invent a legal deadline. Record a timeline only when it comes from the responsible source.

Limit the request to the entry under review. Remove unrelated sensitive information. Keep originals of any supporting document.

Understand the HIPAA boundary without assuming it applies

The HHS medical-records overview says that people can request an amendment when they believe information in a medical or billing record is incorrect. It also explains that a provider or plan must respond and that a statement of disagreement may be available after a denial. That overview concerns HIPAA-covered records and does not establish that every ABA organization, document or family request falls within the same rule.

The current 45 CFR 164.526 eCFR text describes the amendment process for protected health information in a designated record set. It includes grounds for denial, response timing, accepted amendments, denials, statements of disagreement and recordkeeping. The responsible covered entity must determine application to a particular request.

This tracker does not calculate a due date. It does not decide whether an extension is available. A family should preserve the dated response supplied by the responsible entity.

Track acknowledgement and attributed response

Follow-up eventDateSource and exact responseOwnerNext step or statusDelivery confirmedAcknowledgement receivedMore information requestedReview underwayRequest accepted in whole or partRequest denied in whole or partAddendum or link suppliedSeparate billing, payer or grievance route opened

Copy the response rather than summarizing it from memory. Name the office or role that issued it. Preserve any reason, form, contact or reference number that the response provides.

Do not mark the source record corrected merely because someone replied. Confirm what changed and where. Keep an unanswered question open.

Record accepted changes without rewriting history

Accepted-action fieldEntryRequest accepted in whole or partRecord or location affectedCorrection, amendment, addendum or link describedEffective or completion date suppliedPeople or entities the holder says it will notifyUpdated copy requested or receivedFamily question still open

An amendment may be linked to an earlier record rather than erasing it. Preserve the response's description. Do not claim that every downstream copy changed unless the responsible source confirms that action.

Update the family's tracker separately. Maintain the original concern, the response and the final action as visible entries. This creates a chronology rather than a replacement record.

Preserve a denial or disagreement as its own record

Denial or disagreement fieldEntryDenied item and dateReason supplied by the responsible entityInstructions or rights described in the responseStatement-of-disagreement route, if offeredComplaint or other route namedFamily action takenRebuttal or later response receivedFinal open question

A denial is not proof that the family was wrong. A disagreement is not proof that the source record was inaccurate. Preserve both attributed positions.

Do not turn the tracker itself into a statement of disagreement unless the responsible process accepts it in that form. Ask where and how a formal response must be submitted.

Keep access, amendment and correction separate

The HHS right-of-access guidance explains the HIPAA access right and distinctions between access and authorization. Getting a copy, asking for an amendment and authorizing a disclosure are different actions. A family may need to confirm which route matches its goal.

A missing document may call for an access or delivery request. A questioned entry may call for clarification or amendment review. A billing issue may belong with a billing or payer process.

Fictional example: one disputed session-time entry

This fictional example describes no real learner, family, provider, payer or record.

Source record. Mina's father, Theo, downloads a November 12 service note from the portal for fictional Harbor Grove ABA. The note lists the session end time as 5:30 p.m. Theo's calendar and the pickup message both show 4:30 p.m.

Family entry. Theo quotes the time field and writes that he is asking the provider to review whether the end time is accurate. He attaches the pickup message. He does not state that the note is fraudulent or decide that a billing error occurred.

Route and response. The provider's records office asks Theo to use its correction form. Theo records the form date and reference number. The office later states that the time field will be corrected and that billing will review its separate record.

Follow-up. Theo receives an updated copy with the corrected time. He marks only the provider record action complete. The billing review remains open because no billing response has arrived.

The example does not establish HIPAA coverage, a designated record set, a legal deadline, wrongdoing, clinical inaccuracy, billing liability, payer error or required outcome.