Practice Operations
How Infectious Disease Medical Records Arrive Before the Consult
An infectious disease consult without the outside records is a wasted slot. Here is how AI runs the records chase and the fax intake queue inside athenaOne.
In an infectious disease practice the consult and the paperwork are the same appointment. Infectious disease medical records arrive from a hospital, two other offices, and a lab, and if any of it is missing on the day the patient shows up, the visit happens anyway and produces very little. The records chase is the work. It is also the part nobody has hours for.
Infectious disease is a consult specialty, which means almost every new patient arrives with a history that lives somewhere else. Discharge paperwork sits with the hospital. Culture and sensitivity reports sit with a lab. Prior antibiotic courses sit with whoever prescribed them. The referring office sends a fax that names none of it.
The practices are also small. A group with three or four providers does not have a dedicated release of information desk, so the chase gets absorbed by whoever answers the phone, between calls, in the order the faxes happened to land. That order has nothing to do with which patient is scheduled first.
What makes it expensive is the timing. The gap between a referral arriving and a complete chart is measured in days, and the appointment gets booked on day one. A visit that goes ahead on an incomplete chart is not a small loss. It is a slot in a specialty where slots are scarce, plus a second appointment to do it again.
The referral arrives as a fax and stops there
Consult-driven volume shows up as paper. A fax lands in a general inbox, someone opens it, and the patient is real but has no chart yet, no demographics, and no insurance on file. Until that changes, the referral is not workable and it is not visible to anyone looking at the schedule.
That first hop is entirely administrative and it is where the days go. Ingest the fax, read it, build or match the chart, file the document under the right class, and put it in the department bucket that owns it. None of that requires a license and all of it requires someone to sit down and do it in order.
Automation earns its keep here by making the queue behave like a queue. Inbound faxes get ingested and matched against existing charts, a new chart gets created when there is no match, and the document lands in the bucket a human is actually watching. What reaches a person is the exception: a fax too poor to read, a name that matches two charts, a referral for a service the practice does not offer.
The phone is where this shows up as a cost. Asked which tasks eat the most staff time on the phones, practice leaders named eligibility and prior authorization at 45%, scheduling at 31%, and intake at 9%. Intake looks small in that list right up until you notice it is the step that gates the other two.
Requesting records is a chase, not a send
The request itself is trivial. Generate the authorization form, get it signed, fax it to the holder of the record. The reason it consumes a person is what happens after that, which is nothing, repeatedly.
HIPAA gives a covered entity 30 days to act on an individual’s request for access, with a single 30 day extension available. That is the outer bound the other office is working against, and it is not a schedule that cares about your Thursday clinic. The practical response is follow-up: call on day three, call again on day seven, and escalate to a named contact when the first two produce nothing.
Those follow-up calls are identical every time and they are the first thing dropped on a busy day. An automated caller does them on the cadence the practice sets, logs what each office said, and updates the request status on the chart so the scheduler can see it without asking anyone.
The delivery format splits too. Information-blocking rules under the 21st Century Cures Act now require practices to provide electronic access when a patient asks, yet attorney, workers’ comp, and payer requests still arrive by fax and mail. Most practices are running a paper pipeline and a portal pipeline at the same time, and the caller decides which one they are in without knowing they are deciding anything.
Credentialing decides whether the packet was worth building
Small provider counts create a problem bigger practices absorb quietly. Credentialing resolves per provider, per payer, per state, and per treatment type, and in a group with four physicians a single enrollment gap can block a meaningful share of inbound referrals.
The enrollment matrix almost always lives in a spreadsheet outside the EHR, which means nothing in scheduling knows about it. Book a referred patient with a provider who is not enrolled in their plan and you get a visit that happens, a records chase that was completed, and a claim that dies six weeks later.
Most practices cannot hand over a clean enrollment grid because it is too messy to export. The workable artifact is the inverse: a per provider list of the plans they do not take. That list is short, a human can verify it in an afternoon, and it is enough to stop the wrong booking before the chase starts.
So the sequence flips. Eligibility gets checked and the not-taken list gets applied at intake, before anyone spends two weeks assembling a packet. Anything that looks like a real credentialing exception goes to the person who owns the matrix, because that is a human decision with contract consequences and it should never be inferred.
Therapy that runs across sites runs on paperwork
Outpatient parenteral therapy pulls an infectious disease practice into coordination it does not control. Infusions happen at one location, follow-up visits at another, and a home health agency is often holding part of the record. Every one of those handoffs generates a document that has to reach a specific work queue at a specific practice.
The visible failure is a patient who arrives for a follow-up where the paperwork from the infusion site never came across. The less visible one is a document that arrived and got filed to the wrong class, which is the same outcome with a longer search attached.
What helps is boring and mechanical. Documents get routed by class to the department bucket that owns them. Outbound requests to the other sites are generated and faxed on a schedule instead of when someone remembers. Status is written back to the chart so the front desk can answer “did it come in yet” without walking to the fax machine.
The judgment stays where it belongs. The practice defines what a complete packet looks like for each referral reason, and the clinician decides what in it actually matters. The automation reports completeness against that checklist and chases what is missing.
What a human still owns
The boundary deserves to be stated plainly, because records work sits closer to the chart than most front office automation does.
The automation moves paper. It requests records, tracks them, files them under the right document class, routes them to the right queue, and tells the scheduler whether the packet the practice defined is complete. It does not read the contents and decide what is relevant, and it does not summarize what a chart says to anyone.
That line is not a hedge. A completeness check against a named checklist is a fact anyone can audit. A judgment about which culture report matters for this patient is clinical, it belongs to the physician, and a tool that guesses at it creates risk the practice cannot see until it matters.
Drawn that way, the split is comfortable. Your staff stops spending mornings on hold with a hospital release of information line, and the consult starts with a chart that is actually ready.
Key Takeaways
- Treat fax intake as the gating step, not the mailroom. A referral that has not been matched to a chart is invisible to scheduling, and the appointment usually gets booked before anyone opens it.
- Put the records request on a follow-up cadence. The holder of the record has up to 30 days under HIPAA, so the first call is not the work, the third one is.
- Apply the plans-we-do-not-take list at intake. It is the enrollment grid your practice can actually produce, and it stops a two week records chase that ends in a dead claim.
- Route documents by class to a bucket someone watches. A record that arrived and got filed wrong costs the same as one that never came.
- Define what a complete packet looks like per referral reason. Completeness against a written checklist is auditable; deciding what is clinically relevant is not the automation’s job.
- Write request status back to the chart. Most of the phone calls your front desk fields about records are people asking a question the chart could have answered.
The consult is the scarce resource in an infectious disease practice, and right now it is being spent on charts that were not ready. The chase in front of it is repetitive administrative work, which makes it the easiest thing in the building to hand off.
Related reading
Sources
- https://www.mgma.com/mgma-stat/phones-are-still-a-backlog-costing-medical-practices-time
- https://www.mgma.com/mgma-stats/practices-split-regarding-patient-requests-for-electronic-access-to-their-medical-record
- https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-E/section-164.524
Ready to See It in Action?
See how PGA chases outside records before the consult, not after it
Schedule a Demo →Written by Kevin Henrikson