Skip to content
MegAligna

Specialties

Early intervention billing across Part C, Medicaid and plans

Early intervention billing turns a home or childcare visit into a charge for whichever payer your state bills first: Medicaid, a family's plan, or Part C as payor of last resort. MegAligna builds the charge from the visit's delivered minutes and place of service under that payer's settings, and exports it for your biller; it does not transmit claims.

Part C pays last, so the first payer is usually someone else

Federal regulation makes Part C funds the payor of last resort: they may not pay for a service another source (Medicaid, a private plan, another programme) would otherwise cover. In practice that means one toddler’s weekly session can belong to three different payers over a year as coverage starts, lapses and changes, and the same caseload carries all three at once.

How your state sequences them, and whether a family’s plan has to be billed and denied before the programme pays, is set by your state’s Part C system. Nothing here presets it. What the software does is let each payer carry its own rules, so a Medicaid visit and a programme-funded visit on the same afternoon are each charged the way that payer expects.

Minutes and setting, recorded where the session happened

The billable record is the visit itself, captured in the family’s kitchen or the childcare room rather than reconstructed at a desk on Thursday. It carries the delivered minutes, the service code booked for the visit, the provider who delivered it, and the place of service for where it actually took place.

Units are the delivered minutes divided by that payer’s unit length, 15 minutes unless you set otherwise, rounded the way you configure for that payer: down to whole units (the default), to the nearest unit, or left exact. Each visit carries one service code. Medicare’s aggregate 8-minute calculation across several timed codes is not modelled, so a programme that bills that way needs its biller to check the units; the 8-minute rule explains the arithmetic.

Place of service is the field that quietly costs money: a home session billed under an office code is denied weeks later, in bulk. Recording it per visit, with a default per location, is how it survives a caseload.

Electronic visit verification: what is captured, what is not sent

The federal EVV mandate covers Medicaid personal care and home health services; whether your state applies it to early intervention visits is a state decision.

Where you need it, a clinician can verify arrival and departure on the visit: a location fix from the device, or a manual entry that has to carry a reason. Those times are kept apart from the billed session clock, so correcting a mis-tapped start time never rewrites the verification. Visits that raised an exception (a manual entry, a missing location, a departure never recorded) appear on a reconciliation list on the billing screen, and clearing one requires a written explanation. Verification needs a connection at the moment of the tap.

Nothing is sent to your state’s EVV aggregator. There is no aggregator submission, no aggregator file download, and no state has certified this product. If your state requires verification to reach its own system, that step stays with your current process.

Authorized frequency burns down as visits close

An IFSP authorizes a frequency, and the authorization behind it runs out the way ABA authorizations do: silently, mid-period, with visits already delivered against a pool that emptied two weeks ago. Delivered sessions draw the balance down as they are documented, alerts fire at 80 and 90 percent used, and booking checks the remaining balance before the visit is committed.

The hand-off to whoever submits

Finished charges leave as a CSV your biller loads into their own system, with the code, units, place of service, diagnosis pointers, authorization number and rendering provider on each line. The CMS-1500 field guide covers where those land: Box 23 for the authorization, Box 24B for the setting, Box 32 when the service happened somewhere other than your billing address, which in home-based work it always does. A printable CMS-1500 waits on the AMA CPT licence.

MegAligna does not transmit claims to Medicaid, to plans or to the programme. Agencies that submit electronically today should treat that as the limitation it is.

Common questions

Can a Medicaid visit and a programme-funded visit sit on one caseload?
Yes. Each payer record carries its own unit length, rounding, modifiers and rendering-provider rule, and the coverage on file for the service date decides which one a visit is charged under. Which payer your state requires you to bill first is a Part C system question to confirm against your own state's current documentation.
Is visit verification sent to our state?
No. Arrival and departure can be verified and reconciled inside the product, but nothing is submitted to a state EVV aggregator and no state has certified it. If your state requires verification in its own system, that submission stays where it is today.
What happens to a session recorded with no signal in a family home?
Session data is held on the device and synced when the connection returns, so a dead zone does not lose the visit. Two things do need a connection: loading the day's roster beforehand, and the EVV arrival and departure taps themselves.
Are travel and documentation time billed?
Neither is delivered service time, so neither belongs in the unit count. Whether your state programme reimburses travel separately is a programme question, and it varies enough to confirm rather than assume.

Charge a made-up home visit to a test payer

Set up a test payer with your unit length, book a home visit for a made-up child, close it, and read the export line. Real family records wait until a business associate agreement is in place.

Sources

  1. 34 CFR 303.510, Part C funds are the payor of last resort (checked October 14, 2026)
  2. Medicaid.gov, the Cures Act EVV requirement covers personal care and home health services (checked October 14, 2026)