What QA Review Actually Does and Why It Drives Everything That Comes After

When the crew clears the scene and the patient is at the hospital, most people assume the job is done. From the outside, this would make sense. The emergency has been handled, the transport is complete, and the unit is back in service. But for the agency, a completely new process is just beginning.

What happens between the run report and the insurance claim is where agencies quietly lose revenue, expose themselves to compliance risk, and sometimes don’t discover either problem until long after the call itself has been forgotten. That process is QA review, and it carries far more weight than it is often given credit for.

More Than a Proofreading Exercise

QA is often misunderstood as a documentation cleanup step, something closer to proofreading than decision-making. In reality, the reviewer is making binding clinical and legal determinations about what occurred on a call, whether the documentation supports those events, and what level of service can actually be defended if the claim is ever questioned.

Once that determination is made, it becomes the foundation for everything that follows. Billing relies on it. Coding relies on it. The claim submission reflects it. While there may be limited flexibility during the coding process, the practical reality is that the service level established during QA tends to follow the call all the way through reimbursement.

That is a significant amount of responsibility placed on a single review step. It is worth making sure your agency fully understands the downstream consequences of what happens here, because they extend much further than the review itself.

The Determination That Drives Everything

At the center of every QA review is a single question: what level of service was actually provided?

Not what dispatch assigned, not what the sending facility requested, and not what level the crew expected when they began the call. The determination is based on what was documented, what can be supported, and what was actually delivered during patient care.

An ALS unit can respond to a call and ultimately provide only BLS-level care. If the documentation does not clearly demonstrate qualifying ALS interventions, the call is BLS. The credential level of the crew does not change that determination. The service level follows the care that can be substantiated in the patient care report, and the QA reviewer is the one who makes that determination official.

That decision does not exist in isolation. It flows downstream into billing accuracy, reimbursement outcomes, and compliance exposure. An incorrect determination at QA does not simply affect a single claim. Over time, repeated inaccuracies create measurable financial impact or increase the likelihood of regulatory scrutiny.

Three Designations, Rarely Discussed Together

On any single call, there are actually three distinct service level designations in play, and they do not always align.
There is the level that was dispatched, the level that was actually provided on scene, and the level that is ultimately billed to the payer. While these categories are related, they are not interchangeable.

A call dispatched as ALS in which only BLS interventions are performed will ultimately be billed as BLS. The reverse situation is more operationally complex: if a BLS crew arrives on scene and the patient’s condition requires ALS-level intervention, the BLS crew cannot administer that care themselves. They must call in an ALS unit. If ALS responds and provides qualifying interventions, the call is billed accordingly. Dispatch information establishes context, but it does not determine reimbursement, and the crew’s certification level does not expand what care they are authorized to deliver.

Understanding how frequently these three designations diverge is important visibility for any agency that takes revenue integrity and compliance seriously. Without it, small inconsistencies can accumulate into larger operational problems that may not become apparent until much later.

What Bad Documentation Actually Costs

Consider a scenario in which a crew provides ALS-level care but documents the encounter in a way that does not clearly describe the qualifying interventions. The narrative may be vague, key treatments may not be explicitly stated, or required elements may be incomplete. When the QA reviewer cannot confidently identify documentation supporting ALS criteria, the call must be categorized as BLS.

At that point, the claim is submitted at the BLS level, and the revenue associated with the higher level of care is not captured. When this occurs occasionally, it may not attract attention. When it occurs consistently, it becomes a measurable revenue issue tied directly to documentation clarity.

The opposite situation carries even greater consequences. A report may pass through QA with an ALS determination that is not clearly supported by the written documentation. The claim is coded and billed accordingly. If that claim is later reviewed or audited, the agency may be required to defend a service level that cannot be substantiated within the patient care report. At that stage, the concern extends beyond documentation quality and becomes a matter of compliance exposure.

What Good QA Looks Like

Effective QA review involves evaluating the patient care report from the perspective of someone who may later be asked to justify the claim. The reviewer considers whether the documented interventions support the service level billed, whether the timeline is logical, whether mileage is consistent with the narrative, whether required signatures are present, and whether any gaps in documentation have reasonable explanations.

Incomplete fields are not automatically indicators of poor performance. Unresponsive patients, chaotic scenes, and extremely short transport times can all legitimately affect what information crews are able to document during the call. The presence of blank fields is less important than whether the overall report provides a clear and defensible account of the care that was delivered.

When documentation clearly reflects the care provided, the service level determination becomes easier to support, reimbursement becomes more consistent, and compliance risk is reduced. The patient care report tells the story of the call. QA ensures that the story is accurate, complete, and defensible when it matters most. Those consequences are worth keeping in the front of mind at every step of the process.