Medical digital service system and time synchronization method thereof

Abstract

The present application relates to a medical digital service system and a time synchronization method thereof. The medical digital service system includes at least one server, in which a private NTP service and a backend service are deployed. The private NTP service provides a time synchronization service using the local system time of the server where it is located as the time source. The backend service is capable of receiving and processing data generated and uploaded in real time from one or more medical devices; wherein the timestamp of the data is provided by the backend service, and the time based on the timestamp is the time directly provided by the private NTP service, or the local system time of the server where the backend service is located synchronized by the private NTP service. The time synchronization method includes providing a private NTP service and receiving and processing data generated and uploaded in real time from one or more medical devices by the backend service in the backend server, and providing a timestamp for the data.

Description

Technical Field

[0001] The present application relates to the field of medical equipment, and more specifically, to a medical digital service system and a time synchronization method thereof. Background Art

[0002] In the medical digital service system, front-end medical equipment, such as ventilators, anesthesia machines, ECG monitors, infusion pumps, injection pumps, etc., will send their operating data and detection data to the back-end server for processing.

[0003] For data sent from a medical device to a backend server, the original formation time of the data is an important information. The existing conventional processing method is for the medical device to add a timestamp to the data to be sent so that the backend server can identify the time information of the data.

[0004] The timestamps added by medical devices to data are usually based on the system time of the device itself. However, the system time of a medical device will accumulate errors over time, gradually deviating from the real time (such as the global standard time). The system time of the backend server where the backend service is deployed also has the same problem. This will cause the timestamps of the data sent by the medical device to the backend server to deviate or be out of sync with the system time of the backend server.

[0005] Some medical devices allow manual adjustment or setting of their system time so that they can be synchronized with the real time as much as possible, but the accuracy of this adjustment is poor. The back-end server and some medical devices can connect to the Internet and synchronize and calibrate the local system time through some public NTP (Network Time Protocol) services, but this is limited by the network environment. In the case of unstable Internet connection or no Internet, it is impossible to effectively synchronize and calibrate the local system time through the public NTP service, so the asynchrony between the system time of the medical device and the back-end server cannot be avoided. This asynchrony sometimes has serious consequences in the medical environment, because inconsistent timestamps of medical device data may affect diagnosis results and treatment processes.

[0006] In summary, the above describes the problem of time asynchrony between medical devices and backend servers in the prior art.

[0007] In addition, the inventors of the present application have found that if a variety of medical devices with different functional types can be connected to medical digital services for collaborative processing at the same time, there will be some additional effective effects. For example, for a ventilator and a monitor, for the same patient, the meanings represented by the waveform data generated by them at the same moment may have a certain correlation, and this correlation is helpful for the doctor's diagnosis and treatment work or the researcher's research work. For this correlation, compared with the time asynchrony problem between the medical device and the back-end server mentioned above, the relative time deviation or asynchrony between the timestamps of the data of different types of medical devices will be a greater obstacle to the discovery of this correlation. In other words, in the aforementioned situation, only when the relative deviation of the timestamps of the data of the ventilator and the monitor is very small can the doctor or researcher effectively discover and judge this correlation.

[0008] However, the existing medical digital service system usually connects a single medical device to the medical digital service, and does not support multiple different types of medical devices to be connected to the medical digital service for collaborative processing at the same time, and thus does not propose how to solve the time synchronization problem between the data sent by multiple medical devices to the back-end server. Moreover, due to the different clock accuracies in different medical devices, the degree to which their respective system time deviates from the real time will also be different, which makes the time synchronization of data from different medical devices a difficult problem to solve. Summary of the invention

[0009] The purpose of this application is to at least partially solve or alleviate the technical problems existing in the prior art mentioned above.

[0010] According to one aspect of the present application, a medical digital service system is provided, including at least one server, wherein the at least one server is deployed with:

[0011] A private NTP service, wherein the private NTP service uses the local system time of the server where the private NTP service is located as a time source to provide a time synchronization service; and

