Changelog

The in-app changelog now shows all recent entries

• The Changelog and Security Changelog pages were stopping several weeks short of the latest release notes.

The workspace panel no longer peeks above the bar when closed

• A sliver of the closed panel could show at the bottom of the screen at some browser zoom levels.

The Care Context patient rail can be collapsed

• The left patient rail collapses to a narrow strip and back, giving the reclaimed width to the record column.
• Name, age, sex and MRN stay readable while collapsed, and the state is remembered between patients and sessions.

The gender and age tiles show the shape of the distribution

• A proportional bar sits under the counts on the patients list, so the balance across groups is visible at a glance.
• Age reads as a single shade ramp from light to dark; every band's label and count remain on screen.

The patients list summary strip is more compact

• The strip fits six tiles across in two tight rows, leaving more of the work queue on screen.

Claims, Pre-Auth and Denials read as tables in Care Context

• Each tab now shows an identifier, date, status, amount and note in a compact table.
• Denials also show the reason and the appeal window, which was previously buried in body text.

The patients list summary carries the dashboard's revenue-cycle figures

• ABHA Linked, Total Claims, Total Billed, Pre-Auth Approval and Denial Rate now appear alongside patient counts.

Patient list status badge sizes to its label instead of filling the cell

Short messages in Ask Cally no longer read one letter per line

Ask Cally in the terminology tool now matches the rest of Cally

• A dark band behind each message had been removed elsewhere but remained in the terminology workspace.

Care Context records are real tabs, with Documents first

• Each record type opens as its own panel instead of one long scrolling page.
• The encounter card is more compact, so more of the record is visible without scrolling.

Small files no longer display as 0.00 MB

• File sizes now scale to the right unit, so a small document shows in KB rather than rounding to zero.

Preview shows the prompt template instead of an empty stage

Model Response shows the record's real prompt, or a clearly labelled template

• Re-entering a live pipeline previously showed no prompt data even though a response existed.

The pipeline stays on screen when a stage has no data

• A stage without data showed a bare line of text with no patient banner or step strip; the surrounding layout is now kept.

A claim records which pre-authorisation it was filed against

• Opening the claim result from a pre-authorisation record now goes to the right record.

Claim and pre-auth record pages no longer open blank

Patient context is resolved once per record and shared across the page

• A stage could report missing patient context while the patient banner beside it displayed that same patient correctly.

Reopening a submitted record now survives a page reload

• Reloading a reopened record previously lost it and reported that no files had been uploaded.

Every pipeline stage is visible on every journey

• A plain document upload previously hid the Prep, Pre-Auth Result, Claim Result and Payment Acknowledgement steps.

The loading step no longer hangs when recovering an encounter

Pipeline navigation no longer discards completed pre-authorisation work

• Certain navigation paths could reset the pipeline or fail to find the record.

Date of birth is required when registering a patient without ABHA

• Validated as a real calendar date, not in the future, on both the form and the server.

Newly registered patients now appear at the top of the list

• Registering from a later page or with a search active previously left the new patient out of view.

ABHA adoption now has its own dashboard figure

• An ABHA Linked tile shows the count and the share of patients.

Terminology lookups work on all environments

• SNOMED CT, LOINC and ICD searches returned an error where the terminology service was not configured.

Changing the terminology server now takes effect immediately

• A misconfigured terminology service degrades gracefully instead of failing the request outright.

A pre-submit check catches wrong claim codes before they are sent

• Diagnosis and procedure codes are validated against the applicable edition and confirmed to exist.
• Cally can run the same check on codes taken from uploaded documents.

Ask Cally is available inside the terminology workspace

• A Browse and Ask Cally toggle puts the same assistant beside the terminology browser.

Cally can look up, validate and translate clinical codes

• Six read-only terminology lookups covering search, concept detail, validation and translation.
• Codes and terms only — no patient data is sent, and a service error degrades to a plain answer.

The terminology server can be chosen per user, not just per deployment

• A user's choice overrides the organisation default, which in turn overrides the deployment setting.

Common Lab Codes for India are available in the terminology browser

• A curated Indian lab-code set sits alongside the existing terminologies.

Cally shows rotating healthcare facts while it is thinking

Care context linking now lives entirely in the patient cockpit

