Online monitoring of patient for routine checkups

A method, system, and computer program product for performing remote monitoring of a patient during a routine checkup is provided. A local server is adapted for receiving instructions from a medical professional and processing the instructions into commands for remote broadcast. A network device is in remote communication with the local server. At least one modular diagnostic tool is communicable with the network device over a standardized communications link. The at least one modular diagnostic tool is operable by the medical professional based on a second portion of the commands for remote broadcast to obtain the diagnostic information. Upon a communications connection between the modular diagnostic tool and the network device, an automated process is executed to upload the diagnostic information from the modular diagnostic tool to the local server for collection and analysis.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates in general to computers, and more particularly to apparatus, method and computer program product embodiments for online monitoring of remote medical patients by a medical professional using a data processing system.

2. Description of the Related Art

Computers and computer systems are found in a variety of settings in today's society. Computing environments and networks may be found at home, at work, at school, in government, and in other settings. Computers and computer systems, including associated data storage, are increasingly being utilized to lower costs, increase productivity, provide security, and a host of other functions.

In the medical industry, the resources of medical professionals are increasingly spread in a variety of areas. In addition, demand for care has increased, while the supply, particularly of primary care physicians, has not. As a result, an alternative mechanism to meet medical need, such as providing contact with medical professionals for regular checkups, is needed. This alternative mechanism would help the medical professional better manage the increasing demand on their available resources, principally time, and allow for greater access to care for more patients. Currently, an effort is underway to facilitate medical consultations using computers and computing systems. This current effort, as of yet, has not fully addressed the need.

SUMMARY OF THE INVENTION

In light of the foregoing, a need exists for a computer-facilitated mechanism linking a local physician interface to a remote patient interface, as well as a tool connectable to the patient interface that can read the patient's physical condition, to provide diagnostic information to the physician as well as treatment information to the patient in lieu of a face-to-face routine checkup.

Accordingly, in one embodiment, by way of example only, a system for performing remote monitoring of a patient during a routine checkup is provided. A local server is adapted for receiving instructions from a medical professional and processing the instructions into commands for remote broadcast. A network device is in remote communication with the local server. The network device is adapted for processing the commands for remote broadcast received from the local server. At least one modular diagnostic tool is communicable with the network device over a standardized communications link. The at least one modular diagnostic tool is adapted for obtaining diagnostic information from the patient. A first portion of the commands for remote broadcast includes directions to the patient for installation of the at least one modular diagnostic tool in the network device. The at least one modular diagnostic tool is initialized for operation by the network device. The at least one modular diagnostic tool is operable by the medical professional based on a second portion of the commands for remote broadcast to obtain the diagnostic information. The network device, when connected with the at least one modular diagnostic tool over the standardized communications link, executes an automated process to upload the diagnostic information to the local server for collection and analysis by the medical professional.

In an additional embodiment, again by way of example only, a method for performing remote monitoring of a patient during a routine checkup by at least one processor device in communication with a memory device is provided. Instructions from a medical professional are received on a local server. The instructions are processed into commands for remote broadcast. The commands are forwarded for remote broadcast to a network device over a network path. The commands for remote broadcast received from the local server are processed on the network device. The patient is directed to install a modular diagnostic tool in the network device using a first portion of the commands for remote broadcast. The modular diagnostic tool is initialized for operation and communication with the network device over a standardized communications link. The medical professional operates the modular diagnostic tool over the network path using a second portion of the commands for remote broadcast to obtain diagnostic information. Upon a communications connection between the modular diagnostic tool and the network device, an automated process is executed to upload the diagnostic information from the modular diagnostic tool to the local server for collection and analysis by the medical professional.

In still another embodiment, again by way of example only, a computer program product for performing remote monitoring of a patient during a routine checkup by at least one processor device in communication with a memory device is provided. The computer program product comprises a computer-readable storage medium having computer-readable program code portions stored therein. The computer-readable program code portions comprise a first executable portion for receiving instructions from a medical professional on a local server, a second executable portion for processing the instructions into commands for remote broadcast, a third executable portion for forwarding the commands for remote broadcast to a network device over a network path, a fourth executable portion for processing the commands for remote broadcast received from the local server on the network device, a fifth executable portion for directing the patient to install a modular diagnostic tool in the network device using a first portion of the commands for remote broadcast, a sixth executable portion for initializing the modular diagnostic tool for operation and communication with the network device over a standardized communications link, a seventh executable portion for operating the modular diagnostic tool by the medical professional over the network path using a second portion of the commands for remote broadcast to obtain diagnostic information, and an eighth executable portion for, upon a communications connection between the modular diagnostic tool and the network device, performing an automated process on the network device to upload the diagnostic information from the modular diagnostic the local server for collection and analysis by the medical professional.

