Access Rio Observations uses Access Identity to manage user authentication and access. This article answers common questions about logging in, provisioning users, managing ward access, and using personal devices.
How do users log in to the application?
Users authenticate via Access Identity, which supports integration with Active Directory (AD) and can be configured for Single Sign On (SSO) using organisational credentials. Account setup requires the user to exist in the Rio EPR system, with their Evo web portal account linked to their Rio identity.
Is bulk user provisioning supported?
Yes. Bulk upload functionality is available for user onboarding via the web portal.
Can ward access be restricted within the application?
Currently, ward access in Access Rio Observations is inherited directly from the user's access settings in Rio EPR. The ability to restrict ward visibility independently within the application for example, to support phased ward by ward rollouts is on the product roadmap.
How are permissions for the Evo portal configuration area controlled?
The Evo portal has two access levels: User and Admin. Access is managed via Access Identity. Initially, a limited set of users will require access to the configuration areas of the desktop portal. Restriction of specific pages and sections within the desktop is on the roadmap for future releases.
Can staff use personal devices to record observations?
The application supports offline working by caching data securely on the device. The app is designed for use on Trust managed devices with MDM controls in place including jailbreak detection, theft protection, and remote data purge. Trusts should review their own device and data governance policies when considering personal device use.