Access Rio Observations integrates directly with the Rio Electronic Patient Record (EPR) system to synchronise patient data and write completed observations back into the clinical record. This article answers common questions about how that integration works.
How does Access Rio Observations integrate with Rio?
The application integrates with the Rio EPR system to synchronise patient demographic data, ward and bed information, and to write completed observations back into the Rio clinical record. Integration is currently managed via the Legacy Adapter, with a migration to a REST Application Programming Interface (API) planned as part of the product roadmap.
How are sync issues handled for example, duplicate or failed writes?
Duplicate observations: Observations with the same timestamp for the same patient are rejected.
Partial writes: Database transactions reduce the risk of partial writes. An Azure Service Bus queues sync events to Rio, ensuring delivery and identification of failed writes.
Corrupted payloads: Strict validation rules reject invalid or corrupted data.
Replay attacks: Duplicate API requests are identified and blocked.
Can users access the application when there is no network connection?
Yes. The mobile application supports offline working. Observations can be recorded without a live network connection and are synchronised to the server when connectivity is restored.
What is the minimum Rio version required to use Access Rio Observations?
The minimum supported Rio version is 24.01. Organisations on later versions are fully supported. If your Rio system is hosted by Access Group, this is the preferred and recommended configuration.