Networking Aspects of the Electronic Health Records: Hypertext Transfer Protocol Version 2 (HTTP/2) vs HTTP/3.

The rapid development of the digital healthcare and the electronic health records (EHR) requires smooth networking infrastructure to access data using Hypertext Transfer Protocol (HTTP)-based applications. The new HTTP/3 standard should provide performance and security improvements over HTTP/2. The goal of our work was to test the performance of HTTP/2 and HTTP/3 in the context of the EHRs. We used 45,000 test FHIR Patient resources downloaded and uploaded using 20, 50, 100 and 200 resources per Bundle, which resulted in 2251, 901, 451 and 226 HTTP GET and POST requests respectively. The first test downloading 20 resources per Bundle showed that HTTP/3 outperformed HTTP/2 in the local (mean request time 16.57 ms ± 7.2 standard deviation [SD]) and in the remote network (71.45 ms ± 43.5 SD) which is almost 3 times faster. In the 50 and 100 resources per Bundle test the HTTP/3 protocol demonstrated again more than two times gain in downloading performance for remote requests with mean request time 91.13 ms ± 34.54 SD and 88.09 ms ± 21.66 SD respectively. Furthermore, HTTP/3 outperformed HTTP/2 in the constructed clinical dataset remote transfer. In the upload tests HTTP/3 showed only a slight gain in performance merely in the remote network. The HTTP/3 protocol is a relatively new development and a major improvement for the worldwide web. This new technology is still missing in the digital health and EHRs. Its use could offer a major performance gain in situations where data is gathered from multiple remote locations.