Skip to main content

Releases and updates for Access Rio Observations

How software updates are delivered to Access Rio Observations, including release notices, defect management, and mobile app compatibility.

Written by Connor Baeza

Access Rio Observations is a Software as a Service (SaaS) product, meaning all customers receive updates simultaneously. This article answers common questions about how updates are delivered, how defects are managed, and what to expect when a new release affects the mobile app.


How are software updates delivered?

All customers receive updates simultaneously, there is no option to run a different version of the software. Updates are delivered on a rolling basis:

  • Web and desktop updates are deployed continuously with feature switching to control availability.

  • Mobile (iOS and Android) updates follow a scheduled release cadence due to App Store submission and NHS Mobile Device Management (MDM) rollout requirements.


What notice will we receive ahead of a new release?

Release notes detailing new functionality, fixes, and any changes to existing features are issued ahead of each release. Customers are provided with a preview window to review changes and plan testing before a release goes live. For mobile app releases, additional lead time is provided to account for MDM rollout planning.


How are defects managed between releases?

Critical defects are patched and deployed as soon as possible. Smaller fixes are included in the next scheduled release. Release communications include a summary of defects raised, resolved, and any remaining open items with mitigations or workarounds where applicable.


What happens if a backend release is incompatible with an older version of the mobile app?

The mobile app and backend services are designed to run in lockstep. While older app versions may continue to function after certain releases, this cannot be guaranteed where significant backend changes are included. Customers will be notified in advance when a backend release requires a corresponding mobile app update, with guidance on managing the transition.

Did this answer your question?