DETAILED DESCRIPTION OF THE DRAWINGS

The illustrated embodiments below provide mechanisms for communication between a remote patient and a local medical professional over one or more communications links, whereby the medical professional is capable of providing online instruction and related assistance to the patient, while obtaining biometric information (herein also referred to as diagnostic information) from the patient using a modular diagnostic tool.

In addition, the illustrated embodiments provide, through the use of the diagnostic tool, mechanisms whereby the patient may continue to obtain information on an offline basis (either himself or by operation of other medical personnel such as a lab technician). When a connection is again made with the local medical professional, an automated process may be executed to upload the supplemental information from the diagnostic tool to the local medical professional. As will be further described, additional benefits, features, and improvements to current systems and techniques are discussed.

Embodiments of the invention may be described herein in terms of functional and/or logical block components and various processing steps. It should be appreciated that such block components may be realized by any number of hardware, software, and/or firmware components configured to perform the specified functions. For example, an embodiment of the invention may employ various integrated circuit components, e.g., memory elements, digital signal processing elements, logic elements, look-up tables, or the like, that may carry out a variety of functions under the control of one or more microprocessors or other control devices. In addition, those skilled in the art will appreciate that embodiments of the present invention may be practiced in conjunction with any number of data transmission and data formatting protocols and that the system described herein is one example embodiment of the invention.

For the sake of brevity, conventional techniques related to signal processing, data transmission, signaling, network control, the 802.11 family of specifications, wireless networks, additional communications systems and specifications, and other functional aspects of the systems (and the individual operating components of the systems) may not be described in detail herein. Furthermore, the connecting lines shown in the various figures contained herein are intended to represent example functional relationships and/or physical couplings between the various elements. It should be noted that many alternative or additional functional relationships or physical connections may be present in an embodiment of the invention.

The following description refers to elements or nodes or features being “connected” or “coupled” together. As used herein, unless expressly stated otherwise, “connected” means that one element/node/feature is directly joined to (or directly communicates with) another element/node/feature, and not necessarily mechanically. Likewise, unless expressly stated otherwise, “coupled” means that one element/node/feature is directly or indirectly joined to (or directly or indirectly communicates with) another element/node/feature, and not necessarily mechanically. The term “exemplary” is used in the sense of “example,” rather than “model.” Although the figures may depict example arrangements of elements, additional intervening elements, devices, features, or components may be present in an embodiment of the invention.

Referring now toFIG. 1, an exemplary system10for providing remote monitoring of a patient by a medical professional is depicted. System10includes a local server12. An exemplary local server12will be described inFIG. 2, following. Local server12, as the skilled artisan will appreciate, may include a variety of computing environments and platforms. In most cases, local server12includes one or more processing devices in communication with one or more memory devices. In some cases, a database12is operational on, or in conjunction with, the local server12. Database12may store patient information, such as a history of blood glucose test results. In addition, database12may store drug information, such as a patient's prescription drug history as prescribed by the medical professional.

The medical professional, such as a physician or physician assistant, communicates with the local server12via a connected communications channel16. As the skilled artisan will appreciate, communications channel16may comprise a host of available communications schemes, such as an intranet, an extranet, a wide area network (WAN), a local area network (LAN), Ethernet, wireless, and the like. Channel16is connected to a local interface18. Local interface18includes a workstation26(local client) of the local server12. Workstation26may also include a number of computing components, and be connected with a number of peripheral components, such as the depicted graphical user interface (GUI)20, the keyboard22, and mouse24input devices. In one embodiment, for example, the database14operational on local server12is accessed by a physician through the workstation26and viewed on GUI20.

The medical professional may use the workstation26, in combination with local server12, to access additional patient information stored on an interconnected data storage subsystem28. For example, the data storage subsystem28may store a library of drug information, such as drug interaction data, that may be accessed when the medical professional is prescribing a drug to a particular patient to obtain potential adverse drug interaction information that may be provided to the medical professional via workstation26.