[0012] A backend service, wherein the backend service is capable of receiving and processing data generated and uploaded in real time from one or more medical devices; wherein the timestamp of the data is provided by the backend service, and the time based on the timestamp is the time directly provided by the private NTP service, or the local system time of the server where the backend service is located synchronized by the private NTP service.

[0013] Optionally, the server where the private NTP service is located is connected to an external public NTP service, and the public NTP service can provide time synchronization services for the global standard time; wherein, when the public NTP service is available, the server where the private NTP service is located uses the public NTP service to synchronize its local system time with the global standard time.

[0014] Optionally, the medical digital service system also includes the one or more medical devices; wherein, at least one of the one or more medical devices is connected to the private NTP service to synchronize the local system time of the at least one medical device with the time source of the private NTP service.

[0015] Optionally, the private NTP service and the backend service are deployed in the same server; or, the private NTP service and the backend service are deployed in different servers.

[0016] Optionally, the one or more medical devices include a plurality of medical devices, and the plurality of medical devices are of at least two different functional types.

[0017] According to another aspect of the present application, a time synchronization method for a medical digital service system is provided, comprising:

[0018] Provide a private NTP service, wherein the private NTP service uses the local system time of the server where the private NTP service is located as the time source to provide a time synchronization service;

[0019] The backend service in the backend server receives and processes data generated and uploaded in real time from one or more medical devices, and provides a timestamp for the data; wherein the time on which the timestamp is based is the time provided by the private NTP service, or the local system time of the backend server synchronized by the private NTP service.

[0020] Optionally, the time synchronization method further includes: when a public NTP service is available, using the public NTP service to synchronize the local system time of the server where the private NTP service is located with the global standard time.

[0021] Optionally, the time synchronization method further includes: utilizing the private NTP service to synchronize a local system time of at least one of the one or more medical devices with the time source of the private NTP service.

[0022] Optionally, the private NTP service is deployed in the backend server; or, the private NTP service is deployed in another server different from the backend server.

[0023] Optionally, the one or more medical devices include a plurality of medical devices, and the plurality of medical devices are of at least two different functional types. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Figure 1 It is a schematic diagram of the composition of the first embodiment of the medical digital service system according to the present application;

[0025] Figure 2 is a schematic diagram of the composition of the second embodiment of the medical digital service system according to the present application;

[0026] Figure 3 is a schematic diagram of the composition of the third embodiment of the medical digital service system according to the present application;

[0027] Figure 4 It is a schematic diagram of the composition of the first embodiment of the distributed medical digital service system according to the present application;

[0028] Figure 5 is a schematic diagram of the composition of the second embodiment of the distributed medical digital service system according to the present application;

[0029] Figure 6 is a schematic diagram of the composition of the third embodiment of the distributed medical digital service system according to the present application; and

[0030] Figure 7 It is a schematic diagram of the composition of the fourth embodiment of the distributed medical digital service system according to the present application. DETAILED DESCRIPTION

[0031] The technical solution of the present application is described in detail below with reference to the accompanying drawings and specific implementation methods.

[0032] Figure 1-Figure 3 Various embodiments of the medical digital service system according to the present application are shown, and the same figure numbers in different drawings represent the same components or parts.

[0033] like Figure 1 The medical digital service system 101 of the first embodiment shown may include a time server 110 and a backend server 120. A private NTP service 111 may be deployed in the time server 110. The private NTP service 111 may provide a time synchronization service using the local system time 112 of the time server 110 as a time source. That is, when other devices request time synchronization from the private NTP service 111 of the time server 110, the private NTP service 111 will synchronize the local system time 112 to the device that issued the synchronization request.

[0034] The public NTP service 130 in the Internet is well known to people, and it can generally provide a time synchronization service of the global standard time. When the time server 110 is connected to the Internet, the time server 110 can be connected to the public NTP service 130 outside the system, and can send a time synchronization request to the public NTP service 130 outside the system to synchronize the local system time 112 to the global standard time provided by the public NTP service 130.

