System and apparatus for efficiently utilizing network capacity in a healthcare setting

• US 20050144044A1
• Filed: 09/29/2004
• Published: 06/30/2005
• Est. Priority Date: 09/29/2003
• Status: Abandoned Application

• Current Assignee: Siemens Medical Solutions USA Incorporated (Siemens AG)
• Original Assignee: Samsung Electronics Co. Ltd.
• Inventors: Kaitell, Victor Maclean Ebeneza, VanSickler, Michael Treat, Godschall, Christopher Brian
• Application Number:
  US10/952,448
• Publication Number:
  US 20050144044A1
• Time in Patent Office: Days
• US Class Current: 705/3
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 80/00 ICT specially adapted for facilitating communication between medical practitioners or patients, e.g. for collaborative diagnosis, therapy or health monitoring

Abstract

A handheld or portable computing device is provided and capable of providing efficient maintenance of information maintained or stored within a healthcare information system such as an LIS (laboratory information system). Periodically updating information with the server allows the user to perform many specimen collection related tasks efficiently. The handheld device and related system provide improved monitoring of diagnostic sample collection errors and further provides efficient network management of accessing and updating the information on a server through communications with the network such as ping synchronization communications and use of a valid data timer element.

Claims

1. A method for efficiently updating in an asynchronous environment the data stored in portable computing devices with corresponding data stored in a database at a server or accessed via a server, the portable computing devices and database both being configured for use in a healthcare setting and comprising patient data, the method comprising the steps of:

establishing a connection between a portable computing device or PCD and the server;

sending a request for synchronization from the PCD to the server;

starting a response timer;

waiting for a response from the server within a selected wait time;

retransmitting the request for synchronization if a response was not received from the server within the selected wait time;

determining whether the PCD and server need synchronization, if the server successfully receives the request for synchronization, and generating a response for the PCD indicating either a need for synchronization or no need for synchronization; and

transmitting the response from the server to the PCD.

2. A method as claimed in claim 1, wherein the PCD is configured to store patient data in a PCD memory module, and the sending step for sending a request for synchronization comprises the step of generating and transmitting a data stream at the PCD that represents different types of the patient data that are stored in the PCD memory module and state data, the state data being configured to facilitate the determination at the server of whether at least a selected portion of the patient data stored in the PCD memory device is current relative to corresponding patient data stored in the database.

3. A method as claimed in claim 2, wherein the determining step comprises the steps of:

receiving the data stream at the server; and

using the state data in the data stream at the server to compare the different types of patient data in the data stream with corresponding patient data in the database to determine whether at least the different types of patient data in the PCD memory device is current relative to corresponding patient data stored in the database.

4. A method as claimed in claim 1, wherein the PCD is assigned for a specific use selected from the group consisting of use by a specific user, use in a selected physical location, and use for collection of a selected type of patient data, and the determining step comprises determining whether a subset of the patient data stored at the PCD requires synchronization, the subset of patient data corresponding to patient data collected for one of the specific uses.

5. A method as claimed in claim 4, wherein the PCD is configured to store patient data in a PCD memory module, and the sending step for sending a request for synchronization comprises the step of generating and transmitting a data stream at the PCD that represents different types of the patient data that is stored in the PCD memory module and state data, the state data being configured to facilitate the determination at the server of whether at least a selected portion of the patient data stored in the PCD memory device is current relative to corresponding patient data stored in the database, the data stream comprising at least one of a user identifier, a handheld identifier, and a location identifier to identify which selected portion of the patient data needs to be analyzed to determine whether if it requires synchronization with the database.

6. A method as claimed in claim 1, wherein the PCD operates a valid data timer, and further comprising the step of resetting the valid data timer after synchronization and when the response indicates a need for synchronization.

7. A method as claimed in claim 6, further comprising the step of the PCD changing its settings to indicate that the PCD is up to date at the current time.

8. A method as claimed in claim 1, wherein the PCD operates a valid data timer, and further comprising the step of resetting the valid data timer when the server determines that synchronization is not necessary.

9. A method as claimed in claim 8, further comprising the step of the PCD changing its settings to indicate that the PCD is up to date at the current time.

10. A method for efficiently updating in an asynchronous environment the data stored in portable computing devices with corresponding data stored in a database at a server or accessed via a server, the portable computing devices and database both being configured for use in a healthcare setting and comprising patient information, the method comprising the steps of:

establishing a connection between a portable computing device or PCD and the server for sending patient data thereto;