To communicate with a remote patient, local server12is coupled to network30, which again, may include a host of network paths. For example, at least a portion of network30may include the world-wide-web (WWW). To facilitate such communication, local server12, as well as workstation26and data storage subsystem28may be compliant with a number of communications protocols, such as transport control protocol (TCP)/internet protocol (IP).

A patient interface34is connected through an additional communications channel32to the network30. Patient interface34may again include a number of computing components. In one example, the interface34may also include a personal computer with an integrated GUI36, attached keyboard38, and mouse40. Patient interface34may also include additional input devices such as a webcam/microphone58for facilitating voice/visual input from the patient.

The medical professional supplies a network device46to the patient. Medical device46is adapted to establish communications links with the patient interface34and/or network30via communications channels42and44, respectively. In this regard, network device46may use an existing communications channel (such as a universal serial bus, or USB) to establish a communications link between the network device46and the patient interface34. Alternatively, network device46may include a communications adapter (as will be further described) enabling the network device46to establish connectivity directly to network30(such as by scanning available wireless networks).

Network device46will be further described in detail, following. As an overview of the provided functionality, network device46acts as an interface device for a modular diagnostic tool/biometric device54, connecting the device54through the network30to the local server12to the interface26. As with network device46, the functionality of diagnostic tool54will be further explained. It should be noted that a variety of mechanisms may be implemented to connect the diagnostic tool54with the network device46. One such mechanism uses wired communication52over a standardized communications link (in this case, a USB connection). As such, network device46incorporates two USB ports48, into one of which a USB connector50is shown inserted. Alternatively, tool54may use an additional communications channel56(e.g., 802.xx compliant).

As will be further described, the diagnostic tool54is one of a variety of similar tools54that are may be specialized for performing specific medical functionality. For example, one diagnostic tool54may perform blood glucose monitoring functionality, while another diagnostic tool54may monitor blood pressure. Each of the tools54, however, is modular in that they share one or more communications schemes to connect with the network device46using a standardized communications link. For example, each of the tools54may be connectable to the network device46using a USB communications link.

The diagnostic tool54may perform a wide variety of medical functionality to obtain biometric and other diagnostic information. For example, the diagnostic tool may include a blood pressure monitor, pulse oximeter, blood glucose meter, scale, thermometer, otoscope, ophthalmoscope, body fat monitor, heart rate monitor, stethoscope, alcohol screening device, fingerprint scanner, retinal scanner, and pH meter.

The use of a variety of available diagnostic tools54compatible with a single network device46allows for flexibility in providing medical services to a particular patient over system10. For example, a particular patient with diabetes may be provided a blood glucose monitor tool54to routinely provide blood glucose information through system10to a monitoring physician. As will be seen, the blood glucose information may be stored locally on the tool54, and/or uploaded through network device46to the local server12where it is stored on the database14and accessible (along with previous test information) to a monitoring physician. In addition, the tool54may be operable by the physician to perform specific functionality, or the tool may be disconnected from the network device and used to gather information on an offline basis that is later automatically uploaded over the network30to the medical professional when the tool54is subsequently reconnected with the network device46.

The flexibility provided by system10allows the medical professional to provide medical services to a larger patient base without compromising quality of service. In addition, the medical professional may use the various components of system12to perform such functionality as remote diagnosis of medical conditions, and virtual communication over the network30with the patient to suggest follow up action items, such as an instruction to visit a laboratory for further testing or instruction in regards to a prescribed medication. This flexibility alleviates the patient from having to travel, in some cases, great distances to the offices of the medical professional for routine services and checkups.

FIG. 2hereafter provides an exemplary local server12in which the mechanisms of the following embodiments may be implemented. It should be appreciated, however, thatFIG. 2is only exemplary and is not intended to state or imply any limitation as to the particular architectures in which the exemplary aspects of the various embodiments may be implemented. Many modifications to the architecture depicted inFIG. 2may be made without departing from the scope and spirit of the following description and claimed subject matter.

FIG. 2illustrates an exemplary local server12that can be used to implement embodiments of the present invention. Local server comprises a computer61. The computer61includes a processor63and a memory65, such as random access memory (RAM). The computer61is operatively coupled to a display20(such as through workstation26,FIG. 1), which presents images such as windows to the user on the GUI71. The computer12may be coupled to other devices, such as keyboard22, mouse device24, a printer66, etc. Of course, those skilled in the art will recognize that any combination of the above components, or any number of different components, peripherals, and other devices, may be used with the computer61.

