Where should your GFE records live?

Picture the moment every operator hopes never comes. A state board investigator — or a plaintiff's attorney, or your own medical director doing an annual review — asks a simple question: "Show me the good faith exam for this patient's visit on March 14th."

You know the exam happened. Your GFE service confirmed it, or your NP remembers the call. But the exam record is in the vendor's portal under a login one of your admins set up two years ago. The chart from the visit is in your EMR. The booking that ties them together is in your dispatch spreadsheet. Three systems, three logins, and the one document that proves your team did things right is the one that takes a week of emails to retrieve.

Nothing about that operation was non-compliant. The exam was real, the documentation existed. But records you can't produce might as well not exist — and fragmentation, not negligence, is how good operators end up looking bad on paper.

Three ways operators run GFEs — all of them valid

Set aside the record question for a moment and look at how the industry actually staffs good faith exams. Three models dominate, and each one is a reasonable answer to a real constraint:

Here's the part that matters: state boards generally don't grade you on which model you picked. They grade you on whether a qualified practitioner examined the patient before treatment, whether the treatment matched what was authorized, and whether you can prove both. The model is an operations decision. The proof is a records decision — and that's where operations quietly diverge.

The fragmentation problem

Each staffing model produces records somewhere. The outside service keeps exams in its portal. Your practitioner documents in whatever system they use — sometimes your EMR, sometimes their own notes, sometimes a telehealth platform's storage. And the visit itself gets charted wherever your operation charts.

Fragmentation is what happens when those places never connect. The symptoms are recognizable:

The tech at the door can't see the clearance. The exam approved specific services, maybe with restrictions — but that lives in a portal your field team has never logged into. So the tech treats based on the booking notes, and the one document that defines what's clinically authorized plays no role at the point of care.

Nobody can produce the whole story in one place. Exam in system A, chart in system B, the connection between them in somebody's memory. Every audit, board inquiry, or records request becomes an assembly project.

Vendor turnover takes your records with it. Switch GFE services — or lose access when a subscription lapses — and two years of exam records now live behind a login you no longer have. The exams were real; your access to the proof wasn't durable.

Expiration is invisible. GFE clearances have validity windows. When the record lives outside your operational system, nothing warns you that a returning patient's exam lapsed three weeks ago — you find out when someone checks manually, or when someone doesn't.

None of these are indictments of any vendor or any model. Outside services document their exams properly — that's their job, and the good ones do it well. The gap is structural: their records system and your operation are two different places, and the connection between them is the operator's responsibility. It's the same lesson that applies to charting generally: documentation that exists somewhere is not the same as documentation that works for you.

What "the record in the right place" looks like

Whatever systems you use, the target state is the same four properties:

In the chart. The exam record — or at minimum, its essentials plus the actual document — attached to the patient, in the same system as their visits. One patient, one place, whole story.

Visible at the point of care. The person about to start an IV can see that a valid exam exists, what it authorized, and any restrictions — before treating, not after. This is the difference between the GFE as a compliance checkbox and the GFE as a working clinical control.

Tracking its own clock. The validity window lives with the record, and the system — not someone's memory — flags when a returning patient needs a fresh exam.

Durable beyond any vendor relationship. If you switch GFE services tomorrow, every exam they ever performed for you stays in your charts. The vendor relationship ends; your records don't.

An operation with those four properties can answer the investigator's question in thirty seconds, from the same screen their team uses every day. That's the whole game.

How this works in practice

If you're running an outside GFE service today, the fix isn't switching models — it's closing the loop. When the service clears a patient, that clearance gets recorded in the patient's chart: who performed it, when, what's authorized, the validity window, and the exam document itself. Keep the vendor; capture the record.

This is exactly how we built external GFE support in Infuse Pro: the exam happens wherever it happens — your GFE service, an independent telehealth practitioner, anyone — and your team records it against the patient with the provider's name, exam date, validity window, and the uploaded document. From that point it behaves like any GFE in the system: the tech sees the clearance at the door, the validity clock runs automatically, and the record stays in your charts no matter what happens to the vendor relationship. Operators with in-house practitioners get the same properties natively — the exam is performed and documented inside the chart from the start — and hybrids get both paths with one queue.

The point isn't the feature; it's the principle. However the exam gets done, somebody in your operation should be able to open a patient and see their GFE story complete — and if your current setup can't do that, that's the gap worth closing before it matters.