DEVICE DATA SYNCHRONIZATION

• US 20160344808A1
• Filed: 05/20/2015
• Published: 11/24/2016
• Est. Priority Date: 05/20/2015
• Status: Abandoned Application

• Current Assignee: Preventice Solutions, Inc. (Boston Scientific Corporation)
• Original Assignee: Preventice
• Inventors: BUDIMLIC, Elvis A., WOBIG, Gregory S., BURRICHTER, Scott, SMITH, Richard M.
• Application Number:
  US14/717,685
• Publication Number:
  US 20160344808A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04L 67/146 Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding

Abstract

Techniques for synchronizing data between a first device and a second device. A synchronization request is received at the first device, from the second device, specifying at least (i) identifiers assigned to data elements to synchronize, (ii) session identifiers indicating when a last synchronization operation was performed for the data elements at the second device, and (iii) data element values that have been modified. Upon determining that the session identifier within the synchronization request is more recent than a second session identifier for a first one of a plurality of data elements maintained at the first device, the first data element is updated based on the data element values specified within the synchronization request. Embodiments identify data elements having a respective session identifier that is more recent than the session identifier specified within the synchronization request and transmit data values for the identified data elements to the second device.

Claims

1. A method of synchronizing data between a first device and a second device, comprising:

receiving, at the first device, from the second device, a synchronization request specifying at least (i) one or more identifiers assigned to data elements to synchronize, (ii) one or more session identifiers indicating when a last synchronization operation was performed for the one or more data elements at the second device, and (iii) one or more data element values that have been modified since the last synchronization operation was performed;

upon determining that the session identifier within the synchronization request is more recent than a second session identifier for a first one of a plurality of data elements maintained at the first device, updating the first data element based on the one or more data element values specified within the synchronization request;

identifying data elements within the plurality of data elements having a respective session identifier that is more recent than the session identifier specified within the synchronization request; and

transmitting data values for the identified data elements to the second device.

2. The method of claim 1, further comprising:

upon receiving the synchronization request, transmitting a second synchronization request, from the first device, to a third device, specifying at least (i) a second one or more identifiers assigned to the data elements on the first device to synchronize, (ii) one or more session identifiers indicating when a last synchronization operation was performed at the first device and (iii) a second one or more data element values that have been modified on the first device since the last synchronization operation was performed between the first device and the third device; and

in response, receiving a third one or more data element values from the third device, corresponding to the second one or more identifiers specified in the second synchronization request; and

updating, at the first device, the one or more data elements corresponding to the third one or more data element values.

3. The method of claim 1, wherein a first data element in the plurality of data elements comprises biometric data for a patient generated by one or more sensor devices.

4. The method of claim 1, wherein a first data element in the plurality of data elements comprises a health care event that specifies one or more conditions that, when satisfied, designate an occurrence of the health care event.

5. The method of claim 1, wherein assigning the respective identifier to each of the plurality of data elements further comprises:

determining a device identifier that uniquely identifies the first device within the health care environment for the patient;

determining a respective data element identifier for each of the plurality of data elements; and

tagging each of the plurality of data elements with the respective identifier that includes the determined device identifier and the respective data element identifier.

6. The method of claim 1, wherein the synchronization request further specifies a deleted flag for first data element of the plurality of data elements, indicating that the first data element has been deleted on the second device, and further comprising:

upon determining that the session identifier within the synchronization request is more recent than a second session identifier for the first data element on the first device, deleting the first data element on the first device.

7. The method of claim 1, wherein the synchronization request further specifies a deleted flag for first data element of the plurality of data elements, indicating that the first data element has been deleted on the second device, and further comprising:

upon determining that a second session identifier for the first data element on the first device is more recent than the session identifier within the synchronization request, transmitting a response message to the second device that includes at least (i) the identifier assigned to the first data element, (ii) the second session identifier and (iii) a deleted flag for the first data element.

8. The method of claim 1, wherein updating the first data element based on the one or more data element values specified within the synchronization request further comprises:

incrementing the session identifier indicating when the last synchronization operation was performed at the first device; and

tagging the updated first data element with the incremented session identifier.

9. A non-transitory computer-readable medium containing computer program code that, when executed by a processor, performs an operation for synchronizing data between a first device and a second device, comprising:

receiving, at the first device, from the second device, a synchronization request specifying at least (i) one or more identifiers assigned to data elements to synchronize, (ii) one or more session identifiers indicating when a last synchronization operation was performed for the one or more data elements at the second device, and (iii) one or more data element values that have been modified since the last synchronization operation was performed;