• The separate Care Context page has been retired; linking happens in place on the patient record.

Link a care context without leaving the patient cockpit

• New Encounter opens a temporary tab on the patient record instead of navigating away.

A terminology browser in the right-hand rail

• Search a terminology, open a concept, and see its detail without leaving the page.

Cally answers terminology questions with rich result cards

• Clinical term searches and drug information render as readable result rows rather than plain text.

Choose the encounter class when linking a care context

• An Encounter Class option lets staff record whether a visit was outpatient, inpatient or another class.

The product version is shown in the navbar and user menu

The dependency tab no longer displays vulnerability and update posture

• Severity badges and audit summaries were removed from the in-app view.

The dependency tab opens on the core technology stack

• Platform cards come first, with the full package inventory a click behind them.

Pulling health records works again

• Health information requests were being rejected because a key expiry value was sometimes missing.

Care Context cockpit — merged encounter card and a two-tab right panel

• The encounter header and information card are combined into one pinned card.
• Encounters can be cycled from the keyboard.

The dependency inventory is browsable in the product

• A third tab beside Product and Security changelogs lists dependencies per workspace.

ABDM records are a tab on the patient record, grouped by care context

• Requesting consent, checking status, pulling data and viewing records all happen on the chart instead of in a modal.

Request a patient's ABDM records from their chart

• The patient's ABHA is taken from their record, so there is no need to type it again.

Health information type classification now saves

• Documents were being classified correctly but the result was never stored.

Birth dates are no longer invented when building health records

• A placeholder date could reach a patient's ABDM health record when the real one was unknown.

User management endpoints work again

• Every user administration screen was failing because of an incorrect database reference.

Email OTP sign-in works, and permission changes apply across open tabs

Record discovery works for patients with many encounters

• Discovery from the patient's ABHA app could time out when a patient had a large number of visits.

New care context opens pre-filled with the selected patient

• No need to search again for the patient you were already viewing.

The patient list endpoint no longer fails on every request

Patients with a mobile number but no ABHA are now notified

• A notification is sent when records are linked for a patient who has no ABHA address.

Requested health records now arrive end to end

• Records requested from another provider were not completing because two transaction identifiers were being confused.

Link Care Context finds an existing patient and prefills every field

• ABHA number and address, name, gender and date of birth are filled from the matched patient.

Wellness and immunisation records display in the ABDM health app

Diagnostic report bundles conform to the national profile

• Reports that previously failed to display in the patient's health app now render correctly.

Observation-based record types now carry real clinical content

• Shared records previously arrived structurally valid but empty of findings.

Scan and Share documents display in the ABDM health app again

Chief complaints and observations are included in shared records

Pin patients to a watch list from anywhere you meet them

• Pin a patient from the Patients list, the Care Context view or the patient banner — all three stay in sync.
• The Workspace panel now lists your pinned patients with a live count; select one to open it.
• Claim numbers, pre-authorisation references and case identifiers can be copied with one click.

ABHA address verification now works

• Patients can be verified using their ABHA address, which previously failed.
• Verification now returns district, state and PIN code directly from ABDM.
• The choice of OTP system is offered for addresses as well as numbers.

An ABHA number can be verified with either OTP system

• Choose between the Aadhaar OTP and the ABHA-linked mobile OTP when verifying a 14-digit ABHA number.

Communication mobile verification fixed, and a mistyped number can be corrected

• Verifying a communication mobile number during ABHA creation now works.
• A wrongly typed number can be changed from the OTP screen instead of abandoning the process.
• Closing the wizard after the ABHA has been created no longer loses the record.

A custom ABHA address can now be set while creating an ABHA

• The final step of ABHA creation previously failed, leaving the new ABHA with only a default address.
• A rejected request now names the field at fault instead of showing a generic error.

Searching for an ABHA by mobile number works reliably

• The session could fail part-way through because the ABHA number was sent in the wrong format.

ABHA profile actions now show why a request was rejected

• Failures previously appeared as a generic error; the reason reported by ABDM is now shown.
• Applies to mobile and email updates, re-KYC, deactivation, reactivation and deletion.

Clearer Aadhaar validation and complete ABHA creation steps

• An invalid Aadhaar number is flagged immediately with a clear message instead of a generic error.
• New enrolments continue to communication-mobile verification and the ABHA address step instead of ending early.

