RESUMEN
BACKGROUND AND OBJECTIVE: Real-time data (RTD) are data that are delivered immediately after creation. The key feature of RTD is low delivery latency. Information systems in health care are extremely time-sensitive and their building block is the electronic health record (EHR). Real-time data from EHRs play an important role to support decision-making, analytics and coordination of care. This is well mentioned in the literature, but the process has not yet been described, providing reference implementations and testing. Real-time data delivery can technically be achieved using several methods. The objective of this work is to evaluate the performance of different transfer methods of RTD from EHRs by measuring delivery latency. METHODS: In our work we used four approaches to transfer RTD from EHRs: REST hooks, WebSocket notifications, reverse proxy and database triggers. We deployed a Fast Health Interoperability Resources (FHIR) server as it is one of the most widely used EHR standard. For the reference implementations we used Python and Golang. Delivery latency was selected as performance metric, derived by subtracting the timestamp of the EHR resource creation from the timestamp of the EHR resource receipt in millisecond. The data was analyzed using descriptive statistics, cumulative distribution function (CDF), Kruskal-Wallis and post-hoc tests. RESULTS: The database trigger approach had the best mean delivery latency 13.52±5.56 ms, followed by the reverse proxy 14.43±4.58 ms, REST hooks 19.26±5.76 ms and WebSocket 27.32±9.44 ms. The reverse proxy showed a tighter range of the values and lower variability. There were significant differences in the latencies between all pairs of approaches, except for reverse proxy and database trigger. CONCLUSION: Real-time data transfer is vital for the development of robust and innovative healthcare applications. Properties of current EHR systems as a data source predefine the approaches for transfer. In our work for the first time the performance of RTD transfer from the EHRs with reference implementations is measured and evaluated. We found that database triggers achieve lowest delivery latency. Reverse proxy performed slightly slower, but offered more stability, followed by REST hooks and WebSocket notifications.
