Patients
Demographics, documents and a ledger that is always calculated, never stored.
- Primary, secondary and tertiary coverage
- Eligibility results recorded per coverage
- Patient documents and notes
Product
Twelve modules share one patient record, one ledger and one audit trail. Below is what each one does today, in the order a claim travels.
Front office
Patients, coverage, scheduling and charge entry are the start of every claim. UniPractice keeps them tidy so the claim is right the first time.
Demographics, documents and a ledger that is always calculated, never stored.
Appointments by provider and location, with status changes and one click to the encounter.
Service lines priced from the fee schedule, with diagnosis pointers and modifiers.
Providers, referring providers, payers, enrollments, fee schedules and code sets.
Claims & EDI
A rule engine checks every claim before it leaves. Submissions, acknowledgements and rejections are tracked claim by claim, with an audit trail of every change.
A rule engine that catches NPI, date, pointer and payer problems before submission.
Generate 837P batches for the clearinghouse, or produce a CMS-1500 PDF for paper claims.
Draft to closed, with corrected claims (frequency 7) and voids (frequency 8) built in.
Rejected claims open a work item with the reason, the fix and an appeal letter when needed.
Rule engine found errors. Fix in place, rescrub.
back to Draft
999 or 277CA rejected. Work item opened with the reason.
back to Draft (corrected)
835 paid $0. Denial queue, appeal letter, corrected claim (frequency 7).
back to Draft or Closed
Secondary claim created automatically, patient balance to statement.
back to Closed
Frequency code 8 sent to the payer. Nothing is deleted.
back to End
Remits, payments & A/R
Electronic remits post themselves. Denials become work items. Aging and collections are always current, so follow-up starts from facts.
Parse 835 files, post payments and adjustments automatically, and hand off to the secondary payer.
Patient payments applied oldest-first or by hand, refunds, and a ledger per patient.
Aging buckets, a denial queue, follow-up notes and a timely-filing check that flags claims at risk.
Statement runs with dunning levels, plus the reports a billing company reports on.
Under the hood
The parts that must be exactly right are built as separate, tested packages. Nothing in the user interface touches raw X12.
837P generator plus 999, 277CA and 835 parsers, written from publicly available payer and clearinghouse companion guides. Raw files are stored and indexed.
Built-in checks for NPIs, dates, pointers and modifiers. Add your own rules per payer, with plain-language messages.
The 02/12 form as a PDF, box by box, for payers that still want paper.
Balances are always calculated from the ledger, never stored. Amounts are integer cents, so totals reconcile to the penny.
Submission, acknowledgement polling, remit download and timely-filing checks run as background jobs with retries and a health page.
A built-in test clearinghouse for demos, and a Claim.MD connection being tested for production. New connections plug into the same adapter.
Platform console for the SaaS owner: tenants, plans, trials, usage metering and invoices are built in.
See pricingA 30-minute walkthrough on demo data: charge entry to claim, submission to remit, denial to appeal. Bring your questions about your hardest payer.