Choose the right ABHA when a mobile number has more than one

• Searching by mobile now shows an account picker instead of silently using the first result.
• ABHA numbers in the picker are masked to the last four digits.

ABDM linking and consent responses aligned to the current specification

• Care context linking, consent and data-flow acknowledgements now match ABDM's February 2026 schema.

Adding an ABHA address to an existing patient has been withdrawn

• ABDM provides no way to change the preferred ABHA address on an existing account, so the option has been removed.
• A custom preferred address can still be chosen when a new ABHA is created.

Manage an ABHA profile from the Search flow as well as Verify

• Staff who reach a verified profile through Search can now update mobile or email, re-do KYC, and deactivate or delete the profile.

Care context linking no longer fails on the visit description

• Linking a care context to ABDM failed when the visit type was formatted in a way ABDM rejected.

Health records are shared in their full structured format

• Consultations, prescriptions, diagnostic reports, discharge summaries, immunisation and wellness records are now shared as structured records rather than falling back to a stored document.

Health Information Users can subscribe to be notified of new records

• A subscription notifies the Health Information User when a new care context is linked for a patient, or when new data becomes available on an existing one.

A patient's ABHA must be verified before a consent request

• The Health Information User workspace now requires ABHA verification before a consent request can be sent.
• ABHA identifiers are validated before being sent to ABDM.

Consent list shows the patient name and the latest status change

• The consent table adds a patient column and the time of the most recent status change.

Care context linking initiated by the hospital

• Linking tokens are now requested with the details ABDM requires and stored securely for outbound linking.
• Completion depends on ABDM delivering the linking callback.

Scan and Share now completes end to end

• Scanning a facility QR code and giving consent now issues a token and registers the patient's profile.

Aadhaar consent, mobile verification and address guidance during ABHA creation

• The complete ABDM Aadhaar consent declaration is shown and must be accepted before proceeding.
• A communication mobile that differs from the Aadhaar-linked number is now verified separately.
• ABHA address rules and suggestions are shown, with a clear message when an address is already taken.

More record types can be shared in structured form

• Immunisation and wellness records now have structured formats.
• A health information request without a date range now uses a bounded five-year window.

Health record transfers no longer fail part way

• Records requested through ABDM now load and transfer correctly.

Consent requests now reach the gateway correctly

• Consent requests were being rejected because of an incorrect facility identifier, a code used in place of a label, and an end date in the future.

Consent notifications are now saved reliably

• Incoming consent notifications failed to save and were discarded.

Added a Scan and Share link to the sidebar for quicker access

Manage an ABHA profile, and register a patient by scanning their ABHA card

• Update mobile or email, re-do KYC, and deactivate, reactivate or delete an ABHA.
• A new registration method reads an ABHA card QR code from the camera or an uploaded image.

ABDM consent can be read in eleven languages

• The full consent declaration must be accepted before Aadhaar details are entered.
• Available in English plus Hindi, Bengali, Marathi, Telugu, Tamil, Gujarati, Urdu, Kannada, Odia and Malayalam.
• The language and time of acceptance are recorded.

OTP resend limits are now configurable

• Settings gains a maximum number of OTP resends and a wait time between them.
• Applies to ABHA creation, verification and search flows.

Richer patient list, with safety flagging for similar names

• Six columns covering identity, ABHA, age and gender, contact, address and last visit.
• Patients with the same or similar names on a page are flagged, following NHS patient-safety guidance.
• A summary strip shows total patients, recent registrations, gender split and age bands.

Fixed re-registering a new patient with an ABHA from a previously deleted patient

Fixed re-registering with a mobile number from a previously deleted patient

Fixed an error that could prevent creating new patient records

Fixed the claim pipeline progress bar occasionally missing a step

Added full-screen and bottom-panel toggles, and a workspace navigation bar

• Hovering the collapsed sidebar now previews it without shifting page content.

Fixed the Learn More menu and updated user menu links

• The Learn More submenu now opens correctly, with links to About Us, Usage Policy, Privacy Policy, and Terms and Conditions.
• Refer Caladrius now opens the contact page in a new tab.

Left navigation improvements: sub-menu indicators and a Back to App shortcut

