DEVICE DATA SYNCHRONIZATION

• US 20160342670A1
• 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: SMITH, Richard M., BUDIMLIC, Elvis A., WOBIG, Gregory S., BURRICHTER, Scott
• Application Number:
  US14/717,640
• Publication Number:
  US 20160342670A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/273 Asynchronous replication or reconciliation
• CPC Class Codes: G16B 50/00 ICT programming tools or database systems specially adapted for bioinformatics
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Abstract

Techniques for synchronizing data between a first device and a second device. A plurality of data elements relating to a care plan in a health care environment are created and a respective unique identifier is assigned to each of the plurality of data elements. Embodiments transmit a synchronization request to a second device, specifying at least (i) one or more identifiers assigned to data elements to synchronize, (ii) a session identifier indicating when a last synchronization operation was performed at the first device and (iii) one or more data element values that have been modified since the last synchronization operation was performed. In response, a second one or more data element values are received from the second device, corresponding to the one or more identifiers specified in the synchronization request. The first device updates the one or more data elements corresponding to the second one or more data element values.

Claims

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

creating a plurality of data elements relating to a care plan in a health care environment for a patient;

assigning a respective identifier to each of the plurality of data elements, wherein each assigned identifier is unique within the health care environment;

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

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

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

2. 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.

3. 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.

4. 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.

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

6. The method of claim 1, further comprising:

further in response to transmitting the synchronization request, receiving a deleted flag for a data element corresponding to the one or more identifiers specified in the synchronization request, indicating that the data element has been deleted by a device other than the first device.

7. The method of claim 1, wherein updating, at the first device, the one or more data elements corresponding to the second one or more data element values further comprises:

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

tagging each of the one or more updated data elements with the incremented session identifier.

8. 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:

creating a plurality of data elements relating to a care plan in a health care environment for a patient;

assigning a respective identifier to each of the plurality of data elements, wherein each assigned identifier is unique within the health care environment;

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

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

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

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

10. The non-transitory computer-readable medium of claim 8, 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.

11. The non-transitory computer-readable medium of claim 8, 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.

12. The non-transitory computer-readable medium of claim 8, wherein the synchronization request further specifies a deleted flag for one of the plurality of data elements, indicating that the data element has been deleted on the first device.

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

further in response to transmitting the synchronization request, receiving a deleted flag for a data element corresponding to the one or more identifiers specified in the synchronization request, indicating that the data element has been deleted by a device other than the first device.

14. The non-transitory computer-readable medium of claim 8, wherein updating, at the first device, the one or more data elements corresponding to the second one or more data element values further comprises:

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

tagging each of the one or more updated data elements with the incremented session identifier.

15. A system, comprising:

a processor; and

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

creating a plurality of data elements relating to a care plan in a health care environment for a patient;

assigning a respective identifier to each of the plurality of data elements, wherein each assigned identifier is unique within the health care environment;

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

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

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

16. The system of claim 15, wherein a first data element in the plurality of data elements comprises at least one of (i) biometric data for a patient generated by one or more sensor devices and (ii) a health care event that specifies one or more conditions that, when satisfied, designate an occurrence of the health care event.

17. The system of claim 15, 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.

18. The system of claim 15, wherein the synchronization request further specifies a deleted flag for one of the plurality of data elements, indicating that the data element has been deleted on the first device.

19. The system of claim 15, the operation further comprising:

further in response to transmitting the synchronization request, receiving a deleted flag for a data element corresponding to the one or more identifiers specified in the synchronization request, indicating that the data element has been deleted by a device other than the first device.

20. The system of claim 15, wherein updating, at the first device, the one or more data elements corresponding to the second one or more data element values further comprises:

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

tagging each of the one or more updated data elements with the incremented session identifier.