An ABA health record electronic copy problem tracker for families describes a delivered file that will not open, cannot be read as delivered or appears technically incomplete. It records observable facts, safe follow-up and any replacement without deciding that the records are legally incomplete, clinically inaccurate or insecure.

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

Use this after an electronic copy arrives

Use the ABA health record electronic copy problem tracker for families after a copy arrives with an opening or readability problem. Keep the original delivery evidence and do not overwrite the received file while testing.

Choose the path that matches the observed event:

Observed eventRecord it here?Separate next stepFile will not openYesRecord the exact error and limited safe testsPages display as blank, garbled or cut offYesRecord filenames and affected page ranges without clinical excerptsFile is not usable with the family's assistive technologyYesRecord the access need and organization responseRequested record category was not deliveredRecord the delivery fact here, then reconcile scopeUse the records-request trackerA clinical statement appears wrongNoUse the record correction and amendment trackerLink or attachment appears suspiciousStop ordinary testingContact the organization through a trusted route and seek security guidancePortal account cannot be accessedUsually noUse the organization's account-support process

This tracker does not determine whether delivery fulfilled a legal access request. It gives the family a precise record for the responsible office.

Preserve request and delivery evidence

Request or delivery factFamily entryOrganization and officeWrite here. For item 1, add evidence when available.Original request date and referenceWrite here. For item 2, add evidence when available.Requested records and date rangeWrite here. For item 3, add evidence when available.Requested form and formatWrite here. For item 4, add evidence when available.Agreed alternative, if anyWrite here. For item 5, add evidence when available.Delivery date and timeWrite here. For item 6, add evidence when available.Delivery routeWrite here. For item 7, add evidence when available.Sender or portal sourceWrite here. For item 8, add evidence when available.Message or receipt evidenceWrite here. For item 9, add evidence when available.Number of files receivedWrite here. For item 10, add evidence when available.Family-controlled location of untouched originalsWrite here. For item 11, add evidence when available.

Keep the delivered originals unchanged when practical. Work from a copy if the family performs ordinary opening tests. This preserves what was received but does not authenticate the files or certify the storage location as secure.

Inventory files without copying clinical content

Use one row per file or archive. Record metadata visible to the family, not treatment details from inside the record. If a filename itself contains sensitive information, use a private local label in messages that do not need the full name.

Filename as receivedFile typeFile sizeDate receivedPassword or access instruction received?Observed statusYes / no / unclearWrite here. For item 12, add evidence when available.Yes / no / unclearWrite here. For item 13, add evidence when available.Yes / no / unclearWrite here. For item 14, add evidence when available.

If an archive contains several files, note the archive and any visible file list separately. Do not upload the record to a public conversion site merely to identify the format.

Describe the problem exactly

Avoid a broad statement such as “the records do not work.” Observable details help the records or technical team distinguish a password issue, unsupported format, damaged transfer, display problem or accessibility need.

Problem fieldFamily entryDate and time first observedWrite here. For item 15, add evidence when available.Filename affectedWrite here. For item 16, add evidence when available.Device type and operating systemWrite here. For item 17, add evidence when available.Application or browser usedWrite here. For item 18, add evidence when available.Exact error message, if safe to copyWrite here. For item 19, add evidence when available.What appeared on screenWrite here. For item 20, add evidence when available.Page or section range affected, without clinical excerptWrite here. For item 21, add evidence when available.Whether another file from the delivery opensWrite here. For item 22, add evidence when available.Whether the untouched original remains savedWrite here. For item 23, add evidence when available.Accessibility or communication impactWrite here. For item 24, add evidence when available.

Do not label the file corrupt, malicious, incomplete or altered unless a qualified source reaches that conclusion. “The PDF viewer displayed an error” is an observation. “The provider corrupted the record” is an inference.

Limit tests to ordinary, low-risk steps

Families have different devices, technical skills and security circumstances. Every test is optional. Stop before opening or interacting further if a link, attachment, password prompt or application seems unexpected.

Optional testResultDateCopy testedNotesConfirm the download completedWorking copy / original not changedWrite here. For item 25, add evidence when available.Compare filename and size with the delivery messageWrite here. For item 26, add evidence when available.Use an already installed, trusted application that normally opens the stated typeWrite here. For item 27, add evidence when available.Restart the trusted application and try the working copy againWrite here. For item 28, add evidence when available.Follow an organization-provided password instruction already verified through a trusted routeWrite here. For item 29, add evidence when available.

Do not disable security controls, install unknown software, share a password, forward records to an unrelated person or upload protected health information to an unapproved online tool. A family can contact the organization's official records or security route instead of troubleshooting further.

Connect the problem to format and readability

The current access rule at 45 CFR 164.524(c)(2) addresses the form and format of access under the federal rule, including requested formats that are readily producible and other readable electronic formats as agreed in specified circumstances. The HHS electronic-copy FAQ offers a similar general explanation.

Record what the family requested, what the organization delivered and what problem was observed. This tracker cannot decide whether a format was readily producible, whether an alternative is acceptable or whether the organization fulfilled an applicable rule.

