MEDICAL DATA MANAGEMENT SYSTEM AND PROCESS

• US 20140200923A1
• Filed: 03/14/2014
• Published: 07/17/2014
• Est. Priority Date: 08/06/2004
• Status: Active Grant

• Current Assignee: Medtronic Minimed Incorporated (Medtronic Plc)
• Original Assignee: Medtronic Minimed Incorporated (Medtronic Plc)
• Inventors: COHEN, Gary, GOLDSMITH, Joel, ROLLER, Pam S., WIDRAN, Sanford, PATTERSON, George W., DAUGHERTY, James R., ANTWERP, William P. VAN
• Granted Patent: US 10,073,948 B2
• Time in Patent Office: Days
• US Class Current: 705/3
• CPC Class Codes: A61B 2560/0271 using a remote monitoring unit
• CPC Class Codes: A61B 5/0002 Remote monitoring of patients using telemetry, e.g. transmission of vital signals via a communication network A61B5/07 takes precedence; transmission systems for measured values G08C; transmission H04B; transmission of digital information H04L; wireless communication networks H04W
• CPC Class Codes: A61B 5/14532 for measuring glucose, e.g. by tissue impedance measurement
• CPC Class Codes: A61M 2205/3553 remote, e.g. between patient's home and doctor's office
• CPC Class Codes: A61M 2205/52 with memories providing a history of measured variating parameters of apparatus or patient
• CPC Class Codes: A61M 5/1723 using feedback of body parameters, e.g. blood-sugar, pressure measurement of body parameters A61B5/00
• CPC Class Codes: G06F 2221/2113 Multi-level security, e.g. mandatory access control
• CPC Class Codes: G06F 2221/2141 Access rights, e.g. capability lists, access control lists, access tables, access matrices
• 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 15/00 ICT specially adapted for medical reports, e.g. generation or transmission thereof
• CPC Class Codes: G16H 20/10 relating to drugs or medications, e.g. for ensuring correct administration to patients
• CPC Class Codes: G16H 20/17 delivered via infusion or injection
• CPC Class Codes: G16H 20/30 relating to physical therapies or activities, e.g. physiotherapy, acupressure or exercising
• 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 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: G16H 70/20 relating to practices or guidelines

Abstract

Systems and processes for managing data relating to one or more medical or biological conditions of a plurality of subjects (such as patients) over a wide area network, such as the Internet, may be employed for diabetes subjects or subjects with other medical conditions requiring monitoring and/or treatment over time. Such systems and processes provide various functions for several types of users, including patients or subject-users, healthcare provider-users and payor entity-users and combinations thereof, which allow for improved treatment and medical data management of individual subjects and groups of subjects and which allow collection and analysis of aggregate data from many subject sources, for improving overall healthcare practices of providers and subjects (e.g., patients).

Claims

1-71. -71. (canceled)

72. A system for managing medical data on a communication network, the system comprising at least one server connectable for communication on the communication network with at least one healthcare provider computer, at least one computer of an authorized payor entity, and computers of other users, the at least one server being configured for:

receiving payment request information from the at least one healthcare provider computer, the payment request information being associated with a medical treatment of a subject by a healthcare provider;

storing the received payment request information having individual identifiers that identify the subject in a first storage area, and storing medical data that is free of individual identifiers in the second storage area, the medical data being associated with the medical treatment of the subject by the at least one healthcare provider;

providing access to stored payment request information in the first storage area for the authorized payor entity, but not for other users on the communication network; and

providing access to stored medical data in the second storage area for the authorized payor entity and the other users on the communication network.

73. A system as recited in claim 72, the at least one server being further configured for inhibiting access to stored medical data in the first storage area by other users that are not the authorized payor entity.

74. A system as recited in claim 72, wherein individual identifiers comprise at least one of a subjects name, a subject'"'"'s address and a subject'"'"'s work-place.

75. A system as recited in claim 72, the at least one server being further configured for sending a message to the at least one computer of the authorized payor entity, upon receiving the payment request information from the at least one healthcare provider computer, the message indicating that payment request information has been received.

76. A system as recited in claim 75, the at least one server being further configured for receiving a confirmation from the healthcare provider to send the payment request to the authorized payor entity, and sending a message to the at least one computer of the authorized payor entity, in response to receiving the confirmation.

77. A system as recited in claim 72, the at least one server being further configured for receiving the medical data from at least one subject support device with individual identifiers associated with a subject who is using the subject support device.

78. A system as recited in claim 72, wherein the first data storage area and the second data storage area comprise two separate sections of a single data storage device.

79. A system as recited in claim 72, wherein the first data storage area and the second data storage area comprise two separate data storage devices.

80. A method for managing medical data on a communication network on which at least one server is connected for communication with at least one healthcare provider computer, at least one computer of an authorized payor entity, and computers of other users, the method comprising:

receiving payment request information from the at least one healthcare provider computer, the payment request information being associated with a medical treatment of a subject by a healthcare provider;

storing the received payment request information having individual identifiers that identify the subject in a first storage area, and storing medical data that is free of individual identifiers in the second storage area, the medical data being associated with the medical treatment of the subject by the at least one healthcare provider;

providing access to stored payment request information in the first storage area for the authorized payor entity, but not for other users on the communication network; and

providing access to stored medical data in the second storage area for the authorized payor entity and the other users on the communication network.

81. A method as recited in claim 80, further comprising inhibiting access to stored medical data in the first storage area by other users that are not the authorized payor entity.

82. A method as recited in claim 80, wherein individual identifiers comprise at least one of a subjects name, a subject'"'"'s address and a subject'"'"'s work-place.

83. A method as recited in claim 80, further comprising sending a message to the at least one computer of the authorized payor entity upon receiving the payment request information from the at least one healthcare provider computer, the message indicating that payment request information has been received.

84. A method as recited in claim 83, further comprising receiving a confirmation from the healthcare provider to send the payment request to the authorized payor entity, and sending a message to the at least one computer of the authorized payor entity, in response to receiving the confirmation.

85. A method as recited in claim 80, further comprising receiving the medical data from at least one subject support device with individual identifiers associated with a subject who is using the subject support device.

86. A method as recited in claim 80, wherein the first data storage area and the second data storage area comprise two separate sections of a single data storage device.

87. A method as recited in claim 80, wherein the first data storage area and the second data storage area comprise two separate data storage devices.

88. A system for managing medical data on a communication network, the system comprising:

at least one server connectable for communication over the communication network for communication with at least one computer of an authorized payor entity and computers of other users;

at least one data storage device that stores payment request information with individual identifiers in a first storage area, the payment request information being associated with a medical treatment provided to a subject, the individual identifiers identifying the subject;

the at least one data storage device storing medical data that is free of individual identifiers in the second storage area, the medical data being associated with the medical treatment of the subject;

the at least one server providing access to stored payment request information in the first storage area for the authorized payor entity, but not for other users on the communication network; and

the at least one server providing access to stored medical data in the second storage area for the authorized payor entity and the other users on the communication network.

89. A system as recited in claim 88, wherein the at least one server inhibits access to stored medical data in the first storage area by other users that are not the authorized payor entity.

90. A system as recited in claim 88, wherein individual identifiers comprise at least one of a subjects name, a subject'"'"'s address and a subject'"'"'s work-place.

91. A system as recited in claim 88, wherein the at least one server sends a message to the at least one computer of the authorized payor entity, upon receiving the payment request information, the message indicating that payment request information has been received.