Why review before submission
Medical coding review support is a checkpoint between charge entry and submission. Once a claim is sent, a coding problem becomes a denial to work, a corrected claim to file or a payment to return later. Each of those costs more staff time than catching the issue while the claim is still in the office.
Gateway runs the checks and presents what they find. Your coder, biller or clinician decides what to do about it.
What the review looks at
The checks are agreed with the practice in advance and applied the same way to every claim in scope.
- Codes against the note. Does the documentation describe each service on the superbill, and does each service have a diagnosis that relates to it?
- Code pairs. Proposed combinations are compared with the applicable National Correct Coding Initiative procedure-to-procedure edits.
- Units. Quantities are compared with published unit limits and with what the note records.
- Modifiers. Claims with an evaluation and management service and a procedure on the same date are flagged for a person to look at.
- Supporting details. Place of service, rendering clinician, referring provider and authorization number are present where the payer requires them.
- Payer rules. Requirements the practice has confirmed for a given payer are checked for the date of service.
How a flagged claim is handled
A flag is a question, and it arrives with enough context to answer. The reviewer sees the claim, the item in question, the rule or source behind the flag and the relevant part of the note.
The reviewer then has three choices: release the claim as it stands, change it, or return it to the clinician with a documentation question. We record the decision and who made it.
We keep a tally of flags by type. If one clinician’s procedure notes regularly lack an element, or one payer rule keeps catching the same service, the practice hears about the pattern and can fix it at the source through its documentation workflows.
Modifier questions get a person
Modifiers are where shortcuts cause trouble. Modifier 25 requires a significant, separately identifiable evaluation and management service, and the note has to show it. An edit appearing on a claim does not by itself justify adding a modifier.
Some code pair edits cannot be bypassed with any modifier. The review shows which kind of edit applies, so the reviewer is not left guessing. Whether a modifier is appropriate for a particular visit is a judgment for your clinician and coder, based on what was done and documented.
Final decisions stay with the practice
Gateway does not assign final codes, change codes on a claim or decide that a service was medically necessary. Those decisions, and responsibility for the claim that results, stay with the practice.
This is also not a compliance audit or a legal opinion. It is a routine operational check on claims before they go out. A practice that wants a formal retrospective audit should engage a qualified auditor or its own counsel for that purpose.
People first, software where it helps
A review workflow can start with a checklist and a person. For practices with more volume, Gateway helps configure AI-assisted billing and coding review that suggests candidate codes from documented services and checks them against edits. Every suggestion shows its source and reason, and staff review it before anything reaches a payer.
Edits are updated on a published schedule and payer policies change, so part of the work is keeping the checks aligned with the rules in effect on the date of service.
Procedure-heavy and wound care visits
Review earns its place on visits that combine an evaluation with a procedure, involve several procedures on one date or bill products by unit. Wound care has all three.
For wound care practices, a review scope can begin with debridement and product application claims, where the note must support the specific service and quantity billed. Reviewed claims then continue through medical billing support, and anything that still denies is picked up in claims follow-up.
How an engagement starts
Use the practice support inquiry form or call 314-325-0126. No patient information belongs in the form.
We ask which claims cause the most rework and who at the practice will act as reviewer. A sensible first scope is one category of claim. After a few weeks, we look at the flags together: which were useful, which were noise and which checks to add or drop.
Common questions
Does Gateway assign the codes on our claims?
No. Your clinician and coding staff select the codes. The review compares those selections with the documentation and the applicable edits, and raises questions. If the reviewer agrees a change is needed, the reviewer makes it. Our role is to run the process and keep a record of each decision.
Will a review step slow down our claims?
It adds a step, so scope matters. Claims that raise no flags pass straight through. Flagged claims wait for your reviewer, which is why we agree at the start on who that is and how often the queue is cleared. It makes sense to begin with the claim types where a second look is most valuable.
Which rules are the checks based on?
The National Correct Coding Initiative edits and unit limits published by the Centers for Medicare and Medicaid Services, plus payer-specific requirements your practice has confirmed. Each flag names its source. Where a payer’s rule is unclear, we say so and the practice decides how to handle it or asks the payer.
What happens when the reviewer and the clinician disagree?
That is settled inside the practice, under whatever policy it has for coding questions. We do not take a side. The claim is held until the practice reaches a decision, and the outcome is recorded so the same question is easier to answer next time.