Practice Operations
How Plastic Surgery Medical Records Get Ahead of Authorization
Reconstructive cases stall on a records packet assembled from other offices. Here is how AI runs the chase, the forms, and the intake fork in athenaOne.
A plastic surgery practice runs two businesses through one phone number, and plastic surgery medical records are where they stop looking alike. The cosmetic caller needs a price and a date. The reconstructive caller needs a packet built out of three other offices before anything can be scheduled at all. Sorting which one you are talking to, on the call, is the whole job.
Cosmetic and reconstructive work share a building, a surgeon, and a schedule, and almost nothing else. The intake questions are different, the payment path is different, and the paperwork requirement is the difference between a same week consult and a case that sits for a month.
On the reconstructive side the bottleneck is documentation the practice does not hold. Prior records from a referring office, operative history, the notes supporting medical necessity, and the authorization forms that let you request any of it. Every one of those has to be requested, chased, received, and filed before the case can be submitted.
On the cosmetic side the bottleneck is speed. A self-pay inquiry that waits four hours for a callback has usually booked a consult somewhere else. Both problems arrive on the same line, and a front desk trying to serve both ends up serving neither well.
Two lines of business, two document paths, one intake
The first decision on a plastic surgery call is which path the caller is on, and it determines everything downstream. Cosmetic means no records request, a quote, and a deposit conversation. Reconstructive means a packet, an insurance verification, and an appointment that should not be offered until the packet is moving.
Getting that fork wrong is expensive in both directions. Put a cosmetic inquiry through the records path and you have inserted a week of friction into a self-pay sale. Put a reconstructive case on the cosmetic path and the consult happens with nothing to submit afterward.
The athenaOne side of this is appointment types, and they are less stable than most practices assume. A practice can retire its entire cosmetic and procedure type catalog overnight and fold it into a single 15 minute follow-up type, which cannot hold a 45 minute service. Any automation reading the schedule has to work from the catalog as it is configured today, not the one it learned last quarter.
What the automation contributes is consistency on the fork. It asks the questions that separate the two paths, creates the chart, opens the records request when the path calls for one, and books into the appointment type that can actually hold the visit. Anything ambiguous goes to a person rather than being guessed.
The reconstructive packet is assembled from other people’s offices
The packet is rarely one request. A reconstructive case typically needs records from the referring physician, operative or pathology paperwork from wherever the prior procedure happened, and photographs or documentation of prior conservative care, each held by a different organization with a different fax number and a different release form.
The holder of those records is not in a hurry. HIPAA gives a covered entity 30 days to act on a request for access, with one 30 day extension available. Nothing about that timeline is aligned with a surgical schedule, so the only thing that moves it is follow-up.
Follow-up is also the first casualty of a busy week. The request goes out, the coordinator means to call on Thursday, and three weeks later somebody notices the case never got submitted. An automated caller runs that cadence without needing to be reminded, records what each office said, and writes the status back to the chart so the coordinator can see where every open request stands in one place.
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.
The authorization clock is shorter than it used to be
Federal rules have started to compress the back half of this workflow. Under the CMS Interoperability and Prior Authorization Final Rule, impacted payers must send prior authorization decisions within 72 hours for expedited requests and seven calendar days for standard ones, with operational provisions generally beginning January 1, 2026.
That is good news for a reconstructive practice and it moves the pressure forward. If the payer now answers in a week, the four weeks your packet spent in assembly is the remaining delay, and it is entirely yours to fix.
It also raises the cost of an incomplete submission. A packet submitted without the supporting documentation comes back needing more, and the clock restarts on a case that has already burned a month. Completeness before submission is worth more than speed of submission.
So the useful automation target is not the payer conversation. It is the queue in front of it: which requests are open, which came back, which office has gone silent, and which cases are one document away from being submittable today.
The self-pay call is a records problem in disguise
Cosmetic inquiries convert on response time, and most practices lose them to a full voicemail box rather than to a competitor’s pricing. That looks like a marketing problem and it is really an intake capacity problem.
The fix is unglamorous. Answer, capture the inquiry, create or match the chart, and get the consult booked into a type that fits the service. When the caller turns out to be reconstructive after all, the same conversation opens the records request instead of ending in a callback promise.
Coverage on that line is the whole point. Consult inquiries do not arrive during business hours and a call that reaches an after hours message is a call that reaches somebody else next. Answering all of them consistently is the kind of work that scales with volume instead of with payroll.
What comes back to a human is the part worth a human. Pricing conversations, surgical scheduling judgment, and anything where the caller’s situation does not fit the script. The automation handles the traffic and hands over the exceptions with the chart already built.
Where the automation stops
Records work sits close enough to the chart that the boundary should be explicit. The automation requests documents, tracks them, chases them, files them to the right document class, and reports whether the packet the practice defined is complete.
It does not read what those documents say and decide what matters. Medical necessity is argued by the surgeon, in the surgeon’s words, and no part of that belongs to a front office tool. The checklist is administrative; the content is not.
That split is also what makes the automation auditable. “Four of five items received, the operative report is outstanding, the office was called twice” is a fact your coordinator can verify in ten seconds. Anything softer than that would be a tool making a call it has no business making.
Run that way, the practice gets its coordinator back. Instead of spending mornings on hold with release of information lines, they spend them on the cases that actually need a person.
Key Takeaways
- Sort the cosmetic and reconstructive fork on the call, not after it. The two paths need different intake questions, different appointment types, and only one of them needs a records packet.
- Re-read the appointment type catalog rather than trusting last quarter’s map. Practices collapse and rebuild these types without notice, and a 15 minute follow-up type cannot hold a 45 minute service.
- Put every outbound records request on a follow-up cadence. The other office has up to 30 days under HIPAA, so the calendar reminder is the workflow.
- Optimize for a complete submission, not a fast one. With payer decisions now due in 72 hours or seven calendar days, the assembly time in front of the submission is where your delay lives.
- Answer the self-pay inquiry when it arrives. Consult conversion tracks response time, and a voicemail box loses more cosmetic cases than pricing does.
- Keep the automation on completeness, not content. Reporting which packet items are missing is auditable; deciding what the records mean is the surgeon’s work.
Reconstructive cases do not stall because the payer is slow. They stall in the weeks before submission, in a queue of open requests nobody has time to call on, and that queue is administrative work you can hand off today.
Related reading
Sources
- https://www.mgma.com/mgma-stats/practices-split-regarding-patient-requests-for-electronic-access-to-their-medical-record
- https://www.cms.gov/newsroom/fact-sheets/cms-interoperability-and-prior-authorization-final-rule-cms-0057-f
- 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 sorts the intake fork and chases the packet before the case stalls
Schedule a Demo →Written by Kevin Henrikson