• Added AI Dashboard, AI Studio, and Caladrius CRM to the navigation as upcoming features.

Each claim pipeline step now shows its NHCX workflow ID for reference

Consistent next-step navigation on claim and pre-authorization result pages

• Claim Result and Pre-Authorization Result pages now use the same navigation control to move to the next step.
• The Payment Acknowledgement step now updates automatically once the payer's notice arrives.

Improved Payment Acknowledgement page layout and reference number labelling

• The Payment Acknowledgement step now shows the acknowledgement action and full payment details side by side.
• The payment reference number is now labelled correctly as UTR or Claim number depending on what the payer sent.

Payment acknowledgement is now a separate step from the claim result

• Payment acknowledgement now has its own step, separate from the claim decision.
• The step shows the full payment details sent by the payer, including amount, status, payer and recipient, and reconciliation information.

Payment notice acknowledgement status now shown on the Billing page

• Billing now shows an Acknowledged status for payment notices that have been acknowledged.
• Acknowledged claims are no longer shown as awaiting acknowledgement.

Fixed payment notices showing on the wrong claim

• A payment notice could previously appear on every claim linked to the same encounter, with an incorrect amount and reference number.
• Each claim now shows only its own payment notice.

Prep coverage step no longer auto-selects every procedure

• The coverage verification step now requires at least one procedure to be explicitly selected before continuing.

Fixed invisible selected text and improved the document upload step

• Selected text is now visible throughout the application.
• An upload progress indicator now appears while a document is uploading.
• Fixed a button in the required-documents prompt that became invisible on hover.

Fixed incorrect denial reason when a case had denied and accepted claims

• The denial worklist now correctly shows the denial reason instead of Unknown in this situation.

Resolved denials now remain visible on the Denials worklist

• Accepting a denial or partial settlement no longer removes the case from the worklist; it now shows a resolved status instead.

Fixed missing feedback when sending information to a payer

• Sending information with no message now shows a clear prompt instead of appearing to do nothing.
• Send Info and Reprocess results now show a confirmation message regardless of where you are on the page.

NHCX result page shows the transaction identifier and clearer denial guidance

• The NHCX transaction identifier is now shown instead of being left blank.
• Denial triage options are laid out as readable full-width rows.

NHCX result page now shows the actual denial reason instead of a generic message

• Pre-authorization and claim result pages now show the payer's denial reason and recommended next step, matching the Denials worklist.

Improved denial triage: reason codes and correct claim resubmission

• Reprocessing or cancelling a submission now lets the operator select a specific reason code.
• Correcting and resubmitting a denied claim now follows the correct resubmission process with the payer.

Denial codes now show plain-English reasons and recommended next steps

• The full set of denial codes now has a clear explanation and a recommended action, shown on the Denials worklist.

Denials and received payment notices now available from Billing and Denials pages

• The Denials page now includes a tab for reviewing and triaging denied or queried submissions.
• The Billing page now includes a list of received payment notices alongside amounts awaiting acknowledgement.

Improved compliance validation of submissions sent to payers

• Outbound pre-authorization and claim submissions are now validated more strictly against national health data exchange standards to reduce submission errors.

Fixed missing denial reason when the payer sent no denial code

• The Denials worklist now shows the payer's written reason when a formal denial code isn't provided, instead of leaving it blank.

Fixed denial resolution not being saved

• Accepting a denial or partial settlement now saves permanently, so the case doesn't reappear as denied after a refresh.

Pre-authorisation decisions are no longer left unattached

• A payer decision now attaches to its case even when the submission did not carry a case reference.
• Requesting a payer response no longer holds up the button while retries run.

Fixed the left navigation rail not collapsing consistently

• The navigation rail now reliably collapses when viewing a pipeline step, giving more space to the page.

Denial triage can send cancel, release and nullify as well as reprocess

• The full set of NHCX task actions is available, with reprocess remaining the recommended default.

Track the full lifecycle of a claim task

• Every task request and the payer's outcome appear as a timeline on the record.
• Pre-Auth and Claims lists show the latest task state, such as cancel requested or reprocess approved.

Prep steps can now be skipped for encounters that already completed them

• When prep information already exists for an encounter, operators can now skip directly to the care team step instead of re-entering it.

Fixed payer queries appearing on the wrong submission