[0035] The backend server 120 can receive data uploaded by each medical device from the device end 140. The device end 140 may include various medical devices connected to the medical digital service system 101, such as Figure 1 Medical equipment of different functional types, such as ventilators, anesthesia machines, monitors, pumps, blood gas and biochemical analyzers, and warming blankets, are exemplified and schematically represented in the figure.

[0036] The backend server 120 may be deployed with a predetermined backend service 121 to perform the required processing on the data received from the device end 140. The backend service 121 may include, but is not limited to, one or more of data storage, management and analysis services, telemedicine services, intelligent diagnosis services, health management services, etc. In particular, the backend service 121 may also provide a timestamp for the data generated in real time in the medical device in the device end 140 and uploaded to the backend server 120 in real time. Hereinafter, the data generated in real time in the medical device and uploaded to the backend server 120 in real time is referred to as "real-time data".

[0037] It should be understood that the "backend service" in this application is only a general term for the services that the backend server 120 can provide, and the service of providing a timestamp for the real-time data from the medical device described above is a part of the backend service. Of course, the timestamp service can also be named separately, but this does not affect the essence of the various technical solutions in this application. It should also be understood that regardless of whether the real-time data of each medical device from the device end 140 itself carries the timestamp of the medical device itself, in the backend server 120, the timestamp of the real-time data is provided by the backend service 121. In other words, if the real-time data from the medical device itself does not carry a timestamp, the backend service 121 adds a timestamp to the data; even if the real-time data from the medical device itself already carries a timestamp that has been formed at the medical device, then in the backend server 120, the timestamp of the real-time data will be replaced or updated by the backend service 121 to the timestamp provided by the backend service 121, or an additional timestamp will be added for use in the backend service 121.

[0038] The inventor of the present application has found that the backend service 121 uniformly provides timestamps to the real-time data from the device end 140, which can greatly improve the timestamp accuracy between the real-time data from different medical devices. It can be imagined that if the real-time data of different medical devices use the timestamps formed locally in the medical device and are uploaded to the backend service 121, the deviation between the timestamps may be caused by two reasons. The first reason is the network transmission delay from the medical device to the backend service, and the second reason is the deviation of the local system time between the medical devices. The inventor of the present application has found that the network transmission delay of the first reason is negligible, because in the same intranet environment, the network transmission delay of various types of medical devices is basically the same. The second reason, that is, the deviation of the system time between medical devices is the main reason. In this way, in the system 101 of the present application, since the real-time data from each medical device in the device end 140 uniformly uses the timestamp provided by the backend service 121, and does not rely on the local system time of each medical device itself, even if there is a time asynchronism or deviation between the local system times of each medical device, it can ensure that these real-time data are kept in time synchronization or timestamp synchronization in the backend service 121 of the backend server 120. In other words, this approach avoids the problem of asynchrony of timestamps of real-time data uploaded to the backend server 120 due to asynchrony between the times of the medical devices on the device side 140 .

[0039] exist Figure 1 In the medical digital service system 101 shown, the timestamp provided by the backend service 121 may be based on the local system time 122 of the backend server 120 where it is located. That is to say, the content of the timestamp provided by the backend service 121 to the real-time data received from the device end 140 is the local system time 122 when it receives the real-time data. The backend server 120 may send a time synchronization request to the private NTP service 111 of the time server 110 according to a preset frequency or method to synchronize the local system time 122 of the backend server 120 with the time source of the private NTP service 111. As described above, the time source of the private NTP service 111 may be the local system time 112 of the time server 110 where the private NTP service 111 is located.