generating a structured data stream at the PCD comprising different types of patient data and corresponding state data that can be used to determine if the different types of the patient data were changed in a PCD memory device;

transmitting data comprising at least a portion of the patient data stored at the PCD and the structured data stream from the PCD to the server;

analyzing the data from the PCD received at the server for compatibility by determining if at least a portion of the structured data stream is recognized therein;

generating and transmitting from the server an order to the PCD to synchronize at least a portion of the patient data stored therein with corresponding patient data stored in the database if the server determines that the data is not in a compatible format; and

extracting state data from the data sent from the PCD to the server for comparison with corresponding data stored in a database at the server or accessed via the server and determining whether the PCD should synchronize with the database if the data is in a compatible format for the server.

11. A method as claimed in claim 10, wherein the state data comprises time stamps to indicate when the patient data was changed in a PCD memory device.

12. A method as claimed in claim 10, wherein the state data comprises data markers to indicate when the patient data was changed in a PCD memory device relative to corresponding patient data stored in another memory device.

13. A method for efficiently updating in an asynchronous environment the data stored in portable computing devices with corresponding data stored in a database at a server or accessed via a server, the method comprising the steps of:

establishing a connection between a portable computing device or PCD and the server for sending data thereto;

generating a structured data stream at the PCD comprising different data field types and state data that can be used to determine if the data for a corresponding data field type was changed in a PCD memory device;

transmitting data from the PCD to the server, the data comprising the structured data stream;

receiving the data from the PCD at the server;

analyzing at the server at least a portion of the state data received from the PCD to determine if the PCD changed the data, changes to the data comprising at least one of modifications to at least an existing selected portion of the data stored in the PCD and the addition of new data to the PCD;

sending an instruction from the server to the PCD to commence synchronization if the server determines that changes were made to the data stored in the PCD;

sending a response from the server to the PCD indicating that the PCD need not synchronize if the server determines that no changes were made to the data stored in the PCD and that the data stored in the PCT is current with respect to the corresponding data in the database or accessed via the server; and

sending an instruction from the server to the PCD to commence synchronization if the server determines that no changes were made to the data stored in the PCD but the data stored in the PCD is not current with respect to the corresponding data stored in the database or accessed via the server.

14. A method as claimed in claim 13, wherein the state data comprises data markers, and the analyzing step comprises the step of analyzing the sequence of the data markers to determine if the PCD made modifications to the data stored therein or added new data to the data stored therein.

15. A method as claimed in claim 13, further comprising the step of:

operating the server to interrogate the database associated therewith with the state data provided by the PCD to determine if the database has changed and requires synchronization.

16. A method as claimed in claim 15, further comprising the step of responding to the PCD with the results of interrogation indicating whether or not the PCD needs to synchronize.

17. A method as claimed in claim 13, wherein the transmitting step further comprises the steps of:

starting a response timer as the PCD sends the data to the server; and

waiting for a response from the server within a selected wait time.

18. A method as claimed in claim 17, wherein the response timer has a resolution on the order of milliseconds.

19. A method as claimed in claim 17, wherein the PCD waits for a subsequent poll interval or actuated event to retransmit the data if a response was not received from the server within the selected wait time.

20. A method as claimed in claim 19, wherein the PCD logs an event that the server failed to respond when a response is not received from the server within the selected wait time.

21. A method as claimed in claim 17, wherein if a response from the server occurs within the selected wait time, the method further comprises the steps of:

determining from the response transmitted from the server to the PCD whether the PCD needs to synchronize with the server; and

initiating synchronization if the response from the PSS instructs the PCD to synchronize.

22. A method as claimed in claim 13, wherein the PCD operates a valid data timer, and further comprising the step of resetting the valid data timer after synchronization and when the response indicates a need for synchronization.

23. A method as claimed in claim 22, further comprising the step of the PCD changing its settings to indicate that the PCD is up to date at the current time.

24. A method as claimed in claim 13, wherein the PCD operates a valid data timer, and further comprising the step of resetting the valid data timer after each synchronization when the server determines that synchronization is not necessary.

25. A method as claimed in claim 24, further comprising the step of the PCD changing its settings to indicate that the PCD is up to date at the current time.

26. A method as claimed in claim 13, wherein the state data comprises data markers, and the analyzing step comprises the step of analyzing the sequence of the data markers to determine if the PCD made modifications to the data stored therein or added new data to the data stored therein.

27. A method as claimed in claim 26, further comprising the step of uploading selected data and corresponding data markers from the database to the PCD during synchronization.