• A payer query intended for a final claim could previously appear on its related pre-authorization, or vice versa.
• Each submission now correctly shows only its own queries.

Pipeline pages now use the full viewport width

• Pages in the pre-authorization and claim pipeline now automatically collapse the left navigation rail for more working space.

Consistent page layout across NHCX pages

• Prep and record pages now use the same column layout as the rest of the pipeline.

Fixed "File the final claim" failing from the record page

• Filing the final claim from a pre-authorization record page now works correctly instead of failing with a missing bundle error.

Certain actions are now locked while a cancellation is pending

• While a cancellation request is awaiting the payer's response, conflicting actions such as approving or filing a claim are locked, with an option to proceed anyway if needed.

Denied decisions no longer show a misleading pre-authorization reference

• When a request is denied, the result page now correctly labels the reference number as a claim number instead of implying an authorization was granted.

Fixed outdated payer queries appearing on new submissions

• A new pre-authorization or claim submission could previously show a payer query from an earlier, unrelated submission.
• Only queries that match the current submission are now shown.

Unified result page for pipeline and saved records

• Submitting a pre-authorization or claim now goes directly to its record page, used consistently whether viewed live or reopened later.

Result pages now fit the screen without extra scrolling

• Pre-authorization and claim result pages now scroll independently within the viewport, matching the layout used elsewhere in the pipeline.

Payer questions now display in the payer response panel

• The payer's question is now shown in the correct response panel on both pre-authorisation and claim screens, instead of alongside the request.
• Once a decision is reached, the query panel is automatically hidden.

Triggering a payer query now confirms when the query arrives

• The query path previously timed out reporting no response, even though the payer had already replied.

Rejected pre-authorisations no longer appear as approved

• A payer rejection was being read as a completed approval; rejections now display correctly and open denial triage.

Payer query panel no longer stops updating

• The panel showing a payer's query could get stuck displaying outdated information. It now continues to refresh so the latest query is always shown.

Payer queries are no longer missed when a submission was not linked to its case

• Incoming payer queries now attach to the right case, including for submissions made earlier.

Reopened submissions now show the original submitted information

• Reopening a previously submitted pre-authorisation or claim now correctly displays the information that was submitted, instead of showing it as unavailable.
• Supporting document details are also restored correctly when reopening a submission.

Reopened submissions now show the model response and payer decision

• Reopening a submitted pre-authorisation or claim now correctly displays the generated response and the payer's decision, instead of showing them as unavailable.

Reopen a submitted pre-authorisation or claim for edits and resubmission

• Clicking into a submitted record now reopens the full submission process with that record's information pre-filled, so any step can be reviewed.
• Nothing is locked — re-running a step or resubmitting creates a new submission, keeping the original record intact.

Viewing a submitted record now shows its full journey as steps

• Opening a pre-authorisation or claim record now shows the same step-by-step journey view used during submission, with the record positioned on its current step.

Pre-authorisation and claim result pages redesigned into two columns

• Results now show the submitted request on the left and the payer's response on the right, making it easier to compare what was sent with what was received.

Pre-authorisation and claim result pages now lead with the payer's decision

• The payer's decision now appears immediately below the submission confirmation, instead of further down the page.

Improved reliability of responses sent to payer queries

• Fixed a protocol compliance issue that could cause responses to payer queries to be rejected by the gateway.

Claims list now shows claims only, with clearer status wording

• The Claims page previously mixed in pre-authorisations and pre-determinations. It now shows final claims only; pre-authorisations remain on their own page.
• Approved final claims now display as "approved" consistently across the list and status views.

Claims list now updates to reflect the payer's decision

• Some claims kept showing as "submitted" in the list even after the payer approved or rejected them. The list now correctly reflects the payer's decision.

Claim result no longer mislabels the claim number as the pre-authorisation reference

• On final claims, the true pre-authorisation reference is now shown separately from the claim number, instead of the claim number appearing under the pre-authorisation reference.

Fixed an error that could prevent a final claim from being submitted

• Claims that carried a pre-authorisation reference could fail to save due to a data formatting issue. This has been fixed.

Claim result now confirms its link to the originating pre-authorisation

• The claim result now confirms when a submitted claim correctly references its pre-authorisation, and shows a clear warning if that reference is missing.

