WO2012015645A2 - Procédé et système informatisés reliant des dispositifs détenus par des patients à des dispositifs détenus par des médecins - Google Patents

Procédé et système informatisés reliant des dispositifs détenus par des patients à des dispositifs détenus par des médecins Download PDF

Info

Publication number
WO2012015645A2
WO2012015645A2 PCT/US2011/044676 US2011044676W WO2012015645A2 WO 2012015645 A2 WO2012015645 A2 WO 2012015645A2 US 2011044676 W US2011044676 W US 2011044676W WO 2012015645 A2 WO2012015645 A2 WO 2012015645A2
Authority
WO
WIPO (PCT)
Prior art keywords
patient
application
healthcare professional
healthcare
communication device
Prior art date
Application number
PCT/US2011/044676
Other languages
English (en)
Other versions
WO2012015645A3 (fr
Inventor
Bryce Benjamin Sady
Eric V. Schultz
Original Assignee
Quantia Communications, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Quantia Communications, Inc. filed Critical Quantia Communications, Inc.
Publication of WO2012015645A2 publication Critical patent/WO2012015645A2/fr
Publication of WO2012015645A3 publication Critical patent/WO2012015645A3/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0823—Network architectures or network communication protocols for network security for authentication of entities using certificates
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
    • G16H40/60—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices
    • G16H40/67—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices for remote operation
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H80/00—ICT specially adapted for facilitating communication between medical practitioners or patients, e.g. for collaborative diagnosis, therapy or health monitoring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H15/00—ICT specially adapted for medical reports, e.g. generation or transmission thereof
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/16—Implementing security features at a particular protocol layer
    • H04L63/168—Implementing security features at a particular protocol layer above the transport layer

Definitions

  • patients have a difficult time relaying appropriate information to a healthcare professional. For instance, many patients are unable, during an appointment, to recall information about their daily lives that may help the physician better understand a patient's illness or the effectiveness of a treatment regimen.
  • Such weaknesses in communication affect a physician's ability to diagnose and treat a patient, and affect whether a health issue can be prevented or resolved.
  • Embodiments of the present invention include computer-implemented methods or corresponding systems for electronically binding (coupling for communication) a patient to a healthcare professional (i.e. their respective communication devices).
  • a central server acts as a gateway between a patient and healthcare professional.
  • the server may include a patient-server module and a physician-server module, wherein each module enables communications between the patient and healthcare professional.
  • the server may include a data store that holds patient information and healthcare professional information.
  • the method includes receiving a message at a patient communication device, the message being sent by or on behalf of a healthcare professional and including a Uniform
  • URI Resource Identifier
  • a communication device determines whether or not a healthcare application is installed on the patient device. If the application is installed, the patient is registered to access certain application features. On the other hand, if the application is not installed, the patient device is redirected to a gateway for obtaining the healthcare application. Once the patient device is redirected to the gateway, a class of the patient device is determined.
  • the step of determining the class of the patient device may include inspecting a platform signature of the device, and based on the platform signature determining the class of the device. Based on the class of the patient device, an appropriate version of the healthcare application is acquired and installed on the patient device.
  • the patient may be registered with the central server. Registration permits the user to have a unique, individual and private account on the central server and for all subsequent interactions to be associated with that particular account.
  • the unique key received by the patient device may then be used to set the features accessible by the healthcare application.
  • the unique key may be specifically chosen by the healthcare professional to enable access to certain features accessible by the application.
  • the unique key may be used to set a permission level of the healthcare professional to enable the healthcare professional to access certain patient information based on the permission level.
  • the healthcare professional may access the patient information via a web portal.
  • a computer-implemented method for displaying collected patient data illustrating statistical trends.
  • Patient data is collected via a patient device.
  • the data may be input into the patient device or obtained via diagnostic devices.
  • the data is grouped into statistical bins, each bin having an equal statistical range.
  • an average value and standard deviation is calculated for the data values within each bin.
  • a graphical polygon is constructed from a midpoint of a first bin to a midpoint of a second bin, and so on. Once the polygon is created, a graphical line is drawn to bisect the polygon.
  • the polygon and associated bisection line is displayed.
  • the graphical illustration of the collected data may be displayed on the patient device or transmitted to another external device for viewing, such as to a physician's computing device.
  • the graphical polygon may be defined by an upper boundary and a lower boundary.
  • the upper boundary of the polygon is defined at each bin by the average data value plus the standard deviation in the respective bin.
  • the lower boundary is also defined at each bin by the average data value less the standard deviation in the respective bin.
  • the present invention provides a method of enrolling a patient to a specific program.
  • the method includes receiving at a patient device a message from a healthcare professional, the message including a Uniform Resource Identifier (URI) encoded with a unique key.
  • URI Uniform Resource Identifier
  • the unique key is read from the URI and then used to set features on an application installed on the patient device.
  • the set features enable enrollment of the patient to a specific program and enable the healthcare professional to electronically (e.g., over a global network) access patient health related data and provide health instruction to the patient via the application.
  • URI Uniform Resource Identifier
  • Fig. 1 is a block diagram of a computer network system electronically binding a patient to a physician according to an embodiment of the present invention.
  • Fig. 2 is a flow diagram of a method of electronically binding a patient (his
  • Fig. 3 is a block diagram of the computer network system of Fig. 1 acquiring a patient's health related data and transmitting the data to a physician.
  • Fig. 4 is block diagram of the computer network system of Fig. 1 enabling the physician to directly communicate with a patient.
  • Fig. 5 is a graph of a "Time of Day" report of collected health related data of a patient according to an embodiment of the present invention.
  • Fig. 6 is a flow chart of a processor method for determining and plotting the "Time of
  • Fig. 7 is graph of a "Trend" report of collected health related data of a patient according to an embodiment of the present invention.
  • Fig. 8 is a schematic diagram of a computer network environment in which embodiments of the present invention are deployed.
  • Fig. 9 is a block diagram of a computer node in the network of Fig. 8.
  • a patient may be monitored by use of diagnostic equipment and medical monitoring equipment such as a glucose meter, pulse oximeter, or peak flow meter.
  • diagnostic equipment may connect to an external device such as a laptop computer or mobile device (e.g., cell phone, PDA, MP3 player).
  • a patient's health related data may be shared with a physician.
  • Current, naive approaches rely on a portal to act as a mediator between physicians and patients.
  • the portal is simply a communications clearing house or non-intelligent conduit.
  • current methods rely on the use of very specific diagnostic equipment and cannot be generalized to areas outside, for example, glucometry, or to multiple brands of a single class of diagnostic equipment. This is due to supporting software being proprietary, and/or brand specific.
  • the methods described above lack specificity and do not allow a physician to proactively establish particularized and individualized connections to patients. Nor do the methods of the art allow patients to establish an arbitrary connection to a physician's existing infrastructure. Further, current methods do not allow physicians to enroll a patient in an electronic monitoring program (i.e. or to be an active participant in the enrolling process).
  • Fig. 1 is a block diagram of a computer network system 100 for binding a patient to a physician according to an example embodiment of the present invention (in the electronic communications sense).
  • the example computer network environment 100 includes a diagnostic devices 118, a patient mobile computing device 50, central server 60, and a physician's clinical infrastructure 55 which includes a web portal 125.
  • the central server 60 includes a patient server module 110, database/data store 115, and physician server module 120.
  • the physician's clinical infrastructure 55 includes, for example, fax, email and Electronic Medical Record (EMR) services.
  • EMR Electronic Medical Record
  • the system 100 includes a method for healthcare professionals to provide a health data collection software application 54 or patient education software application 54 to a patient's mobile computer device 50 (e.g., a smartphone, calculator, media player, or portable entertainment unit).
  • a patient's mobile computer device 50 e.g., a smartphone, calculator, media player, or portable entertainment unit.
  • the method also enables a healthcare professional to subsequently monitor that patient's health information or monitor the patient's completion of disease and wellness education.
  • the physician transmits the unique key to a patient via a central server 60.
  • the unique key is not consumed until the patient has acquired the application 54, for example from a mobile software application marketplace, installed the application 54 on his mobile device 50, and registered with system 100. Once registered as a software application 54/system 100 user, the unique key is consumed and the patient-server module 110 pairs the patient to the healthcare professional.
  • the unique key may be an existing sequence such as a National Provider Identifier, telephone number, or an electronic mail address, or it may be a computer-generated abstraction of these, or it may be randomly generated and assigned.
  • the system 100 includes a method to investigate if the user has already been enrolled, downloaded and installed the software application 54. If the user/patient device 50 already uses the application 54, the patient server module 1 10 pairs the existing user to a new healthcare professional without requiring the user to download new software or deleting any previous relationships or data. All associated healthcare professionals will have access to the patient's health information until or unless the patient removes the physician from the list of authorized viewers.
  • the system 100 includes a method for the healthcare professional to specify what kind of content and appearance should be transmitted with or by the software application 54.
  • the healthcare professional may select to transmit a "heart failure" version of the software application 54.
  • Physician server module 120 stores this setting/information from the physician in database 115, and patient server module 110 employs this information in interactions with the patient device 50 and execution of application 54.
  • the application 54 initializes through patient server module 110 and adjusts in real-time to have the appearance and content of the "heart failure" version of the software application. This is accomplished by the patient device 50 consuming the aforementioned key transmitted in the original URI to obtain current settings from patient server module 110 (i.e., the pertinent physician specified version of software application 54 for this patient at this time).
  • patient server module 110 grants permission to this version of the application to view the additional materials of the "heart failure" (physician selected/set) version of the software application. The user is not prompted to re-download the software application 54 to patient device 50.
  • the patient server module 110 and the physician server module 120 provide data and features to the patient device 50 and physician infrastructure 55 respectively.
  • the patient server module 110 and the physician server module 120 are preferably segregated so that no one service can be exploited to reveal information about another service.
  • Fig. 2 is a flow diagram of a system 100 and its method 200 of binding (in an electronic communications sense) a patient to a physician and, subsequently, capturing patient health related data.
  • the invention method 200 begins at step 201.
  • a health care provider (HCP) or physician sends a message to patient's mobile computing device 50 via the central server 60 and web portal 125.
  • central server 60 attaches a Uniform Resource Identifier (URI) encoded with a unique key or code to the message.
  • URI Uniform Resource Identifier
  • the patient communication device 50 receives the message.
  • the patient at step 225, activates the URI (that is, patient device 50 sends an HTTP request to the URI address).
  • step 230/central server 60 determines whether a health data collection software application 54 or patient education software application 54 is installed on the patient's mobile computing device 50.
  • step 235 redirects the patient device 50 to a gateway/market place for obtaining the software application 54.
  • step 240 the unique key from the original server 60 message of step 215 is temporarily stored.
  • the gateway/market place server 60 determines a class or type of the patient device 50.
  • the server 60 may determine the class of the device 50 by inspecting the HTTP request. For example, the server 60 may inspect a cookie that contains the device 50 profile information sent with the HTTP request. Alternatively, the server 60 may inspect the request for a browser signature identifying the platform that the device 50 is operating on, and based on the platform, the server 60 may determine the class of device 50.
  • the server 60 Upon determining the class of patient device 50, the server 60, at step 250, transmits to patient device 50 a pertinent copy of the software application 54 and the temporarily stored unique key.
  • the software application 54 is installed on the patient mobile computing device 50 and the unique key is locally refreshed at device 50.
  • step 255 launches the software application 54.
  • Step 260 determines whether the current launch is the first time the software application 54 has been launched. If it is the first launch of the software application 54 for patient device 50, then step 270 redirects the patient device 50 to display a registration page.
  • step 275 the patient registers through the displayed registration page to central server 60 as a user of the software application 54.
  • the patient device 50 Upon registration, the patient device 50, at step 280, consumes the unique key.
  • step 265 the patient mobile computing device 50 reads the unique key encoded in the URL Based on the unique key, steps 282 and 284 of central server 60 set up application features and physician permissions (e.g., accessibility to patient data) according to stored data/information in data store 115.
  • application features and physician permissions e.g., accessibility to patient data
  • patient health related data is captured and stored in a mobile computing device storage 52. This data may be streamed or intermittently stored to storage 52. Once all the patient data is stored to storage 52, at step 290, the application 54 or patient server module 110 determines whether the data is transmittable to central server 60. If not, the data is stored in the mobile computing device storage 52. If the data is transmittable, at step 292, patient device 50/application 54 transmits the data to patient server module 110 for storing to server storage 115.
  • physician server module 120 analyzes and processes the patient data as stored in server storage 1 15.
  • the data may be converted to various graphical charts, spread sheets, analysis output/reports showing statistical trends.
  • physician server module 120 generates reports, graphs, and analytical charts. These are rendered as web-pages through web portal 125 and viewed by a physician at step 296.
  • Fig. 3 is a block diagram of computer network system 100 acquiring patient health related data and transmitting the health related data to a physician.
  • Patient mobile computing device 50 includes software application 54 that enables the capturing and transmission of patient health related data. Further, the software application 54 may analyze the captured data and create easy to read reports that are then transmitted to a physician's clinical infrastructure 55.
  • the patient mobile device 50 may be connected, either wirelessly or directly, to diagnostic devices 1 18 such as a glucose meter, pulse oximeter, or peak flow meter.
  • Patient health information may be collected through a variety of means, both human- mediated and directly from diagnostic devices: including wirelessly through Bluetooth, GPS, cellular radio signal, 802.1 la/b/g/n, etc.; wired via an adapter; a camera to collect an
  • interpretable image of a barcode or readout a microphone to collect the audible reading or to transcribe the user's voice; a gyroscope or motion detection system; the input of a patient or virtual keyboard on a touchscreen.
  • the software application 54 pairs health information with a date and time stamp from the internal clock of the mobile computing device 50. If information is to be expressed as a span, the clock of the mobile computing device 50 measures the span. For example, the clock can be used to measure the amount of time an individual is exercising and transmit that information as health data to a central server 60 for analysis.
  • the system 100 may also include a method for patients to use their mobile computing device 50 to find their clinician by providing a minimum amount of information, such as last name and zip code or zip code and specialty or a nearby latitude and longitude and specialty.
  • Patient device 50 transmits a query to central server 60 database 1 15.
  • Central server 60 returns query results to patient device 50.
  • the user can select the correct item from search results, and edit or customize information about each clinician, or contact them.
  • the system 100 may also include a method for patients to transmit reports to clinicians using multiple contact methods managed by a gateway 60; that is, even if the device 50 does not have a modem, patient server module 110 receives reports from patient device 50/application 54 and can fax the report to physicians. Similarly, devices 50 without email or un-configured email can, through patient server module 110, email a report to physicians.
  • Patient server module 110 may communicate reports and patient data to physician server module 120 (and/or database 115) for rendering, through EMR or web portal 125, for physician viewing. Physicians or patients can determine how they prefer to receive reports.
  • the system 100/software application 54 may include a method to help patients plan meals by calculating the nutritional content of arbitrary serving sizes of individual ingredients, summed together.
  • the system 100 may also include a method to help patients store information (in server database 115) regarding frequently consumed meals by automatically recalling food pairing and serving sizes, and storing this information as a single meal data to be recalled at a later date.
  • the system 100 may include a method to allow patients to share the ingredients data, serving sizes, and nutritional content of single meals with other patients, along with a user-generated title for the meal and comments on the meal. Other patients can subsequently rate, comment, or approve the recipe.
  • the system 100, through central server 60 also includes a method to help patients calculate their insulin dosage based on identifying foods they are about to eat or have eaten using database 115, or by manually inputting known carbohydrate values and compensating for known fiber content.
  • Fig. 4 is block diagram of computer network system 100 enabling a physician to directly communicate with a patient.
  • the system 100 includes a remotely-programmable method to notify patients if data has not been collected for a specified duration or time period.
  • This alarm is settable by physicians, through web portal 125, setting parameters, rules, criterion, or the like in patient server module 110 and stored in data store 115.
  • the alarm may also be settable by patients from their mobile computing device 50/software application 54. If the criteria to trip the alarm are met, the user is notified. For example, an alarm may be set if a patient goes one week without making an entry in their food diary.
  • the patient server module 110 Once set, if routine checks of that alarm condition, by the patient server module 110, discover that there has been no food diary entry for that patient for one week, the patient server module 110 generates/transmits reminder messages to the patient device 50 so that the patient is reminded to make entries in his food diary.
  • the system 100 also includes a remotely-programmable method to notify patients on their mobile computing device 50 of impending scheduled tests or visits to the clinic.
  • the system 100 either coordinates with another application for storing appointments and/or dates on the mobile device 50, or stores the appointment on a database 115 of central server 60 and notifies the user at the appropriate time.
  • Fig. 5 is a graph of a "Time of Day" report of collected health related data of a patient according to principles of the present invention.
  • Embodiments of the present invention include a method to produce a report ("Time of
  • Day Report 500 500 that demonstrates statistical trends or models of a typified day or an actual duration.
  • the report is intended, for example, to provide clinicians a "snapshot" of the period since the last visit and can be used to measure a large number (e.g., many days) of patient- determined or home-monitored values such as but not limited to blood pressure, weight, activity, nutrient intake, medications, mood, pain, blood glucose concentration, resting heart rate or blood oxygen concentration.
  • the report is also intended to provide patients a visual cue for establishing tighter control of a particular reading. An example is to display average and variance of glucose concentration in the blood over a typified day by time periods from multiple days worth of data values.
  • physician server module 120 (a) dividing the day into a maximum number of arbitrary, equal-length, portions or bins 510a- «, each with a plurality of data points 550a-rc, (b) calculating the average and standard deviation of values in each bin 510 or division of the day, and (c) displaying a representation of the standard deviation and average by time of day. This can be accomplished using curve-smoothing techniques, bar charts, or lines drawn from the average or standard deviation of one bin 510a to the average or standard deviation of a next bin 510b, ...n, to form a surrounding polygon 530.
  • Division of a day into bins 510a- is based on division with least number of data points greater than one, for the maximum number of divisions of a 24-hour day.
  • a polygon 530 is constructed as follows.
  • a line 540 serving as the average data value is drawn from the midpoint 520a of one division (bin 510a) to the midpoint 520b of the next division (bin 510b) to midpoints 520c, d, ...n in each succeeding division (bins 510 c, d, ...ri).
  • An area 530 (shown shaded) across the first division 510a is defined by an upper boundary value of the average (drawn line 540 value) plus standard deviation in the first division 510a, and a lower boundary value of the average (drawn line value) less the standard deviation for the first division 510a.
  • the area 530 is defined by the average (drawn line value) plus standard deviation across the division 510b as the upper boundary and the average less the standard deviation across the division/bin 510b as the lower boundary.
  • Upper and lower boundaries are similarly defined for each division/bin 510 c, d, ... n.
  • the generated polygon (shaded area) 530 is bisected by line 540 representing the change in average data value across divisions/bins 510a- ⁇ .
  • Fig. 6 is a flow chart of a method for determining and plotting the "Time of Day" report 500 of Fig. 5.
  • the invention method 600 begins at step 601.
  • patient health related data is obtained from data store 115.
  • each value (as uploaded from devices 50 to patient server module 110 and stored in data store 115 by module 110) from the retrieved data is analyzed.
  • method 600 determines whether the subject value is within a clinically "normal" range. If the value is normal, step 625 plots the value in the subject graph 500 as "inside bounds.” If the value is not normal, step 615 plots the value "outside bounds.”
  • the inside bound and outside bound values may be plotted and rendered in graph 500 in different colors, shapes, or sizes to distinguish each type of value.
  • a maximum "y” value is determined. Subsequently, at step 635, each value is grouped into bins by dividing the day into a maximum number of arbitrary, equal-length, portions or bins 510a- «. Within each bin 510, at steps 640 and 645, a per bin average value and standard deviation is calculated for all values falling within the respective bin 510a- «. At step 650, an x-axis offset is determined.
  • a polygon 530 is created by plotting and filling across each bin 510 the respective average values +/- the standard deviations calculated by steps 640 and 645.
  • the polygon 530 is bisected by plotting and connecting the average value from one bin 510a- to the next.
  • Fig. 7 is graph of a "Trend" report 700 of collected health related data of a patient and generated by physician server module 120.
  • a time axis (x-axis) 705 is a proportional axis with the first time value in a data set on the left, and the last time value on the right. Then data points are distributed proportionately on this axis 705.
  • a Least Squares line 710 is plotted by beginning with the ⁇ -intercept 715 and plotting for the slope at the maximum value of the x-axis. Line 710 visually represents to a physician a trend for this patient. For example, if the data points are measured blood sugar levels over a span of time for a patient, then line 710 visually represents an upward trend in blood sugar level of the patient.
  • FIG. 8 illustrates a computer network or similar digital processing environment in which the foregoing and other embodiments of the present invention may be implemented.
  • Client computer(s)/devices 50 and server computer(s) 60 provide processing, storage, and input/output devices executing application programs and the like.
  • Client computer(s)/devices 50 can also be linked through communications network 70 to other computing devices, including other client devices/processes 50 and server computer(s) 60.
  • Servers 60 in Figs. 8 and 9 may include application store servers and the like.
  • Communications network 70 can be part of a remote access network, a global network (e.g., the Internet), a worldwide collection of computers, Local area or Wide area networks, and gateways that currently use respective protocols (TCP/IP, Bluetooth, etc.) to communicate with one another.
  • Other electronic device/computer network architectures are suitable.
  • Fig. 9 is a diagram of the internal structure of a computer (e.g., client processor/device 50 or server computers 60) in the computer system of Fig. 8.
  • Each computer 50, 60 contains system bus 79, where a bus is a set of hardware lines used for data transfer among the components of a computer or processing system.
  • Bus 79 is essentially a shared conduit that connects different elements of a computer system (e.g., processor, disk storage, memory, input/output ports, network ports, etc.) that enables the transfer of information between the elements.
  • Attached to system bus 79 is I/O device interface 82 for connecting various input and output devices (e.g., keyboard, mouse, displays, printers, speakers, etc.) to the computer 50, 60.
  • Network interface 86 allows the computer to connect to various other devices attached to a network (e.g., network 70 of Fig. 8).
  • Memory 90 provides volatile storage for computer software instructions 92 and data 94 used to implement an embodiment of the present invention (e.g., patient server module 110, physician server module 120, and respective processes 200, 600 for binding a patient to a healthcare professional, determining and plotting reports 500, 700, and the like).
  • Data 94 includes database/store 115.
  • Disk storage 95 provides non- volatile storage for computer software instructions 92 and data 94 used to implement an embodiment of the present invention.
  • Central processor unit 84 is also attached to system bus 79 and provides for the execution of computer instructions.
  • the processor routines 92 and data 94 are a computer program product (generally referenced 92), including a computer readable medium (e.g., a removable storage medium such as one or more DVD-ROM's, CD-ROM's, diskettes, tapes, etc.) that provides at least a portion of the software instructions for the invention system.
  • Computer program product 92 can be installed by any suitable software installation procedure, as is well known in the art.
  • at least a portion of the software instructions may also be downloaded over a cable, communication and/or wireless connection.
  • the invention programs are a computer program propagated signal product 107 embodied on a propagated signal on a propagation medium (e.g., a radio wave, an infrared wave, a laser wave, a sound wave, or an electrical wave propagated over a global network such as the Internet, or other network(s)).
  • a propagation medium e.g., a radio wave, an infrared wave, a laser wave, a sound wave, or an electrical wave propagated over a global network such as the Internet, or other network(s).
  • Such carrier medium or signals provide at least a portion of the software instructions for the present invention routines/program 92.
  • the propagated signal is an analog carrier wave or digital signal carried on the propagated medium.
  • the propagated signal may be a digitized signal propagated over a global network (e.g., the Internet), a telecommunications network, or other network.
  • the propagated signal is a signal that is transmitted over the propagation medium over a period of time, such as the instructions for a software application sent in packets over a network over a period of milliseconds, seconds, minutes, or longer.
  • the computer program product 92 is carried on a propagation medium that the computer system 50 may receive and read, such as by receiving the propagation medium and identifying a propagated signal embodied in the propagation medium, as described above for computer program propagated signal product.
  • carrier medium or transient carrier encompasses the foregoing transient signals, propagated signals, propagated medium, storage medium and the like.
  • the invention system maybe implemented in WTRUs (wireless transmit/receive units), such as cell phones and PDAs.
  • WTRUs wireless transmit/receive units
  • cell phones and PDAs such as cell phones and PDAs.

Abstract

Un procédé et un système informatisés relient électroniquement un dispositif de communication détenu par un patient à un ou plusieurs dispositifs détenus par un professionnel de la santé grâce à la transmission d'un message comprenant un identificateur de ressource uniforme (URI) codé à l'aide d'une clé unique. Cette clé unique est utilisée par le dispositif de communication du patient afin d'appairer ledit patient à un professionnel de la santé bien précis et permettre la communication électronique. Lorsqu'ils sont appairés, il est possible que le patient et le professionnel de la santé soient en contact direct. De plus, la liaison entre le dispositif du patient et le ou les dispositifs du professionnel de la santé permet la collecte de données relatives à la santé et l'analyse des données constituant des informations statistiques. Les données et informations qui en résultent peuvent être affichées d'une manière qui montre une tendance statistique. Cet affichage peut aider les professionnels de la santé à poser un diagnostic et à traiter le patient.
PCT/US2011/044676 2010-07-27 2011-07-20 Procédé et système informatisés reliant des dispositifs détenus par des patients à des dispositifs détenus par des médecins WO2012015645A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US36803910P 2010-07-27 2010-07-27
US61/368,039 2010-07-27

Publications (2)

Publication Number Publication Date
WO2012015645A2 true WO2012015645A2 (fr) 2012-02-02
WO2012015645A3 WO2012015645A3 (fr) 2012-03-29

Family

ID=45530656

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2011/044676 WO2012015645A2 (fr) 2010-07-27 2011-07-20 Procédé et système informatisés reliant des dispositifs détenus par des patients à des dispositifs détenus par des médecins

Country Status (1)

Country Link
WO (1) WO2012015645A2 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015095655A1 (fr) * 2013-12-19 2015-06-25 Opentv, Inc. Soins de santé à distance via un système de communication de télévision
SE543935C2 (en) * 2016-09-06 2021-09-28 Addi Medical Ab Healthcare monitoring method and system for secure communication of patient data

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060206013A1 (en) * 2005-02-28 2006-09-14 Rothman Michael J System and method for improving hospital patient care by providing a continual measurement of health
US20080077072A1 (en) * 2006-08-15 2008-03-27 Richard Keenan Analyte detection system with user interface providing trend display
US20080077431A1 (en) * 2006-09-25 2008-03-27 Calder William J Digital communication and monitoring system for patients and doctors
US20090150831A1 (en) * 2007-12-07 2009-06-11 Roche Diagnostics Operations, Inc. Method and system for configuring a consolidated software application

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060206013A1 (en) * 2005-02-28 2006-09-14 Rothman Michael J System and method for improving hospital patient care by providing a continual measurement of health
US20080077072A1 (en) * 2006-08-15 2008-03-27 Richard Keenan Analyte detection system with user interface providing trend display
US20080077431A1 (en) * 2006-09-25 2008-03-27 Calder William J Digital communication and monitoring system for patients and doctors
US20090150831A1 (en) * 2007-12-07 2009-06-11 Roche Diagnostics Operations, Inc. Method and system for configuring a consolidated software application

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015095655A1 (fr) * 2013-12-19 2015-06-25 Opentv, Inc. Soins de santé à distance via un système de communication de télévision
SE543935C2 (en) * 2016-09-06 2021-09-28 Addi Medical Ab Healthcare monitoring method and system for secure communication of patient data
US11188676B2 (en) 2016-09-06 2021-11-30 Addi Medical Ab Healthcare monitoring method and system for secure communication of patient data

Also Published As

Publication number Publication date
WO2012015645A3 (fr) 2012-03-29

Similar Documents

Publication Publication Date Title
Sieverdes et al. Improving diabetes management with mobile health technology
Farmer et al. A real-time, mobile phone-based telemedicine system to support young adults with type 1 diabetes.
US10747849B2 (en) Facilitating health management of subjects
CA2751173C (fr) Kiosque de sante
EP2988671B1 (fr) Système de prise en charge du diabète au moyen d'un dispositif médical
JP2022514646A (ja) 断続的監視
CN104137108B (zh) 用于移动电话的糖尿病管理应用
Shaw et al. Self-monitoring diabetes with multiple mobile health devices
US20170061074A1 (en) Telemedicine system and method
US20030036683A1 (en) Method, system and computer program product for internet-enabled, patient monitoring system
US10103947B2 (en) Processing of portable device data
US20040172447A1 (en) Systems and methods for managing data
US20080154099A1 (en) Health monitoring system and method
AU2016343818A1 (en) A system and method for mobile platform designed for digital health management and support for remote patient monitoring
US20080077436A1 (en) Home based healthcare system and method
US7798961B1 (en) Acquisition and management of time dependent health information
US20220020487A1 (en) Processing of Portable Device Data
KR20170130493A (ko) 환자 간호 시스템
MX2013000005A (es) Sistema y metodo para cumplimiento de medicacion.
US20150134344A1 (en) Personal Health Data Gathering for Incentive and Insurance Rating Purposes
US20140214443A1 (en) Systems and Methods for Displaying Metrics Associated With a Health Improvement Program
Radin et al. The Healthy Pregnancy Research Program: transforming pregnancy research through a ResearchKit app
US20160015321A1 (en) Oral health monitoring and management
David et al. Innovative health informatics as an effective modern strategy in diabetes management: a critical review
Yingling et al. An evaluation of digital health tools for diabetes self-management in Hispanic adults: exploratory study

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11812959

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11812959

Country of ref document: EP

Kind code of ref document: A2