Billing
Connect the note, the claim, and the follow-up
A claim comes back with a question. The biller needs the note, the provider needs to know what is missing, and somebody has to contact the payer. Start by making those handoffs easier to follow.
Keep coding review tied to the clinical record, and give every AR call a clear purpose. Measure claim outcomes using one agreed definition so your team can tell whether the work is improving.
Start with the note behind the code.
A coding suggestion needs supporting documentation. During a demo, ask to see the suggested code alongside the relevant part of a fictional clinical note. Have a provider and someone from billing review the example together.
You do not need to change how your notes are written to use ScribeSync for coding. Medical coding is available independently of the clinical scribe, so your team can work from existing documentation. You can also use the two together.
Look at how a question gets resolved before submission. Who checks the suggestion? Who clarifies the documentation? Who makes the final decision? ScribeSync provides medical coding support for review; your providers and billing team remain responsible for the final record and codes.
Define “first pass” before comparing results.
Ask what the number actually counts. Is it claims accepted by a clearinghouse, claims accepted by a payer, or claims paid without rework? Pick a definition and use it consistently. Otherwise, two reports can look different without describing a real change.
Track comparable periods and break out the reasons work comes back. Documentation, coding, coverage, and other issues may need different fixes. The aim of ScribeSync’s coding support is to help catch avoidable gaps before submission; a specific first-pass rate or denial reduction is not guaranteed.
Give the follow-up call a job.
A claim-status call, a denial follow-up, and a patient-balance call are different conversations. Decide what you want to learn and what information is needed before placing the call. Don’t make the person reviewing it guess why it happened.
ScribeSync supports AR follow-up calls for these tasks. Your team reviews the outcome and decides whether to correct information, gather documentation, follow up again, or take another step. A completed call is not the same as a resolved balance.
- Which account or claim is this about?
- What question should the call answer?
- What did the payer or patient say?
- Who owns the next action and its due date?
Try a small group of accounts first.
Choose an approved trial with a clear purpose, such as a group of status inquiries. Review the call outcomes with your billing lead. Track unresolved questions, repeat work, and how much staff time is still needed—not only the number of calls completed.
Bring your verification process into the discussion too. ScribeSync supports real-time insurance checks and verification calls earlier in the visit workflow. We can walk through the relevant parts together without assuming you need to change everything at once.