837 Professional (837P)
Outbound professional claim batches with scrub, transmit, ack tracking, and retry.
Integrations
Connect ObsidianRCM to your billing ecosystem.
Clearinghouses, payers, identity providers, payment gateways, and your own systems — through X12, REST, FHIR, and webhooks.
837 Institutional (837I)
UB-04 institutional claims with facility defaults and institutional scrub rules.
835 ERA
Inbound remittance files, auto-post, posting exceptions, and reconciliation.
999 / 277CA
Acknowledgement and claim status tracking in the EDI hub.
Clearinghouse transport
Vendor-agnostic SFTP/HTTP — connect your clearinghouse; BYO credentials.
Eligibility
Integrated eligibility workflows with standard vendor paths for enterprise deployments.
FHIR R4
Read APIs: Patient, Encounter, Claim — for EHR and interop partners.
Patient payments
Payment plans and installment collection via gateway integration and webhooks.
SSO (SAML)
Enterprise single sign-on with IdP group → role mapping.
SCIM
User provisioning from your identity provider.
REST APIs
Authenticated APIs across billing modules for custom integrations.
Webhooks
Outbound event delivery for automation and external systems.
ObsidianRCM core
ClaimsEDI hubPaymentsDenialsAPIs
REST · FHIR R4 · Webhooks · X12 837/835
External systems
ClearinghousePayersIdP / SSOEHR (read)Payment gatewayYour apps
Integration details, API documentation, and sandbox access are provided during onboarding and enterprise evaluation — not on the public marketing site.
Need a specific integration?
Describe your clearinghouse, IdP, or EHR connection in a demo request.