[0040] The above describes the processing method for the timestamp of the real-time data sent by the device end 140 to the back-end server 120. It should be understood that in some application scenarios, the data of a part of the medical devices in the device end 140 may not be formed in real time or may not be uploaded to the back-end server 120 in real time after being formed. For such non-real-time data, a different processing method from that of real-time data can be adopted, for example, after it is uploaded to the back-end server, the original timestamp provided by the medical device itself is still used instead of the timestamp provided by the back-end service 121. It is easy for those skilled in the art to distinguish and process real-time data and non-real-time data differently. However, for non-real-time data, such a demand is generated accordingly, that is, the local system time of each medical device in the device end 140 is also kept basically synchronized with the time of the back-end service 121 of the back-end service 120 as much as possible, so that the basic time synchronization can still be guaranteed between the data after it is uploaded to the back-end server 120, although this synchronization does not need to achieve the same high synchronization accuracy as real-time data. In addition, for medical devices, whether it is real-time data or non-real-time data, in addition to being uploaded to the back-end service 121 for processing, these data may also need to be processed locally on the medical device, such as displaying or printing, etc. This also hopes that the local system time of the medical device itself is as accurate as possible, and that the time between medical devices and between medical devices and back-end services is basically synchronized.

[0041] For this reason, Figure 1 As shown, the medical device in the device end 140 can be connected to the private NTP service 111 of the time server 110 to synchronize the local system time of the medical device with the time source of the private NTP service 111. The term "connection" used here refers to the connection of the data and / or instruction transmission path. As mentioned above, the time source of the private NTP service 111 can be the local system time 112 of the time server 110 where the private NTP service 111 is located. It should be understood that not all medical devices in the device end 140 must use the private NTP service for time synchronization, and some or all medical devices that can and need to perform the time synchronization can be selected to perform the time synchronization operation.

[0042] So, for Figure 1In the medical digital service system 101 shown, since each medical device on the device side 140 and the backend server 120 can use the private NTP service 111 to synchronize time, it is possible to achieve basic time synchronization between each medical device on the device side 140 and the backend service 121 of the backend server 120. Further, as mentioned above, the time server 110 can also synchronize the time source of the private NTP service 111 (i.e., the local system time 112 of the time server 110 where the private NTP service 111 is located) to the global standard time provided by the public NTP service 130 using the external public NTP service 130, so that the device side 140 and the backend server 120 in the medical digital service system 101 are synchronized with the global standard time.

[0043] It should be understood that for the real-time data uploaded to the back-end server 120 by each medical device on the device side 140, if only the time alignment or time synchronization between the real-time data of different medical devices is considered, it can be achieved only by the technical means of the back-end service 121 uniformly providing a timestamp. The use of the private NTP service 111 for time synchronization of the back-end server 120 and / or the device side 140 as mentioned above is not necessary, and the use of the public NTP service 130 for time synchronization of the local system time 121 of the time server 110 is also not necessary.

[0044] Figure 1 The medical digital service system 101 shown can also perform time synchronization when the public NTP service 130 is unavailable. When the medical digital service system 101 itself is only arranged in a local area network environment without access to the Internet, or when the system 101 is connected to the Internet but the connection is unstable or blocked, the public NTP service 130 will be permanently or temporarily unavailable. At this time, since the private NTP service 111 itself uses the local system time 112 of the time server 110 where it is located as the time source, it does not affect the back-end server 120 and the device end 140 using the private NTP service 111 to use the time source as the reference time for time synchronization. In this way, the medical digital service system 101 can be suitable for normal execution of time synchronization work when there is no Internet or the Internet quality is poor.

[0045] Figure 2The medical digitization service system 102 of the second embodiment is shown. The medical digitization service system 102 is basically similar to the system 101 of the first embodiment, and the difference between the two lies in the time source of the backend service 121 of the backend server 120. In the system 101, the time source of the backend service 121 is the local system time 122 of the backend server 120 where it is located, which is synchronized by the private NTP service 111, and a timestamp is provided to the real-time data from the device end 140 based on the local system time 122. In comparison, in the system 102, the backend service 121 in the backend server 120 is directly provided by the private NTP service 111, which can be obtained by the backend service 121 sending a time synchronization request to the private NTP service 111 of the time server 110 to obtain the time provided by the private NTP service 111, and a timestamp is provided to the real-time data from the device end 140 based on the time. The advantage of this approach is that the scalability of the backend server 120 can be improved. When multiple backend servers are used, the time consistency of the backend services in the multiple backend servers can be further ensured, which will be more clearly understood in conjunction with the description of the distributed medical digital service system 202 below. Except for the aforementioned differences, the other parts of the medical digital service system 102 can refer to the description of the system 101.

