Release notes

1 October 2026

The day the revenue cycle stopped working on a subset of claims, and the day the build was audited against its own claims.

Written for: Evaluators tracking what the platform does today · Existing customers · Anyone reviewing what changed and when

Claims depth, payments, and a 26-item audit

Claims

Claims carry more of what a payer requires: the provider identifier, a second diagnosis, the 2000C service line, and coordination of benefits between two payers.8afe3cf3
A pre-submission scrubber checks a claim before it leaves, rather than after a payer rejects it.8afe3cf3
Authorisation policy and submission rules are held per payer, so the rule that applies is the payer's own rather than a general one.fa8ae848
Manual charge entry checks the role of the person entering it, and carries exact decimal amounts rather than rounded ones.fa8ae848

An organisation can connect its own payment account, so that card payments - where card processing is enabled for that deployment - settle to the practice rather than to ArkCloud.483c6725
A policy for medical record numbers, new-patient requests, a mailbox for clearinghouse responses, and a payment ledger recording what was received against what was charged.483c6725

A 26-item audit of the revenue-cycle build, with the privacy safeguards corrected and a claim that arrives already wrapped caught rather than double-processed.6809b9d9

An accuracy pass over the product pages, the structured data search engines read, the sitemap and the redirect from the www hostname.256c598a