Use of Mobile Communications Device to Direct Medical Workflow and as a Repository of Medical information

• US 20090164253A1
• Filed: 10/27/2006
• Published: 06/25/2009
• Est. Priority Date: 10/27/2005
• Status: Abandoned Application

• Current Assignee: Hugh Lyshkow
• Original Assignee: Hugh Lyshkow
• Inventors: Lyshkow, Hugh
• Application Number:
  US12/084,155
• Publication Number:
  US 20090164253A1
• Time in Patent Office: Days
• US Class Current: 705/3
• CPC Class Codes: G06F 16/5866 using information manually generated, e.g. tags, keywords, comments, manually generated location and time information
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 20/10 relating to drugs or medications, e.g. for ensuring correct administration to patients
• CPC Class Codes: G16H 30/20 for handling medical images, e.g. DICOM, HL7 or PACS
• CPC Class Codes: G16H 40/67 for remote operation
• CPC Class Codes: H04L 63/0272 Virtual private networks
• 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: H04W 12/033 of the user plane, e.g. user's traffic
• CPC Class Codes: H04W 4/12 Messaging; Mailboxes; Announcements

Abstract

This invention comprises DICOM and/or HL7 based methods that enable a healthcare worker equipped with a smartphone with any form of Internet connectivity to securely direct the transfer of medical information from DICOM or HL7 compatible storage sites, including the user'"'"'s own smartphone, to another DICOM/HL7 or non-DICOM compatible device where the information is wanted and needed. A method for securely transferring DICOM and/or HL7 data, by SMS reference, to another smartphone equipped with the software is also disclosed, as is transferal to non-DICOM or HL7 compliant devices by E-Mail or MMS message. This invention uses standard wireless communications and network protocols to expedite the flow of patient-information between physicians, wherever they are located, and repositories of needed patient information, e.g. PACS or HIS, thus improving healthcare and reducing healthcare costs. Finally, an individual can use this invention to store their Personal Health Record (PHR) on their smartphone and securely transport their PHR in its original DICOM or HL7 format.

Claims

1. A method comprising identifying a first data storage device that is configured to store medical information for a patient in a protocol format that complies with jurisdictional laws related to protection of privacy of said medical information;

locating said medical information in said first data storage device; and

directing said first data storage device to securely and automatically send said medical information to a second data storage device in a manner that complies with said jurisdictional laws.

2. The method of claim 1 wherein said protocol format is one of a Digital Imaging and Communication in Medicine (DICOM) protocol format;

a Health Level 7 (HL7) protocol format; and

a protocol format compliant with Health Insurance Portability and Accountability Act (HIPAA).

3. The method of claim 1 further comprising storing said medical information received from said first data storage device at said second data storage device.

4. The method of claim 3 wherein said storing includes storing said medical information at said second data storage device in said protocol format.

5. The method of claim 3 further comprising requiring said second data storage device to send to said first data storage device an acknowledgement of receipt and storage of said medical information and removing said medical information from storage in said first data storage device upon receipt of said acknowledgement from said second data storage device.

6. The method of claim 1 wherein said locating and said directing steps are performed in real-time.

7. The method of claim 1 further comprising providing an operation selection menu on said second data storage device and allowing a user of said second data storage device to perform said locating and directing steps using said operation selection menu.

8. The method of claim 1 wherein said second data storage device is operationally compliant with said protocol format and said first and said second data storage devices are configured to operatively recognize each other, wherein said method further comprises providing a third data storage device that is operationally compliant with said protocol format and configuring said third data storage device to perform said identifying, locating and directing steps.

9. The method of claim 8 further comprising providing a fourth data storage device that is operationally compliant with said protocol format and that is configured to operatively recognize said first data storage device and configuring said third data storage device to direct said first data storage device to securely and automatically send said medical information to said second and said fourth data storage devices.

10. The method of claim 8, wherein each of said first, second, and third data storage devices is one of a non-portable computing device configured to perform secure data communication in a manner that complies with said jurisdictional laws;

a portable, wireless device configured to perform secure data communication in a manner that complies with said jurisdictional laws, wherein said portable, wireless device is one of cellular telephone, a smartphone, a Personal Digital Assistant (PDA), a Tablet PC (Personal Computer), a laptop computer capable of wireless communication, and a Blackberry®

mobile communication device; and