Result pages now show copyable submission identifiers

• Pre-authorisation and claim result pages now show the correlation ID and related reference numbers, each with a one-click copy option.

Pre-authorisation reference no longer blank on approval

• In some cases the payer did not return a pre-authorisation reference on approval, leaving it blank and blocking the related final claim. The app now finds an alternative reference so it is always shown.
• Also fixed a related issue where a missing claim number on submission meant the payer had nothing to return, and an error affecting care team information display.

Approved claims now show full adjudication detail

• Approved claims previously showed blank totals and item-level detail even though the payer had returned them. The full breakdown — per-procedure adjudication, amounts, and payment — is now shown.
• This also fixes the display for partially approved and denied claims.
• Payment acknowledgement now pre-fills from the payer's payment notice, so the operator just needs to confirm it.

Improved document type detection and required-document tracking

• Health information type detection during document processing has been corrected so classified documents display properly.
• The health information type selected during processing is now saved to the document.
• Uploaded documents that fulfil a payer's required-document request are now tracked reliably, including after a page refresh.

Added claim cancellation/reprocessing, search, and payment notice follow-up

• Providers can now cancel a submitted pre-authorisation or claim, or request reprocessing, directly from the result page.
• Added the ability to search submitted claims by claim number, date range, or policy/product number.
• Gateway errors and protocol error notifications are now surfaced directly in the app instead of only on the NHA portal, and a payment notice card was added showing amount, date, and reference with an acknowledge action.

Open any submission's result directly from the Claims or Pre-Auth list

• Clicking a row on the Claims or Pre-Auth list now opens its result page directly — decision, identifiers, payer queries, and next steps — without needing to replay the submission.

Respond to payer queries with supporting documents, end-to-end

• The app now shows the payer's actual questions on a pending pre-authorisation or claim, including which documents they're asking for.
• Providers can respond by attaching the requested documents and/or a note, directly from the result page.

Added an experimental NHCX Search tool in Settings

• Operators can search submitted claims by entity type and filters, or submit a custom search request, and view the payer's response as it arrives.

NHCX Status Check now includes an action selector

• The Settings status check tool now requires selecting the type of submission being checked (coverage eligibility, pre-authorisation, claim, communication, or payment notice), matching the official NHCX portal.

A generative view for the Model Response step

• The Model Response step offers a generative layout alongside the classic view, with the classic view remaining the default.
• The layout is composed from a fixed set of approved components, and the claim is never re-fetched to build it.

Patient banner now shows consistently on result pages

• The patient information banner is now shown on the pre-authorisation, claim, and payment result pages, matching the rest of the submission journey.

Added NHCX status check in Settings

• Operators can now enter a correlation ID to check the status of a pre-authorisation or claim directly from Settings, and view the payer's response as it arrives.

NHCX participant directory in Settings

• Browse payers, providers and third-party administrators by role, with search.
• Codes, endpoints and certificate details can be copied directly from the table.

Upload readiness now reflects the payer's specific document requirements

• The upload screen now shows exactly which documents the payer requires for a claim, with the ability to upload and link each one directly against its requirement.
• Attempting to continue with required documents missing now shows the same detailed checklist, with an option to proceed anyway.

Full claim details now shown on pre-authorisation and claim result pages

• Diagnosis, procedures, priced line items, insurance, care team and supporting documents are now shown alongside the payer's decision.
• Practitioner, insurer, provider and facility names are now shown instead of reference codes, along with supporting document titles.

Detailed authorisation requirements now shown for each procedure

• For every selected procedure, you can now see whether authorisation is required and the allowed, used, remaining, copay and deductible amounts.
• A "Valid from" date was added alongside "Valid until" in the coverage details.

Plan name and sum insured now shown from the coverage eligibility check

• The coverage summary now shows the plan name and sum insured amount.
• Coverage details are now sourced from the insurer's response rather than only the initial request.

Multiple pre-authorisations and claims can now be filed per visit

• Previously, a second pre-authorisation or claim for the same visit was blocked. This restriction has been removed.

Fixed claims showing placeholder data instead of real patient and policy details

• Submissions now correctly carry the selected patient's actual policy and coverage information.

Fixed pre-authorisation requests being silently converted to claims

• A pre-authorisation request now always stays a pre-authorisation unless a claim is explicitly chosen.

