What works on day one, and what waits on you
Every row below is read from the same records the product and the rest of this site use - the Rehab capability registry, the integration status list, the AI register and the live email and SMS checks - so when something changes, its row moves on its own.
Read live from the registries
Works as soon as you sign up
Nothing to connect. These work in the trial on the hosted service today.
Your account
14-day free trial
AvailableSign up and get a 14-day free trial of RCM, Rehab, Access, Care, Insights and Workforce, with no card.
Details: 14-day free trialSingle sign-on
Configured, verification pendingGoogle sign-in. A Microsoft Entra ID provider exists in code but is registered only when its credentials are set, and the sign-in page shows no Microsoft button. SAML (Okta, OneLogin) is switched off until ArkCloud can verify SAML signatures.
Details: Single sign-onEmail delivery
SendingOutbound transactional email - portal links, notifications, statements and payment receipts - through SendGrid or an SMTP server, whichever the deployment has configured. Outside production, sends are recorded as simulated.
Details: Email delivery
Referrals, scheduling and the patient's visit
Referral intake
AvailableReferrals received, triaged and accepted into care - creating the patient record and opening the episode in one step.
Details: Referral intakePatient workspace
AvailableRehab patient caseload, admission and patient-level profile.
Details: Patient workspaceEpisodes of care
AvailableCourses of rehabilitation care, with an enforced lifecycle.
Details: Episodes of careSchedule and check-in
AvailableNative outpatient scheduling: book, confirm, check in, start a visit, complete, cancel and record a no-show.
Details: Schedule and check-inProvider availability and bookable slots
AvailableRecurring weekly availability per provider, dated exceptions, group capacity and expiring slot holds.
Details: Provider availability and bookable slotsService catalogue
AvailableWhat the organisation offers, how long each service takes, what it costs, and whether a patient may book it.
Details: Service catalogueWaitlist
AvailablePatients waiting for a slot, matched to openings by when they can actually come.
Details: WaitlistCancellation and no-show fees
AvailableWhether a late cancellation or a missed visit is chargeable, how much, and who forgave it.
Details: Cancellation and no-show feesCalendar subscription
AvailableA clinician subscribing to their own ArkCloud schedule from Google, Outlook or Apple Calendar.
Details: Calendar subscriptionPatient self-scheduling
AvailableA patient choosing and booking a NEW appointment time for themselves.
Details: Patient self-schedulingOnline check-in
AvailableA patient (or their scheduling proxy) checks in for a booked visit from the portal, before arriving.
Details: Online check-inIntake and consent forms
AvailableQuestionnaires a practice sends patients before a visit, completed from a link and attached to the record.
Details: Intake and consent formsTwilio (SMS)
SendingOutbound SMS, checked against the patient's contact consent. Inbound STOP replies withdraw SMS consent once the number's inbound webhook points at /api/webhooks/twilio-sms. Outbound voice calls are not available: they are refused and nothing is recorded.
Details: Twilio (SMS)
Documentation and outcomes
Encounters
AvailableContacts in which care was delivered, with their documentation and billing state on the same row.
Details: EncountersClinical note signature and amendment
AvailableComplete, sign, co-sign, amend and lock a clinical note, with superseded text preserved verbatim.
Details: Clinical note signature and amendmentTreatment plans
AvailableA plan of care per episode, with goals, review cycles and signatures. Goals are the existing clinical-goal records, not a second set.
Details: Treatment plansUtilization review
AvailableAuthorizations recorded, tracked and reviewed: what the payer granted, what is left, and when they must next be called.
Details: Utilization reviewOperational reporting
AvailableSchedule performance: visits held, missed and cancelled, utilisation of declared availability, and new versus returning patients.
Details: Operational reporting
Billing and payments
Revenue cycle
AvailableAuthorizations, charge capture and the financial outcome of a course of care.
Details: Revenue cycleBenefits verification
AvailableStaff record the benefits a payer stated for an episode - copay, coinsurance, deductible, out-of-pocket and the plan's visit limit - by phone or the payer's portal.
Details: Benefits verificationClaim checks before submission
Live · Rules, not AIEvery claim is checked against a set of rules before it is sent; a claim with a blocking finding is stopped with the reasons listed. Live in ArkCloud RCM.
Details: Claim checks before submissionDenial sorting and follow-up
Live · Rules, not AIDenials are categorised from their reason codes into a work queue, with appeal deadlines and follow-up tasks. Live in ArkCloud RCM.
Details: Denial sorting and follow-up
AI assistance
Clinical Brain: questions about an episode
LiveA therapist asks a question about the episode or assessment in front of them - the latest score, what is still outstanding, what the documentation status is - and gets an answer built only from that patient's governed record. Live in ArkCloud Rehab on the episode and assessment pages, for staff permitted to view rehab patients.
Details: Clinical Brain: questions about an episodeClinician-reviewed SOAP draft from visit notes
LiveFrom what the therapist recorded for today's visit (Quick Capture selections and typed notes) and the episode's own record, the assistant proposes a structured Subjective / Objective / Assessment / Plan draft. Every sentence must cite its source; unsupported sentences are removed before the therapist sees the draft. Live on the hosted service, which turns it on for patient records (REHAB_SOAP_DRAFT_MODE=phi with the approved model host named). It is off by default in the software, so another deployment must switch it on.
Details: Clinician-reviewed SOAP draft from visit notesProgress report and discharge summary narratives
LiveWhen an editable progress report or discharge summary is opened, an AI draft of its narrative sections is prepared beside the document: progress toward goals and reassessment findings, or course of care and goals met. Live on the hosted service. It uses the same deployment setting as the Draft SOAP note (REHAB_SOAP_DRAFT_MODE), off by default in the software.
Details: Progress report and discharge summary narrativesPatient message reply drafts
LiveWhen a patient conversation is waiting for a reply, a short draft appears in the reply box, labelled as an AI draft. The billing portal inbox in ArkCloud RCM works the same way. Live in ArkCloud Rehab patient messages and the RCM billing portal inbox. The deployment can switch it off with MESSAGE_AI_REPLY_DRAFTS=off.
Details: Patient message reply draftsAccount assistant
LiveOn a patient account, billing staff can ask questions about that account - its balance, claims, open denial codes, what payers assigned to the patient, any payment plan and recent contacts - and get a written answer in the account's AI tab. Live in ArkCloud RCM for staff permitted to view accounts. On by default; an administrator can switch it off in Settings > AI.
Details: Account assistantDenial appeal letter draft
LiveCreate Appeal on a denial opens with the letter already drafted, a list of what it relies on (reason codes, the claim line, the signed note, the authorization, the plan of care, your appeal template) and a list of gaps to fill. Live in ArkCloud RCM under Denials. An administrator can switch it off for the organisation in Settings > AI; the deployment can switch every RCM draft off with RCM_AI_DRAFTS=off.
Details: Denial appeal letter draftGoal suggestions and plan-of-care drafting
LiveBeside the goal form, Suggest goals proposes goals written toward the episode's documented limitations and findings; beside the plan of care, Draft with AI drafts the problem statement, interventions and discharge criteria. Nothing is created until the therapist saves it. Live on the hosted service. It uses the same deployment setting as the Draft SOAP note (REHAB_SOAP_DRAFT_MODE), off by default in the software, and the patient's AI agreement.
Details: Goal suggestions and plan-of-care drafting
Hospitals, EHRs and other systems
FHIR R4 API
AvailableSession-authenticated FHIR R4 read and search of your own Patient, Coverage, Claim and ExplanationOfBenefit data, plus Patient create. No SMART on FHIR or OAuth and no update, so external systems cannot use it.
Details: FHIR R4 API
Works once you connect your own account
Built, and waiting on an account or credentials only your practice can hold. Each row says what you supply.
Your account
Your existing data
Set up with youMoving records from your previous system is scoped with you before you start.
Details: Your existing data
Billing and payments
Billing insurers
Built, not connectedYou supply: A clearinghouse account, and enrollment with each payer you bill so claims can be sent electronically. Payer enrollment can take several weeks, so start it early; until it is done, claims are built and validated but not sent.
837P professional claims, and 837I institutional claims for a facility set up to bill on the UB-04, are uploaded to one clearinghouse's SFTP mailbox, and its 999, 277CA and 835 replies are collected from the same mailbox every 15 minutes while the worker service and Redis are running. The same mailbox carries 276 claim status inquiries (once a day, for claims still awaiting adjudication 14 days after submission and not asked about in the previous 7) and their 277 answers, which can change a claim's status but never post a payment; batch 270 eligibility inquiries with their 271 answers, used when no real-time eligibility connection is configured; and inbound 834 benefit enrollment files (or staff uploads), which become proposed coverage changes that staff approve or reject - none is applied automatically. Vendor-neutral; set on the back-office Credentials page. An SFTP password or private key, and a submitter contact phone or email (CLEARINGHOUSE_SUBMITTER_CONTACT_PHONE / _EMAIL), are also required. Built, and not connected until those mailbox credentials are entered: nothing is transmitted until then, and none of it has been tested with a payer. Real-time eligibility is separate.
Details: Billing insurersEligibility checks
Built, not connectedYou supply: An eligibility vendor account with your own credentials before real-time eligibility can run.
Real-time 270/271 eligibility checks sent to Availity's REST API. Configured for the whole deployment, not per organisation. Without it, a check is not answered on the spot: when the clearinghouse mailbox is configured it is queued and sent as a batch 270 through the mailbox, and the screen says so until the payer's 271 arrives.
Details: Eligibility checks
Hospitals, EHRs and other systems
Outside records import (FHIR R4, C-CDA)
Set up per organisationYou supply: The credentials belong to your organisation, so an administrator creates the connection; nothing is exchanged until they do.
Imports a patient's conditions, procedures, allergies, medications, observations (laboratory, vital signs, oxygen), encounters, clinical notes, imaging reports and study metadata, and service requests from a hospital over FHIR R4 (SMART Backend Services), read-only, and reads uploaded FHIR R4 Bundle and C-CDA files, into proposals a licensed clinician reviews; nothing reaches the chart unreviewed. Imports record purpose of use and authorisation basis and are listed in the Interoperability Center. One connection per hospital; each hospital must register and activate ArkCloud's client. The generic path ran once against the public SMART Health IT reference sandbox with synthetic data (2026-10-03), which proves the protocol flow only; Epic and Oracle Health profiles are tested only against ArkCloud's own synthetic profiles. No EHR vendor connection is verified, and images are not retrieved.
Details: Outside records import (FHIR R4, C-CDA)FHIR referral exchange
Set up per organisationYou supply: The credentials belong to your organisation, so an administrator creates the connection; nothing is exchanged until they do.
Receives FHIR R4 referrals (ServiceRequest, Patient, Practitioner, Coverage) from a referring EHR - pulled with SMART Backend Services or pushed with an HMAC signature - matches the patient without ever merging records, and reports accepted, scheduled, completed or declined back to the referrer. Contract-tested against a simulated partner only; no partner connection has been proven.
Details: FHIR referral exchange
Not available yet
Not something you can use today, whatever you connect. Each row says why.
Your account
Paying for your subscription online
Not switched onOnline checkout is not switched on yet; our team sets up your subscription with you. RCM and Rehab are subscribed through our team until online checkout opens; Access, Care, Insights and Workforce continue through our team.
Details: Paying for your subscription online
Documentation and outcomes
Outcome measure registry
Clinical content requiredPublished measures with derived availability and citations.
Details: Outcome measure registryDeterministic scoring
Scoring definition requiredScoring against a validated, version-pinned implementation.
Details: Deterministic scoringScore interpretation
Not yet availableExplaining what a score means against published thresholds.
Details: Score interpretationAutomatic note generation (no clinician draft step)
Not yet availableNotes drafted automatically from episode context and approved metadata. Notes clinicians write, sign and co-sign are a separate, available capability.
Details: Automatic note generation (no clinician draft step)
Billing and payments
Payment gateway
Built, not connectedThe implementation exists. This deployment holds no credentials for it, so nothing is being exchanged. Patient and staff card payments through Stripe's card form, saved cards and AutoPay on portal payment plans - all charged on each practice's own connected Stripe account once that practice completes Connect onboarding. Needs STRIPE_SECRET_KEY, NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY and STRIPE_WEBHOOK_SECRET (and STRIPE_CONNECT_WEBHOOK_SECRET for connected-account events). No ACH.
Details: Payment gateway
AI assistance
Visit recording and voice intake (speech-to-text)
In developmentWith everyone in the room told and agreeing, a visit can be recorded from the therapy note and transcribed as it happens; the transcript can be added to the clinician's visit notes for the Draft SOAP note. Intake forms can be asked aloud and answered by voice.
Details: Visit recording and voice intake (speech-to-text)AI coding suggestions
Not available · Not builtArkCloud does not suggest diagnosis or procedure codes with AI.
Details: AI coding suggestions
Hospitals, EHRs and other systems
Custom integrations
Built, not connectedThe implementation exists. This deployment holds no credentials for it, so nothing is being exchanged. An experimental, read-only API (claims, appointments, the webhook event list) authenticated by scoped API keys your administrator creates. Off until the deployment and your organisation both enable it. Anything beyond it is a project agreed with ArkCloud.
Details: Custom integrationsOutbound webhooks
Built, not connectedThe implementation exists. This deployment holds no credentials for it, so nothing is being exchanged. Signed (HMAC-SHA256) event delivery to an HTTPS endpoint your administrator registers and verifies, with retries and a delivery log. Events carry identifiers and statuses, not patient demographics or note text. Off until the deployment and your organisation both enable it.
Details: Outbound webhooksAmazon Connect
Built, not connectedThe implementation exists. This deployment holds no credentials for it, so nothing is being exchanged. An embedded Amazon Connect softphone (CCP) with screen-pop to the caller's account. Your organisation supplies its own Connect instance.
Details: Amazon ConnectEpic
Built, not usable yetA Rehab administrator can configure a read-only hospital record import connection with an Epic profile, built to Epic's SMART Backend Services requirements (a private-key JWT, not a client secret). It has been tested only against ArkCloud's own synthetic Epic-style test profile and is not yet verified against an Epic system; each hospital must register and activate ArkCloud's client first. EHR sync is not available: every sync operation answers 501, and nothing is written back to Epic. No MyChart, Care Everywhere or App Orchard integration exists.
Details: EpicOracle Health (Cerner)
Built, not usable yetA Rehab administrator can configure a read-only hospital record import connection with an Oracle Health profile (SMART Backend Services). It has been tested only against ArkCloud's own synthetic Oracle-style test profile and is not yet verified against an Oracle Health system; each hospital must provision ArkCloud's client first. EHR sync is not available: every sync operation answers 501, and nothing is written back.
Details: Oracle Health (Cerner)MEDITECH
Not builtPlanned. A MEDITECH hospital record import connection can be recorded by a Rehab administrator, but where the hospital offers only SMART app launch (not built) it is shown as unsupported, and nothing has been tested against MEDITECH. There is no demographic or financial exchange with MEDITECH Expanse.
Details: MEDITECHHL7 v2 interfaces
Built, not usable yetAn HL7 v2 parse and generate library (parses ADT, ORM, ORU, DFT, SIU and others; generates ADT A01/A03/A08, DFT P03 and ACK) exists in code. An administrator can parse, validate or generate a message through the HL7 API, but there is no MLLP listener and no inbound interface and nothing is sent, so no system can exchange HL7 messages with ArkCloud.
Details: HL7 v2 interfaces
Where these come from
Rehab rows show the state the product itself resolves, as on ArkCloud Rehab. Integration rows use the statuses on Integration status, and what you supply is the list on Pricing. AI rows are from AI at ArkCloud. Email and SMS follow the same checks as System status.
