Getting started
What works today
One list of every capability these guides mention and its status right now. Use it to check what a clinic can rely on before you plan around it.
Written for: Clinic owners and buyers · Clinic administrators · Clinicians evaluating ArkCloud
How to read this page
Each capability is in exactly one of eight states. A screen that opens is not the same as a task that works from start to finish, so a capability is only marked Available when the whole task works today for a clinic that has done nothing special. Anything that needs a switch, an approval or settings is marked as needing configuration; anything that needs an account with an outside service is marked as needing a connection.
- Available
- Works in ArkCloud today with no special setup.
- Available with configuration
- Works once your organisation switches it on or completes the setup it needs.
- Needs an external connection
- Built in ArkCloud, and needs an account or contract with an outside service before it works.
- Limited preview
- Usable in a limited way while it is being completed; not for routine production use.
- Partially available
- Some of it works today; the page says exactly which part.
- In development
- Being built. Not available to use yet.
- Not available
- ArkCloud does not do this.
- Not independently verified
- Built, but not yet proven end to end in production. Ask us before relying on it.
This page is generated from the same source the other guides use when they show a status, so the two cannot disagree. When a status changes, it changes here and on every page that mentions it at the same time. Product availability (which products you can buy) is listed separately on The products and what each does.
Getting started and platform
| Capability | Status | What that means here |
|---|---|---|
| Sign in with email and password | Available | Every account can sign in with its email address and password. Forgotten passwords are reset by email, and ten wrong passwords in a row lock the account for 15 minutes. |
| Sign in with Google | Not independently verified | The Continue with Google button is switched on. Which Google accounts it admits depends on how ArkCloud's Google sign-in is set up, and that has not been confirmed for customer accounts. Plan on email and password, and ask ArkCloud before rolling out Google sign-in. |
| Sign in with Microsoft | Not available | There is no Microsoft sign-in on the ArkCloud sign-in screen. |
| SAML single sign-on (Okta, OneLogin and similar) | Not available | SAML sign-in is switched off and every SAML sign-in is refused. Okta and OneLogin are not offered. |
| Multi-factor authentication with an authenticator app | Available | Six-digit codes from an authenticator app, plus one-time recovery codes. Required for every administrator before any application opens; optional for everyone else. |
| Require multi-factor authentication for every user | Available with configuration | An administrator can extend the requirement from administrators to every user in the organisation.Requires: An administrator switches on Require 2FA for all users in Account settings. It applies from each user's next sign-in. |
| Codes by text message, or hardware security keys | Not available | The only second factor is an authenticator app. Codes by text message or email, and hardware keys, are not offered. |
| Application launcher | Available | After sign-in, lists every ArkCloud product and opens the ones your organisation holds and your role may enter. If you can open only one, you go straight into it. |
| Patient search in the Rehab header | Available | From any Rehab screen, search the caseload and open a patient's chart. Results show name, date of birth, record number and whether there is an active episode. |
| Custom roles or editable role permissions | Not available | The sign-in roles are fixed. There is no separate therapist, front-desk or biller role, and a role's permissions cannot be edited. |
| Registration and clinical staff functions (Rehab) | Available with configuration | Separates registration work (demographics, contact details, insurance, consent) from clinical work (clinical intake review and clinical documentation) for each person. Until a person is given a function, they can do both.Requires: An administrator assigns each person Registration, Clinical or both under Rehab settings, Staff functions. |
| Billable signing authority for clinicians | Available with configuration | A clinician can sign, co-sign or amend a note only when they have a discipline grant for the episode, an active staff record and a current licence; without them the signature is refused. Billing checks the same records again as of the signing date.Requires: An administrator completes each clinician's set-up under Rehab settings, Clinicians, including their staff record and licence. |
| Clinic setup checklist | Available | Shows administrators what is in place and what is still missing before go-live (billing identifiers, locations, clinicians ready to sign, payers, fee schedule, services, policies), worked out fresh from your records each time. |
| 14-day trial by self sign-up | Available | Signing up creates a new organisation with you as its administrator and a 14-day trial of every product except Clinical. |
| Sample patients in a new organisation | Available | Each new organisation gets its own small set of clearly fictional sample records. Nothing is sent to a patient or payer from them, and an administrator can remove them in one step. |
| Real patient data paths closed until a BAA is signed | Available | Until ArkCloud records your signed Business Associate Agreement, imports, connections to other systems, online patient forms and portal invitations are refused, and every screen shows a notice to use sample or test data only. |
| Organisation AI switch | Available | One switch turns every AI feature off or on for your organisation. It is on unless an administrator turns it off, and rule-based features keep working when it is off. Visit recording has its own setting and is not controlled by this switch. |
| AI draft of a visit note (SOAP) | Available with configuration | Inside a visit note, proposes Subjective, Objective, Assessment and Plan from what the clinician recorded for that visit and the episode's own record. The clinician inserts, edits or discards each section.Requires: The organisation AI switch on (the default). Where the clinic has installed the patient AI agreement, the patient's signed yes to AI-assisted notes. |
| AI draft of progress report and discharge summary narratives | Available with configuration | Drafts the progress-toward-goals and reassessment sections of a progress report, and the course-of-care and goals-met sections of a discharge summary, from recorded facts only. It never drafts goals, the plan of care, discharge status or recommendations.Requires: The organisation AI switch on (the default). |
| AI suggestions from outside records | Available | For an imported outside record, suggests history and precaution items, each quoting the document word for word and marked uncertain, for a clinician to accept, edit or reject. |
| Patient AI agreement | Available with configuration | A form the patient signs with two separate yes-or-no choices: AI-assisted notes, and audio recording. Once installed, it is enforced for AI visit-note (SOAP) drafts and for starting a visit recording.Requires: An administrator installs the agreement on the Forms page, after the practice has reviewed its wording. If it is not installed, nothing is gated by it. |
| AI review attestation at signing | Available | A note that contains AI-drafted text, or for which an AI draft was delivered, cannot be signed until the clinician confirms they reviewed every AI-drafted section and that the signed note is their own documentation. |
| Signed notes are frozen; changes are amendments | Available | Signing freezes the note text and the signer's credentials. A later change is an amendment with a reason, and the earlier wording is kept. Locking is permanent. |
| Visit recording and dictation with speech-to-text | Limited preview | Built into Rehab visit and evaluation notes: speech is transcribed on ArkCloud's own servers and the clinician decides what to use. Accuracy has been tested on synthetic speech only, and it is not released for routine clinical use.Requires: The organisation's voice setting switched on, the recording permission, and in-the-room consent for each recording. |
| Structured entries proposed from an evaluation recording | Limited preview | From an evaluation transcript, a rule-based reader (not AI) proposes screening answers, range-of-motion and muscle-test values and assistance levels, each beside the words it came from, for the clinician to accept, correct or reject.Requires: Visit recording available to the organisation (see above). |
| Incoming call routing on Twilio (hours, phone menus, ring groups, voicemail) | Not independently verified | ArkCloud answers each call on a Twilio number from your routing plan: opening hours and holidays, a press-a-key menu, phones rung all at once or one after another, forwarding, and voicemail that ArkCloud copies out of Twilio, stores encrypted and transcribes, with the transcript on the call routing screen. Conversations are not recorded. It has not yet been run on a live Twilio number.Requires: A Twilio account under a signed Business Associate Agreement, the operator's Twilio credentials and public callback address, and each number's voice webhook pointed at ArkCloud. Voicemail transcripts also need the deployment's speech-to-text service. |
| Incoming call routing published to Amazon Connect | Not independently verified | The same routing plan is published to your own Amazon Connect instance as a contact flow and hours of operation, and the number is pointed at it. Incoming calls on the line appear in ArkCloud's call list once Connect sends its contact events to ArkCloud. Connect has no built-in voicemail, rings phones one after another only, and keeps holiday closures in Connect itself. It has not yet been published to a live instance.Requires: Your Amazon Connect instance and access keys saved in ArkCloud, with permission to create contact flows and hours of operation and to route phone numbers; the number claimed in that instance. |
| Calls from your own phone system in ArkCloud call history | Not independently verified | If your existing phone system keeps routing calls, it can send signed call events (ringing, answered, missed, ended) so incoming calls appear on ArkCloud's call routing screen. ArkCloud does not route these calls.Requires: Your phone system able to send a signed web request for each call event. |
| AI review of a saved note | In development | A check of a saved note for gaps and contradictions. Built, and switched off for customer organisations. |
| Notes written and signed without the clinician | Not available | ArkCloud never writes, completes or signs a note on its own. Every draft waits for the clinician. |
| AI-suggested goals and plan-of-care text | Available | Suggested goals, and a drafted problem statement, interventions and discharge criteria for the plan of care. They are proposals with their sources that the clinician inserts into the form and saves; the target, target date, visit frequency and duration are always the clinician's. AI never decides treatment. |
| AI diagnosis or procedure coding | Not available | AI does not choose diagnosis or procedure codes. Codes come from what staff record and the service a visit was booked under. |
Front desk and Access
| Capability | Status | What that means here |
|---|---|---|
| Referral intake and acceptance into care (Rehab) | Available | Staff record a referral, triage it, and accept it into care. Accepting creates or links the patient and opens the episode in one step; an existing patient is matched only by exact record number or by a person choosing them. |
| Referral queue (Access) | Available | A shared queue of inbound referrals with status New, In review, Accepted, Scheduled or Declined. An Access referral is a log entry, not a patient record, until it is sent to Rehab. |
| Send to Rehab (referral, registration or waitlist entry) | Available | An Access administrator sends the record to Rehab after confirming how the name splits into first and last and the date of birth. Nothing is re-typed; nothing is guessed.Requires: An Access administrator, and an organisation that also has ArkCloud Rehab. |
| Electronic (FHIR) referrals from a referring EHR | Needs an external connection | Built: referrals can arrive from a referring organisation's system and status updates go back. Each organisation sets up its own connection, and no connection to a live partner system has been proven.Requires: A referral exchange connection agreed and configured with the referring organisation. |
| Receiving faxes directly | Not available | ArkCloud has no fax line or fax inbox. A faxed referral is entered by hand as a referral, and the faxed pages can be scanned and uploaded as an outside record. |
| Referral summary (AI) and missing-information checklist | Available with configuration | A quote-backed AI summary of why the patient was referred, beside a rule-built checklist of what the referral is missing. The checklist works without AI. The summary changes nothing on the referral.Requires: The deployment's outside-record AI switch (on for the hosted service) and the organisation's AI switch. |
| Registering a patient (Rehab) | Available | Add patient searches for an existing record first, then creates one with name, date of birth and record number. A strong possible duplicate is refused unless someone confirms it. |
| Digital registration queue (Access) | Available | Registrations in progress with status Draft, Submitted, In review or Completed. A registration is not a patient chart until an Access administrator sends it to Rehab. |
| Demographic, contact and emergency-contact updates | Available | Edited on the patient's chart under Registration details. Once an administrator assigns staff functions, only registration staff (and administrators) can change these details; a patient's report of a change becomes a task, never an edit. |
| Registration and clinical staff functions | Available with configuration | An administrator can mark each person as registration staff, clinical staff or both. Registration staff maintain demographics, contact, insurance and consent; clinical staff review clinical intake. Someone with no function assigned can do both.Requires: An administrator assigns functions under Rehab settings, Staff functions. |
| Front-desk flags, interpreter and accessibility line, front-desk-only notes | Available with configuration | A clinician flags a wrong or missing detail (for example insurance or an interpreter need) for the front desk; registration staff see open flags on the patient's Registration & admin tab and on a clinic-wide list, fix the detail and mark the flag resolved. Nobody is notified when a flag is raised. Interpreter and accessibility needs show as one line on the chart and the episode, and administrative notes are kept by registration staff.Requires: An administrator assigns staff functions. The flag control appears only for staff assigned the clinical function without the registration function; until functions are assigned, everyone can edit registration details directly and nobody sees it. |
| Referring-provider directory | Partially available | Staff can add an outside physician or practitioner with an NPI (checked for a valid check digit) and a Direct address or fax number, and mark the entry verified, recording how it was checked. There is not yet a screen to edit or remove an entry, or to match a referral to an entry. A listed provider gets no access to ArkCloud. |
| Uploading scanned and electronic documents (outside records) | Available | Any Rehab user can upload a PDF, scanned image (JPEG, PNG, TIFF), C-CDA or FHIR bundle file from Outside records or from a patient's chart, naming the document type and the sending organisation. |
| Virus and malware scanning of uploads | Available | Every uploaded outside record is scanned before anyone can open it; a file that is infected, still being scanned or could not be scanned cannot be opened. Patient uploads in the portal are scanned before they are stored and refused if the scan fails. |
| Patient photo of a medication list (portal intake) | Available | On the portal intake's medications step a patient can add a photo or PDF of their medication list. It is marked patient-reported, nothing is read from it automatically, and a clinician opens it from the intake review. |
| Reading text from scanned documents (OCR) | Not available | ArkCloud does not read the text of a scanned page or photo. Information from a scanned document reaches the chart only when a person transcribes it and a clinician accepts it. |
| Direct connection to a desktop scanner | Not available | There is no scanner driver or scan-to-ArkCloud button. Scan with your scanner's own software to a PDF or image file, then upload the file. |
| Patient Documents tab, upload templates and document sign-off | Available | On a patient's Documents tab, Add a document offers one-press templates for a physician referral, signed plan of care, insurance card, photo ID, signed consent and letter, which fill in the category, title and how it arrived. Any filed document can be sent to a named colleague to sign off as reviewed. |
| Clinician review of outside-record information | Available | Anyone who can read a record can transcribe items from it as proposals. Only a credentialed clinician can accept, edit, reject or defer them; nothing reaches the chart without that decision. |
| Booking visits and courses of visits | Available | Staff book single visits or recurring courses against an episode, from the service catalogue, on each clinician's availability. Clashes with leave or other visits are refused unless a reason is given. |
| Online booking and new-patient requests | Available with configuration | Established patients can book follow-ups in the portal, and new patients can request a first visit on your public booking page for staff to approve. All of it is off until an administrator turns it on.Requires: An administrator switches on self-scheduling (and new-patient requests), sets a public booking address, and marks services and availability as open to patients. |
| Checking a patient in at the desk | Available | Check in on the Rehab schedule, or Mark arrived on the Access check-in board, sets the visit to Checked in and records who did it and when. |
| Alerting the therapist when a patient arrives | Not available | Checking a patient in sends no notification, message or alert to the therapist, and the schedule does not refresh by itself. The therapist sees Checked in on the schedule or the dashboard when the page is opened or reloaded. |
| Urgent intake answer alert | Available | When a patient's intake answer screens positive for an urgent symptom, the attending clinician, the person who started the intake, and supervisors and administrators get an in-app alert. The screen is rule-based and can miss a concern phrased differently. |
| Online check-in before the visit (patient portal) | Available with configuration | The patient confirms details and insurance, completes the forms sent for the visit and checks in from the portal. It does not mark them arrived; the front desk still checks them in. Off by default.Requires: An administrator turns on 'Patients may check in online before a visit'. |
| Copay collection at online check-in | Needs an external connection | Built, and not usable on the hosted service today: card payment needs the practice's own connected payment account, and none is connected, so no copay is collected online.Requires: A connected Stripe account for the practice. |
| Start visit and the Write note link | Available | After check-in, Start visit on the schedule opens the visit record. Only then does the row show Write note, which opens the episode at the notes with that visit already chosen. |
| Appointment reminders (email and text) | Available with configuration | Reminders go by email or text for visits on the Rehab schedule once an administrator turns them on. Texts go only to patients with recorded text consent; a STOP reply is recorded as an opt-out. Carrier registration for US text messages was still being completed in late October 2026, so texts may be filtered.Requires: An administrator turns reminders on and chooses the channel. Patients need recorded email or text consent. |
| Patient messages from the portal | Available with configuration | One inbox for care-team and billing questions patients send from the portal. Care-team messaging is off until an administrator turns it on with a response time and clinic phone number.Requires: An administrator switches on care-team messaging in Rehab settings. |
| Waitlist | Available | Patients waiting for capacity are held as records with the days and times they can attend. The Rehab waitlist matches a freed slot and books an accepted offer; the Access waitlist is a capacity queue that can be sent to Rehab. |
| Intake and consent forms sent by link | Available | Staff send a form as a private link. The patient is emailed the link when they have agreed to email; otherwise staff pass it on. Signatures are a typed name; drawn signatures are not available. |
| Reviewing a patient's intake answers | Available | Every answer arrives as patient-reported and changes nothing until a person accepts, confirms, corrects or disputes it. Contact and consent items go to registration staff; history, medicines, allergies and symptoms go to clinicians. |
| Recording insurance coverage | Available | Staff record the patient's coverage (primary, optional secondary, or self-pay) in the episode's billing setup. Patients cannot edit coverage; a reported change becomes a task. |
| Electronic insurance eligibility checks | Needs an external connection | Built as a real payer inquiry, never simulated into an answer. Not connected on the hosted service today, so no eligibility answer is returned.Requires: Availity credentials, or a clearinghouse mailbox, configured for the deployment. |
| Benefits verification by phone or payer portal | Available | Staff record what the payer said, how and with what reference. It supplies the copay and counts visits against plan limits; it is not an electronic eligibility answer. |
| Prior authorization tracking | Available | Requests and approvals are tracked by hand in visits, days or units. Nothing is sent to the payer electronically. A missing authorization never blocks care; it holds the charge. |
| Handoff from the front desk to clinical staff | Partially available | The handoff happens through shared records: the visit's status on the schedule, the episode, outside records waiting for clinical review, and intake answers waiting for review. There is no handoff message or alert, apart from the urgent intake alert. |
| From completed visit to charge | Available | Completing the visit records the service it was booked under. Completing and signing only refresh its billing readiness: Ready to bill, or held with each reason. Nothing creates a charge automatically; a Rehab administrator, who holds the fee-management permission, posts it with Post charge. |
| Sending claims to payers | Needs an external connection | Claims are built and checked in ArkCloud RCM, and are not transmitted on the hosted service today: no clearinghouse is connected, so a submitted claim answers Not sent and stays pending.Requires: A clearinghouse connection configured for the deployment. |
Rehab clinical documentation
| Capability | Status | What that means here |
|---|---|---|
| Six note types on every episode | Available | Initial Evaluation, Visit note, Progress Report, Re-evaluation, Plan of Care and Discharge Summary, each a template of sections that follows the episode's setting and discipline. |
| Template review by your practice | Available with configuration | ArkCloud has not clinically validated the note templates. An administrator records your practice's own review of each template version; until then the editor shows a working-draft notice.Requires: An administrator records the review under Administration, Documentation templates. |
| Progress Report opens with the reporting period | Available | A new Progress Report starts with the period since the last signed report, the visit count, first and last visit, each goal's recorded description, status, baseline, target and date, and each outcome score recorded on the episode with its arithmetic change from the first. Facts only; it never says a patient improved. |
| Progress-report due dates | Available with configuration | A Progress Report is shown as due only after an administrator sets your practice's cadence (every N visits, every N days, or both). With no cadence set, nothing is ever due.Requires: An administrator sets the cadence under Administration, Progress reports. |
| Fill the Plan of Care note from the treatment plan | Available | A Plan of Care note can be filled from the episode's structured treatment plan (frequency, duration, review date, the physician sign-off and linked goals), so the two say the same thing. |
| AI SOAP draft on a visit note | Available with configuration | On a visit note, Draft SOAP note proposes Subjective, Objective, Assessment and Plan text from what is recorded for the visit and the episode. You insert, edit or discard each section. Switched on for the hosted service.Requires: Your organisation's AI switch on. Where your clinic uses the patient AI agreement, the patient must have signed it and answered yes to AI-assisted notes. |
| AI narrative draft on a Progress Report or Discharge Summary | Available with configuration | Proposes text for Progress toward goals and Reassessment findings (Progress Report), and Course of care and Goals met / outcomes (Discharge Summary), from recorded goals, visit counts and earlier signed notes. Never drafts updated goals, the plan, discharge status or recommendations.Requires: Your organisation's AI switch on, and the same hosted AI setting as the visit-note draft. |
| AI drafting for evaluations, re-evaluations and plans of care | Available | On any unsigned templated note, including an Initial Evaluation, a Re-evaluation and a Plan of Care, the AI action beside a field drafts that section from what the clinician typed, confirmed findings and guided answers, with its sources; too little to draft from gets questions instead. For PT, Draft assessment is shaped by the note type: an evaluation, a visit (follow-up), a progress report and a discharge summary each get their own structure and evidence rules, and a progress report needs an earlier and a current value before it is drafted. OT and SLP assessments keep the general structure. There is no one-click whole-SOAP draft for these notes, and nothing enters the note until the clinician inserts it. |
| Build a visit note from your selections (no AI) | Available | Quick Capture selections can be turned into note text by fixed rules, with no AI. It is not marked AI-assisted and works when AI is off or the patient has declined AI. |
| Recording a visit or an evaluation | Limited preview | Built into visit notes (Record this visit, Dictate a summary) and into evaluations, re-evaluations, progress reports and discharge summaries (Record this evaluation). Not yet released for routine clinical use. A Plan of Care has no recording.Requires: Switched on for your organisation, the recording permission, and an approved speech-to-text service. |
| Sign, amend, lock and addenda | Available | The author signs and the text freezes. A signed note changes only by amendment (with a reason, keeping the old wording), can be locked permanently, and can take signed addenda. |
| Signing requirements for each clinician | Available with configuration | A clinician can sign only once they have a discipline grant, an active staff record and a current professional licence, with no expired credential.Requires: An administrator sets this up under Outpatient, Clinician billing. |
| Co-signature | Available | A second clinician with signing authority can co-sign a signed note. Where the author has a supervisor recorded, only that supervisor can co-sign, and billing waits for it. |
| AI review attestation at signing | Available | A note that contains AI-drafted text, or for which an AI draft was shown, cannot be signed until the signer ticks a statement that they reviewed every AI-drafted section. |
| Sending signed notes to a referring provider | Needs an external connection | A signed evaluation, plan of care, progress report, re-evaluation, discharge summary or daily note is listed on the episode's Notes view under Share with an outside provider, but no Direct secure messaging or fax service is connected, so ArkCloud does not send a signed note anywhere today. The panel says that sending is not available.Requires: A Direct messaging or fax service connected to ArkCloud, and each recipient verified in the outside-provider directory. |
| Patient chart | Available | One page per patient in five tabs - Home, Clinical history, Documents, Timeline, and Registration & admin - with allergies and precautions shown above the tabs on every view. |
| Health timeline | Available | Everything recorded for the patient and received from outside organisations in one date order, filterable by visits and notes, diagnoses, medications and allergies, precautions, results, outside documents and referrals. |
| Patient Home with tabs | Available | The patient chart is split into Home (Rehab record and episodes of care, with one-press links to start a note), Clinical history (allergy verification, outside records, problems and medications), Documents, Timeline, and Registration & admin. Allergies and precautions stay above the tabs. |
| Episode page in views | Available | The episode page opens in six views: Overview, Notes, Evaluation, Goals & outcomes, Care team & billing, and History. Each shows only its own panels; allergies, precautions and the AI agreement status stay on every view. |
| Patient documents and colleague sign-off | Available | Each patient has a Documents tab listing everything filed to the chart by category, plus completed patient forms. Anyone in Rehab can ask a named colleague to sign a document off as reviewed; only that colleague can sign it off. A sign-off records who reviewed which document and when - it changes nothing in the document. |
| Recording outcome scores you obtained | Available with configuration | Enter the score from an instrument you administered outside ArkCloud, see the first and latest score side by side, and add score lines to a draft note. ArkCloud does not administer the instrument or compute the score.Requires: A clinical lead approves each instrument for your clinic, confirming the clinic holds any licence it needs. |
| Administering and scoring measures inside ArkCloud | Partially available | The framework for administering a measure inside ArkCloud and scoring it is built, but no measure has been published, so nothing can be administered or scored this way yet. |
| Today dashboard | Available | Today's visits, the episodes that need attention and what each is waiting on, your clinical work areas, and recent episodes. |
| Work queue | Available | Unsigned notes, notes awaiting co-signature, plans of care missing or due, progress reports due, missing discharge summaries, authorization problems and billing holds, shared across the team. |
| Home exercise programme builder | Available | Build a home programme inside the episode: filter your library by region, focus, difficulty, discipline, specialty, equipment, position and goal, star favourites, preview an exercise, add several at once, set every dose, and print what you gave the patient. Nothing reaches the patient until a licensed clinician, a supervisor or an administrator gives it to them. |
| Home programme templates | Available with configuration | Personal templates for each therapist and clinic templates for everyone. Pick a body area and templates filed there are ranked by what is documented, each with the reason; exercises that conflict with an active precaution are left out. Nine ArkCloud starter templates (knee, low back, shoulder, neck, balance, general mobility) are written by ArkCloud, carry no doses and have not been clinically reviewed.Requires: A licensed clinician at your clinic reviews and approves each clinic template before it is offered as clinic-approved. |
| Licensed exercise videos and templates | Not available | ArkCloud has no licence for any third-party exercise library. Exercises are ArkCloud's own written starter content or what your clinic writes; a demonstration video is a link your clinic chooses, never hosted or copied by ArkCloud. The library can record a licensed source once a licence exists. |
SOAP, body map and treatment activities
| Capability | Status | What that means here |
|---|---|---|
| Writing a note yourself | Available | Every note type opens as empty template sections that you type into. Nothing is prefilled, the note saves as you type, and you sign it when it is complete. |
| Quick Capture (structured visit entry) | Available | On a visit note: pain today, what the patient reports, interventions with their focus, treatment activities, AROM/PROM, MMT, tolerance and goal progress, chosen from lists. Nothing is pre-selected and nothing is carried forward from an earlier visit. |
| Build from your selections (no AI) | Available | Turns what you selected in Quick Capture into note sentences with fixed wording, with no AI involved. You insert each section yourself, and the note is not marked AI-assisted. |
| AI-assisted SOAP draft (visit notes) | Available with configuration | Proposes Subjective, Objective, Assessment and Plan text from what is recorded for the visit. The draft appears beside the note; you insert, edit or ignore each section, and signing an AI-assisted note asks you to confirm you reviewed it.Requires: Your organisation's AI switch turned on by an administrator and, where your clinic uses the patient AI agreement, the patient's signed yes to AI-assisted notes. Drafting itself is switched on for the hosted service. |
| Voice-assisted entry | Limited preview | Visit recording and spoken summaries on visit notes, and evaluation recording with proposed entries, are built but not released for routine use. A transcript or proposal never enters a note until you review it and insert or accept it.Requires: Released to an organisation only after clinical, legal and accuracy sign-off. |
| Reading measurements from typed notes | Available | Text such as "R shoulder AROM flexion 120" typed or pasted into the visit-notes box is offered as a proposed measurement for you to add. It reads text, not audio. |
| Structured pain and patient report (visit notes) | Available | Pain now on 0-10, where, which side, and better, unchanged or worse since the last visit; up to six short statements of what the patient reports; and a free-text change since the last visit. |
| Structured history fields (chief complaint, onset, pain best and worst, sleep, headaches) | In development | Separate fields for chief complaint, mechanism of onset, best and worst pain, sleep and headaches are being built. Today these are written in the note's free-text sections, or recorded through body-map items and guided questions where those exist. |
| Range of motion (AROM/PROM) and manual muscle testing | Available | Joint, motion, side, AROM or PROM and degrees; or joint, motion, side and an MMT grade from 0 to 5 with plus and minus grades. Each value is stored as a measurement and shown beside the earlier value when one exists. |
| Grip and pinch, edema and sensation readings | Available | Dynamometer grip and pinch in pounds or kilograms, edema by tape or volumeter, and sensation by monofilament or two-point discrimination, each with its side and the unit as read. |
| Mobility, transfers, gait and balance observations | Available with configuration | One activity at a time (for example sit to stand, walking on level or uneven surfaces, stairs, standing balance) with the assistance level, whether you observed it or the patient reported it, and activity-specific observations such as gait pattern or rail use.Requires: Saving body-map, guided-question and mobility entries is a deployment switch. It is on for the hosted ArkCloud service. |
| Body map and region pick-lists | Available with configuration | Choose a region on the body map or by typing its name, then tick what applies from that region's draft lists of conditions, symptoms, examination findings, functional limitations, history, treatment context and special tests. Save without confirming, or confirm.Requires: Saving body-map, guided-question and mobility entries is a deployment switch. It is on for the hosted ArkCloud service. |
| Guided questions by region | Available with configuration | Yes / No / Unsure questions for the region you opened plus general screening questions. Yes ticks the matching items; No and Unsure are kept as answers and tick nothing; a red-flag Yes shows a prompt to consider medical review and never blocks you.Requires: Saving body-map, guided-question and mobility entries is a deployment switch. It is on for the hosted ArkCloud service. |
| Special tests with results | Available with configuration | Named special tests for the region, each recorded as positive, negative or inconclusive. ArkCloud does not suggest which tests to perform and does not interpret a result.Requires: Saving body-map, guided-question and mobility entries is a deployment switch. It is on for the hosted ArkCloud service. |
| Outcome-measure suggestions from the recorded region | Available with configuration | Once a region has a saved finding on the episode, instruments your clinic has approved that match it are listed first, each with its reason. A fixed rule, not AI.Requires: A clinical lead approves each instrument for your clinic before it can be suggested or scored. |
| Region-specific ROM/MMT fields and note template | In development | Choosing a body region does not yet change the visit note's range-of-motion and strength fields or the note template. Linking the two is being built. |
| Confirmed findings into the note | Available | Body-map and mobility findings you have confirmed are shown as text first and then placed into the matching note section when you choose to add them. Selected-but-unconfirmed findings never reach a note. |
| What Assessment and Plan still need | Available | On a visit note, before any draft, ArkCloud lists what Assessment and Plan can rest on, what is missing (accepted goals, a plan of care, an earlier value, the patient's response, today's functional status) and today's measurements beside earlier values. Fixed rules, no AI. |
| Checks on AI-drafted text | Available | Every drafted sentence is checked against what was recorded. A number, side or assistance level that is not in the record is removed, negation and uncertainty must survive, and an Assessment with nothing recorded today is left blank. The checks catch invented facts, not clinical correctness. |
| Goals with baseline, target and date | Available | Goals belong to the episode: your wording, optionally measured against a range of motion or an MMT grade (joint, motion, side), with a baseline, target, target date and rationale. A goal is proposed, accepted by a clinician, and closed as met, partially met, not met or discontinued. |
| Short-term and long-term goal types | In development | Goals are not yet split into short-term and long-term. State the time frame in the goal's wording and target date. |
| Progress toward goals at each visit | Available | On a visit note you mark each accepted goal Progressing, No change, Regressed, Met or Not assessed today. It is your judgement; nothing is inferred. |
| Structured treatment plan and plan reviews | Available | One active plan per episode with interventions, visits per week, duration, discharge criteria, review date and physician certification details. Each review records the outcome, progress and changes to the plan. |
| AI deciding goals or the plan of care | Not available | AI does not write goals, plans of care or treatment decisions. The AI draft's Plan section only restates the plan you typed for the visit, your dictated summary or the active plan of care. |
| Interventions provided, with focus | Available | Choose what you did from the service families offered for the episode's discipline (all of them on a multidisciplinary episode), then what it focused on and an optional detail. The list is a draft vocabulary. |
| Treatment activities with dosage and response | Available | Up to 30 activities per visit, each with a name, category, sets, reps, resistance or load, minutes, assistance, modifications and the response observed today. They appear in the note's Objective lines. |
| Start from last visit and treatment history | Available | Offers the most recent earlier visit's activities as unticked rows; only rows you tick as done today are added, marked as started from a previous visit, with the response left blank. Treatment history lists earlier visits' activities, newest first. |
| Charges created from interventions or activities | Not available | Recording an intervention or activity never creates or changes a charge. The billable service comes from the service the visit was booked under, or one recorded by hand, and an administrator posts the charge. |
AI, voice and outcome measures
| Capability | Status | What that means here |
|---|---|---|
| AI-assisted SOAP drafting (visit notes) | Available with configuration | Switched on for this deployment. Drafts Subjective, Objective, Assessment and Plan text for a SOAP visit note from what is recorded; the clinician reviews, inserts, edits and signs.Requires: Your organisation's AI switch left on (Settings, AI). Where your clinic has added the patient AI agreement, the patient's signed yes to AI-assisted notes. |
| AI narrative drafts (progress report, discharge summary) | Available with configuration | Prepared when an editable progress report or discharge summary is opened: Progress toward goals and Reassessment findings, or Course of care and Goals met / outcomes. Shown beside the document; nothing is written in until you insert it.Requires: Your organisation's AI switch left on (Settings, AI). The patient AI agreement is not checked for these drafts. |
| Patient AI agreement | Available with configuration | An optional form the clinic adds and sends to patients. Once added, it is enforced for the AI SOAP draft and for visit and evaluation recording. It is not enforced for the progress report and discharge summary drafts or for dictating a summary.Requires: An administrator adds it under Forms (Patient AI agreement, Add the AI agreement). Until it is added, nothing is gated by it. |
| AI review attestation at signing | Available | Signing a note that contains inserted AI text, or for which an AI draft was delivered, requires the signer to attest that they reviewed every AI-drafted section and that the signed note is their own documentation. |
| Build from your selections (no AI) | Available | Arranges today's Quick Capture selections as note text without any AI. It is not marked AI-assisted and stays available when AI is off or the patient declined AI. |
| Notes written or signed without the clinician | Not available | AI never writes into a note by itself and never signs, submits or sends anything. A clinician inserts drafted text section by section and signs the note. |
| AI drafts for evaluations, re-evaluations, plans of care and goals | Available | Beside a note's fields, AI drafts the assessment, plan or goals section from what the clinician typed, confirmed findings and guided answers - no recording needed - and improves the wording of a written field without changing its numbers, sides, grades or negations. Suggest goals proposes goals from documented limitations and findings, and the plan of care can be drafted beside its problem statement, interventions and discharge criteria; a goal's target and date and the plan's frequency and duration are always the clinician's. For PT the assessment follows the note type - evaluation, visit, progress report or discharge - and an improvement, a goal status, tolerance, home-program independence, a prognosis or a need for skilled care is kept only when the cited record shows it. AI never drafts discharge status or recommendations, and nothing is saved until the clinician inserts and saves it. |
| Clinical Brain handoff summary | Available with configuration | A read-only 3 to 5 sentence handoff for a covering clinician. It never drafts, scores, interprets or recommends.Requires: Your organisation's AI switch left on, and an approved model on the deployment. |
| Explain this measure with AI | Not available | Explains only a published outcome measure. No measure is published, so there is nothing for it to explain today. It never explains a patient's score. |
| Patient message reply drafts | Available with configuration | A short draft reply in the reply box, labelled as an AI draft. You edit it and press Send; nothing is sent automatically.Requires: Your organisation's AI switch left on, and an approved model on the deployment. |
| Missed-visit outreach messages | Available with configuration | Rewrites one patient's rule-built reschedule message in a warmer tone. You copy it and send it through your usual channel.Requires: Your organisation's AI switch left on, and an approved model on the deployment. |
| Record this visit (visit notes) | Limited preview | Records the visit in the room and transcribes it in 15-second parts. Speech-to-text availability has been intermittent and accuracy has been tested on synthetic speech only, so do not plan clinic workflows around it yet.Requires: Voice switched on in your organisation's Voice settings, a role permitted to record encounter audio, an approved speech-to-text service on the deployment, and where your clinic uses the patient AI agreement, the patient's yes to audio recording. |
| Dictate a summary (visit notes) | Limited preview | The clinician dictates a short recap of the visit. The transcript becomes a source for the AI SOAP draft; it is not written into the note. Same speech-to-text limits as visit recording.Requires: The same as visit recording. The patient AI agreement is not checked when dictating a summary. |
| Record this evaluation, with proposed entries | Limited preview | On an initial evaluation, re-evaluation, progress report or discharge summary, a rule-based reader (no AI) proposes guided-screening answers, range of motion and strength values, and assistance levels from the transcript. Nothing is recorded until you accept or correct each one.Requires: The same as visit recording. Accepting screening answers and assistance levels also needs body-map saving, which is switched on for this deployment. |
| No audio kept; transcripts deleted on schedule | Available | Audio is held only while a part is transcribed and is never stored. Transcript text is encrypted and erased after your organisation's retention period (90 days unless changed), or at once when you discard it or the patient withdraws consent. |
| Voice on a plan of care | Not available | A plan of care has no Subjective/Objective/Assessment/Plan sections, so the microphone is shown disabled with that reason. |
| Voice filling structured fields by itself | Not available | Nothing heard is recorded automatically. Visit-note transcripts are text you review; evaluation recordings produce proposals that you accept, correct or reject one by one. |
| Speaker identification, translation and audio upload | Not available | The in-room transcript does not say who spoke, nothing is translated, and an audio file cannot be uploaded. Transcription happens only from the microphone during the session. |
| Choosing the outcome measures your clinic uses | Available with configuration | A clinical lead chooses instruments from a catalogue of 24, attesting that the clinic has checked the source and holds any licence. Until an instrument is chosen it is listed but cannot be scored.Requires: A supervisor or administrator, under Administration, Outcome measures your clinic uses. |
| Recording a score you obtained | Available with configuration | On the episode, a clinician enters the score obtained by administering the instrument outside ArkCloud. Each value is range-checked and dated; baseline and latest are shown with the arithmetic change.Requires: The instrument chosen by your clinic. Staff who only register patients cannot enter scores. |
| Administering a questionnaire in ArkCloud | Not available | ArkCloud does not show instrument items or forms, and patients cannot complete a measure in ArkCloud or the portal. |
| Automated scoring and interpretation | Not available | ArkCloud never computes a total from item responses, and applies no MCID, MDC or cut-off. Change is reported as arithmetic and the scale's better direction, never as improved or significant. |
| Governed measure registry | Partially available | The registry, licence records, evidence provenance and review workflow exist. No measure has been published through it, so nothing can be administered or scored there. |
| Outcome reporting across patients | Not available | Recorded scores appear on the episode, in a note when added, and as a source for the AI SOAP draft. They are not reported on Reports, Analytics or the dashboard counters, and the progress report and discharge summary drafts do not use them. |
Integrations
| Capability | Status | What that means here |
|---|---|---|
| Building and validating claim files (837P and 837I) | Available | ArkCloud builds each claim as a professional claim (837P), or an institutional claim (837I) when the billing facility is set up to bill on the UB-04, and checks it before it can be sent. |
| Sending claims to payers | Needs an external connection | Claims are built, not transmitted, until a clearinghouse mailbox is connected. On ArkCloud's hosted service no clearinghouse is connected today, so a submitted claim answers "Not sent" and stays Pending.Requires: A clearinghouse account with an SFTP mailbox, entered once for the deployment by ArkCloud, and your own enrollment with each payer. |
| Collecting acknowledgements and remittance (999, 277CA, 835) | Needs an external connection | Automatic collection of acknowledgements and electronic remittance (ERA) every 15 minutes needs the clearinghouse mailbox, which is not connected. Staff can upload an 835 or acknowledgement file on ERA/EOB Posting, or key a paper EOB, today.Requires: The clearinghouse mailbox, plus ERA enrollment with each payer through your clearinghouse. |
| Claim status inquiries (276/277) | Needs an external connection | Built: once a day ArkCloud asks the payer about claims still awaiting a decision 14 days after submission, and records the answer. It runs only through a connected clearinghouse mailbox, so no inquiry is sent on the hosted service today.Requires: The clearinghouse mailbox. |
| Member enrollment files (834) into coverage proposals | Partially available | Staff can upload an 834 benefit enrollment file today; each coverage change becomes a proposal that a person approves or rejects, and nothing changes a patient's coverage until it is approved. Receiving 834 files automatically needs the clearinghouse mailbox.Requires: The clearinghouse mailbox, for automatic receipt only. |
| Payer (provider) enrollment | Not available | ArkCloud does not enroll your practice or clinicians with payers, for claims, ERA or EFT, and does not track enrollment applications. Your practice does this with each payer and your clearinghouse. |
| Real-time eligibility checks (270/271) | Needs an external connection | Built: a check sent while you wait, with the payer's answer stored. It needs a real-time eligibility vendor account, which is not connected on the hosted service, so no check is answered today.Requires: Availity credentials, configured once for the deployment by ArkCloud. |
| Batch eligibility through the clearinghouse | Needs an external connection | Without a real-time connection, a check can be queued and sent as a batch 270 through the clearinghouse mailbox, with the payer's 271 recorded when it arrives, usually hours later. The mailbox is not connected on the hosted service.Requires: The clearinghouse mailbox. |
| Recording benefits a payer stated | Available | Front desk and billing staff record what the payer said by phone or portal - copay, coinsurance, deductible, out-of-pocket, network status, visit limit and the call reference - on the episode in Rehab or on the Benefits worklist in Access. It is labelled as recorded, never as a payer response. |
| Tracking prior authorizations | Available | Staff record each authorization by hand - payer, service, contacts and references, decision, approved dates and visits - and ArkCloud counts visits used against it as charges are posted. The billing-readiness checks read it. |
| Electronic prior authorization requests (278) | Not available | ArkCloud does not send authorization requests to payers. Your team submits by phone, fax, mail or the payer's portal and records the result. |
| Entering a referral by hand (including faxed referrals) | Available | Staff enter a referral from a fax, letter or phone call in Rehab or Access. Converting the referral creates the patient and the episode of care. ArkCloud does not receive faxes itself. |
| Electronic referrals from a referring EHR (FHIR) | Not independently verified | Built: referrals received over FHIR R4 from a referring organisation's system arrive on Rehab's Electronic referrals screen for a person to review, and status updates go back to the referrer. Each organisation sets up its own connection, and it has never been proven with a real referring partner.Requires: A referral-exchange connection your Rehab administrator sets up with the referring organisation. |
| Receiving or sending faxes | Not available | There is no fax line or fax service in ArkCloud. A faxed document is entered or uploaded by staff. |
| Recording a physician's plan-of-care certification | Available | The physician signs the plan of care outside ArkCloud. A clinician with signing authority, or a Rehab administrator, then records who certified it, their NPI, the date signed and the date the certification runs to; ArkCloud shows when it has expired. |
| Sending signed notes and plans to physicians | Needs an external connection | ArkCloud has the sharing workflow - verified recipients, a confirmation step, a purpose (for information, or asking the physician to certify a plan of care) and delivery tracking - but no Direct messaging or fax service is connected, so nothing is sent to a physician today.Requires: A Direct (HISP) or fax service, under a business associate agreement, connected to ArkCloud by us. |
| Direct secure messaging | Not available | ArkCloud has no Direct secure messaging address or connection. |
| Uploading outside records | Available | Staff upload a document or an exported record file, match it to the patient, and a licensed clinician reviews what it contains before anything reaches the chart. |
| Importing records from a hospital system (FHIR) | Not independently verified | Built: a read-only import from a hospital's FHIR R4 service into proposals a clinician reviews. Each hospital must register ArkCloud first; it has been tested only against ArkCloud's own test profiles and a public test server, never against an Epic or Oracle Health system.Requires: A connection your Rehab administrator sets up with each hospital. |
| Two-way EHR synchronisation (Epic, Oracle Health, MEDITECH) | Not available | ArkCloud does not synchronise with, or write back to, a hospital EHR, and has no MyChart integration. Every EHR sync operation is refused. |
| HL7 v2 interface (ADT, SIU, DFT feeds) | Not available | There is no HL7 interface: no listener, no inbound feed and nothing sent. A message library exists that an administrator can use to check or build a single message. |
| FHIR R4 view of your own data | Partially available | Signed-in users can read and search your organisation's own records as FHIR R4 resources and create a patient. Outside systems cannot use it, because it accepts only an ArkCloud sign-in, not SMART on FHIR or OAuth. |
| Email to patients | Available | Portal invitations, statements, receipts, reminders and notifications are emailed from ArkCloud's hosted service, from an authenticated arkcloudhealth.com address. |
| Text messages to patients | Partially available | Texts are sent from ArkCloud's hosted account, only to patients who have agreed to texts, and STOP replies are honoured. US carrier registration (A2P 10DLC) for the sending number is not yet complete, so texts to US phones may be filtered until it is. Calls are not available. |
| Card payments, saved cards and AutoPay | Needs an external connection | Built on Stripe, with each practice paid into its own Stripe account. Not switched on for the hosted service today: payments run in a non-charging mode and no Stripe keys are set, so no card can be charged. Payments received another way can still be recorded. No ACH.Requires: Stripe enabled for the deployment by ArkCloud, then your administrator connects your practice's Stripe account. |
| Amazon Connect softphone | Needs an external connection | Built: an embedded softphone that opens the caller's account. It needs an Amazon Connect instance and is not set up on the hosted service, so the Call Center menu does not appear.Requires: An Amazon Connect instance, configured for the deployment. |
| Sign in with Google | Available | Staff can sign in with a Google account. The same lockout and two-factor rules apply as for a password sign-in. |
| Microsoft or SAML single sign-on (Entra ID, Okta, OneLogin) | Not available | Not available. Microsoft sign-in is written but not switched on and has no sign-in button; SAML is refused until ArkCloud can verify SAML signatures. There is no SCIM user provisioning. |
| ArkCloud API (read-only, API keys) | Available with configuration | Built and switched off on the hosted service. When on, it is experimental and read-only: claims, appointments and the event list, using scoped keys your administrator creates.Requires: ArkCloud switches the API on for the deployment, then your administrator enables it and creates keys. |
| Outbound webhooks | Available with configuration | Built and switched off on the hosted service. When on, ArkCloud sends signed event notices (identifiers and statuses, not patient details or note text) to an HTTPS address your administrator registers and verifies, with retries and a delivery log. Never yet run against a customer's receiver.Requires: ArkCloud switches the API on for the deployment, then your administrator enables webhooks and verifies an endpoint. |