Fixed status checks for claims and pre-authorisations not reaching the insurer

• Status queries are now correctly addressed to the insurer holding the decision.

Fixed claims and pre-authorisations not receiving an insurer decision

• Submissions are now sent in the complete format insurers require in order to review and respond.

Fixed resubmitting a claim or pre-authorisation failing with a duplicate error

Incoming payer callbacks are now recorded completely in the audit trail

• Some inbound callbacks were not being written to the transaction record.

Fixed hard-to-read text colour in the AI prompt editor

Restored automatic document type detection during upload

• The suggested document type now appears again after a document is scanned, without overriding manual selections.

Fixed formatting issues in the changelog view

• Entries with multiple points now display as a single, readable item instead of literal formatting symbols.

AI-generated claim response no longer lost when navigating away

• The response, validation result and selected model are now saved and restored when you return to the step.

Fixed the preparation step disappearing from the claim timeline

Added ability to actively check for pre-authorisation and claim decisions

• If the insurer does not automatically send a decision, you can now request a status update.

Added a Submit Claim action on the pre-authorisation list

• Approved pre-authorisations can now be submitted as a claim directly from the list.

Added a Payments tab on the Billing page

• Shows accepted claims that are awaiting payment acknowledgement.

Simplified the Denials page

• The Appeals and worklist tabs were removed; core denial management remains.

Practitioner and facility registry details now shown for claims

• The verified practitioner registry ID now pre-fills automatically, and facility registry details are now displayed.

Improved the pre-authorisation and claim decision view

• Added copy and download actions and a visible validity window for the authorisation reference.
• Added a per-procedure breakdown of the insurer's decision, including approved amounts.

Payment details shown on the payment acknowledgement step

• The step shows the amount, payment date, reference and the matched claim, and pre-fills the acknowledgement.

File a final claim directly from an approved pre-authorisation

• The approved pre-authorisation reference and validity period are carried over automatically.

Redesigned the claim preparation flow layout

• A guided step-by-step layout now shows results alongside each step.

Link related visits to a claim

• An optional control on the preparation step lists the patient's other visits by date, type and status so they can be linked.

Benefit selections are now saved so they are not lost after a refresh

Policy period, sum insured and wallet balance now captured automatically

Payment notices are now automatically received and linked to the matching claim

Added ability to record admission source for a visit

Added a plain-English coverage summary

• Shows plan details, total benefits, sum insured or wallet balance, and whether the policy is active.

Added in-app notifications when a payer decision arrives

• Emergency status is now preserved after a page refresh.
• The claim status indicator on the patient page can now be clicked to resume the journey.

Denial worklist on the Denial Management page

• Lists cases in a denied or queried state with their reason and last update, and opens denial triage for each.

Added a Check status option to look up payer decisions on submitted claims

• While a claim or pre-authorisation is pending, you can check whether the insurer has responded.

Added a pre-submission check to catch issues before filing a claim or pre-authorisation

• Blocks submission when a pre-authorisation reference is missing on a claim, or a care team member's practitioner ID is not verified.
• Warns, without blocking, when fewer supporting documents are attached than expected or eligibility checks were not run.
• For emergency admissions, these checks become dismissable warnings so treatment can proceed first.

Added an emergency admission (treat-first) option when preparing a claim

• Marking an admission as an emergency skips the pre-authorisation step and files directly as a claim.
• Shows a treat-first notice throughout the process.

The full payer response is shown on the claim result

• Eligibility, insurance plan and decision responses are rendered in full rather than summarised.
• Includes the parties involved and per-benefit detail such as required documents and approval flags.

Improved date handling in claim generation to prevent formatting errors

• Dates are now consistently converted to a standard format before submission.

Fixed an empty payer decision screen shown before the insurer responded

• The result page now stays in the awaiting state, with status-check controls visible, until a decision actually arrives.

Fixed the benefits check step getting stuck on Awaiting callback

• The step now completes using the plan's published requirements if the insurer doesn't respond within a short wait, so you can continue.

Fixed a save error caused by day-first date formats in generated claims

• Dates such as 30-10-2024 are now correctly converted rather than misread, preventing claim submissions from failing to save.

Fixed the result page failing to track a submitted claim's decision status

