What is preserved in Rio Evo
The following elements of Rio are preserved in Rio Evo and will be migrated as part of the transition:
Entire database contents from Rio as you know it today.
Clinical record structure: care plans, assessments, progress notes, local configuration and correspondence formats.
Patient data: all patient demographic, clinical, and historical data held in Rio will persist in Rio Evo.
Care pathways: the pathway structures configured for your services will be replicated and can be further optimised in Rio Evo.
User accounts and role configurations: existing role-based access permissions are carried forward.
Reporting: existing reports and data extracts will be available in Rio Evo, with enhanced analytics available through the Evo platform.
What changes in Rio Evo
The following areas are meaningfully different in Rio Evo compared to current Rio:
Infrastructure: Rio Evo is cloud-native. This reduces IT overhead and improves resilience.
User interface: Rio Evo has a modern, role-based interface. Users see a workspace (Spaces) configured for their role, reducing the cognitive load of navigating a complex system.
Platform tools: Rio Evo users have access to Spaces (individual workspaces for each user), Feeds (real-time data integration), and SSO (single sign-on across platform products).
What a move to Rio Evo involves
Moving from Rio to Rio Evo is a managed process. Access Health provides:
A dedicated team working alongside your organisation's project and clinical leads.
Data validation and reconciliation at each stage.
Configuration of Rio Evo to reflect your current Rio setup before go-live.
Training for clinical, operational, and administrative staff.
A hypercare period post go-live with enhanced support.
Timelines are agreed on an organisation-by-organisation basis. Rio Evo is anticipated to be customer-ready in Autumn 2026, with Early Adopter Programme places available for organisations wishing to move early.
Further information
For further detail on what move involves for your specific organisation, contact your Customer Success Manager. A detailed planning article will be published in the Knowledge Base in the coming weeks.