Patient information management method

• US 20080114689A1
• Filed: 10/31/2007
• Published: 05/15/2008
• Est. Priority Date: 11/03/2006
• Status: Abandoned Application

• Current Assignee: RIC INVESTMENTS LLC (Respironics Incorporated)
• Original Assignee: RIC INVESTMENTS LLC (Respironics Incorporated)
• Inventors: Ball, Scott, Psynik, Kevin, Tracey, Steve, Barker, Bob, Bowen, Kevin, Paul, Zachary D.
• Application Number:
  US11/932,009
• Publication Number:
  US 20080114689A1
• Time in Patent Office: Days
• US Class Current: 705/51
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G16H 10/20 for electronic clinical trials or questionnaires
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 15/00 ICT specially adapted for medical reports, e.g. generation or transmission thereof
• CPC Class Codes: G16H 40/20 for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
• CPC Class Codes: G16H 40/63 for local operation
• CPC Class Codes: G16H 40/67 for remote operation
• CPC Class Codes: G16H 50/20 for computer-aided diagnosis, e.g. based on medical expert systems
• CPC Class Codes: G16H 50/70 for mining of medical data, e.g. analysing previous cases of other patients
• CPC Class Codes: H04L 2209/60 Digital content management, e.g. content distribution
• CPC Class Codes: H04L 2209/80 Wireless network architectures or network communication protocols for wireless network security H04W12/00
• CPC Class Codes: H04L 2209/88 Medical equipments
• CPC Class Codes: H04L 63/0272 Virtual private networks
• CPC Class Codes: H04L 9/3271 using challenge-response

Abstract

A computer-implemented system for patient information management, including at least one database having a plurality of data fields populated with patient data, clinician data, physician data, healthcare provider data, device data, medical data, health data, presentation data, identification data, administrator data, or any combination thereof. The system provides a patient information interface in communication with the at least one database for selectively and dynamically presenting data fields to the users that are configured for access to the interface. A set of program instructions is configured to facilitate communication of data between at least one patient device and the system. A communication for patient information management and a method of facilitating the secure transmission of data of a patient device over a network to a patient management system are also disclosed.

Claims

1. A method of facilitating the secure transmission of data of a patient device over a network to a patient management system, the method comprising the steps of:

enabling communication between the patient device and a communications device; and

transmitting, by the communications device, data to a patient management system server, wherein the transmission occurs over a network, and wherein the data is patient data, device data, medical data, health data, presentation data, identification data, or any combination thereof.

2. The method of claim 1, wherein the network is a Virtual Private Network, the Internet, a wireless local area network, a wireless wide area network, a Wi-Fi network, or any combination thereof.

3. The method of claim 1, wherein the method further comprises the steps of:

transmitting, by the communications device, patient data to an Internet service provider server; and

transmitting, by the Internet service provider server, patient data to the patient management system server.

4. The method of claim 1, wherein the method further comprises the step of transferring, by a storage device, patient data to an intermediate server in communication with the communications device.

5. The method of claim 1, wherein the communication between the communications device and the patient management system server are secure communications conducted according to a cryptographic protocol, the Secure Sockets Layer protocol, the Transport Socket Security protocol, or any combination thereof.

6. The method of claim 1, wherein the communications device initiates contact with the patient management system server.

7. The method of claim 1, further comprising the step of authenticating communications from the communications device through a remote data acquisition server in communication with the patient management system server.

8. The method of claim 1, wherein the communication between the communications device and the patient management system are conducted according to a challenge protocol.

9. The method of claim 8, wherein the challenge protocol comprises:

pre-providing a challenge algorithm to the patient device, the communications device, or any combination thereof;

transmitting a key from the patient management system server to the communications device;

processing the key by the patient device and/or the communications device according to the challenge algorithm, thereby obtaining a response key;

transmitting the response key from the communications device to the patient management system server; and

determining whether the response key is valid by comparing the response key to an expected response key.

10. The method of claim 9, further comprising the steps of:

if the response key is valid establishing further secure communications between the patient management system server and the communications device; and

if the response key is invalid;

closing the communication link between the patient management system server and the communications device;

requesting a retry by the communications device;

sending a subsequent key from the patient management system server to the communications device;

generating a notification by the patient management system server for a user;

or

any combination thereof.

11. The method of claim 8, further comprising the steps of:

pre-providing a response key format to the patient device, the communications device, or any combination thereof;

transmitting the response key in the response key format from the communications device to the patient management system server; and

determining whether the response key format is valid by comparing the response key format to an expected response key format.

12. The method of claim 11, further comprising the steps of:

if the response key format is valid, establishing further secure communications between the patient management system server and the communications device; and

if the response key format is invalid;

closing the communication link between the patient management system server and the communications device,

requesting a retry by the communications device,

sending a subsequent key from the patient management system server and the communications device,

generating a notification by the patient management system server for a user, or

any combination thereof.

13. The method of claim 8, further comprising the steps of:

transmitting, by the patient management system server patient data, device data, medical data, health data, presentation data, identification data, or any combination thereof, to the communications device; and

communicating the transmitted data from the communications device to the patient device.

14. The method of claim 13, wherein the transmitted data is prescription data.

15. The method of claim 13, wherein the transmitted data is device data, the method further comprising the step of modifying, based upon the transmitted device data, at least one patient device setting, at least one patient device configuration, or any combination thereof.

16. The method of claim 1, further comprising the step of visually indicating, by the communications device, call status data.

17. A method of displaying medical information for a plurality of patients in a consolidated format;

displaying a patient identifier associated with each patient;

displaying a graphical representation of notification data related to such a patient at a location proximate to the patient identifier; and

providing a link to review details of the notification data represented by the graphical representation.

18. A method of providing data to a physician having a plurality of patients, wherein a first patient in the plurality of patients is associated with a first HCP/clinician and a second patient in the plurality of patients is associated with a second HCP/clinician, comprising:

providing a central database that contains first information associated with the first patient and second information associated with the second patient;

providing the first HCP/clinician access to the first information and not the second information;

providing the second HCP/clinician access to the second information and not the first information; and

providing the physician access to both the first information and the second information.

19. A method of providing notifications between various users in a data management system, comprising:

providing a data management system that includes patient information associated with a patient;

providing a home care provider (HCP)/clinician associated with such a patient, a physician associated with such a patient, or both, access to the patient information;

entering a notification by such physician into the data management system; and

automatically sending the notification to such a patient and to such an HCP/clinician.

20. A method of providing notifications between various users in a data management system, comprising:

providing a data management system that includes patient information associated with a patient;

providing a home care provider (HCP)/clinician associated with such a patient, a physician associated with such a patient, or both, access to the patient information;

entering a notification by such an HCP/clinician into the data management system;

automatically sending the notification to such a patient; and

providing such an HCP with an option to send the notification to such a physician.