Generally, the computer61operates under control of an operating system (OS)51(e.g. z/OS, OS/2, LINUX, UNIX, WINDOWS, MAC OS) stored in the memory65, and interfaces with the user to accept inputs and commands and to present results, for example through a GUI module59. Although the GUI module59is depicted as a separate module, the instructions performing the GUI functions can be resident or distributed in the operating system51, an associated application program53, or implemented with special purpose memory and processors. The computer61also implements an email application/server55for providing email notification from the medical professional to the patient, or vice-versa.

Database14is operational on computer61, and resides in memory65in the depicted embodiment. The database14as shown includes prescription and drug interaction data57associable with a particular patient. Database14may also store data collected during online patient consultation. Database14may also store offline results monitored on behalf of the patient through data analysis using the application program53. The computer61also optionally comprises an external data communication device60such as a modem, satellite link, Ethernet card, wireless link or other device for communicating with other computers, e.g. via the Internet or other network.

Data storage device62is a direct access storage device (DASD)62, including one or more primary volumes holding a number of datasets. DASD62may include a number of storage media, such as hard disk drives (HDDs), tapes, and the like. Data storage device62may also include a number of storage media in similar fashion to device62. The device68may be designated as a backup device68for holding backup versions of the number of datasets primarily stored on the device62. As the skilled artisan will appreciate, devices62and68need not be located on the same machine. Devices62may be located in geographically different regions, and connected by a network link such as Ethernet (such as incorporated into subsystem28(FIG. 1)). Devices62and68may include one or more volumes, with a corresponding volume table of contents (VTOC) for each volume.

In one embodiment, instructions implementing the operating system51, the computer program53, and the database14are tangibly embodied in a computer-readable medium, e.g., data storage device62, which may include one or more fixed or removable data storage devices, such as a zip drive, disk64, hard drive, DVD/CD-ROM, digital tape, etc., which are generically represented as the disk64. Further, the operating system51and the computer program53comprise instructions which, when read and executed by the computer61, cause the computer61to perform the steps necessary to implement and/or use the present invention. Computer program53and/or operating system51instructions may also be tangibly embodied in the memory65and/or transmitted through or accessed by the data communication device60. As such, the terms “article of manufacture,” “program storage device” and “computer program product” as may be used herein are intended to encompass a computer program accessible and/or operable from any computer readable device or media.

Embodiments of the present invention may include one or more associated software application programs53that include, for example, functions for managing a distributed computer system comprising a network of computing devices, such as a storage area network (SAN) as part of data storage subsystem28(FIG. 1). The program53may operate within a single computer61or as part of a distributed computer system comprising a network of computing devices (such as computer61and workstation26,FIG. 1). The network may encompass one or more computers connected via a local area network and/or Internet connection (which may be public or secure, e.g. through a VPN connection), or via a fibre channel Storage Area Network or other known network types as will be understood by those skilled in the art. (Note that a fibre channel SAN is typically used only for computers to communicate with storage systems, and not with each other.)

The local server12may process instructions from the medical professional to the patient, or operational commands for the diagnostic tool54(FIG. 1) into commands that are sent over the network from the local server12to the patient. A portion of the commands may relate to directions that are provided to the patient, such as directions for installation of the diagnostic tool in the network device. The local server, the network device, the patient interface, or an additional device may process these commands. An additional portion of the commands may relate to operation of the diagnostic tool itself. For example, a physician may remotely operate the diagnostic tool by use of the interface18and with the assistance of the patient.

Turning toFIG. 3, an exemplary network patient-side portion70of system10(FIG. 1) is depicted, showing an exemplary network device46in communication with a diagnostic tool54. Network device46includes one or more application programs75implemented to facilitate communication between the network device46and another component over the network link84, such as the patient interface34(FIG. 1) using interface/adapter72. Network device46includes a processor74and onboard memory76, operational in many respects similar to that of local processor12. Interface/adapter72(such as a network adapter72) provides communication over a standardized communication link56, such as a USB connection with the diagnostic tool54. Adapter72is also coupled to the patient interface34, network30, or both (FIG. 1) over network link84.

As the skilled artisan will appreciate, the standardized communication link may include a variety of communications mechanisms. For example, the standardized communications link may be compliant with a universal serial bus (USB) communications protocol, an internet protocol (IP), an Institute for Electrical and Electronics Engineers (IEEE) wired or wireless communications protocol, a wireless application protocol (WAP), a local area network (LAN) protocol, a wide area network (WAN) protocol, a global system for mobile communication (GSM) protocol, and an AppleTalk® protocol.