28. A method as claimed in claim 27, further comprising the step of the PCD communicating its new state to the server at the onset of the next synchronization process after uploading from database.

29. A method as claimed in claim 13, wherein the PCD is assigned to operate in a selected physical location and the data in the database comprises data specific to the selected physical location, and further comprising the step of the server interrogating the database with the data markers provided by the PCD to determine if portions of the database relevant to information specific to the selected physical location assigned to the PCD require synchronization.

30. A method as claimed in claim 29, wherein the physical locations are selected from the group consisting of a floor, a wing, a section of a building, or a building of a facility in which the PCD operates.

31. A method as claimed in claim 29, further comprising the step of transmitting from the server to the PCD interrogation results indicating whether or not the specific PCD needs to synchronize with relevant data tables specific to the selected physical location stored in the database.

32. A method as claimed in claim 31, wherein the data tables are specific to at least one of specimen collection and medication administration information to provide a subset of patient information recorded in a Hospital Information System or HIS.

33. A method as claimed in claim 13, wherein the server is a specimen management server and the data being synchronized between the portable computing device and at least one of the server and the database comprises at least one of specimen sample data, patient identifiers, specimen collection orders, cancellation order codes, and specimen collection container identifiers, user identifiers, PCD identifiers, and physical location identifiers.

34. A method as claimed in claim 13, wherein the server is connected to at least one of a patient database and a specimen order database, and the PCD and server are synchronized to allow tracking of collected specimens and matching to patient identification information stored in at least one of the patient database and specimen order database.

35. A method as claimed in claim 34, wherein said at least one of a patient database and a specimen order database is selected from the group consisting of a hospital information system or laboratory information system

36. A method for efficiently updating in an asynchronous environment the data stored in portable-computing systems with corresponding data stored in a database at a server or accessed via a server, the method comprising the steps of:

forwarding a query from a PCD to the server to determine if either the server or the network connecting the server to the PCD is unavailable;

when the PCD is unable to connect to the server, forwarding at least one other query from the PCD to the server after the occurrence of at least one of a predetermined interval of time and a predetermined event; and

when the PCD connects to the server, generating and sending a structured data stream to the server, the server being configured to extract data from the data stream sent from the PCD and determine if the PCD should synchronize with the server.

37. A method as claimed in claim 36, further comprising the step of logging a failed attempt event if the PCD is unable to connect to the SMS.

38. A method as claimed in claim 36, wherein the query is an ICMP echo request (PING).

39. A method as claimed in claim 38, wherein the server returns an ICMP echo (PING) response to the PCD within a prescribed period of time after the ICMP echo request (PING) if the connection is not terminated.

40. A method as claimed in claim 38, wherein the server returns an ICMP echo (PING) response to the PCD upon the occurrence of a predetermined event after the ICMP echo request (PING) if the connection is not terminated.

41. A method as claimed in claim 40, wherein the predetermined event is selected from the group consisting of a subsequent poll interval and a selected event.

42. A portable computing device or PCD for use in a healthcare setting comprising:

an input module for entering patient information;

a memory module for storing patient information;

a communication module for allowing the portable computing device to communicate with at least one of a server and a healthcare information database, the communication module comprising at least one of a wireless interface and a wireline interface for connecting to at least one other computing device or network of computing devices, the other computing device or network of computing devices comprising at least one of the server and the healthcare information database;

a cradle interface element for connecting the PCD to a cradle when placed therein, the cradle being configured for connection to at least the other computing device or network of computing devices;

a processing module connected to the memory, the input module, the cradle interface element and the communication module, and being programmable to automatically initiate synchronization of at least a portion of the patient information stored in the memory module with corresponding patient information stored in at least one of the server and the healthcare information database for updating, the synchronization being initiated when selected events occur, the selected events being selected from the group consisting of the placement of the portable computing device in the cradle and wireless communication with at least the other computing system to allow intermittent synchronization, the processing module being programmable to provide at least one of the server and the healthcare information database with state data corresponding to selected patient information in the memory module for the determination of whether the information in the memory module is in need of updating or not in need of updating.

43. A PCD as claimed in claim 42, wherein the input module comprises at least one of a keypad, a scanner, an imager, a radio frequency identification reader and an infrared identification reader.

44. A PCD as claimed in claim 42, further comprising an output module for selectively indicating the patient information to the user, the output module comprising at least one of a display, an audio output and a printer.

45. A PCD as claimed in claim 42, wherein the server is operable to send a response to the portable computing device indicating that synchronization is not necessary, the processing module being programmable to defer synchronization.

