Abstract：
BACKGROUND: Electronic health records (EHR) emerged as a digital record of the data that is generated in the healthcare.
OBJECTIVE: In this paper the transfer times of EHRs using the Hypertext Transfer Protocol and WebSocket in both local network and wide area network (WAN) are compared.
METHODS: A python web application to serve Fast Health Interoperability Resources (FHIR) records is created and the transfer times of the EHRs over both HTTP and WebSocket connection are measured. 45000 test Patient resources in 20, 50, 100 and 200 resources per Bundle transfers are used.
RESULTS: WebSocket showed much better transfer times of large amount of data. These were 18 s shorter in the local network and 342 s shorter in WAN for the 20 resource per Bundle transfer.
CONCLUSIONS: RESTful APIs are a convenient way to implement EHR servers; on the other hand, HTTP becomes a bottleneck when transferring large amount of data. WebSocket shows better transfer times and thus its superiority in such situations. The problem can be addressed by developing a new communication protocol or by using network tunneling to handle large data transfer of EHRs.
OBJECTIVE: In this paper the transfer times of EHRs using the Hypertext Transfer Protocol and WebSocket in both local network and wide area network (WAN) are compared.
METHODS: A python web application to serve Fast Health Interoperability Resources (FHIR) records is created and the transfer times of the EHRs over both HTTP and WebSocket connection are measured. 45000 test Patient resources in 20, 50, 100 and 200 resources per Bundle transfers are used.
RESULTS: WebSocket showed much better transfer times of large amount of data. These were 18 s shorter in the local network and 342 s shorter in WAN for the 20 resource per Bundle transfer.
CONCLUSIONS: RESTful APIs are a convenient way to implement EHR servers; on the other hand, HTTP becomes a bottleneck when transferring large amount of data. WebSocket shows better transfer times and thus its superiority in such situations. The problem can be addressed by developing a new communication protocol or by using network tunneling to handle large data transfer of EHRs.
摘要：
背景：电子健康记录（EHR）是在医疗保健中生成的数据的数字记录。
目的：本文比较了在局域网和广域网（WAN）中使用超文本传输协议和WebSocket的EHR传输时间。
方法：创建了一个PythonWeb应用程序，用于提供快速健康互操作性资源(FHIR)记录，并测量了EHR通过HTTP和WebSocket连接的传输时间。在每束传输20、50、100和200个资源中使用45000个测试患者资源。
结果：WebSocket显示了大量数据的更好传输时间。对于每个Bundle传输20个资源，本地网络中的时间缩短了18秒，WAN中的时间缩短了342秒。
结论：RESTfulAPI是实现EHR服务器的便捷方式；另一方面，HTTP成为传输大量数据时的瓶颈。WebSocket显示了更好的传输时间，因此在这种情况下具有优越性。可以通过开发新的通信协议或通过使用网络隧道来处理EHR的大型数据传输来解决该问题。
目的：本文比较了在局域网和广域网（WAN）中使用超文本传输协议和WebSocket的EHR传输时间。
方法：创建了一个PythonWeb应用程序，用于提供快速健康互操作性资源(FHIR)记录，并测量了EHR通过HTTP和WebSocket连接的传输时间。在每束传输20、50、100和200个资源中使用45000个测试患者资源。
结果：WebSocket显示了大量数据的更好传输时间。对于每个Bundle传输20个资源，本地网络中的时间缩短了18秒，WAN中的时间缩短了342秒。
结论：RESTfulAPI是实现EHR服务器的便捷方式；另一方面，HTTP成为传输大量数据时的瓶颈。WebSocket显示了更好的传输时间，因此在这种情况下具有优越性。可以通过开发新的通信协议或通过使用网络隧道来处理EHR的大型数据传输来解决该问题。
