General Surgery Medical Records and the Pre-Op Packet Chase

General surgery medical records work is invisible until a case gets pushed. The consult happened, the date is on the board, and then somebody discovers the clearance letter from the primary care office never arrived, or the outside imaging referenced in the referral was never actually sent. The case moves, the block goes unused, and three other patients wait a week longer.

A surgical episode is a chain: consult, pre-operative work, the case itself, and post-operative follow-up. Each link depends on paperwork produced by somebody who does not work for you. Referring offices send referrals without the records they mention. Clearance letters come back on their own schedule. Forms for employers and insurers arrive with deadlines nobody negotiated.

The practice absorbs all of it through the same phone line that new patients are calling. Records work is interrupt-driven, deadline-bound, and completely unglamorous, which is why it ends up assigned to whoever is least able to say no to it.

And the failure is expensive in a way the front desk never sees on a report. A missing document does not show up as a records problem. It shows up as an empty operating block.

The packet is a checklist with owners, and nobody owns the chase

Every general surgery practice has a version of the same list: outside imaging, relevant labs, the clearance letter, the completed history forms, insurance documentation. What varies is who chases each item and how anybody knows the current state.

In most practices the answer is a person, a spreadsheet, and a memory. That works until volume rises or that person takes a week off. Health information exchange has improved how records move between organizations, but it has not eliminated the phone call to the office that has not sent anything yet.

Automating this starts with making state explicit. For each upcoming case, which items are outstanding, who holds them, when they were last requested, and what the deadline is. Once that state exists in athena rather than in someone’s head, the chasing itself is repetitive outbound work, and repetitive outbound work is exactly what an automated caller does well without getting tired or embarrassed about calling the same office for the fourth time. Once the state is explicit, the chase becomes the same kind of workflow as pre-op patient communication.

Referrals arrive without the records they reference

This is the most common single gap and it is fixable early. A specialist we work with asked whether our system could notice that an inbound referral referenced labs or imaging that were not attached, and then automatically call the referring office to request them. That is a records chase triggered by document intake, and it happens days before anyone would otherwise notice.

Inbound referrals also arrive in more ways than practices expect. At some specialty practices they come as flat PDF faxes explicitly not structured as orders, through a provider-facing portal for high-volume referring offices that want status back, and as self-referrals from patients. The staff question that follows is whether an automated system can pull from the five different inboxes where referrals actually land, rather than one assigned queue.

So the intake side has to be plural by design. Sweep every channel and every athena department documents can land in, classify what arrived, and open the chase for whatever the referral says exists but did not come with it.

Clearance is a scheduling dependency, not just a document

Procedure scheduling frequently requires a clearance visit first, which turns a request to book surgery into a multi-appointment dependency: the clearance appointment, then the case, with the document arriving between them. Book me a surgery date is really a sequence, and the sequence has an ordering constraint the calendar does not enforce.

Gates can also appear inside the chart itself. A chart alert can block a procedure outright, then move to a state where the procedure is permitted but has to be scheduled at least thirty days out. A date rule with a real consequence for the schedule.

The automation reads that the gate exists and reacts to it administratively. It holds the booking, chases the outstanding document, and offers dates only inside the window the practice defined. It never evaluates the gate, never decides whether it applies, and routes anything it cannot resolve to staff with the chart reference attached. The authorization side of that dependency is covered separately in surgical prior authorization.

Sending records out is document generation plus a fax

The outbound half of the job is often ignored in vendor conversations because it is unfashionable. Receiving offices still want faxes and are not planning to stop. A records-request template can generate the document and attach it to an outbound fax, which is the actual shape of the workflow rather than an idealized version of it.

The status calls that follow are pure overhead. Did you get it, when did it go out, can you resend. Every one of those is answerable from state the system already holds, which makes them a good fit for automated handling on both the inbound call and a proactive outbound confirmation.

Post-operative paperwork extends the same pattern. Disability and leave forms, work status letters, and documentation requests all follow the case, all have deadlines, and all get chased the same way. All of it runs off the document and case records themselves, which is why it depends on working inside athena.

The line between chasing and reading

Worth stating plainly because it defines what is safe to automate. The system chases documents, tracks their state, routes them to the correct athena work queue, generates release paperwork, sends it, and reports status to whoever asks.

It does not read the content of a record and decide whether it satisfies the requirement. A clearance letter arriving is an administrative event. Whether that letter is sufficient is a call for your clinical staff, and the workflow hands it to them with the document attached and the case date visible so they can make it quickly.

That split keeps the automation inside the front office where it belongs, and it happens to be where nearly all of the wasted minutes are anyway.

Key Takeaways

Make packet state explicit per case: what is outstanding, who holds it, when it was last requested, and the deadline. You cannot automate a chase that lives in someone’s memory.
Sweep every channel and every athena department where referrals and documents land. Practices routinely discover referrals sitting in a queue nobody monitors.
Trigger the outside-records chase off the referral itself when it references labs or imaging that did not arrive, not the week before the case.
Treat clearance as a scheduling dependency with an ordering constraint, not as a document that will turn up eventually.
Build the outbound side too. Records go out as a generated document plus a fax, and the status calls that follow are answerable from state you already hold.
Draw the line at content. Chasing, routing, and status are administrative. Whether a document satisfies the requirement stays with clinical staff.

Cases do not usually slip because of anything that happened in the operating room. They slip because a piece of paper was three days late and nobody was assigned to notice. Making that chase automatic, inside the same athena document classes and department queues your staff already work, protects the block schedule that everything else in a surgical practice depends on.

Sources