Product tour
Scheduling, coverage and billing
From booking an appointment to a claim and a remittance. The payer side is simulated.
Diagram: the revenue path. The clearinghouse and the payer are simulators inside the hub; the fee schedule and code sets are synthetic.
What exists Pilot
- Scheduling: resources, weekly templates, appointment types, booking with conflict checks, reschedule, cancel, no-show, waitlist, check-in, rooming and a waiting room.
- Coverage: primary, secondary and tertiary coverage with subscriber details, stored eligibility results, expiry and re-verification.
- Billing: charge capture, claim build and scrub, remittance and denial handling, payment posting, patient statements and A/R aging.
- Separation of duties: capturing a charge, managing a claim, submitting it and posting a payment are four different permissions.
- Printing: Code 128 wristbands, labels and chart prints go to a logged, rate-limited, simulated printer queue; protected compartments need a stated purpose and a step-up.
Simulated, and limits Simulated
- Eligibility and claims go to a simulated clearinghouse, not to a payer.
- The fee schedule and code sets are synthetic: no licensed CPT, and no real payer rates.
- There is no attached printer driver: print jobs go to a simulated printer queue.
- No patient payments or online payment.
- No prices are shown on this site.
Common questions
Does AuroraMed submit real claims?
No. Claims go to a simulated clearinghouse inside the hub. The claim build, scrub and remittance handling are real code run on synthetic data. Connecting to a real clearinghouse and licensing real code sets are future work.
Why separate the billing permissions?
So one person cannot capture a charge, submit the claim and post the payment alone. The four steps are separate actions in the permission matrix.
See scheduling, coverage and billing on synthetic data
A short walkthrough. No patient information needed.