In one embodiment, processor74receives the broadcast commands from the local server12, interpreting them as commands for control of the diagnostic tool, or instructions to be disseminated to the patient. Control commands are forwarded over the link56to the diagnostic tool54. Instructions may be provided to the patient interface over link84, where they may be converted to text, audio and video that is displayed to the patient over GUI36(FIG. 1). In some embodiments, network device46, in cooperation with the patient interface34, local server12, medical professional interface18, etc., may implement a voice-over-internet-protocol (VOIP) exchange, webcam session, voice or text chat session, and the like between the patient and medical professional. In this way, the patient may engage in dialogue or text communication with the medical professional during a particular session.

Returning toFIG. 3, tool54also includes a processor78coupled to a memory device86, as well as an integrated interface/adapter80. Memory86is capable of storing diagnostic information88, as well as application processes90that are executed in certain scenarios as will be explained, following. Interface/adapter80again functions as a communications interface between one or more interconnected biometric devices (such as a heart rate monitor) and the tool54over communications link82. Interface/adapter80also provides for communication between the tool54and the network adapter46.

In one embodiment, the processor78, in certain scenarios, executes one or more processes90. For example, the tool54may execute one of the processes90to upload diagnostic information88stored in the memory86through the network adapter46to the medical professional once a determination is made that the tool54is connected over link56with the network device46, and through link84with the local server12.

Turning now toFIG. 4, an exemplary blood pressure monitor100is shown as one of an available number of modular diagnostic tools54. Blood pressure monitor100includes an LCD display102for displaying systolic information, diastolic information, and time. Monitor100also includes user input buttons104, cuff106, and hose108for providing air pressure to expand cuff106. As the skilled artisan will appreciate, the illustrated tool54includes the electronic subcomponents necessary to perform blood pressure testing on a patient. Monitor100is made modular by USB communications link56implementing USB connector50between tool54and network device46(FIG. 3).

Turning toFIG. 5, an exemplary blood glucose meter110is depicted as an additional example of a modular diagnostic tool communicable with the network device. In the depicted embodiment, the glucose meter110establishes a wireless communications link with an antenna47of the network device46using a standardized communications link such as 802.11a/b/g or an equivalent. Meter110includes a housing112, a probe114for taking blood readings, display116, and input buttons118. Example operations of the monitor100and meter110will be further described, following.

Turning toFIGS. 6 and 7, various methods are depicted as examples of online patient monitoring/offline data collection using the mechanisms of the present invention. As one skilled in the art will appreciate, various steps in these methods may be implemented in differing ways to suit a particular application. In addition, the described methods may be implemented by various means, such as hardware, software, firmware, or a combination thereof operational on or otherwise associated with the storage environment. For example, the methods may be implemented, partially or wholly, as a computer program product including a computer-readable storage medium having computer-readable program code portions stored therein. The computer-readable storage medium may include disk drives, flash memory, digital versatile disks (DVDs), compact disks (CDs), and other types of storage mediums.

Turning first toFIG. 6, method150begins (step152) by the interface associated with the medical professional receiving input/instructions from the medical professional (step154). The input may take place as the medical professional operates an input device connected to the workstation previously described. As a following step, the instructions are processed by the local server into commands for remote broadcast (step156).

The commands are forwarded by the local server to the network device over a network path (step158) where they are processed by the network device (step160). As a part of processing the commands, the network device provides installation direction to the patient for connecting the modular diagnostic tool into the network device (step162). This direction may be pursuant to one of several communications schemes, such as a text or voice chat, VOIP communication, or a webcam session.

Pursuant to the installation directions, the patient connects the diagnostic tool that was supplied to them by the medical professional (step164). The network device initializes the diagnostic tool for operation. The network device recognizes the diagnostic tool (for example, over a Bluetooth® communications channel or by recognition of a USB port insertion), and executes an automated process to query the tool for any diagnostic information stored on the device (step166). If the network device determines that diagnostic information is available (step168), the diagnostic tool, either by itself or in conjunction with the network device, executes an automated process to upload the diagnostic information through the network device to the local server (step170).