upon determining that the session identifier within the synchronization request is more recent than a second session identifier for a first one of a plurality of data elements maintained at the first device, updating the first data element based on the one or more data element values specified within the synchronization request;

identifying data elements within the plurality of data elements having a respective session identifier that is more recent than the session identifier specified within the synchronization request; and

transmitting data values for the identified data elements to the second device.

10. The non-transitory computer-readable medium of claim 9, the operation further comprising:

upon receiving the synchronization request, transmitting a second synchronization request, from the first device, to a third device, specifying at least (i) a second one or more identifiers assigned to the data elements on the first device to synchronize, (ii) one or more session identifiers indicating when a last synchronization operation was performed at the first device and (iii) a second one or more data element values that have been modified on the first device since the last synchronization operation was performed between the first device and the third device; and

in response, receiving a third one or more data element values from the third device, corresponding to the second one or more identifiers specified in the second synchronization request; and

updating, at the first device, the one or more data elements corresponding to the third one or more data element values.

11. The non-transitory computer-readable medium of claim 9, wherein a first data element in the plurality of data elements comprises biometric data for a patient generated by one or more sensor devices.

12. The non-transitory computer-readable medium of claim 9, wherein a first data element in the plurality of data elements comprises a health care event that specifies one or more conditions that, when satisfied, designate an occurrence of the health care event.

13. The non-transitory computer-readable medium of claim 9, wherein assigning the respective identifier to each of the plurality of data elements further comprises:

determining a device identifier that uniquely identifies the first device within the health care environment for the patient;

determining a respective data element identifier for each of the plurality of data elements; and

tagging each of the plurality of data elements with the respective identifier that includes the determined device identifier and the respective data element identifier.

14. The non-transitory computer-readable medium of claim 9, wherein the synchronization request further specifies a deleted flag for first data element of the plurality of data elements, indicating that the first data element has been deleted on the second device, and further comprising:

upon determining that the session identifier within the synchronization request is more recent than a second session identifier for the first data element on the first device, deleting the first data element on the first device.

15. The non-transitory computer-readable medium of claim 9, wherein the synchronization request further specifies a deleted flag for first data element of the plurality of data elements, indicating that the first data element has been deleted on the second device, and the operation further comprising:

upon determining that a second session identifier for the first data element on the first device is more recent than the session identifier within the synchronization request, transmitting a response message to the second device that includes at least (i) the identifier assigned to the first data element, (ii) the second session identifier and (iii) a deleted flag for the first data element.

16. The non-transitory computer-readable medium of claim 9, wherein updating the first data element based on the one or more data element values specified within the synchronization request further comprises:

incrementing the session identifier indicating when the last synchronization operation was performed at the first device; and

tagging the updated first data element with the incremented session identifier.

17. A system, comprising:

a processor; and

a memory containing computer program code that, when executed by the processor, performs an operation for synchronizing data between a first device and a second device, comprising;

receiving, at the first device, from the second device, a synchronization request specifying at least (i) one or more identifiers assigned to data elements to synchronize, (ii) one or more session identifiers indicating when a last synchronization operation was performed for the one or more data elements at the second device, and (iii) one or more data element values that have been modified since the last synchronization operation was performed;

upon determining that the session identifier within the synchronization request is more recent than a second session identifier for a first one of a plurality of data elements maintained at the first device, updating the first data element based on the one or more data element values specified within the synchronization request;

identifying data elements within the plurality of data elements having a respective session identifier that is more recent than the session identifier specified within the synchronization request; and

transmitting data values for the identified data elements to the second device.

18. The system of claim 17, the operation further comprising:

upon receiving the synchronization request, transmitting a second synchronization request, from the first device, to a third device, specifying at least (i) a second one or more identifiers assigned to the data elements on the first device to synchronize, (ii) one or more session identifiers indicating when a last synchronization operation was performed at the first device and (iii) a second one or more data element values that have been modified on the first device since the last synchronization operation was performed between the first device and the third device; and

in response, receiving a third one or more data element values from the third device, corresponding to the second one or more identifiers specified in the second synchronization request; and

updating, at the first device, the one or more data elements corresponding to the third one or more data element values.

19. The system of claim 17, wherein assigning the respective identifier to each of the plurality of data elements further comprises:

determining a device identifier that uniquely identifies the first device within the health care environment for the patient;

determining a respective data element identifier for each of the plurality of data elements; and

tagging each of the plurality of data elements with the respective identifier that includes the determined device identifier and the respective data element identifier.

20. The system of claim 17, wherein updating the first data element based on the one or more data element values specified within the synchronization request further comprises:

incrementing the session identifier indicating when the last synchronization operation was performed at the first device; and

tagging the updated first data element with the incremented session identifier.