Format comparisonFamily entryFormat originally requestedWrite here. For item 30, add evidence when available.Format deliveredWrite here. For item 31, add evidence when available.Alternative previously discussed or agreedWrite here. For item 32, add evidence when available.Problem with opening or ordinary readabilityWrite here. For item 33, add evidence when available.Assistive-technology or accessible-format needWrite here. For item 34, add evidence when available.Replacement or alternative requested nowWrite here. For item 35, add evidence when available.Organization responseWrite here. For item 36, add evidence when available.

The HHS professional right-of-access guidance provides operational explanations about electronic copies, form and format for covered entities. Use it as background, not as a ruling on one delivery.

Send a focused problem report

Copyable message:

I am following up on the electronic health-record copy delivered on [date] for request [reference]. The file named [filename] was delivered as [file type]. On [device and application], I observed [exact error or display problem] on [date and time]. I preserved the original and tried only these ordinary steps on a copy: [steps]. Please confirm the responsible office and provide either a replacement in the requested format or a readable alternative your office and I can discuss. Please do not include unrelated clinical details in an ordinary reply. My accessibility or communication need is [need, if relevant].

Send the message through a trusted organization route. Include only the metadata needed to identify the delivery unless the organization provides a verified way to transmit more.

Track the organization's response

Date and timePerson or officeResponse or instructionReplacement promised?Route statedEvidence savedNext stepYes / no / unclearWrite here. For item 37, add evidence when available.Yes / no / unclearWrite here. For item 38, add evidence when available.Yes / no / unclearWrite here. For item 39, add evidence when available.

Record a promise as an attributed statement, including the source and date. This page cannot promise that the organization will provide a replacement or set the legal timing.

Reconcile a replacement or alternative

When another copy arrives, keep it distinct from the original delivery.

Reconciliation itemOriginal deliveryReplacement or alternativeFamily observationDelivery dateWrite here. For item 40, add evidence when available.Filename and typeWrite here. For item 41, add evidence when available.File countWrite here. For item 42, add evidence when available.Opens in the family's ordinary trusted applicationYes / no / unclearReadable as displayedYes / no / unclearWorks with stated accessibility needYes / no / unclearRequested categories visibly representedYes / no / unclearRemaining technical issueWrite here. For item 43, add evidence when available.

“Visibly represented” is not a clinical or legal completeness finding. If a requested category appears absent, return to the records request and delivery tracker and ask the organization to reconcile the scope.

Preserve accessibility without deciding compliance

The Department of Justice effective-communication guidance describes context-specific auxiliary aids and services for covered organizations. Record the family's need, the barrier encountered and the response. Applicability and compliance require qualified review.

Access needBarrier observedFamily requestOrganization responseOutcomeScreen-reader compatibilityWrite here. For item 44, add evidence when available.Large print or magnificationWrite here. For item 45, add evidence when available.Language or interpreter supportWrite here. For item 46, add evidence when available.Captioned or relay communicationWrite here. For item 47, add evidence when available.OtherWrite here. For item 48, add evidence when available.

Close with a factual endpoint

EndpointEvidence and dateReplacement opens and is readable for the family's stated useWrite here. For item 49, add evidence when available.Agreed alternative receivedWrite here. For item 50, add evidence when available.Some files work and identified files remain unresolvedWrite here. For item 51, add evidence when available.Organization says no replacement will be providedWrite here. For item 52, add evidence when available.Issue moved to access-denial or scope follow-upWrite here. For item 53, add evidence when available.Security concern moved to the organization's official security routeWrite here. For item 54, add evidence when available.No endpoint yet; next owner and follow-up dateWrite here. For item 55, add evidence when available.

Do not close the tracker based only on silence. Do not use the endpoint to declare legal fulfillment, record authenticity, clinical accuracy, security or a violation.

Fictional filled example

This example is invented and is not a security, completeness or compliance conclusion.

FieldFictional entryOrganizationNorth Grove Behavior Services records officeOriginal requestJune 4 request for treatment plans and progress summaries from March through May as readable electronic copiesDeliveryJune 12 portal download with two PDF filesObserved problemFile named ProgressSummaries.pdf produces “file cannot be opened” in the family's existing PDF application; TreatmentPlans.pdf opensSafe testsDownload completion confirmed; working copy tried once in the same trusted application; original preservedFamily messageJune 12 portal message identifies filename, error and application without attaching clinical pagesAccessibility needScreen-reader-compatible replacement requestedOrganization responseJune 13 records-office message says it will export a replacement PDF and provide a new portal noticeReplacementNew file received June 14; opens in the family's ordinary application and is readable with the family's screen readerEndpointTechnical follow-up closed; family uses the separate records-request tracker to reconcile requested categories

The family records that the replacement worked for its stated use. It does not conclude that either file was complete, authentic, secure or legally sufficient.

Limits of this tracker

This tracker cannot determine which law applies, who may request access or what belongs in a designated record set. It cannot decide whether delivered files are complete, authentic or clinically accurate, or whether a format is readily producible or accessible. It also cannot decide whether transmission or storage is secure, whether an event is a breach or malware incident, whether access was timely, or whether a violation or remedy exists. Preserve the original evidence and seek current guidance from the responsible records, privacy, security, clinical, accessibility, payer, regulator, state-law or legal source.

Related resources

Sources

These sources do not certify a file, format, delivery route or family device. The BACB code is not a technical-file or privacy-law standard.

Finni resources

Ready for the next step?

Find ABA care near you