Questions we hear most — answered directly.

Medical coding, claims, denial management, payments and AR follow-up, reporting and executive analytics, a client-facing portal, and role-based administration — all on one data model. See Platform for the full architecture.

One platform. Coding jobs, claims, denials, and payments share a single schema and a single audit trail — there's no export/import step between modules.

Yes. A pilot uses the same product every customer runs — there is no separate, limited trial mode. Request a demo to discuss scope and timeline.

It's built on a pluggable provider architecture. You can run it against a local, deterministic model with zero external calls, or connect Anthropic, OpenAI, or Azure OpenAI — the choice is yours, made per deployment.

No. It surfaces suggestions inside the coding workstation. The coder and QA reviewer remain the decision-makers, consistent with the platform's separation-of-duties design.

A scoring engine, not a workflow. It runs DRG grouping, Clinical Rules, and Clinical Decision Support once per encounter and derives coding-completeness, documentation-quality, compliance, and denial-risk scores from that single analysis.

There is no third-party certification today. The platform implements technical controls consistent with HIPAA's Security Rule expectations — access control, audit logging, encryption in transit. A signed BAA, encryption-at-rest configuration, and compliance sign-off are deployment-specific and depend on your infrastructure and hosting choices. See Security and Compliance for the full, honest breakdown.

Every query is scoped to your organization at the application layer, with an optional database-level Row-Level Security backstop for defense in depth.

Yes. Six default roles cover most teams out of the box, and administrators can build fully custom roles from a 27-resource permission catalog.

The audit log is hash-chained — each entry cryptographically links to the one before it — and a dedicated action lets an Owner verify the full chain hasn't been altered.

Not as a live, real-time integration today. ERA/835 remittance data is imported via file upload or paste. We won't claim an integration partnership that doesn't exist — if this is a requirement, tell us during your demo and we'll be direct about fit.

There's no built-in bulk data-migration tool. Migration is scoped per customer, typically as part of implementation — see our implementation process for how this is planned.

Pricing is customized to your organization's size, modules, and license type (Trial, Standard, or Enterprise). Contact sales for a quote — see Pricing.

Support is a direct-contact model today — email or, for client-portal users, in-app messaging to your account team. We're direct about this rather than implying a live chat or ticketing system that doesn't exist yet.