• Status checks and updates now work correctly after a claim or pre-authorisation is submitted.

Fixed filing the final claim returning a Route not found error

Fixed a false warning that auth-requirements had not been completed before submission

Fixed the pre-submission check blocking claims that already had a verified care team

Fixed the care team step getting stuck on Loading

• Also fixed an error that prevented encounter and claim status details from loading correctly.

Fixed pre-authorisation and claim result screens not checking for the payer's decision

Fixed the coverage page going blank while waiting for the insurer's response

Fixed the benefits check step not receiving a response from the insurer

Repeated claim preparation no longer creates duplicate cases

• Entering preparation more than once for a visit could create separate cases, so a payer response sometimes appeared on the wrong one.

Fixed claim requests being routed to the wrong insurer

• Requests now use the correct insurer code so responses are received instead of going unanswered.

Claim details now show the insurer's latest response

• Progress steps now adapt depending on whether it's a claim or a pre-authorisation.
• You can specify whether a pre-authorisation is new or an enhancement to an existing one.

NHCX claims are now part of the unified document and claims workflow

• Prepare, submit, and track pre-authorisations and claims in one continuous flow, with guided next steps for denials.
• Each claim can only be filed once.

The care team step now prefills practitioner details from the encounter

Fixed a blank page in the deployed application

• A packaging problem could stop the application loading after deployment.

Fixed the sidebar and other areas sometimes showing the wrong user role

Fixed new users with a pending role being sent to the wrong page after login

Search by ABHA address now verifies directly with ABDM

• The ABHA address tab verifies with ABDM instead of searching local records, and shares the same result view as the mobile tab.

Search results now show mobile number, district, state and PIN code

• Details come from ABDM where available, falling back to the patient's existing record.

Claim denial reasons are now categorized to help guide the appropriate next step

Cally understands more of the application, with safeguards

• Cally can work across the dashboard, claims, pre-authorisation, denials and billing pages.
• Actions respect the signed-in user's permissions, ask for confirmation before acting, and keep patient identifiers out of responses.

Cally can create and search patients

• Create a patient, search patients, or open registration from the chat; the patient list refreshes automatically.
• Patient identifiers are masked in anything the assistant returns.

Uploaded documents are checked before they are stored

• A validation step confirms an upload is a healthcare document, and explains in the chat when one is rejected.

Corrected request type sent for claim and pre-authorisation submissions

• Submissions to the insurer network now correctly identify whether the request is a claim or a pre-authorisation.
• Submissions are now linked to the facility and the corresponding case record.

Dark mode toggle now works across most of the app

• Charts and a few visual elements still use the light theme and will be updated in a future release.

Check whether an ABHA address is available, with alternative suggestions

Added a button to view and download your ABHA card after ABHA creation

Clearer messages when a request fails

• Timeouts, rate limits and server errors now show a readable explanation instead of a technical code.

Added an explainer describing the benefits of ABHA

Choose which name to keep when a patient's name differs from their ABHA

• A side-by-side comparison offers keeping the current name or using the name held against the ABHA.

Improved matching of existing patient records during ABHA linking to reduce duplicates

A matching mobile number now merges ABHA details onto the existing patient

• Names are no longer overwritten automatically — the difference is raised for staff to decide.

Improved patient matching accuracy when linking care context records, even with minor name differences

ABHA number search now works with or without dashes

Patient discovery tolerates small differences in name spelling

Added Hindi language support with a language switcher

Added font size controls for improved accessibility

Improved layout on small mobile screens

Improved color contrast for better accessibility

• Some secondary and accent colors are still being updated to meet full accessibility standards.

Recorded consent is required before any ABHA flow

• A consent dialog carrying the Aadhaar Act declaration must be accepted, unchecked by default, with the time of acceptance recorded.

Added a limit of 3 attempts for OTP entry, with lockout messaging

OTP screens handle expiry clearly

• When the timer runs out the code field is disabled and a resend option appears.

Aadhaar numbers are now masked on screen, with an option to reveal them

OTP entry is masked, with a show and hide toggle

Going back during ABHA creation now clears previously entered OTP and identity details

Initial ABDM readiness baseline

• Patient search, ABHA creation via Aadhaar OTP, ABHA login, care context linking, health record upload and the insurance claim flow.