Cloud-to-local, local-to-cloud switching and synchronization of medical images and data

Abstract

A method to prevent conflict during synchronization of medical data between a cloud repository on a cloud server and a plurality of local repositories on a plurality of local servers of healthcare facilities connected to the cloud server is provided. The plurality of local servers includes a first local server and the plurality of local repositories includes a first local repository on the first local server. The method includes, while a connection between the first local server and the cloud server is established, causing the first local server to: receive remote data from the cloud repository; store the remote data in the first local repository as local data; and in response to the connection between the first local server and the cloud server getting disconnected, causing the first local server to: access the first local repository instead of the cloud repository; and restrict editing on the first local repository.

What is claimed is: 
     
         1 . A method to prevent conflict during synchronization of medical data between a cloud repository on a cloud server and a plurality of local repositories on a plurality of local servers of healthcare facilities connected to the cloud server, wherein the plurality of local servers comprises a first local server and the plurality of local repositories comprises a first local repository on the first local server, the method comprising:
 while a connection between the first local server and the cloud server is established, causing the first local server to:
 receive, from the cloud repository, remote data sent from any of the plurality of local servers to the cloud repository, 
 store the remote data in the first local repository as local data, and 
 if the first local server determines that the remote data is being updated by any of the plurality of local servers, restrict editing that can be performed on the local data; and 
   in response to the connection between the first local server and the cloud server getting disconnected, causing the first local server to:
 access the first local repository instead of the cloud repository; and 
 restrict editing on the first local repository. 
   
     
     
         2 . The method according to  claim 1 , wherein the method further comprising:
 in response to the connection between the first local server and the cloud server getting reestablished, causing the first local server to:
 re-access the cloud repository, and 
 if any local data on the first local repository was added by the first local server while the connection was disconnected, send the added local data to the cloud repository. 
   
     
     
         3 . The method according to  claim 2 , wherein the first local repository is coupled to a local computer. 
     
     
         4 . The method according to  claim 1 , wherein if the local data is being edited by the first local server, the first local server sends a notification to the cloud server to inform the plurality of local servers that store the remote data that the local data is being updated at the first local server. 
     
     
         5 . The method according to  claim 1 , wherein
 the editing of the local data is restricted to adding new information as new local data for a predetermined patient, and   the editing on the first local repository is restricted to adding new information as new local data associated with the predetermined patient or a new patient.   
     
     
         6 . The method according to  claim 5 , wherein editing of existing local data in the first local repository is prohibited when editing is restricted. 
     
     
         7 . The method according to  claim 5 , wherein the remote data and the local data are DICOM-format images or a patient's medical reports that includes metadata. 
     
     
         8 . The method according to  claim 7 , wherein the metadata comprises a patient ID, a patient name, an attributed facility ID, a patient report information, and an image information. 
     
     
         9 . The method according to  claim 8 , wherein the metadata is editable by a user through a graphical user interface (GUI) displayed by a computer coupled to the plurality of respective local servers. 
     
     
         10 . The method according to  claim 1 , wherein the local repository is a repository disposed in a medical facility. 
     
     
         11 . The method according to  claim 7 , wherein the DICOM-format images are taken using a modality in a medical facility connected to a computer coupled to the plurality of respective local servers. 
     
     
         12 . The method according to  claim 1 , wherein the cloud repository on the cloud server is a repository for a cloud-based Picture Archiving and Communication System (PACS). 
     
     
         13 . A non-transitory computer-readable medium (CRM) storing instructions that cause a first local server coupled to a computer to perform an operation to prevent conflict during synchronization of medical data between a cloud repository on a cloud server and a plurality of local repositories on a plurality of local servers of healthcare facilities connected to the cloud server, wherein the plurality of local servers comprises the first local server and the plurality of local repositories comprises a first local repository on the first local server, the operation comprising:
 while a connection between the first local server and the cloud server is established, causing the first local server to:
 receive, from the cloud repository, remote data sent from any of the plurality of local servers to the cloud repository, 
 store the remote data in the first local repository as local data, and 
 if the first local server determines that the remote data is being updated by any of the plurality of local servers, restrict editing that can be performed on the local data; and 
   in response to the connection between the first local server and the cloud server getting disconnected, causing the first local server to:
 access the first local repository instead of the cloud repository; and 
 restrict editing on the first local repository. 
   
     
     
         14 . The CRM according to  claim 13 , wherein the operation further comprising:
 in response to the connection between the first local server and the cloud server getting reestablished, causing the first local server to:
 re-access the cloud repository, and 
 if any local data on the first local repository was added by the first local server while the connection was disconnected, send the added local data to the cloud repository. 
   
     
     
         15 . The CRM according to  claim 13 , wherein
 the editing of the local data is restricted to adding new information as new local data for a predetermined patient, and   the editing on the first local repository is restricted to adding new information as new local data associated with the predetermined patient or a new patient.   
     
     
         16 . The CRM according to  claim 15 , wherein editing of existing local data in the first local repository is prohibited when editing is restricted. 
     
     
         17 . A system that prevents conflict during synchronization of medical data, comprising:
 a cloud server;   a cloud repository on the cloud server; and   a plurality of local repositories on a plurality of local servers of healthcare facilities connected to the cloud server, wherein the plurality of local servers comprises a first local server and the plurality of local repositories comprises a first local repository on the first local server,   while a connection between the first local server and the cloud server is established, causing the first local server to:
 receive, from the cloud repository, remote data sent from any of the plurality of local servers to the cloud repository, 
 store the remote data in the first local repository as local data, and 
 if the first local server determines that the remote data is being updated by any of the plurality of local servers, restrict editing that can be performed on the local data; and 
   in response to the connection between the first local server and the cloud server getting disconnected, causing the first local server to:
 access the first local repository instead of the cloud repository, and 
 restrict editing on the first local repository. 
   
     
     
         18 . The system according to  claim 17 , wherein
 in response to the connection between the first local server and the cloud server getting reestablished, causing the first local server to:
 re-access the cloud repository, and 
 if any local data on the first local repository was added by the first local server while the connection was disconnected, send the added local data to the cloud repository. 
   
     
     
         19 . The system according to  claim 17 , wherein
 the editing of the local data is restricted to adding new information as new local data for a predetermined patient, and   the editing on the first local repository is restricted to adding new information as new local data associated with the predetermined patient or a new patient.   
     
     
         20 . The system according to  claim 19 , wherein editing of existing local data in the first local repository is prohibited when editing is restricted.