What does a fax confirmation establish for the workflow?
Keep the fax confirmation, confirm the records custodian and request version, and link any resend to the original request until intake is acknowledged.
When a provider cannot locate a medical-records request, a successful transmission record is useful history. It does not tell your team which intake queue holds the packet, whether the authorization was accepted, or whether records are ready. Treat the situation as an open request-location exception. Preserve the packet and confirmation together, then identify the receiving operation and its next action. This checklist addresses that narrow exception for Texas PI teams; counsel remains responsible for legal service and deadline questions.
Match the confirmation to the saved packet
Match the confirmation to the exact packet. Record the original send time, destination used, result and page count if available. Compare the requested facility, document types and service dates with the saved version. A confirmation attached to a different packet cannot explain what this request contained. Keep client identifiers and copies inside the firm’s approved systems rather than in public worksheets or screenshots.
Confirm the facility, document type and custodian
UTHealth Houston’s records-routing guidance warns that requests may be directed to individual providers or clinics that are not the custodian. It identifies separate UT Physicians medical-records and billing-records routes. That is a practical reason to check the requested document type before repeating the original transmission.
Houston Methodist’s nonpatient-request instructions direct an authorization to the facility where care occurred. Confirm the actual treatment facility, then use its current official instructions. If a web page, saved form and older address book disagree, confirm the route through the published office contact before sending. Do not choose a destination merely because an earlier transmission succeeded.
Ask for a location result and processing state
Ask the receiving operation to locate the saved request using the identifiers permitted by your firm’s approved process. Request an intake reference and the received date shown in its system. Separately ask whether the request is ready for processing or waiting on a requirement. Texas Health’s request-status guidance describes a received-request letter with a Verisma access code for tracking. Other providers may use different references; the useful evidence is acknowledgment of the particular request.
A located request can still be blocked. UT Physicians’ legal-billing instructions require its request form and payment for processing, and direct medical-record requests elsewhere. Record the actual missing item and assign the firm decision. Do not turn a billing-record requirement into a universal medical-records rule or approve a charge during a routine status check.
Choose the next action from the actual exception
Use this decision table after the lookup. The status should describe the evidence obtained, while the next action identifies what one person must do. If the receiving operation cannot give a definite answer, preserve that uncertainty instead of selecting the nearest completed status.
Swipe across the table to see every column. Keyboard users can focus the table and use the arrow keys.
| Lookup result | Next action | Evidence to retain |
|---|---|---|
| Not located | Confirm the route and follow the approved resend instruction. | Lookup date, receiving department and unresolved request reference. |
| Wrong custodian | Confirm the correct department and transfer or resend process. | Original route, correction reason and source of the new instruction. |
| Located but blocked | Assign the specific missing item to its firm approver. | Intake reference, requirement and responsible reviewer. |
| Already processing | Record the next update checkpoint without creating another active request. | Intake reference, processing status and agreed follow-up date. |
| Records reportedly sent | Check the approved receipt destination before marking received. | Delivery reference and actual receipt or missing-file result. |
Keep one exception card and linked resend history
Add a compact exception card to the existing request record. It should explain why the original attempt did not produce a located request and what changed on the follow-up. The medical-records request tracker already covers the wider request lifecycle; this card supplies the missing decision history without creating a second competing tracker.
Swipe across the table to see every column. Keyboard users can focus the table and use the arrow keys.
| Field | What to record |
|---|---|
| Original request | Internal ID, original attempt date and private packet-version link. |
| Transmission evidence | Destination used, confirmation reference and available page count. |
| Confirmed receiving route | Facility, custodian, document category and dated instruction source. |
| Lookup outcome | Not located, located with reference, or still uncertain. |
| Correction or resend | Requested change, firm approval if needed and linked follow-up event. |
| Next checkpoint | Named owner, next review date and evidence needed to resolve the exception. |
If the receiving operation asks for a resend, confirm the route, whether the packet should remain unchanged, and how the duplicate attempt should be identified. Link the new transmission to the original request. A corrected authorization or expanded date range needs an explicitly recorded version and the appropriate firm approval. Never silently replace the original packet or turn a scope change into an ordinary resend.
A fictional resend that preserves the original request
Fictional example: matter F-001 has request R-01 for a clinic’s February through April records. The saved packet is version 1. A fax confirmation exists, but the records office cannot locate the request. The assigned paralegal confirms the custodian through the official contact and records an instruction to resend the unchanged packet through the confirmed route. Attempt 2 stays under R-01, with its own timestamp and confirmation.
The office later supplies intake reference X-204 and its received date. The paralegal records that the location exception is resolved, with processing still pending. The original attempt date remains visible for the firm’s review. No records have been received in this example, and no conclusion about a legal deadline follows from the resend or the reported intake date.
Close the location problem without closing the whole request
Close the location exception when the receiving operation identifies the request and its processing state, with the source, date and remaining requirement recorded. Keep the overall records request open until delivery and review are separately addressed. The medical-records follow-up guide covers those later stages, including a provider reporting that records were sent while the firm still has nothing to review.
For a defined provider status question, review VerifyMD’s sample workflow or discuss setup with the team. Live provider calling requires assisted setup and explicit owner activation. This checklist does not describe an active VerifyMD fax-sending service. Any provider response still needs the firm’s review against the requested scope. Official provider guidance was checked on October 23, 2026.
Explore provider follow-up and source review for your firm. Live calls require agreed setup and activation.
Book a demo