a server computer that is configured to perform secure data communication in a manner that complies with said jurisdictional laws, wherein said sever computer is one of a Picture Archiving and Communications Systems (PACS) server, a Radiology Information Systems (RIS) server, a Hospital Information Systems (HIS) server, a Cardiology Information System (CIS) a Laboratory Information System (LIS), a Magnetic Resonance (MR) imager, a Computerized Tomography (CT) Scanner, and an Electronic Medical Records (EMR) server.

11. The method of claim 1 further comprising storing said medical information received from said first data storage device at said second data storage device in said protocol format;

providing a third data storage device that is operationally compliant with said protocol format, and wherein said first and said third data storage devices are configured to be operatively non-cognizant of each other, whereas each of said first and said third data storage devices is configured to operatively recognize said second data storage device; and

transferring said medical information from said first data storage device to said third data storage device by configuring said second data storage device to securely and automatically send said medical information stored therein to said third data storage device.

12. The method of claim 1 wherein said second data storage device is operationally non-compliant with said protocol format, and wherein said directing step includes performing one of directing said first data storage device to securely and automatically send said medical information to said second data storage device using a MIME (Multipurpose Internet Mail Extension) encoded electronic mail;

directing said first data storage device to securely and automatically send said medical information to said second data storage device as an MMS (Multimedia Messaging Service) message; and

directing said first data storage device to securely and automatically send an electronic mail containing a non-encoded textual and pictorial representation of said medical information to said second data storage device.

13. The method of claim 1 further comprising providing a third data storage device that is operationally compliant with said protocol format;

configuring said third data storage device to obtain location information for said medical information in said first data storage device;

sending said location information to said second data storage device as an SMS (Short Message Service) message; and

configuring said second data storage device to use said location information in said SMS message to direct said first data storage device to securely and automatically send said medical information to said second data storage device.

14. The method of claim 1 wherein said medical information includes one or more of a patient-specific record created for said patient;

a test result for said patient; and

a patient-specific report information for said patient.

15. The method of claim 1 wherein said locating includes locating said medical information in said first data storage device using communication signals generated under said protocol format.

16. The method of claim 1 further comprising establishing a communication link between said first and said second data storage devices via a secure data communication network, wherein said data communication network includes a cellular telephone network, the Internet, a secure Local Area Network (LAN), a Virtual Private Network (VPN), a Wireless Local Area Network (WLAN), a Wide Area Network (WAN), a Bluetooth-based Personal Area Network (PAN), and a broadband wireless access network based on Wi-Fi, WiMax or IrDa protocols, and performing said locating and directing steps over said data communication network.

17. A data communication device configured to execute a program code, which, upon execution, causes said device to identify a first data storage device that is configured to store medical information for a patient in a protocol format that complies with jurisdictional laws related to protection of privacy of said medical information;

locate said medical information in said first data storage device; and

direct said first data storage device to securely and automatically send said medical information to said data communication device in a manner that complies with said jurisdictional laws.

18. The data communication device of claim 17 wherein said program code, upon execution, causes said data communication device to further store said medical information received from said first data storage device in said protocol format;

and securely transfer said medical information from said data communication device to a second data storage device that is operationally compliant with said protocol format, and wherein said first and said second data storage devices are configured to be operatively non-cognizant of each other, whereas each of said first and said second data storage devices is configured to operatively recognize said data communication device.

19. The data communication device of claim 17 wherein said program code, upon execution, causes said data communication device to further establish a communication link with said first data storage device via a secure data communication network, wherein said data communication network includes one or more of a cellular telephone network, the Internet, a secure Local Area Network (LAN), a Virtual Private Network (VPN), a Wireless Local Area Network (WLAN), a Wide Area Network (WAN), a Bluetooth-based Personal Area Network (PAN), and a broadband wireless access network based on Wi-Fi, WiMax or IrDa protocols.

20. The data communication device of claim 17 wherein said program code, upon execution, causes said data communication device to further securely and automatically send said medical information to a second data storage device using a MIME (Multipurpose Internet Mail Extension) encoded electronic mail, wherein said second data storage device is operationally non-compliant with said protocol format;

securely and automatically send said medical information to said second data storage device as an MMS (Multimedia Message Service) message;

or securely and automatically send an electronic mail containing a non-encoded textual and pictorial representation of said medical information to said second data storage device.

21. (canceled)

22. (canceled)

23. (canceled)

24. (canceled)

25. (canceled)

26. (canceled)

27. (canceled)