RCMbox Platform
Clearinghouse-ready billing infrastructure
Ship and evolve custom billing logic with programmable workflows and end-to-end traceability — in development and production.
Built for teams building billing products
Software vendors, RCM teams, and providers building custom billing workflows — from early-stage to enterprise.
Building a billing module inside their platform.
Building in-house processing and automation.
Building custom billing for their own operations.
When you need RCMbox
When you need custom billing logic and a platform that lets you ship new workflows fast while keeping every production run explainable.
Payers, states, and client-specific rules evolve constantly, and you need a safe way to extend logic without rewriting core code.
Business logic should live in workflows with explicit steps, triggers, and states, not scattered across services and cron jobs.
For any run, see inputs, steps executed, outputs produced, acknowledgements received, and what to do next.
You need a headless backend that integrates with your EHR and data model and your product UI, not a locked UI system.
Add new transaction types, new routing rules, and new steps while reusing the same core building units across workflows.
Keep your existing clearinghouse and transport path today, then swap, add, or split routes later without rewriting the platform.
Capabilities
The core platform pieces you get out of the box, designed for extension and debugging.
Run healthcare transaction workflows with explicit steps, triggers, transitions, and states, built to be extended safely.
Draft and modify workflows in the developer UI from templates or from scratch, with AI assistance to speed up iteration.
Connect via API or SFTP, convert to/from X12, and route transactions through your clearinghouse/transport provider — with auditable routing rules.
Workflow execution is powered by Temporal (open source): durable state, retries/timeouts, operational visibility, and scaling controls for production workloads.
Inspect a specific run end-to-end from inputs to steps to outputs, replay with known inputs, and understand exactly what happened and why.
Start with a baseline operations UI your team can tailor instead of building every screen from scratch.
How workflow steps and workflows fit together
A short technical view of how the platform stays extensible while keeping production runs explainable.
Reusable units for validation, mapping, routing, submission, matching, retries, and more.
Compose steps into an executable pipeline with clear triggers, transitions, and states.
Add your own steps, modify existing workflows, and integrate external systems safely.
Any specific run can be traced step by step: what executed, what data it used, what it produced, and where it failed.
- FHIR database on PostgreSQL (JSONB)
- Multiple APIs: FHIR, SQL, GraphQL, Bulk, and Subscriptions
- Security and access control: OAuth2, multi-tenancy, policy-based access
- SDKs: TypeScript, C#, and Python
- Deployment options: Hosted or self-hosted
Powered by Aidbox
RCMbox is built on Aidbox, a production-grade FHIR server and data platform.
Go live fast with Health Samurai
Ship your first production workflows quickly, then keep evolving the system without accumulating a maintenance nightmare.
For a straightforward setup, teams can get to first production claims in under a month because the core workflow foundation is already in place.
Delivered billing modules in production, including work on a billing module for Sandata's Agency Management Platform.
We can build quickly, then either keep evolving it with you or hand it off to your team with a clean, maintainable foundation.
Tell us what you are building (transactions, payers, integration path) and your target go-live date.
Leave a note about your use case - we will reply with a few time slots.