[0046] Figure 3 The medical digitization service system 103 of the third embodiment is shown. The medical digitization service system 103 is basically similar to the system 102 of the second embodiment, and the difference between the two is that the functions of the time server 110 and the backend server 120 of the system 102 are combined in one backend server 120 in the system 103. This is particularly advantageous when the backend service 121 is only arranged in a single backend server, so that the private NTP service 111 can be deployed in the backend server that usually has high hardware performance, and the private NTP service 111 can synchronize the time of the backend service 121 within the same server, avoiding the delay that may be caused by network transmission.

[0047] Figure 4-Figure 6 Various embodiments of the distributed medical digital service system according to the present application are shown, wherein Figure 1-Figure 3 The same or similar components and parts of the medical digital service system are marked with the same reference numerals. Figure 1-Figure 3 The parts or portions marked with the symbol "1**" in Figure 4-Figure 6 The reference numeral "2**" is used to mark the same or similar components or parts as those corresponding to "1**". Figure 4-Figure 6 In the present invention, the number of the component or part indicated by the original number is indicated by adding "'" to the number.

[0048] See also Figure 4 The distributed medical digital service system 201 of the first embodiment can be considered as Figure 1 The distributed server version of the system 101 is shown. Figure 1 The system 101 is shown with a single backend server 120, Figure 4 The system 201 shown has multiple backend servers, and the backend services 221 are distributedly deployed in the distributed servers formed by these backend servers. Figure 4 Only two backend servers 220 and 220 ′ are schematically shown in the figure, but it can be understood that there may be more backend servers in the distributed medical digital service system 201.

[0049] like Figure 4 As shown, the distributed medical digital service system 201 may also include a load server 250, and the load server 250 may be deployed with a load balancing service 251. For the data uploaded from the device end 240 to the back-end servers 220 and 220' (whether real-time data or non-real-time data), the load balancing service 251 can monitor the status of each back-end server, and distribute the data to different back-end servers for processing according to a certain algorithm (such as polling, weighted polling, etc.) to ensure that the workload of each back-end server is relatively balanced and improve the overall performance of the system. The timestamp operation provided by the back-end service 221 in each back-end server 220 and 220' to the real-time data from the device end 240, the operation on the non-real-time data, the time synchronization operation performed by each back-end server 220 and 220' and the device end 240 through the private NTP service 211, and the time synchronization operation of the time server 210 on its local system time 212 using the public NTP service 230 are all the same as those mentioned above. Figure 1 The corresponding operations of the described system 101 are the same. It should be particularly noted that, similar to the systems 101-103 described above, when the public NTP service 230 is unavailable, the distributed medical digital service system 201 can still use the private NTP service 211 to synchronize the time with the local system time 212 of the time server 210 as the time source, which can be seen in the relevant description of the systems 101-103 in the above text.

[0050] It should be noted that when the local system time 222 and 222' of the backend servers 220 and 220' is synchronized by the private NTP service 211, the backend servers 220 and 220' usually send synchronization requests to the private NTP service 211 independently. In this way, due to the difference in the time and / or frequency of sending synchronization requests, there may be some deviation or asynchronization between the local system time 222 and 222' of different backend servers 220 and 220' for a period of time, although such deviation or asynchronization may be small. At the same time, the time source of the backend service 221 in each backend server 220 and 220' is the local system time 222 and 222' of the backend server 220 and 220', which is synchronized by the private NTP service 111. In this way, since the backend services 221 in each backend server 220 and 220' provide timestamps based on the local system time 222 and 222' of each backend server 220 and 220' when processing the real-time data from the device end 240 allocated by the load balancing service 251, the possible deviation between the local system time 222 and 222' will cause the backend services 221 in different backend servers 220 and 220' to provide timestamps for the real-time data from the device end 240.