46. A PCD as claimed in claim 42, wherein the processing module is programmable to generate a structured data stream for transmission to at least one of the server and the healthcare information database, the structured data stream indicating the state data corresponding to a plurality of data types stored in the memory module and selected from the group consisting of patient identifiers, orders, specimen collection container identifiers, location identifiers, user identifiers, cancel order codes, and medication identifiers, the state data being configured to facilitate the determination by the server of whether or not at least a portion of the patient information in the memory module requires synchronization.

47. A PCD as claimed in claim 42, wherein the state data comprises at least one time stamp, and the processing module is programmable to receive and update only a portion of the patient information stored in the memory module from at least one of the server and the healthcare information database, the portion of the patient information corresponding to the patient information in the memory module that has changed in at least one of the server and the healthcare information database since the time stamp provided in the structured data stream.

48. A PCD as claimed in claim 42, wherein the memory module stores patient identifiers, and at least one of specimen collection orders, specimen collection container identifiers, and medication identifiers.

49. A PCD as claimed in claim 48, wherein the memory module further stores user identifiers and physical location identifiers where the portable computing device is assigned for use.

50. A PCD as claimed in claim 49, wherein the physical location identifiers correspond to healthcare locations selected from the group consisting of a ward, a section of a building, a floor, a section of a floor, and a building of a facility.

51. A PCD as claimed in claim 42, wherein the processing module operates a valid data timer element wherein to ensure information on the PCD is substantially recent and to communicate information to a user relating to the suitability of the data at the PCD for selected PCD operator tasks, the information being presented in a form selected from the group consisting of indicating lapsed time since a last successful synchronization, indicating lapsed time since removing the handheld from a cradle or other connection to the server, indicating lapsed time since inserting the handheld into a cradle or other connection to a server, and indicating time until an expiration event occurs when using a countdown module.

52. A portable communication device as claimed in claim 51, wherein the processing module is operable to control the PCD to deactivate temporarily once the valid data timer element has expired or a predetermined amount of time has lapsed.

53. A portable communication device as claimed in claim 51, wherein the processing module is programmable to control the PCD in tracking the duration of time since the last successful synchronization of the PCD with a database, and activating the data output module once a predetermined duration of time is exceeded since synchronization with an external database through or on a server.

54. A portable communication device as claimed in claim 51, wherein the processing module is programmable to control the data output module in accordance with dormant and active phases, the data output module being operated automatically after a certain amount of time has lapsed corresponding to the expiration of the dormant phase and the beginning of the active phase.

55. A portable communication device as claimed in claim 51, wherein the processing module is programmable to control the data output module in accordance with plural phases, the data output module indicating during a first phase that the data is recent, and indicating to the user that the data is not recent after the first phase expires and the a new phase begins.

56. A portable communication device as claimed in claim 55, wherein the processing module is programmable to operate with a time period set by the programmer for the selected amount of time that needs to lapse after the first stage before the new phase begins.

57. A portable communication device as claimed in claim 51, wherein the processing module is programmable to only allow resetting of said valid data timer element by a user with authorization via at least one of a password and system administrative code.

58. A portable communication device as claimed in claim 57, wherein an authorized user can re-enable the PCD by any one of a plurality of methods selected from the group consisting of hitting a reset button on the PCD or corresponding cradle element to commence two-way communication between the server and the PCD, synchronizing the PCD by introducing the PCD into a zone whereby the zone delimits radio frequency communication between an RF receiver integral with the PCD and a RF transceiver element within the zone, introducing the PCD into a cradle, activating a software command executable on the handheld by activating an icon displayed on the handheld screen.

59. A portable computing device (PCD) operating in a healthcare environment comprising:

a input module for receiving data relating to a patient;

a memory module for storing the data, the data comprising at least one physical location in which the PCD is assigned for use, patient identification data for at least the patients located at the physical location assigned to the PCD, and at least a subset of patient healthcare information comprising healthcare data for the patients located at the physical location assigned to the PCD, the healthcare data being selected from the group consisting of specimen sample data, patient identifiers, specimen collection orders, cancellation order codes, and specimen collection container identifiers, user identifiers, and physical location identifiers;

a processing module programmable, when PCD is placed in a cradle, to initiate synchronization with a server to update at least one of the patient identification data and the patient healthcare information stored in the memory module when the data therein is not current, and to defer synchronization to a subsequent time when the data therein is current.

60. A PCD as claimed in claim 59, further comprising an output module for selectively indicating the patient identification data and the patient healthcare information to the user, the output module comprising at least one of a display, an audio output and a printer.