Authorization Tracking That Connects Dates, Units, and Actual Services

Track the decision, not just the request

AHCA states that Florida Medicaid BA services require prior authorization for reimbursement. Its BA information page directs requests to the recipient’s SMMC plan or, for recipients outside SMMC, to Acentra. Confirm the correct route before treating a submission acknowledgment as progress toward an approval.

Use distinct statuses such as preparing, submitted, information requested, approved, partially approved, denied, and superseded. An acknowledgment proves receipt only to the extent stated by the receiving system. It should not become an “approved” status because someone entered a number into a required field.

Attach the actual decision notice or a controlled link to it. Record who reviewed the notice and when. If the notice is ambiguous, preserve that ambiguity as an open question rather than filling the gap from a previous authorization.

Build a register that can answer practical questions

For each authorization, record the payer and program, patient identifier, authorization identifier, effective period, authorized service categories or codes, approved quantities, and any stated conditions relevant to operations. Preserve the units exactly as the notice expresses them. If staff also need an hours view, label it as a conversion and document the method.

Do not collapse separate services into one balance merely because they share an approval letter. A combined total can hide exhaustion of one category while another remains available. Keep the original decision distinct from later amendments so staff can see which version governed a particular encounter.

• What does the current decision actually approve?
• Which service dates fall within its stated period?
• Which quantities are used, pending reconciliation, or reserved for future planning?
• Who owns renewal preparation and unresolved payer questions?

Separate planned use from delivered use

Maintain different totals for scheduled, delivered, claim-ready, submitted, and paid activity. These are operational categories, not interchangeable definitions of consumption. Decide how your organization will track each category against the payer’s rules, and document which record supplies each number.

For a fictional example, a cancellation should remove an appointment from the planning forecast without creating a delivered service. A completed encounter awaiting documentation review belongs in a pending category; excluding it entirely could make the remaining balance look larger than it is. A rejected claim also should not automatically erase evidence that the service occurred.

Reconcile balances at a frequency suited to service volume. Investigate differences between your register and a payer portal before making scheduling promises. A portal may update on a different cycle, and neither screen should be treated as self-explanatory.

Set renewal milestones backward from the actual deadline

Section 7 of the Florida Medicaid BA coverage policy expressly addresses fee-for-service and includes authorization before initiation and at least every 180 days thereafter. Do not copy that interval into every managed-care workflow without checking the applicable plan and decision.

Choose internal preparation milestones based on the actual expiration date, required materials, staff availability, and payer submission instructions. Internal reminders are planning choices, not payer rules. Label them accordingly. Give the team enough visibility to identify missing materials before a renewal becomes urgent.

Keep clinical decisions with qualified clinicians. Administrative forecasting can show an approaching expiration or a potential balance problem, but it should not determine treatment intensity or encourage unnecessary visits merely to use remaining units.

Handle transitions and close each authorization cleanly

When a recipient changes plans or a new approval arrives, create a transition task. Verify the effective dates, determine which decision applies to each upcoming encounter, and review any unresolved services from the prior period. Do not assume an old authorization transfers automatically or that a new one retroactively covers a gap.

At closure, reconcile outstanding encounters and claims, preserve the decision history, and identify any unresolved follow-up. An authorization is one part of a supportable billing record, alongside eligibility, service delivery, documentation, and other applicable requirements. Treating it as a payment guarantee invites avoidable surprises.

A useful register makes uncertainty visible early. The best operational outcome is that the next person can explain the status, the evidence, and the next action without reconstructing the case from scattered emails.