[0051] Figure 5 The distributed medical digital service system 202 of the second embodiment shown in FIG. Figure 2 The system 102 shown in FIG. 1 solves the aforementioned time stamp deviation problem in a similar manner. The distributed medical digital service system 202 is basically similar to Figure 4 The difference between the system 201 shown in the figure lies in the time source of the backend service 221 of the backend servers 220 and 220'. In the system 202, the backend service 221 in the backend servers 220 and 220' directly requests the private NTP service 211 of the time server 210 to obtain the time provided by the private NTP service 211, and provides a timestamp to the real-time data from the device end 240 based on the time. It should be understood that although the backend service 221 is deployed in a distributed server environment composed of multiple backend servers, the backend service 221 can issue a synchronization request to the private NTP service 211 as a whole and obtain the returned time. The backend services 221 located in each backend server 220 and 220' all use the same return time to process the data, including providing a timestamp to the real-time data from the device end 240. Compared to Figure 4 The system 201 shown, Figure 5The system 202 shown further ensures the time consistency of the backend services 221 in the multiple backend servers 220 and 220'. Except for the aforementioned differences, the other parts of the distributed medical digital service system 202 can refer to the description of the system 201.

[0052] Figure 6 The distributed medical digital service system 203 of the third embodiment is shown. Figure 5 The system 202 shown is basically the same, except that a time synchronization relay service 213 is added to the time server 210. The time synchronization relay service 213 can periodically send a request to the private NTP service 211 to obtain the time at a predetermined frequency, and after obtaining the time returned by the private NTP service 211, it actively distributes it to each backend server 220 and 220' by broadcasting or other appropriate methods. Figure 6 In the example, the time synchronization transfer service 213 directly distributes the time to the backend service 221. It can be understood that based on Figure 6 In a variant embodiment of the system 203 shown in FIG. 203 , the time synchronization transfer service 213 can also actively distribute the time to each backend server 220 and 220 'to synchronize their respective local system time 222 and 222 ', and the backend service 221 uses the local system time 222 and 220 'of the server where it is located to provide a timestamp for the real-time data. This active distribution method can also solve Figure 4 The system 201 shown may have a deviation problem between the local system times 222 and 220' of different backend servers 220 and 220'.

[0053] Figure 7 The distributed medical digital service system 204 of the fourth embodiment is shown. Figure 6 The system 203 shown is substantially the same except that Figure 6 The private NTP service 211 and the time synchronization transfer service 213 provided by the central time server 210 and the load balancing service 251 provided by the load server 250 are all deployed in the same support server 260. The term "support server" used here refers to a server that provides supporting services for the back-end servers 220 and 220' and the device end 240, such as the private NTP service 211, the time synchronization transfer service 213, the load balancing service 251 or other service servers. Figure 4-Figure 6The time server and load server shown in are also support servers in this sense. Integrating the required support services in the same support server 260 is conducive to selecting a high-performance server as the support server 260 while controlling costs. The high-performance server, for example, has a high-precision and high-stability clock so that it can provide accurate local system time 212 for a long time when there is no available public NTP service 230 or when the public NTP service 230 is unstable. Figure 7 In the example, the time synchronization transfer service 213 directly distributes the time to the backend service 221. It can be understood that based on Figure 7 In a variant embodiment of the system 204 not shown, the time synchronization transit service 213 can also actively distribute time to each back-end server 220 and 220' to synchronize their respective local system time 222 and 222', and the back-end service 221 uses the local system time 222 and 220' of the server where it is located to provide timestamps for real-time data.

[0054] for Figure 1-Figure 7 The medical digital service systems 101-103 and 201-204 shown provide private NTP services 111 and 211, and the device ends 140, 240 and the back-end servers 120, 220, 220' obtain synchronization time through the private NTP services 111 and 211. The private NTP services 111 and 211 use the local system time 112, 212 of the servers 110, 210, 260 where they are located as the time source, which realizes the isolation of the time synchronization operation from the network connection of the external Internet. Even when the system is not connected to the Internet or is connected to the Internet but the public NTP services 130, 230 are unavailable, time synchronization can still be achieved within the system, thereby improving the robustness of time synchronization, and also ensuring the consistency of the data in the medical devices in the back-end service 211 and the device ends 140, 240 in the time dimension.