As a following step, the medical professional proceeds to operate the diagnostic tool over the network path using the network device (step172). For example, the patient may, at the request of the medical professional, install the cuff of a blood pressure monitor. The medical professional may then perform some initialization functions remotely over the network path, and then operate the monitor by causing the cuff to expand with air and take readings as the cuff is slowly relieved of air pressure. In this fashion, the medical professional has the ability to perform medical services on a live basis with the assistance of the patient.

Once the readings are taken, the diagnostic tool stores the information in onboard memory (step176). The medical professional then uploads the diagnostic information, through the network device, to the local server (step178). If the local server determines that previous medical records/information is available for this particular patient (step180), then the diagnostic information, such as test results, are analyzed against the previous information (step182). In any event, the local server, in cooperation with database14(FIGS. 1,2) analyzes the data and provides to the medical professional. In one embodiment as shown, the analysis data provided to the medical professional may include a drug analysis obtained by comparing patient drug information (e.g., prescriptions assigned to the patient) with stored drug interaction data (step184). In other embodiments, the analysis data may include recommendations for the medical professional to suggest laboratory work or additional testing to the patient.

The medical professional reviews the analysis data and/or recommendations provided by the local server (step186). Based on the analysis data, the medical professional provides directives to the patient (step188), such as suggestions to obtain additional lab work, additional testing, schedule an on-site visit, and the like. Again, these directives may be provided pursuant to the communications scheme engaged in previously, such as VOIP, voice/text chat, and webcam session. The patient then disconnects the diagnostic tool (step190), and the method150then ends (step192).

Turning now toFIG. 7, method200illustrates exemplary offline data collection capabilities of the modular diagnostic tool. Method200begins (step202), with the patient using the tool to collect diagnostic information subsequent to the online exchange with the medical professional described previously in method150(FIG. 6) (step204). For example, the patient may continue to take blood pressure and/or blood glucose readings.

As a next step, the diagnostic tool stores the diagnostic information in onboard memory as previously described (step206). At a later time, the patient connects the diagnostic tool (e.g., wired or wireless) to the network device (step208). Here again, the network device recognizes the diagnostic tool on its network and queries the diagnostic tool for information (step210). If diagnostic information is determined to be stored on the device (step212), an automated process is executed to upload the diagnostic information through the network device to the local server (step214) where it is accessible by the medical professional.

The local server stores the diagnostic information in its database (either locally or on an associated data storage subsystem) accessible by the medical professional (step216). If previous medical records/information is available in the system for the patient (step218), the diagnostic information obtained from the instant situation is analyzed against the previous information (step220). Here as before, this analysis is provided to the medical professional for review in the form of recommendations, drug analysis information, etc. (step222). The medical professional reviews the analysis (step224).

The diagnostic tool may provide information to the medical professional in a variety of scenarios. For example, at a particular time, diagnostic information may not be obtained from the patient (again, step212), but time may have elapsed for the patient to obtain such diagnostic information (such as an additional blood glucose test). Based on operation of application program(s) executed on the local server per a particular situation (such as appointment scheduling, test scheduling, data analysis, drug analysis, calendaring, input from the medical professional, and the like), the local server sends further information to the patient via the local server's associated email server (step226). This further information may include such information as test results, appointment information, drug analysis, notices, invoices, etc. For example, based on particular blood glucose results obtained by the patient over a period of time, the local server may determine that an immediate follow-up appointment is warranted. The local server may check the calendar of the medical professional and query the patient for an appointment date. Once the patient verifies the appointment date, the date is scheduled in the system's calendar and a notification is emailed to the patient and/or medical professional. In addition, the system and/or the medical professional may interpret the glucose results. The results may then be similarly forwarded to the patient.

While the foregoing methods150and200provide exemplary functionality of the mechanisms of the present invention, the skilled artisan will appreciate that similar functionality may be carried out using the flexibility provided by the modular diagnostic tool. For example, the patient may visit a laboratory and obtain testing that may be stored on the diagnostic tool's onboard memory. Once the patient returns home, they may reconnect the diagnostic tool to the local server. Once the diagnostic tool is again recognized by the network device, the automated processes may again be executed to upload the laboratory data to the local server for collection and analysis by the medical professional. In additional embodiments, the patient interface34, network device46, and/or diagnostic tool54(FIGS. 1,3) may be adapted to contact emergency medical personnel in case of a medical emergency, such as a paramedic team or hospital emergency room. For example, if a patient provides diagnostic information indicating a medical emergency, appropriate responding personnel may be contacted. The diagnostic information may be electronically forwarded to the responding personnel for analysis.