Skip to content

What each product does

ArkCloud Health runs several products on one platform. Pick a product to see its capabilities - and where something is not built yet, this page says so instead of listing it as though it were.

Revenue Cycle Management

Capabilities

ArkCloud RCM is the billing office's workspace from charge to collected payment: claims, remittance posting, denials and appeals, patient statements, payment plans, self-pay collections and revenue reporting. Charges arrive from ArkCloud Rehab once a visit's documentation passes its checks. Electronic claim submission and eligibility checks need your own clearinghouse mailbox and Availity credentials.

Collections & work queues

Balance-after-insurance and self-pay recovery, with the compliance controls that work requires.

  • Rule-based work queues and routing
  • Account prioritisation and work distribution
  • Promise-to-pay tracking
  • FDCPA-aware contact controls
  • TCPA consent checked before automated contact
  • Letter generation (print and send yourself)
  • Agent scripting

Claims & denials

Submission, remittance and appeal, on real X12 rather than a stub.

  • Claims submission and tracking (X12 837), through your clearinghouse once enrolled and configured
  • Remittance processing (ERA / 835), through your clearinghouse once enrolled and configured
  • Clearinghouse SFTP mailbox: 837P out; 999, 277CA and 835 collected back
  • Denial management and appeals
  • Claim scrubbing and payer rules
  • Eligibility verification (270/271 through Availity, with your credentials)
  • Prior authorisation tracking

Payments & patient billing

Taking money, posting it, and proving it reconciles.

  • Card payment processing through Stripe, once a Stripe account is connected
  • Payment posting and reconciliation
  • Payment plans
  • Patient statements
  • Refunds and adjustments
  • Bank file import, with partial automatic matching
  • Processor tie-out and variance reporting

Analytics & reporting

AR performance, forecasting and the reports finance actually asks for.

  • AR ageing and revenue analytics
  • Denial analytics
  • Agent and queue performance
  • Collections forecasting
  • Executive dashboards
  • Custom reports
  • Export to CSV and XLSX

Contact centre

Voice and messaging wired into the account being worked, once your Amazon Connect, Twilio and SendGrid accounts are connected.

  • Amazon Connect telephony
  • Inbound queues and agent-placed calls
  • Call recording with authenticated callbacks
  • Transactional SMS and email via Twilio and SendGrid
  • Voicemail and call flows

Platform, security & compliance

The parts every ArkCloud product inherits.

  • Multi-tenant isolation enforced in the database, not only in queries
  • Role-based access control and permission elevation
  • AES-256 encryption of designated PHI fields at rest (not every demographic field)
  • Append-only audit trail of changes; PHI-access logging in progress
  • MFA enforced for privileged roles
  • SSO via Google
  • Seven-year retention policies; cold-storage archival once an S3 archive bucket is configured
  • EHR connectors in code (Epic, Oracle Health, athenahealth; FHIR R4, read-only); hospital record import is configured per hospital by a Rehab administrator and is not yet verified against any vendor
  • HL7 v2 message parsing (no inbound interface listener yet)

One platform underneath

Whichever product you use, the identity, tenant isolation, audit trail and security boundary are the same ones. Products build on the platform rather than beside it.