[0055] When the medical digital service systems 101-103 and 201-204 are connected to the Internet and the public NTP services 130, 230 are available, the public NTP services 130, 230 can be used to synchronize the local system time 112, 212 of the server where the private NTP services 111, 211 are located with the global standard time, and the private NTP services 111, 211 can be further used to synchronize the medical devices in the device end 140, 240 in the system and the back-end servers 120, 220, 220' with the global standard time.

[0056] In addition, the backend services 121, 221 in the backend servers 120, 220, 220' provide timestamps for the real-time data received from the device ends 140, 240, instead of using the timestamps provided by the medical devices for the data generated (even if the local system time of each medical device is synchronized via the NTP service), which can further improve the alignment accuracy of the timestamps of the real-time data of each medical device. This is particularly beneficial in discovering, judging and studying the correlation between the data of different types of medical devices at the same moment as described above.

[0057] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit the present invention. Although the present invention is described in detail with reference to the embodiments, it should be understood by those skilled in the art that any modification or equivalent replacement of the technical solutions of the present invention does not depart from the spirit and scope of the technical solutions of the present invention and should be included in the scope of the claims of the present invention.

Claims

1. A medical digital service system, comprising at least one server, wherein the at least one server is deployed with: A private NTP service, wherein the private NTP service uses the local system time of the server where the private NTP service is located as a time source to provide a time synchronization service; and A backend service capable of receiving and processing data generated and uploaded in real time from one or more medical devices; wherein, The timestamp of the data is provided by the backend service, and the time based on which the timestamp is based is the time directly provided by the private NTP service, or the local system time of the server where the backend service is located synchronized by the private NTP service.

2. The medical digital service system according to claim 1, characterized in that: The server where the private NTP service is located is connected to an external public NTP service, and the public NTP service can provide time synchronization services of the global standard time; wherein, when the public NTP service is available, the server where the private NTP service is located uses the public NTP service to synchronize its local system time with the global standard time.

3. The medical digital service system according to any one of claims 1-2, characterized in that: Also included are the one or more medical devices; wherein at least one of the one or more medical devices is connected to the private NTP service to synchronize the local system time of the at least one medical device with the time source of the private NTP service.

4. The medical digital service system according to any one of claims 1 to 3, characterized in that: The private NTP service and the backend service are deployed in the same server; or, the private NTP service and the backend service are deployed in different servers.

5. The medical digital service system according to any one of claims 1 to 4, characterized in that: The one or more medical devices include a plurality of medical devices, and the plurality of medical devices are of at least two different functional types.

6. A time synchronization method for a medical digital service system, comprising: Provide a private NTP service, wherein the private NTP service uses the local system time of the server where the private NTP service is located as the time source to provide a time synchronization service; The backend service in the backend server receives and processes data generated and uploaded in real time from one or more medical devices, and provides a timestamp for the data; wherein the time on which the timestamp is based is the time provided by the private NTP service, or the local system time of the backend server synchronized by the private NTP service.

7. The time synchronization method according to claim 6, characterized in that: Also includes: When a public NTP service is available, the public NTP service is used to synchronize the local system time of the server where the private NTP service is located with the global standard time.

8. The time synchronization method according to any one of claims 6 to 7, characterized in that: It also includes: using the private NTP service to synchronize the local system time of at least one of the one or more medical devices with the time source of the private NTP service.

9. The time synchronization method according to any one of claims 6 to 8, characterized in that: The private NTP service is deployed in the backend server; or, the private NTP service is deployed in another server different from the backend server.

10. The time synchronization method according to any one of claims 6 to 9, characterized in that: The one or more medical devices include a plurality of medical devices, and the plurality of medical devices are of at least two different functional types.

Images