WO2018218162A1 - Telemedicine systems - Google Patents

Abstract

An example telemedicine system is an emergency response system. The system includes a first mobile device, which includes a one touch medical emergency connection button; wireless audio and video connection capability; secure texting capability; and customizable rules for sending and receiving broadcast messages and/or group calls. The system also includes a communication hub, which is to receive a signal in response to the activation of the one touch medical emergency connection button. The communication hub includes an integrated scheduler with information for first and second on call doctors; and protocol for: first attempting to connect the first mobile device with a mobile device of the first on call doctor; and upon recognizing a failure to connect the first mobile device with the mobile device of the first on call doctor, then attempting to connect the first mobile device with a mobile device of the second on call doctor.

Description

TELEMEDICINE SYSTEMS

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001 ] This application claims the benefit of Indian Provisional Application Serial Number 201741018573, filed May 26, 2017, the contents of which is incorporated by reference herein in its entirety.

BACKGROUND

[0002] Telemedicine involves the use of telecommunication and information technologies to provide clinical health care from a distance. Telemedicine enables a physician to provide clinical advice, such as a diagnosis, to a patient in another geographical location. Previously, telemedicine was performed using telephones, fax machines, or radios. For example, one physician might communicate a patient's symptoms to another using a radio, so as to obtain advice on the best course of treatment. Similarly, a patient in South Africa might fax his or her medical records to a physician located in the United States. The physician could then make a telephone call to the patient in order to give the patient an opinion regarding the patient's affliction.

BRIEF DESCRIPTION OF THE DRAWINGS

[0003] Features of examples of the present disclosure will become apparent by reference to the following detailed description and drawings, in which like reference numerals correspond to similar, though perhaps not identical, components. For the sake of brevity, reference numerals or features having a previously described function may or may not be described in connection with other drawings in which they appear.

[0004] FIG. 1 illustrates a hardware configuration wherein a system disclosed herein may be implemented;

[0005] FIG. 2 depicts a block diagram illustrating an overview of a system disclosed herein involving remote patient care; [0006] FIG. 3 depicts examples of the medical equipment that may be incorporated into a system disclosed herein;

[0007] FIG. 4 depicts a block diagram of a height measuring unit;

[0008] FIGS. 5a and 5b depict profile views of a first height measuring unit;

[0009] FIG. 6a depicts a profile view of a second height measuring unit with an arm in a retracted position;

[0010] FIG. 6b depicts a profile view of the height measuring unit of Figure 6a worn by a person with the arm in an extended position;

[001 1 ] FIG. 6c depicts a profile view of a third height measuring unit;

[0012] FIG. 6d depicts a profile view of the height measuring unit of Figure 6c worn by a person;

[0013] FIG. 7 depicts a block diagram of a weight measurement unit;

[0014] FIG. 8 depicts a block diagram of a portion of a stethoscope unit;

[0015] FIG. 9a depicts a profile view of a stethoscope unit with the stethoscope removed;

[0016] FIG. 9b depicts a profile view of the stethoscope unit of FIG. 9a with the stethoscope attached;

[0017] FIG. 10 depicts a block diagram of a pulse oximeter;

[0018] FIG. 1 1 depicts a profile view of a BP measurement unit;

[0019] FIG. 12 depicts a block diagram of a system to automate control of the lights and other aspects of a room;

[0020] FIG. 13 depicts a block diagram of an alarm and monitoring system;

[0021 ] FIG. 14 depicts a block diagram of an example of a method for providing telemedicine;

[0022] FIG. 15 depicts a block diagram of an example of a method of providing telemedicine;

[0023] FIG. 16a is a block diagram of a patient system disclosed herein;

[0024] FIG. 16b is a schematic diagram of a patient mobile device and a portion of a home graphical user interface displayed on the patient mobile device;

[0025] FIG. 16c is a schematic diagram of a patient mobile device and another portion of the home graphical user interface displayed on the patient mobile device; [0026] FIG. 17a is a schematic diagram of a healthcare professional mobile device and a home graphical user interface displayed on the healthcare professional mobile device;

[0027] FIG. 17b is a schematic diagram of a healthcare professional mobile device and a rounding list graphical user interface displayed on the healthcare professional mobile device; and

[0028] FIG. 18 is a schematic diagram of an emergency response system disclosed herein.

DETAILED DESCRIPTION

[0029] The examples disclosed herein are telemedicine systems. These

telemedicine systems include a patient system, a healthcare professional system, and an emergency response system. These systems include telemedicine components, devices, and/or applications that enable patients (or caretakers) and physicians in physically separate locations to interact. These systems may be implemented using a variety of hardware running specialized software so as to enable these interactions. Software, firmware, or the like operate as a set of instructions running in executable memory of a processor residing on a computing device. The computing devices may be used alone or in a networked configuration.

[0030] Overview of Networked Hardware

[0031 ] FIG. 1 illustrates a hardware configuration 100 wherein a system can be implemented on one or more computing devices 104, 105, and 106 used by different users 101 and connected over a network 103. The computing devices may comprise computers 104, 105, and/or base stations 106. The network 103 is suitable for connecting the one or more computers 104, 105, and 106 and may comprise one or more networks such as a local area network (LAN), a wide area network (WAN) such as the Internet, telephone networks including telephone networks with dedicated communication links and/or wireless links, and wireless networks. In the illustrative example shown in FIG. 1 , the network 103 is the Internet. Each of the one or more computing devices 104, 105, and 106 is connected to the network 103 via a suitable communication link, such as a dedicated communication line or a wireless communication link. The system may be implemented using software that is either local or operating from a remote server 102 such as a web server over the Internet. Further, with the rapid growth of Internet technology and portable wireless technology, other computing devices, such as cell phones 1 10, handheld devices 1 1 1 , portable tablets 1 12, or portable computers 1 13 may be used place of or in addition to the one or more computing devices 104, 105, and 106.

[0032] Each of the one or more computing devices 104, 105, 106, 1 10, 1 1 1 , 1 12, 1 13 comprises a central processing unit (CPU) and an input/output (I/O) unit;

additionally, the computing devices 104, 105, 106, 1 10, 1 1 1 , 1 12, 1 13 may further comprise a display device communicatively coupled to the I/O unit, a storage device, and a memory. In an example, each of the one or more computing devices 104, 105, and 106 further includes one or more standard input devices such as a keyboard, a mouse, speech processing means, and/or a touchscreen. The computing devices may be running any suitable operating system (e.g., WINDOWS®, UNIX®, operating systems of Oracle, etc.) In an example, the memory includes a Graphical User Interface (GUI) that is used to convey information to and receive information from a user of the one or more computing devices 104, 105, and 106 via the display device and I/O unit as described herein. In an example, the GUI includes any user interface capable of being displayed on a display device including, but not limited to, a web page, a display panel in an executable program, or any other interface capable of being displayed on the one or more computing devices 104, 105, and 106 respective display device.

[0033] In the examples disclosed herein, each of the patient system, the healthcare professional system, and the emergency response system includes a plurality of specific, structured GUIs. Each GUI is paired with a prescribed functionality directly related to the graphical user interface's structure. In some instances, the GUIs and associated functionalities are addressed to and resolve various problems with other telemedicine systems.

[0034] For example, the patient system improves the portability of information from different hospital systems and doctor practices. In prior systems, patient records were maintained at a particular office or hospital, or the patient could access the records electronically through different web portals affiliated with the various healthcare professionals. The patient system also keeps an audit trail for accuracy and timeliness of data, creates a continuum of records between health care data and accounting data, and improves efficiency in a cost effective manner.

[0035] For another example, the healthcare professional system disclosed herein provides point of care integration of charge tracking. In particular, the healthcare professional system integrates rounding lists, patient records, patient encounter coding, and billing in a single application, which allows a healthcare professional to seamlessly track and code charges. In prior systems, patient encounters were recorded by healthcare professionals, and transmitted to a separate billing department for coding, and then transmitted to the patient or an insurance company.

[0036] For yet another example, the emergency response system disclosed herein provides one touch connection with a communication hub (which locates an on call doctor suitable for consulting on the particular emergency). In some instances, this system puts an appropriate doctor in contact with the first responder who is with the patient prior to the patient physically arriving at a healthcare facility. This is unlike prior systems, where a patient immediately interacts with an emergency medical technician, but not a doctor. In other instances, the emergency response system puts an appropriate specialist in contact with the consulting physician who is with the patient.

[0037] As will be recognized by one of skill in the art, each of the cell phones 1 10, handheld devices 1 1 1 , different portable tablets 1 12, or computers 1 13 may be configured similarly to the one or more computing devices 104, 105, and 106, taking into account the various design considerations of these respective devices.

[0038] The GUI may be transmitted to the one or more computing devices 104, 105, and 106 or other devices 1 10, 1 1 1 , 1 12, or 1 13 via the network 103. In one example, the GUI is displayed using commercially available hypertext markup language ("HTML") viewing software such as, but not limited to, Microsoft Internet Explorer, Google Chrome, Apple Safari, or Mozilla Firefox, or any other commercially available HTML viewing software. [0039] In another example, the GUI is displayed using executable code stored locally on one of the one or more computing devices 104, 105, and 106 or other devices 1 10, 1 1 1 , 1 12, or 1 13. For example, the GUI may be displayed using a standalone executable application or App. The GUI may be updated or modified using information received via the network 103. For example, the stand-alone executable application on one of the computing devices 104, 105, or 106 could display a list of names, where the names are updated using information received via the network 103.

[0040] The GUI may reside on a remote server 102. Alternatively, a portion of the GUI or of the information displayed by the GUI may reside on a remote server 102. The remote server 102 may include one or more separate servers. The remote server 102 may be a web server. The remote server 102 may comprise a CPU, memory, and separate storage device and be communicatively coupled to the network 103. The remote server 102 may contain an information storage device that may be a relational database, such as Microsoft's SQL, SYBASE®, etc. or any other database, such as an open source database.

[0041 ] Overview of Remote Patient Care

[0042] With reference now to FIG. 2, a block diagram providing an overview of a system 200 in accordance with the examples disclosed herein is shown.

[0043] Prior to the development of telemedicine, a doctor needed to be physically located near his or her patient in order to formulate a diagnosis and provide treatment. For example, a doctor might need to conduct a basic physical examination of the patient, including measuring her height, weight, and blood pressure. The doctor would likely conduct an interview with the patient, asking her about her symptoms and any relevant family history of illness. Further, he may need to perform tests, such as examining a sample of the patient's blood using a microscope or performing an imaging test using x-rays or magnetic resonance imaging (MRI). Finally, the doctor may need to provide treatment to the patient, for example, by writing a prescription and instructing her as to her treatment regimen. Each of these tasks required that the doctor physically be in the same location as the patient. [0044] In an example, using the system shown in FIG. 2, a doctor performs all of the foregoing tasks without being in the same physical location as the patient.

Specialized equipment allows interactions between two individuals, such as a patient and her doctor, who may be in different physical locations. In an example, the equipment 202 includes a server 102 connected to one or more computing devices, such as one or more computers 104, 105, and 106 or other devices 1 10, 1 1 1 , 1 12, or 1 13, via a network 103.

[0045] In an example, the equipment 202 includes a server 102 connected to at least two computing devices using the Internet. A first computing device (e.g., computer 104 or a suitable mobile device) is located in physical proximity to a first person, such as a doctor. A second computing device 1 10 (e.g., cell phone, tablet computer, etc.) is located in physical proximity to a second person, such as a patient. These computing devices exchange information between one another using the network 103. The computing devices 104 and 1 10 may either exchange information directly or indirectly, for example by using the server 102 as an intermediary. By using the computing devices 104, 1 10, the patient and doctor may interact together, for example by exchanging video, audio, and/or other data. The information may be securely transmitted using encryption. In an example, the information transmitted between the computing devices may be supplemented by additional information sent by the server 102. For example, video data sent by the second computing device 1 10 may be sent to the first computing device 104; at the same time, additional data (such as an electronic medical history or test results) may be transmitted from the server 102 to the first computing device 104. Alternatively, in an example, a server 102 is not used and the two computing devices 104 and 1 10 are directly linked via the network 103.

[0046] In an example, the system 200 includes hardware 204 located proximate to the patient. In an example, the hardware 204 includes a base station 106 that is connected to a WAN such as the Internet. This connection may be either wired or wireless. Using the WAN, the base station 106 communicates with a server 102 or other computing device, such as a computing device 104 located proximate to the doctor. The base station 106 is configured to transmit and receive information (e.g., audio, video, and/or other data) and commands. In an example, the base station is further connected to a LAN, either wirelessly using a communication protocol such as ZigBee (a specification based on the IEEE 802.15 standard), Bluetooth (formerly the IEEE 802.15.1 standard), or Wi-Fi (the IEEE 802.1 1 standard) or via a wired connection using a communications protocol such as Ethernet or RS-232. In an example, the base station 106 includes input devices, such as a video camera, microphone, and/or keyboard. In an example, the base station 106 includes output devices, such as a display screen and/or speaker. In an example, these input and output devices are used to simulate having the physician physically present in the room with the patient. For example, the display screen may display the physician's face while the speaker emits the physician's voice. The video camera and microphone may record the patient and transmit that information directly to the physician or to the server 102, where the information may be stored or processed. In an example, the physician is similarly recorded by a video camera and/or microphone; this information is transmitted to the base station where it is presented to the patient. Alternatively, in an example, a program running on the server 102 or base station generates visual and/or auditory information that is presented to the patient. In an example, this information is a virtual representation of a physician, including a computer-generated image of a physician's face and computer-generated audio of a physician's voice. Alternatively, this information may be prerecorded video and/or audio of a physician or textual information, such as instructions for the patient.

[0047] The hardware 204 may be connected to various devices located proximate to the patient using the LAN. These devices may, for example, include a device configured to perform an automated examination of the patient (e.g., using a video camera and/or microphone) and may include various medical equipment 208 such as a microscope, an environmental control element 210 (also referred to as a lighting and automation system) that may adjust lighting and other automation systems, an alarm system 212, and an RFID tracking system 214. Each of these elements is discussed in greater detail herein. These devices may be controlled by signals sent over the LAN by the base station. Further, these devices may be controlled via signals received by the base station over the WAN and retransmitted to the devices over the LAN. These devices may transmit information, such as the current conditions of the device or measurements obtained regarding the patient, to the base station over the LAN. This information may be retransmitted to another computing device such as the server 102 or the computing device located proximate to the doctor using the WAN.

[0048] As discussed above, in an example, the system 200 includes one or more devices to enable a patient and a physician to interact, which may include one or more video cameras, displays, microphones, and speakers. In an example, a device located proximate to the patient includes a video camera, display, microphone, and speaker. A corresponding device located proximate to a physician similarly includes a video camera, display, microphone, and speaker. In an example, the devices are communicatively coupled, enabling videoconferencing between the patient and physician. In an example, one or more of the devices may be a smartphone, tablet, or computer. In an example, the device proximate to the patient is integrated with the base station.

[0049] In an example, the system 200 includes a device 206 that performs an automated examination of the patient, for example, by using a display, video camera, and microphone. In an example, a video of a physician asking the patient questions is shown on the display using the device 206 located proximate to the patient. In an example, the video is prerecorded. In an example, the video is artificially generated (e.g., is an animation). The patient's answers are then recorded using the video camera contained in the device 206 located proximate to the patient. In an example, the video or animation instructs the patient to perform certain actions, such as raising the patient's arms above his or her head or using medical equipment 208 (e.g., the patient may be instructed to step onto a scale). The results of these actions are then recorded. In an example, the recorded information is sent to a physician in a separate physical location. In an example, the recorded information is sent to the physician in real time. In an example, the recorded information is saved and shown to the physician at a later time.

[0050] In an example, the system 200 comprises software 216. In an example, the software includes a GUI. In an example, the GUI allows a remotely located user to control and interact with the hardware located proximate to a patient, including the base station and various other devices located proximate to the patient. In an example, the software comprises elements including a dashboard 218, a Digital Imaging and Communications in Medicine ("DICOM") viewer and universal uploader 220, a directory 222, a diagnosis tracker 224, alerts provided to patients or doctors 226, and electronic medical records ("EMR") 228. Each of these elements is discussed in greater detail herein.

[0051 ] The system 200 illustrates an example of patient care when the doctor (or other healthcare professional) and the patient are located remote from one another. In the patient system 10 (see FIGS. 16a through 16c) and the healthcare professional system 12 (FIGS. 17a and 17b) disclosed herein, the computing device 1 10' of the patient and the computing device 104' of the healthcare professional may be equipped to engage in the remote patient care described herein. It is to be understood that these devices 1 10', 104' are also respectively configured with different GUIs and associated functionalities that enable the patient to perform certain patient related tasks (that may or may not directly involve the healthcare professional) and the healthcare professional to perform certain healthcare professional related tasks (that may or may not directly involve the patent). Examples of the GUIs and associated functionalities of the patient system 10 will be described in reference to FIGS. 16a through 16c, and the GUIs and associated functionalities of the healthcare

professional system 12 will be described in reference to FIGS. 17a and 17b.

[0052] Patient System

[0053] As shown in Fig. 16a, an example of the patient system 10 includes a mobile device 1 10'. The mobile device 1 10' may be the same as the computing device 1 10, and thus includes a display and a user input device. As examples, the display may be a liquid crystal display, and the user input device may be a switch, keyboard, mouse, or touchscreen.

[0054] In the patient system 10, the display is for presenting a plurality of graphical user interfaces, each of which is associated with at least one patient related workflow. The plurality of graphical user interfaces includes an appointment graphical user interface 16, including an appointment scheduling workflow; a medication graphical user interface 18, including a medication reminder alert; a prescription graphical user interface, including a prescription refill workflow; a records graphical user interface 20; and a personal health graphical user interface 22. Also in the patient system 10, the user input device is for initiating the at least one of the patient related workflows.

[0055] As shown in FIGS. 16b and 16c, the plurality of graphical user interfaces of the patient system 10 further includes a home graphical user interface 24. As shown in FIG. 16b, the home GUI 24 includes an appointment menu 26; a medication menu 28; an emergency call menu 30; a plurality of vital icons 32; and a tab bar 34 including a home icon, an appointment icon, a records icon and a my health icon. As shown in FIG. 16c, the home GUI 24 also includes a visit summary icon 36; a prescription icon 38; a medications icon 40; and a results icon 42. Each of these menus 26, 28, 30 or icons 32, 36, 38, 40, 42, or icons in the tab bar 34 may be tapped by a user (e.g., patient or caregiver of the patient) in order to initiate a corresponding GUI.

[0056] The appointment menu 26 may be selected to open up the appointment graphical user interface 16. The appointment GUI 16 may include a health care directory and a book appointment option. The directory may provide a listing of health care providers, including doctors and other health care employees. The health care directory may also include laboratory locations and/or radiology locations. The data in the health care directory may be stored in a remote server 102, which provides an information database listing health care providers, such as hospitals and clinics, as well as a list of doctors located at each location, the doctors specialty, accepted insurance plans, etc. As such, doctors may be listed by specialty, location, affiliations, and/or insurance plans accepted. The patient may use the health care directory of the appointment menu to select a doctor, lab, or radiology center. Once the doctor or other health care professional, lab, or radiology center is selected, the GUI 16 may show a list, calendar, etc. of dates and times that are open to book an appointment. The patient can select a date and time, and then transmit the appointment request to the doctor or other health care professional, lab, or radiology center. The patient system 10 transmits a message (e.g., electronic mail, text message) to a scheduling computing device associated with the doctor or other health care professional. A user of the scheduling computing device can cross-check that the requested appointment is actually available, and then can send a confirmation communication back to the patient system informing the patient that the appointment has, in fact, been made. Alternatively, is the requested appointment has become unavailable, the user of the scheduling computing device can send a communication back to the patient system informing the patient that he/she needs to select another appointment.

[0057] The medication menu 28 may be selected to open up the medication graphical user interface 18. The medication GUI 18 may include a medication reminder alert. Upon selecting the medication reminder alert, the medication GUI 18 displays a medication name box, a duration box, a start date box, an end date box, days of the week icons, hour and minute icons, and a dosage box. The medication GUI 18 may also display a notes or description box. Each of the boxes may have information input therein using, for example, a touch screen keyboard or other input device. The day may be selected by touching the appropriate day of the week icon, and the hour and minute icons may present a scrolling menu so the patient can readily select the hour and minute at which the medication is to be taken. Using the medication GUI 18, the patient can select a date and time, and then input information about the type of medication that is to be taken at that date and time. The patient may also have the option of setting a recurrence, for example, if the medication is to be taken daily or weekly or monthly.

[0058] The medication icon 40 of the home GUI 24 (shown in FIG. 16c) enables the patient to access a list of his/her medications (e.g., current medications, or current and past medications). This information may be stored on a remote server 102 in the patient's electronic medical record 228.

[0059] The home GUI 24 may also include the prescriptions icon 38, which may be used to initiate a prescription refill workflow. To initiate this workflow, the prescriptions icon 38 may be selected. The patient is then presented with a prescription GUI 19 (FIG. 16a), which may include a box for inserting a prescription number, a box for inserting a pick-up date and time, and a box for inserting the name of the pharmacy that filled the original prescription. The box for inserting the pick-up date and time may also have an icon that, when selected, will display a list, calendar, etc. of dates and times that the patient can select from. The box for inserting the name of the pharmacy may also have an icon that, when selected, will open up a directory that provides a listing of pharmacies. The data in this directory may be stored in a remote server 102, which provides an information database listing pharmacy names, addresses, and phone numbers. Using this directory, the patient can select the pharmacy that filled the original prescription. After inputting the refill number, pick-up time and date, and the pharmacy information, the patient system 10 transmits a message (e.g., electronic mail, text message) to a computing device associated with the pharmacy. A user of the computing device can cross-check the refill number, and then can send a confirmation communication back to the patient system 10 informing the patient that the refill will be filled, or that the patient should contact the pharmacy directly.

[0060] Referring back to FIG. 16b, the emergency call menu 30 provides a one touch icon that will connect the mobile device 1 10' with an emergency medical team/technician. The call may initially be received at an automated dispatcher that identifies the appropriate emergency medical team/technician based on the location of the mobile device 1 10' making the call. Upon identifying the emergency medical team/technician that is available and closest in proximity to the mobile device 1 10', the dispatcher connects the mobile device 1 10' with a computing device of the emergency medical team/technician. The location of the mobile device 1 10' can be transmitted to the computing device with the call.

[0061 ] The plurality of vital icons 32 illustrates to the patient his/her most recently input vital reading(s), such a blood pressure, weight, height, heart rate, temperature, etc. In an example, the patient may use medical equipment 208, a scale, a

thermometer, or another suitable device to measure the vital sign, and then may manually input the information into the patient system 10 using an add icon (as shown in FIG. 16b with some of the vital icons 32). Alternatively, the vital sign reading may be transmitted directly from the medical equipment 208 used to obtain the vital sign reading to the mobile device 1 10'. Still further, the vital sign reading may be updated when the patient visits a healthcare professional, and then may be transmitted directly from a computing device of the healthcare professional to the patient system 10 or from the computing device of the healthcare professional to the server 102 and then to the patient system 10. [0062] The records graphical user interface 20 may be opened using the records icon in the tab bar 34. When the icon is tapped, the records graphical user interface 20 opens and presents a login and password screen for the patient to access his/her medical records. The medical records may be stored in a single electronic health record system. The electronic health record system may be integrated with the various medical equipment and computing devices disclosed herein. An electronic health record is a digital collection of patient information compiled at one or more meetings in any care delivery setting. A patient's record typically includes patient demographics, progress notes, problems, medications, vital signs, past medical history, immunizations, laboratory data, and radiology reports. The electronic health record system provides a web browser and/or application-based system available on multiple platforms (including the patient system 10) which provides access to electronic health records. The electronic health record system enables information to be quickly and seamlessly shared between patients, physicians, billers, pharmacists, treatment facilities, and integrated medical equipment. In the patient system 10, the patient can access his/her electronic records from his/her mobile device 1 10'.

[0063] In an example, records graphical user interface 20 of the patient system 10 may allow the patient to generate and transmit a health summary to his/her healthcare professional, such as to the emergency medical team during an emergency call or to the doctor's office. This may be desirable so the healthcare professional can have a summary of daily vital sign recordings without the patient having to physically go into the healthcare professional's office. It is to be understood that the patient system also enables sharing of other documents between the patient and healthcare providers.

[0064] The personal health graphical user interface 22 may be opened using the my health icon in the tab bar 34. When the icon is tapped, the personal health graphical user interface 22 provides the patient with options to customize his/her patient portfolio. The personal health GUI 22 presents the user with the opportunity to update his/her personal information, update preferences on which icons to include on the home GUI 24, billing information, primary care physician information, etc.

[0065] In an example, the plurality of graphical user interfaces of the patient system 10 further includes a payment graphical user interface. The payment GUI may present payment options for the patient, such as a credit or debit card payment, automatic debit from the patient's bank account, or another electronic payment. The payment GUI may be used to submit a single payment to a payment processor, which is distributed to the physician, pharmacist and/or a treatment facility, as needed.

[0066] As shown in FIGS. 16b and 16c, the patient system 10 also includes a visit summary icon 36. When the patient does visit his/her doctor, a summary of the visit can be transmitted from the doctor's computing device 104 to the patient system 10, and may be accessed by tapping the visits summary icon 36.

[0067] As shown in FIGS. 16b and 16c, the patient system 10 also includes the tab bar 34. This tab bar 34 may include icons that provide one touch access to the home GUI 24, the appointment GUI 16, the records GUI 20, or the personal health GUI 22.

[0068] While not shown, the mobile device 1 10' may further include a digital imaging and communications in medicine (DICOM®) viewer. This enables the patient to receive images created in the DICOM® format. The viewer component on the mobile device 1 10' works in conjunction with a component running on a server 102. In an example, these components are stand-alone software components that run locally, as an application (also known as an "App"). In an alternative example, these components are run via the Internet using a protocol such as the World Wide Web.

[0069] The server component provides access to the images. As will be

understood by one of skill in the art, DICOM® provides both a file format and a communications protocol to enable medical information to be handled, stored, printed, and/or transferred. In an example, the server 102 supports DICOM® images including monochrome or color images with the color palette specified in RGB or YBR. In an example, the server 102 supports multiple video and image formats, including

DICOM® files (used for test information such as that generated by MRI, CT or x-ray), JPEG, and MP4, among other formats.

[0070] In an example, the DICOM® files may be uploaded to the server component from a variety of sources, including networked computing devices and the specialized medical equipment discussed herein. In an example, the server component may check the credentials of users, for example, using the lightweight directory access protocol ("LDAP") or remote authentication dial in user service ("RADIUS") so as to ensure confidential information is only accessed by authorized users. In an example, all information transmitted between the server 102 component and other components (e.g., mobile device 1 10') is encrypted so as to further protect confidential information in transit.

[0071 ] In an example, the server component includes lists of each user's favorite items and recently accessed items. In an example, the server 102 component supports audit logging, particularly regarding doctor/patient interactions. In an example, the server 102 component allows a user to access patient records using a name, an identification number such as a social security number ("SSN"), or other identifying information such as a patient's date of birth ("DOB").

[0072] In an example, viewer component on the mobile device 1 10' may be accessed either using a local application or App on the device 1 10' (such as iPad®), or using a web-based application, and interacts with the server component running on one or more remote servers 102. In an example, the viewer component provides a welcome screen that provides a brief explanation of the software features available, lists a number of recently accessed options, and lists a number of features selected by a user, such as the user's favorite features. The viewer component allows a user to access, view, and manipulate information, such as DICOM® files. For example, the viewer component may display a DICOM® image along with overviews, such as a ruler to indicate the scale of the image. Detailed image data may be presented. A user may compare multiple files side by side. In an example, the viewer component allows users to access either a quick view or a detailed view of a file.

[0073] In the patient system 10, the software may be secured so as to be compliant with the Health Insurance Portability and Accountability Act ("HIPAA") in protecting personal health information ("PHI"). Moreover, any communications, including video, audio, and text (e.g., email or text messages), made through the patient system 10 are secured and/or encrypted.

[0074] Healthcare Professional System

[0075] The healthcare professional system 12 disclosed herein includes a local application or a web-based application that can help physicians with the process of capturing charges when performing rounds. As will be described in further detail, the application provides the healthcare professional with tools for capturing charges associated with a patient encounter in real time. As such, the application captures the total cost and data from admitting a patient until discharge.

[0076] As shown in FIG. 17a, an example of the healthcare professional system 12 includes a mobile device 104'. The mobile device 104' may be the same as the computing device 104, and thus includes a display and a user input device. As examples, the display may be a liquid crystal display, and the user input device may be a switch, keyboard, mouse, or touchscreen.

[0077] In the healthcare professional system 12, the display is for presenting a plurality of graphical user interfaces, each of which is associated with a charge tracker workflow. The charge tracker workflow generally includes generating a patient encounter record during rounds, coding the procedure(s), prescription(s), etc. of the patient encounter, and transmitting a bill to an appropriate third party, such as a claims clearing house. The plurality of graphical user interfaces that may be used to facilitate the charge tracker workflow includes a rounding list GUI, a patient health record GUI; a coding GUI; and a billing GUI.

[0078] FIG. 17a illustrates the home GUI 44 of the healthcare professional system 12. The home GUI 44 includes respective icons 46, 48, 50, 52, 54 for initiating each of the plurality of graphical user interfaces of the healthcare professional system 12. A rounding list icon 46 may be used to initiate the rounding list GUI, a patient list icon 48 may be used to initiate the patient health record GUI, and a coding icon 50 may be used to initiate the coding GUI. As shown in FIG. 17a, the icons also include a scan icon 52 and a favorites icon 54. Each of the GUIs and their associated functions will now be described in further detail.

[0079] When the healthcare professional taps the patient list icon 48, the patient health record GUI opens up. The patient health record GUI may first display a patient list. The patient list may include basic patient information of all of the patients admitted in the particular unit in which the healthcare professional works. The basic patient information may include the name, hospital or other identification number, and gender. The healthcare professional can tap any individual patient name to pull up his/her electronic health record. As discussed herein, a patient's record typically includes patient demographics, progress notes, problems, medications, vital signs, past medical history, immunizations, laboratory data, and radiology reports. The healthcare professional may utilize the patient list to review the number of admitted patients, to refresh his/her memory of a patient's name and gender when making rounds, to review a patient's electronic health record, etc.

[0080] When the healthcare professional taps the rounding list icon 46, the rounding list GUI opens up. An example of the rounding list GUI 47 displayed on the healthcare professional's mobile device 104' is shown in FIG. 17b. The rounding list GUI 47 provides the healthcare professional with information and tools that allow the healthcare professional to perform rounds efficiently by creating and updating an encounter for each rounding patient in real-time, and by tracking charges for the encounter in real-time.

[0081 ] As shown at the top of FIG. 17b, the rounding list GUI 47 may display the date and the healthcare facility name.

[0082] The rounding list GUI 47 may have a spreadsheet format. The spreadsheet format displays basic patient details, facility identification number (FIN), the medical record number (MRN, which is used by the facility as a systematic documentation of a patient^'s medical history and care during each facility stay), patient's location within the facility, the rounding doctor's name, and a plurality of icons (as well as an icon legend or key (on the far right of FIG. 17b)) that simplify the rounding process for the healthcare professional. As shown in FIG. 17b, the rounding list GUI 47 may also include the primary care physician (PCP) of each of the admitted patients.

[0083] The basic patient details may include all of the patients admitted in the particular unit and their birth date. It is to be understood that the patient information displayed on the rounding list GUI 47 may include a hyperlink that, when tapped, will opens up the patient's electronic health record. Once the patient's electronic health record information is opened, the healthcare professional can generate a new record for the encounter/evaluation, and record information (e.g., progress notes, problems, medications, vital signs, etc.) for the encounter/evaluation in the record. Once the patient's electronic health record information is updated for the encounter, the healthcare professional can save the information and return to the rounding list GUI 47. The links between the rounding list GUI 47 and the electronic health records keep the healthcare professional from having to go back to the home GUI 44 and tapping on the patient list icon 48.

[0084] It is to be understood that the healthcare professional system 12 may further include a healthcare professional server 102 in communication with the mobile device 104', the healthcare professional server 102 having a memory that stores the patient rounding list and patient health records.

[0085] The plurality of icons of the rounding list GUI 47 may include a seen status icon 56. Prior to rounds, each patient has an empty box under the seen status icon 56. Upon completing an encounter with a particular patient, the healthcare

professional can tap the empty box and a check, X, eye icon, or other symbol will appear in the empty box indicating that the patient has been seen during the particular rounding period.

[0086] The plurality of icons of the rounding list GUI 47 may also include a coding status icon 58. The coding status may display one of three colored charts - a red chart, a yellow chart, or a green chart (although other colors and/or symbols may be used). The red chart is the default symbol, as it means that a patient

encounter/evaluation (and coding of the patient encounter) has not been started. The yellow chart means that a patient encounter/evaluation (and coding of the patient encounter) has been completed. The yellow chart may also indicate that clinical notes have not yet been added. The green chart means that a patient encounter/evaluation and coding of the patient encounter has been completed, and that the healthcare professional has added clinical notes to the encounter/evaluation.

[0087] During an encounter/evaluation, the healthcare professional may obtain data from the patient, perform a diagnosis, order tests and/or labs, etc. Each of these procedures is associated with one or more medical code(s), and the healthcare professional can input the code(s) in order to keep track of the medical claim in real time. The healthcare professional may have to look up a proper medical code based on the diagnosis, medical procedure(s), test(s), lab(s), prescription(s), etc. that is/are performed or ordered during the patient encounter/evaluation. The codes may be ICD codes (International Classification of Diseases), CPT codes (Current Procedure Terminology), or HCPCS codes (Healthcare Common Procedure Coding System). To initiate the coding GUI, the healthcare professional may use the coding icon 50 on the home GUI 44, or the rounding list GUI 47 may have a link that can open the coding GUI. The coding GUI may present the ICD interface, the CPT interface, or the

HCPCS interface, and the healthcare professional can use these interfaces to look up particular codes. Once the desired code(s) is/are identified, the healthcare

professional may input the code(s) into the record generated for the patent

encounter/evaluation. Alternatively, the coding GUI may allow the healthcare professional to copy the code(s) and paste them into the record for the encounter.

[0088] Referring back to the rounding list GUI 47 and FIG. 17b, the plurality of icons may also include a group icon 60. Prior to rounds, each patient has an empty box under the group icon 60. If the physician making the rounds is part of the patient's health care insurance group, the status can be updated with a green (or other colored) symbol. Alternatively, if the physician making the rounds is not part of the patient's health care insurance group, the status can be updated with a red (or other colored) symbol. The colored symbols may be used to determine whether the charges are in- network or out-of-network charges. The rounding doctor may input his/her name, and may also click on the group icon to indicate whether he/she is an in-network or out-of- network doctor. The group icon status may also automatically update to in-network or out-of-network when the doctor inputs his/her name. In these instances, rounding list GUI 47 cross-checks the doctor's name with a list of providers associated with the patient's recorded insurance company or companies. The list of providers may be stored in a remote server, such as server 102, which may be affiliated with the healthcare professional facility or with the insurance company.

[0089] The plurality of icons may also include an edit patient information icon 62. This icon 62 may be selected to access the individual patient's health record in the electronic health record system. If the icon 62 is selected during rounds, the color of the icon may change from yellow (default color, indicating no changes made) to green if information is changed and saved in the health record. The color change of the icon 62 indicates that the patient information was edited during the rounds taking place at the associated day and time.

[0090] The plurality of icons may also include a hand off icon 64. The hand off icon

63 enables the exchange of clinical and management information between the medical and other care providers. It improves patient safety during exchange of patient's medical information.

[0091 ] The rounding list GUI 47 may also include a facsimile ("fax") icon 68. If the rounding physician needs to send a facsimile as part of his/her rounds (e.g., to the patient's primary care physician), he/she may do so using the rounding list GUI 47. Tapping the facsimile icon 68 will initiate the mobile device's camera, and the physician can take a picture of the document to be faxed. An application associated with the rounding list GUI 47 can send the picture as a fax to an input number. The rounding list GUI 47 may also include a fax status icon 70, which indicates whether or not a fax was successfully transmitted. Prior to rounds, each patient has an empty box under the fax status icon 70. If the physician making the rounds sends a fax and it is successfully transmitted, the status can be updated with a green (or other colored) symbol (e.g., a green checkmark). If the physician making the rounds sends a fax and it is unsuccessful in its transmission, the status can be updated with a red (or other colored) symbol. These colored symbols allow the physician to know, in real time, whether the faxed information was received by the intended recipient.

[0092] While not shown in FIG. 17b, the rounding list graphical user interface 47 may also include a dictation tool; and a transcription tool. The dictation tool may be any medical dictation software used to record any notes, orders, etc. during the patient encounter, and may utilize the microphone of the mobile device 104'. The

transcription tool may be a remote service provider that receives the physician's recorded encounter record, and transcribes the recorded information and inputs the information into rounding list graphical user interface 47 and the appropriate patient electronic health record. As such, in some examples, the healthcare professional system 12 further includes a virtual scribe having real-time and secure access to the patient encounter information. Alternatively, the dictation and transcription tool may be integrated, e.g., the NUANCE® DRAGON® tool, and thus may perform voice to text recordation. The rounding list graphical user interface 47 may also include a handwriting recognition tool. With this tool the doctor can take notes on a screen of the mobile device 104' using his/her finger or a stylus, and the handwriting recognition tool can transcribe the notes.

[0093] When pathology or radiology is ordered during a patient encounter, the rounding list graphical user interface 47 can bring up an order page. This page can auto-populate with patient and/or previously recorded notes for the encounter. This page can also transmit the order to a desired lab or radiology center, including to other facilities. Similarly, when a prescription is ordered during a patient encounter, the rounding list graphical user interface 47 can bring up a prescription page. This page can auto-populate with patient and/or previously recorded notes for the encounter. This page can also transmit the order to a desired pharmacy, either within the facility (e.g., if the medication is to be given during the patient's facility stay) or outside of the facility (e.g., if the patient is to be discharged soon).

[0094] While not shown, the rounding list GUI 47 may present access to a physician directory, so that the rounding physician can easily find a suitable physician to consult or take over. The physician directory allows the rounding doctor to quickly look up physicians by name, specialty, location and/or department; to view a doctor's profile; to connect with the other physician using secure messaging or audio video calling; to refer or hand off the patient; and/or to tap on a phone number to call the other physician. The directory may be local or remote directory of doctors and other health care employees associated with the healthcare facility. This directory allows doctors within an ecosystem to find and refer patients to others in the ecosystem and transmit patient data across a secure platform. This component may be a standalone internal communication tool for the facility, or part of a network of facilities and doctors.

[0095] While not shown in FIGS. 17a or 17b, the plurality of GUIs further includes the billing graphical user interface. The billing GUI may be initiated, for example, from the home GUI 44 using a billing icon (not shown) or from an individual patient encounter. Once the patient encounter/evaluation is complete, it is saved and transmitted to a billing department within the facility or to a third party billing agency. As such, the healthcare professional system 12 may further include a billing agency server in communication with the mobile device 104', the billing agency server to receive the bill/invoice. In an example, the billing GUI is configured to automatically transmit an email with a summary of the patient encounter (including any codes) for billing purposes. Data transmission encrypts and uses standard formats to facilitate ready integration with existing billing software. The billing department or third party may double check that the physician coding is correct, and can generate an invoice that is transmitted to an insurance company, the patient, or another party for payment.

[0096] In the example shown in FIG. 17a, the scan icon 52 enables the physician to access the camera of the mobile device 104' to scan a barcode on a patient's identification tag, to scan a barcode on a patient's chart, to scan an invoice/printed bill, or the like. Upon scanning, any information associated with the barcode can be brought up on the display of the mobile device 104'.

[0097] In some examples, the healthcare professional system 12 further includes a favorites GUI. As shown in FIG. 17a, the home GUI 44 of the healthcare professional system further includes favorite icon 54. The favorites icon 54 opens the favorites graphical user interface, which provides user-defined dashboard reports. The physician can generate dashboard reports for a particular patient, for a particular code, etc. As an example, monthly coding statistics may be generated to identify the types of ailments being diagnosed and billed. As another example, advanced clinical searches may be performed based on the type of problem, the procedure performed, the age of the patient, the gender of the patient, etc. The favorites icon 54 may also allow the healthcare professional to create favorite codes (having user-identified names) that, when input, will auto-populate with ICD, CPT and/or HCPCS that the user associated with the favorite code.

[0098] While not shown, the mobile device 104' may further include a digital imaging and communications in medicine (DICOM®) viewer. This enables the physician to receive images created in the DICOM® format. The DICOM® viewer of the mobile device 104' may also include drawing tools for the physician to highlight, measure, and/or draw shapes on the image(s). Moreover, the DICOM® viewer of the mobile device 104' may also enable Hounsfield Unit Calculation for selected points in the image detailed view. Still further, the DICOM® viewer of the mobile device 104' may also allow the physician to play an image series with a selected frame rate. The viewer component on the mobile device 104' works in conjunction with a component running on a server 102. In an example, these components are stand-alone software components that run locally, as an application (also known as an "App"). In an alternative example, these components are run via the Internet using a protocol such as the World Wide Web.

[0099] As shown in FIG. 17a, the healthcare professional system 12 also includes a tab bar 57. This tab bar 57 may include icons that provide one touch access to a setting GUI (the gear icon), a help GUI (the question mark icon), the healthcare professional directory (the person icon), facility disclaimers (the chart icon), and a log out option (the log out symbol icon).

[0100] In the healthcare professional system 12, the user input device is for initiating the charge tracker workflow. For example, the user input device (e.g., touchscreen of mobile device 104') may be used for accessing the patient rounding list and creating a patient encounter using the rounding list graphical user interface 47; recording patient encounter information using the patient health record graphical user interface; requesting a code using the coding graphical user interface; and initiating transmission of a bill associated with the patient encounter to a billing agency using the billing graphical user interface.

[0101 ] In the healthcare professional system 12, the software may be secured so as to be compliant with the Health Insurance Portability and Accountability Act

("HIPAA") in protecting personal health information ("PHI"). Moreover, any

communications, including video, audio, and text (e.g., email or text messages), made through the healthcare professional system 12 are secured and/or encrypted.

[0102] The healthcare professional system 12 also enables real time audits of the rounding physician's logging and credentialing procedures.

[0103] Emergency Response System

[0104] The emergency response system 14 disclosed herein connects the mobile device of a healthcare professional (e.g., a medical technician, a consulting physician (e.g., an emergency room doctor), a nurse, etc.) to a suitable physician for the particular emergency with a single click. An example of the emergency response system 14 is shown in FIG. 18.

[0105] As shown in FIG. 18, the emergency response system 14 includes a first mobile device 104", which includes a one touch medical emergency connection button, wireless audio and video connection capability, secure texting capability, and customizable rules for sending and receiving broadcast messages, group calls, and combinations thereof; a communication hub 72 to receive a signal in response to the activation of the one touch medical emergency connection button of the first mobile device 104", and including an integrated scheduler with information for a first on call doctor, and a second on call doctor; and protocol for first attempting to connect the first mobile device 104" with a mobile device of the first on call doctor; and upon

recognizing a failure to connect the first mobile device 104" with the mobile device of the first on call doctor, then attempting to connect the first mobile device 104" with a mobile device of the second on call doctor.

[0106] A method involving the emergency response system 14 may include recognizing that an incoming signal is associated with a one touch medical emergency connection button; identifying, through an integrated scheduler, information for a first on call doctor, and a second on call doctor; and sequentially attempting to connect a first mobile device, from which the incoming signal is received, with a mobile device of the first on call doctor, or the second on call doctor until a connection is established.

[0107] The first mobile device 104" may be the device of an emergency medical technician caring for a patient, or of a physician consulting with a patient, or may be located in an ambulance transporting a patient. In the latter instances, the device 104" may be used by any member of an emergency medical team.

[0108] The one touch medical emergency connection button is displayed as part of the home GUI of a rapid response application, which may be local or web based. The home GUI of a rapid response application is shown in FIG. 18. The home GUI may also include a tab bar 74 that enables a user to switch to a chat, phone, or video mode once a connection is made.

[0109] When pressed, the one touch medical emergency connection button initiates a phone call to a communication hub 72 from the mobile device 104". When pressed, the mobile device 104" may also transmit its location as data accompanying the phone call. In an example, the one touch medical emergency connection button transmits an automated alert with a location of the first mobile device 104" to the communication hub 72.

[01 10] In some examples, the communication hub 72 automatically answers the incoming call, and the signal of call indicates to the hub 72 i) that the call was initiated using the one touch button and ii) the location of the first mobile device 104". The communication hub 72 may include an automated operator that asks the caller to verbally state or type in the type of emergency. In response to receiving a verbal or textual response identifying the emergency, the communication hub 72 accesses the integrated scheduler, which includes information for on call doctors at local hospitals.

[01 1 1 ] The integrated scheduler can identify which on call doctors to attempt to contact by i) the identified type of emergency (e.g., cardiac arrest, stroke, etc.) and ii) by the location information received with the phone call. For example, if the

emergency is a stroke, the integrated scheduler can identify the hospital nearest to the received location and the stroke team doctors of that hospital that are then-currently on call. The integrated scheduler is programmed to retrieve information for a first on call doctor that is suitable for responding to the identified emergency, and a second on call doctor suitable for responding to the identified emergency in case the first on call doctor does not answer his/her mobile device. In some instances, several first on call doctors and several second on call doctors may be identified. For example, with the stroke emergency, the first on call doctor is a first on call vascular doctor, a first on call neurological doctor, or both; and the second on call doctor is a second on call vascular doctor, a second on call neurological doctor, or both.

[01 12] The communication hub 72 includes protocol for first attempting to connect the first mobile device 104" with a mobile device of the first on call doctor; and upon recognizing a failure to connect the first mobile device 104" with the mobile device of the first on call doctor, then attempting to connect the first mobile device 104" with a mobile device of the second on call doctor. When several first on call doctors and several second on call doctors are identified, the communication hub 72 may attempt to connect each of the first on call doctors before attempting to connect each of the second on call doctors. Using the previously mentioned stroke example, the communication hub 72 may attempt to connect the first mobile device 104" with a mobile device of the first on call vascular doctor, and then a mobile device of the first on call neurological doctor if the first on call vascular doctor does not answer, and then a mobile device of the second on call vascular doctor if the first on call neurological doctor does not answer, and then a mobile device of the second on call neurological doctor if the second on call vascular doctor does not answer.

[01 13] While not shown in FIG. 18, in some examples, the emergency response system 14 includes a registration module operatively connected to the communication hub 72; and an admission, discharge, and transfer (ADT) system operatively connected to the communication hub 72. The registration module allows the user of the first mobile device 104" to register the patient prior to arriving at the facility (e.g., hospital). The registration module enables the generation of unique patient IDs that will interface with the hospital's ADT system. The registration module may be capable of accessing a patient directory with multiple search capabilities, such as, by name, date of birth, sex, and identifiers like driver's license, passport, etc. The name alert search is able to retrieve patients with the same first and last names, and flag a user on the hospital ADT end of a potential conflict.

[01 14] In other examples, the communication hub 72 may include a live operator that receives the initial call. In these instances, a computing device may present the location of the first mobile device 104" on a display. The live operator converses with the caller, accesses the integrated scheduler using the computing device, and attempts to call the various on call doctors that are identified.

[01 15] Once a connection between the first mobile device 104" and an on call doctor is made, the communication hub 72 (automated operator or live operator) disconnects from the call. It is to be understood that the communication between the first mobile device 104" and an on call doctor is maintained with the communication hub 72 disconnects.

[01 16] Once a connection between the first mobile device 104" and the on call doctor is made, the on call doctor can virtually assist the emergency medical technician or the consulting physician (who is physically with the patient) with the emergency. The initial connection may be a voice call, but then either the user of the first mobile device 104" or the on call doctor may switch to an audio video call (using tab bar 74) so that the on call doctor can view the patient. If desirable, the initial connection may be transmitted to a chat, where text messages are exchanged.

[01 17] The on call doctor's mobile device may be equipped with or have access to the application described for the healthcare professional system 12. As such, the on call doctor can readily access the patient's electronic health record(s), and can keep track of charges for services rendered during the emergency response

communication.

[01 18] In some examples, the on call doctor's mobile device can also include a digital imaging and communications in medicine viewer; and an electronic prescription platform. The DICOM® viewer allows the on call doctor to view and mark up any DICOM® images in the patient's record. The electronic prescription platform allows the on call doctor to remotely submit a prescription for the patient. In some instances, the prescription may be submitted before the patient reaches the healthcare facility.

[01 19] In some examples, the on call doctor's mobile device includes a camera and associated software that allows the on call doctor to draw a box around an area of interest on the patient (who is shown on the screen using audio video communication) and then to zoom in on the selected area of interest. The camera software may also enable pinch in and out zooming, or swiping to view left, right, up or down.

[0120] The on call doctor's mobile device may also have access to a telemedicine cart. The telemedicine card may provide the on call doctor with the healthcare professional directory, the ability to direct the call to another doctor who may be more appropriate for handing the emergency (e.g., the vascular doctor may hand off the emergency to the neurological doctor), and/or to make another consultation call while in communication with the first mobile device 104". The telemedicine cart may also provide the on call doctor with the ability to associate an escalation level with the emergency so that the team at the hospital is aware of the severity of the emergency when the patient arrives. The escalation levels may also implement a call-forwarding feature that attempts to link in or forward the communication with the first mobile device 104" to another, more appropriate physician for the particular emergency. [0121 ] In the emergency response system 14, the software may be secured so as to be compliant with the Health Insurance Portability and Accountability Act ("HIPAA") in protecting personal health information ("PHI"). Moreover, any communications, including video, audio, and text (e.g., email or text messages), made through the emergency response system 14 are secured and/or encrypted.

[0122] Medical Equipment

[0123] Any examples of the systems 10, 12, 14 disclosed herein may include medical equipment 208. In any of the example systems 10, 12, 14, the medical equipment 208 may be located proximate to the patient. Referring now to FIG. 3, a block diagram depicting an overview of suitable medical equipment 208 is provided. In an example, the medical equipment 208 interacts with a base station using a communications network such as a LAN, as described above. Either a single LAN may be used, with one or more devices communicating with the base station using a single communications network, or multiple LANs may be used, with each allowing one or more devices to communicate with the base station. Alternatively, in an example, the medical equipment 208 interacts directly with a remotely located server 102 or other computing device using a WAN 103.

[0124] In an example, the medical equipment 208 communicates with a base station using a LAN with the ZigBee specification. ZigBee allows for the creation of a local area network using small, low-powered digital radios. ZigBee is secured by symmetric encryption keys, allowing for the transmission of encrypted data. In an example, the base station serves as the coordinator of the ZigBee network, with each of the associated devices acting as nodes. The network may be structured in a star configuration (wherein each medical device communicates directly with the base station), a tree configuration (wherein some medical devices communicate with each other while others communicate directly with the base station), a mesh configuration (wherein each medical device communicates with every other medical device and the base station), or in another suitable configuration, as recognized by one of skill in the art. [0125] As shown in FIG. 3, in an example, the medical equipment 208 includes: a height-measuring unit 302; ultrasound/Doppler probes 304; a stethoscope 306; a microscope 308; a temperature measuring unit 310; a pulse oxidation ("pulse ox") measuring unit 312; a weight measurement unit 314; a sensor 316 to analyze blood so as to measure troponin, complete blood count ("CBC"), and/or electrolytes in the blood and/or to detect congestive heart failure and fluid retention; a blood pressure (BP) measuring unit 318; a fundus camera 320; an electrocardiograph ("ECG" or "EKC") 322; and an ophthalmoscope 324. Other examples of medical equipment 208 include a body fat analyzer or a tonometer. As will be understood by one of skill in the art, still other medical devices may also be adapted for use in a system in accordance with the examples disclosed herein.

[0126] Generally speaking, any medical device 208 may be adapted to work with a system 10, 12 14 disclosed herein by supplying a component of the system 10, 12, 14 with an appropriately configured adapter, such as the adapter discussed below.

Additionally, particular examples of specialized medical devices 208 designed to operate with any of the systems 10, 12, 14 in accordance with an example of the present invention are herein.

[0127] Height Unit

[0128] A device for measuring the height of a person (a "Height Unit"), such as a patient, for use in a system 10, 12, 14 disclosed herein. With reference to FIG. 4, a block diagram illustrating component parts of a Height Unit 400 is shown. In an example, the Height Unit 400 includes a microcontroller 406, such as an RL-78 microcontroller. In an example, the microcontroller 406 is attached to an input device 408 (such as a switch), an accelerometer 410, an output device 412 (such as a buzzer), a communications unit 414 (such as a ZigBee unit), and an ultrasonic sensor 416. The Height Unit 400 may also include a low battery indicator 418 and a power-on indicator 420. These indicators 418, 420 may be in the form of light emitting diodes ("LEDs").

[0129] In an example, the Height Unit 400 includes a power supply 404. In an example, the power supply 404 is separate from the main body 402 of the Height Unit 400. In an example, the power supply 404 includes a battery 422 and a power switch 424 configured to disconnect the battery from the main body 402 of the Height Unit 400. In an example, the battery 422 is a nine-volt (9V) battery. In an example, the power supply 404 further comprises a low-dropout ("LDO") regulator 426 which provides a minimum voltage supply to the Height Unit 400, such as a five-volt (5V) supply.

[0130] In an example, the battery 422 is a rechargeable battery (e.g., a lithium-ion battery) of approximately 3,500 mAH. This type of battery 422 will provide

approximately 7-8 hours of uninterrupted operation. The capacity of the battery 422 may be increased to provide additional operational hours needed without recharging.

[0131 ] In an alternative example, the Height Unit 400 is powered by an alternating current (AC) power supply rather than a battery 422. In an example, the Height Unit converts the AC signal to a direct current (DC) signal using an AC/DC converter. In an example, the power switch 424 is connected so as to disconnect the main body 402 of the Height Unit 400 from the power supply 404.

[0132] In an example, the switch 408 attached to the microcontroller 406 enables manual control of the Height Unit 400 by an individual in physical proximity to the Height Unit 400. For example, a nurse may cause the Height Unit 400 to begin collecting measurements by flipping the switch 408.

[0133] In an example, the ultrasonic sensor 416 is used to measure the distance between the Height Unit 404 and the floor. By holding the Height Unit 400 level and even with the top of a patient's head, the height of the patient may be determined. In an example, the Height Unit 400 uses the accelerometer 410 to determine when the Height Unit 400 is level, thereby preventing incorrect measurements from being obtained.

[0134] As shown in FIGS. 5a and 5b, in an example, a Height Unit 500 includes a body 502 sized so as to fit on a person's head. A chin strap 504 is attached to the body 502 and is configured so as to secure the Height Unit 500 on a person's head. The body 502 includes a protrusion 502a located at the forward end of the Height Unit 500. A rear portion 502b is located on the body 502 opposite the protrusion 502a and holds a plurality of downward-facing ultrasonic sensors 416. In an example, the body 502 is configured to house one or more accelerometers 410, ultrasonic sensors 416, the microcontroller 406, the ZigBee module 414, and the power supply 404. In an example, the indicators 418, 420, and switch 408 are mounted on the exterior surface of the body 502.

[0135] As shown in FIGS. 5a and 5b in an example, the protrusion 502a extends laterally from the body 502. In use, the interior surface of the body 502 rests against the highest portion of a patient's head. The body 502 is thereby positioned next to the patient's head. When the one or more accelerometers 410 indicate that Height Unit 500 is held level, that is, held so that the protrusion 502a is substantially parallel to the floor, the microcontroller 406 uses the plurality of ultrasonic sensors 416 to measure the distance between the Height Unit 500 and the floor. If necessary, the

microcontroller 406 can adjust the distance (e.g., by adding in the distance between the plurality of ultrasonic sensors 416 and the bottom surface of the protrusion 502a) so as to accurately determine the person's height. As will be clear to one of skill in the art, other methods may be used to calculate the height of a person using the one or more accelerometers 410 and the plurality of ultrasonic sensors 416 in the Height Unit 500.

[0136] In an example, a buzzer, speaker, or other sound generating device 412 attached to the microcontroller 406 produces a sound to indicate that a height measurement has been successfully obtained. For example, one tone may sound to indicate that the Height Unit 500 is waiting to obtain a measurement until the Height Unit 500 is held level. A second tone may then play to indicate that the height measurement has been obtained.

[0137] Once the height measurement is obtained, the microcontroller 406 may then use the ZigBee module 414 (or another communication module) to communicate the measured height to the base station 106, the server 102, the mobile device 1 10', and/or directly to a physician located remotely from the Height Unit 500. In an example, this communication occurs wirelessly. In an example, the measurement is sent from the microcontroller 406 to a Single Board Controller ("SBC"). The SBC may be, by way of example, a tablet PC such as portable tablet 1 12, a handheld device 1 1 1 , a portable computer 1 13, or another computer 105 running a master program and located remotely from the Height Unit 500. There need not be any wired connection between the Height Unit 500 and the SBC and the signal may be transmitted using a communication network such as the network 103. As such, the Height Unit 500 may be operated by a remotely located physician.

[0138] As shown in FIGS. 6a and 6b, in an example, a Height Unit 600 includes a body 602 attached to a chin strap 604 and an arm 606 which extends away from the rear of the body 602. The arm 606 is configured to hold the plurality of ultrasonic sensors 416 on a downward facing side thereof. In an example, the arm 606 is configured to move between a retracted position (as shown in FIG. 6a) to an extended position (as shown in FIG. 6b). The extended position enables the plurality of ultrasonic sensors 416 to have an unobstructed path to the floor. In the retracted position, the arm 606 takes up less room so as to allow for easy storage and transportation of the Height Unit 600.

[0139] As shown in FIGS. 6c and 6d, in an example, a Height Unit 620 comprises a body with a forward support 610a and rearward support 610b and an arm 608 configured to hold the plurality of ultrasonic sensors 416 on a downward facing side thereof.

[0140] Weight Unit

[0141 ] A device for measuring the weight of a person (a "Weight Unit"), such as a patient, for use in the systems disclosed herein 10, 12, 14 will now be discussed. With reference to FIG. 7, a block diagram illustrating component parts of a Weight Unit 700 is shown. In an example, a Weight Unit 700 includes a microcontroller 706, such as an RL-78 microcontroller. In an example, the microcontroller 706 is operatively connected to an input device 708 (such as a switch), an analog to digital converter (ADC) module 716, and a communications unit 714 (such as a ZigBee unit). The ADC module 716 may in turn be operatively connected to a preamplifier 712 (also termed a preamplification module or preamp), which in turn may receive the output from a weight-loading cell 710. The weight-loading cell 710 creates an analog output signal indicative of the amount of force applied to the cell 710. For example, the weight- loading cell 710 may include a strain gauge that deforms in a predictable fashion when subjected to a force, thereby reflecting the magnitude of the force applied to the strain gauge in the deformation of the gauge. This deformation is further reflected in the change in magnitude of an electrical signal; as the strain gauge deforms, the effective electrical resistance of a wire similarly changes, thereby generating an analog signal representative of the force. In an example, four strain gauges may be used in a Wheatstone bridge configuration in a single load cell 710.

[0142] By having a patient stand on the weight-loading cell 710, an analog signal representative of the patient's weight may be obtained. This analog signal is magnified, if necessary, by the preamp module 712 and converted to a digital signal by the ADC module 716. The signal is then provided to the microcontroller 706, which may convert the signal into a number representing the person's weight and transmit that number to the base station, the server 102, the mobile device 1 10', or directly to a computing device in proximity to a remotely located physician using the

communication module 714. Alternatively, the signal may be converted once it received by the base station 106, server 102, the mobile device 1 10', or other computing device in proximity to the remotely located physician. In an example, the measurement is sent from the microcontroller 706 to an SBC. The SBC may be, by way of example and not limitation, a tablet PC such as portable tablet 1 12, a handheld device 1 1 1 , a portable computer 1 13, or another computer 105 running a master program and located remotely from the Weight Unit 700. There need not be any wired connection between the Weight Unit 700 and the SBC and the signal may be transmitted using a communication network such as the network 103. As such, the Weight Unit 700 may be operated by a remotely located physician.

[0143] In an example, a buzzer, speaker, or other sound generating device (not shown) may be attached to the microcontroller 706. In an example, the buzzer is used to indicate that a weight measurement has been successfully obtained. For example, one tone may sound to indicate that the Weight Unit is waiting to obtain a

measurement until a reliable reading can be saved. A second tone may then play to indicate that a measurement has been successfully obtained. In an alternative example, another output device (such as a display) is used to provide feedback to a patient. In an example, a display is operatively connected to the microcontroller 706 and displays a patient's weight visually.

[0144] In an example, the Weight Unit 700 resolves a patient's weight in multiples of 10 grams with a minimum weight sensitivity of 500 grams and maximum capacity of 400 kilograms.

[0145] In an example, the Weight Unit 700 comprises a power supply 704 and a main body 702. In an example, the Weight Unit is battery powered and the power supply 704 comprises a battery 722 (such as a 9V battery), a power switch 724, and an LDO 726. In an example, the battery 722 is a rechargeable battery (e.g., a lithium- Ion battery) of approximately 3,500 mAH. Such a battery will provide approximately 7- 8 hours of uninterrupted operation. The capacity of the battery 722 may be increased to provide additional operational hours needed without recharging. In an example, the Weight Unit 700 includes a low battery indicator 718 and a power-on indicator 720. These indicators 718 720 may be in the form of light emitting diodes, or LEDs. In an example, the battery 722 is a nine-volt battery and the low-dropout regulator (LDO) provides a minimum power supply, such as a five-volt supply, to the Weight Unit 700. In an example, the power switch 724 is configured so as to connect or disconnect the power supply 704 from the main body 702.

[0146] In an alternative example, the Weight Unit 700 may be powered by a standard AC power supply. The Weight Unit may convert the AC signal to a DC signal using a standard AC/DC converter. A power switch may be connected so as to disconnect the Weight Unit from the power supply.

[0147] In an example, the Weight Unit 700 includes a housing with a lower horizontal plate separated from an upper horizontal plate. The load cell 710 is located therebetween, such that when a patient steps onto the upper horizontal plate, force is transferred from the upper horizontal plate through the load cell to the lower horizontal plate and the floor.

[0148] In an example, the Weight Unit 700 is configured such that a mechanical frame may be removably attached to the Weight Unit 700. By way of example, the mechanical frame may be removably attached to the upper horizontal plate. In an example, the mechanic frame is configured to removably hold a baby-carrier or other baby-holding mechanism. By first measuring the weight of the mechanical frame and baby-carrier alone before measuring the weight of these items with an infant placed in the baby-carrier, the Weight Unit may be used to accurately and easily determine the weight of an infant.

[0149] Stethoscope

[0150] A specialized stethoscope (Stethoscope Module) for use in a system 10, 12, 14 disclosed herein will now be discussed.

[0151 ] As is known by one of skill in the art, a stethoscope is an acoustic medical device for listening to the internal sounds of a human body. A stethoscope may be analog and transmit sound acoustically between a bell and one or more earpieces, for example, by utilizing a series of hollow air-filled tubes to carry the sound. Alternatively, a stethoscope may be electronic and convert the acoustic sound waves into electrical signals. Examples disclosed herein may use either design.

[0152] With reference to FIG. 8, a block diagram illustrating component parts of a Stethoscope Module 800 is shown. The Stethoscope Module 800 connects to the ear connector(s) 810 of a standard acoustic stethoscope or electronic stethoscope.

Alternatively, in an example, the Stethoscope Module 800 is configured to directly receive an electrical signal from an electronic stethoscope. In an example, the

Stethoscope Module 800 includes a microcontroller 806, such as an RL-78

microcontroller. In an example, the microcontroller 806 is operatively connected to an input device 808 (such as a switch), a communication module 814, and a

microphone/preamplifier module 812. Alternatively, in an example, the microcontroller 806 is directly connected to an electronic stethoscope and receives an electrical signal therefrom. The microphone input and preamp module receives the input from a stethoscope ear connector. In an example, the communication module 814 is a Bluetooth module containing a transceiver for communicating with another remotely located transceiver utilizing the Bluetooth protocol.

[0153] In an example, the Stethoscope Module 800 is wirelessly connected to a stethoscope, for example through the use of the communication module 814. In an example, the communication module 814 comprises a Bluetooth transceiver which allows the Stethoscope Module to be located remotely from the stethoscope. For example, the majority of the Stethoscope Module may be stored in a backpack or worn on a strap around an individual's neck. A small subunit containing a Bluetooth transceiver and the microphone input and preamp module may be plugged into the stethoscope's earpiece so as to allow the Stethoscope Module 800 to receive and transmit sounds from the stethoscope to the base station 106, the server 102, the mobile device 1 10', or another computing device such as a computing device located proximate to a remotely located physician.

[0154] In the case of an acoustic stethoscope, the microphone input and preamp module 812 is configured to include a microphone to convert the acoustic sound waves into electrical signals. The preamplifier 812 is configured to amplify the electrical signals as needed prior to transmitting the signals via the Bluetooth module to the microcontroller. In an example, the microphone input and preamp module 812 is configured to directly receive the electrical signals output by an electric stethoscope. In an example, the preamplifier is configured to boost the electric signals prior to relaying them to the microcontroller 806.

[0155] In an example, the Stethoscope Module 800 is located in close proximity to the stethoscope. In such an example, as shown in FIG. 8 the microphone input and preamp unit 812 may be directly connected to the microcontroller 806, without utilizing the communication module 814.

[0156] In an example, the Stethoscope Module 800 comprises a power supply 804 and a main body 802. In an example, the power supply 804 comprises a battery 822. In an example, the battery 822 is a rechargeable battery (e.g., a lithium-ion battery) of approximately 3,500 mAH. Such a battery will provide approximately 7-8 hours of uninterrupted operation. The capacity of the battery 822 may be increased to provide additional operational hours needed without recharging. The Stethoscope Module 800 may also include a low battery indicator 818 and a power-on indicator 820. These indicators 818 and 820 may be in the form of light emitting diodes, or LEDs.

[0157] In an example, the power supply 804 comprises a nine-volt battery 822 coupled to a low-dropout regulator (LDO) 826 which provides a minimum power supply, such as a five-volt supply, to the main body 802. In an example, a power switch 824 is connected so as to disconnect the battery and the LDO from the main body 802. In an alternative example, the Stethoscope Module comprises a standard AC power supply. The power supply 804 converts the AC signal to a DC signal using a standard AC/DC converter. In an example, a power switch 824 is connected so as to disconnect the main body 802 of the Stethoscope Module 800 from the power supply 804.

[0158] As shown in FIG. 9a, in an example, a Stethoscope Module 900 includes a body 902 with a pair of ear connectors 904a and 904b, each disposed on an end of the body 902. In an example, the body 902 is supported by a stand 906. In an example, the components of the Stethoscope Module 800 are housed within the body 902. In an example, the body 902 includes a diaphragm 908 centrally disposed on the body 90 for recording a patient's heartbeat without the use of a separate stethoscope. The diaphragm 908 is operatively connected to the microcontroller 806. In use, the Stethoscope Module 900 is held such that the diaphragm is proximate to a patient's chest. By measuring small changes in air pressure, the diaphragm 908 may record the patient's heartbeat. Alternatively, a standard stethoscope may be employed by placing the stethoscope's earpieces proximate to the ear connectors 904a and 904b.

[0159] As shown in FIG. 9b, once the stethoscope 910 is properly connected to the Stethoscope Module 900, the stethoscope may be used as usual.

[0160] In an example, a buzzer, speaker, or other sound generating device (not shown) may be operatively attached to the microcontroller 806 and configured to produce a sound to indicate that a measurement has been successfully obtained. For example, one tone may sound to indicate that the Stethoscope Module 800 is ready to obtain a measurement. A second tone may then play to indicate that the Stethoscope Module 800 has successfully obtained a measurement and may be removed from a patient's chest.

[0161 ] Medical Device Adapter

[0162] An adapter for using a standard medical device with a system 10, 12, 14 disclosed herein will now be discussed. In an example, the adapter 1000 is connected to a standard or off the shelf medical device (not shown), such as by way of example and not limitation, a pulse oxidizer, a stethoscope, a scale, an EKG, a blood pressure monitor, or another medical device. The adapter 1000 then relays information produced by the medical device to another device, such as a base station 106. In an example, the adapter 1000 relays information directly to a computing device 104 located proximate to a physician. In an alternative example, the adapter relays information indirectly, such as through a base station 106, server 102, or another intermediary device.

[0163] In an example, the adapter 1000 receives commands from another device, such as the base station 106, a server 102, or another device such as a computer device located proximate to a physician. In an example, the adapter 1000 comprises an output module (not shown) operatively connected to the medical device and controls the operation of the standard medical device to which it is attached based on the received commands. In this way, the adapter effectively allows a remotely located user (such as a physician) to receive the information produced by the medical device and control the medical device, just as if the physician were physically located proximate to the medical device.

[0164] In an example, the adapter 1000 includes a microcontroller 1006, such as an RL-78 microcontroller. The microcontroller 1006 governs the operation and functioning of the adapter 1000. In an example, the microcontroller 1006 is attached to a communications unit 1014 (such as a ZigBee and/or Bluetooth module). The communications unit 1014 enables communication between the adapter 1000 and the base station 106 or other computing devices. In an example, the adapter 100 includes an input device or sensor 1010 which is configured to receive information from a particular medical device. For example, the input device 1010 may comprise a microphone, a camera, a pressure sensor, or an input terminal for receiving an electrical signal either wirelessly or via one or more wires. In an example, the adapter 1010 includes an output device (not shown) which is configured to provide commands to a particular medical device. For example, the output device may comprise one or more servomotors or other actuators, a speaker, or an output terminal for outputting an electrical signal either wirelessly or via one or more wires. In an example, the adapter includes a manual input device (not shown), such as, for example, a switch, keyboard, mouse, or touchscreen. In an example, the manual input device allows an individual located in proximity to the adapter 100 to interact with the adapter 1000. For example, a first position of a switch may indicate that the adapter 1000 should begin

communicating with the base station 106.

[0165] In an example, the adapter 1000 comprises a display, such as a liquid crystal display (LCD) 1002. In an example, the LCD 1002 is used to display

information to a user of the adapter 1000.

[0166] In an example, the adapter 1000 includes a power supply 1004 and a main body 102. In an example, the adapter is battery powered. In an example, a

rechargeable battery (e.g., a lithium-ion battery) of approximately 3,500 mAH is used. Such a battery will provide approximately 7-8 hours of uninterrupted operation. The capacity of the battery may be increased to provide additional operational hours needed without recharging. The adapter 1000 may also include a low battery indicator 1016 and a power-on indicator 1018. These indicators 1016 and 1018 may be in the form of light emitting diodes, or LEDs. In an example, the power supply 1004 comprises a nine-volt battery coupled to a low-dropout regulator (LDO), which provides a minimum power supply, such as a five-volt supply, to the main body 1002 of the adapter 1000. In an example, a power switch is connected so as to disconnect the battery and the LDO. In an alternative example, the power supply 1004 is a standard alternating current (AC) power supply. The power supply 1004 converts the AC signal to a direct current (DC) signal using a standard AC/DC converter. In an example, a power switch is connected so as to disconnect the adapter from the power supply.

[0167] For example, an adapter may be configured to interact with a standard optical microscope. Such an adapter may include an input device including one or more cameras which are configured to interact with the eye pieces on the microscope and an actuator configured to adjust the position of a slide under the microscope's lens. By viewing images transmitted from the cameras and sending commands to the actuators, a remotely located physician may interact with the microscope just as if he were physically present. [0168] Pulse Oximeter

[0169] A specialized pulse oximeter (referred to herein as a pulse oximeter or oximetry module) for use in 10, 12, 14 disclosed herein will now be discussed.

[0170] As is known by one of skill in the art, pulse oximetry is a non-invasive method for measuring a person's oxygen, or O_2, saturation. Pulse oximetry measures the wavelengths of light that are preferentially absorbed by either oxyhemoglobin or deoxyhemoglobin. Pulse oximetry may be performed using either transmissive pulse oximetry or reflectance pulse oximetry. To perform transmissive pulse oximetry, a sensor may be placed on a thin part of a person's body, such as the tip of a finger or an earlobe, opposite a light source. By passing light through the person's body and measuring the changes in absorption of various wavelengths of light, the person's O2 saturation may be determined. For reflectance pulse oximetry, the sensor is placed adjacent to the light source and measures the wavelengths of backscattered light. Examples of the present invention may use either design.

[0171 ] With further reference to FIG. 10, in an example, an Oximetry Module may include a structure similar to the adapter 1000 discussed above. In an example, the Oximetry Module includes a microcontroller 1006, such as an MSP 430 microcontroller or a RL-78 microcontroller. In an example, the microcontroller 1006 is attached to a display device 1008, such as a liquid crystal display (LCD) to display information to a person proximate to the Oximetry Module. The Oximetry Module may further include a wireless communication unit 1014 (such as a ZigBee unit). The microcontroller 1006 is connected to one or more light emitters and light sensors, such as an infrared ("IR") light emitter, a red light emitter, an IR light sensor and a red light sensor. In an example, the IR emitter is configured to emit light at a wavelength of 660 nm and the IR emitter is configured to emit light at a wavelength of 940 nm. In an example, a single photodiode is used to detect both IR and red light. In an example, the light emitters are LEDs configured to cycle through a sequent IR LED on, red LED on, then both off at a rate of thirty times per second. In an example, the emitter and sensor are arranged for transmissive oximetry. In an example, the emitter and sensor are arranged for reflective oximetry. In an example, a combined IR emitter/detector is used. In an example, the IR emitter and detector are connected to the microcontroller via an h-bridge circuit. Based on the light detected by the IR emitter, the microcontroller may determine various information regarding a patient, such as the patient's O2, saturation. This information may then be transmitted from the Oximetry Module to the base station 106, the server 102, the mobile device 1 10', or another computing device such as a computing device located proximate to a remotely located physician. Alternatively, the Oximetry Module may transmit the raw measurements obtained from the IR detector for later interpretation.

[0172] In an example, the Oximetry Module is battery powered. A rechargeable battery (e.g., a lithium-ion battery) of approximately 3,500 mAH may be used. Such a battery will provide approximately 7-8 hours of uninterrupted operation. The capacity of the battery may be increased to provide additional operational hours needed without recharging. The Oximetry Module may also include a low battery indicator and a power-on indicator. These indicators may be in the form of light emitting diodes, or LEDs. Power may be supplied to the Oximetry Module by a nine-volt battery coupled to a low-dropout regulator (LDO), which provides a minimum power supply, such as a five-volt supply, to the adapter. A power switch may be connected so as to disconnect the battery and the LDO. In an alternative example, the Oximetry Module may be powered by a standard AC power supply. The Oximetry Module may convert the AC signal to a DC signal using a standard AC/DC converter. A power switch may be connected so as to disconnect the Oximetry Module from the power supply.

[0173] In an example, the measurement is sent from the microcontroller to a Single Board Controller ("SBC"). The SBC may be, by way of example and not limitation, a tablet PC such as portable tablet 1 12, a handheld device 1 1 1 , a portable computer 1 13, or another computer 105 running a master program and located remotely from the Oximetry Module. There need not be any wired connection between the Oximetry Module and the SBC and the signal may be transmitted using a communication network such as the network 103. As such, the Oximetry Module may be operated by a remotely located physician.

[0174] In an example, the Pulse Oximeter includes a body configured to surround a patient's finger. A first portion of the body is placed beneath the patient's finger and a second portion of the body is placed above the patient's finger. The two portions are joined by a hinge which is spring loaded so as bias the two portions together. In an example, the light emitters are located on the first portion facing the light sensors located on the second portion opposite thereto. In an alternative example, the body comprises a single portion which may be held against a patient's skin. The light emitters and light sensor are located adjacent to one another.

[0175] BP Measurement Unit

[0176] A specialized blood pressure (BP) monitoring unit (referred to as a "BP Unit," a "BP Measurement Unit" herein) for use in a system 10, 12, 14 disclosed herein will now be discussed.

[0177] A blood pressure meter or sphygmomanometer is a device used to measure a person's blood pressure. A blood pressure monitor may include an inflatable cuff which is placed around a patient's arm. An automatic pump increases the pressure in the cuff and restricts the blood flow through the patient's arm. A sensor in the meter measures the pressure in the cuff. Typically, the meter records the pressure at which blood flow (i) just begins flowing through the arm and (ii) flows unimpeded. In use, the cuff is placed smoothly and snugly around the patient's upper arm, at roughly the same vertical height as the patient's heart while the patient is seated with his or her arm supported. The cuff must be appropriately sized for the patient; if the cuff is too loose, the meter will register an incorrect low pressure while if the cuff is too tight, the meter will register an incorrectly high pressure. A blood pressure measurement may include both the systolic pressure, or pressure in a person's arteries when his or her heart beats (e.g., contracts) and the diastolic pressure, or pressure in the person's arteries between heartbeats (e.g., while the heart relaxes).

[0178] With further reference to FIG. 10 and the associated description above, in an example, the electronics contained in a BP Unit are generally similar to those in the adapter 1000. In an example, the sensor 1010 includes a pressure gauge configured to measure the pressure in a cuff. In an example, the sensor 1010 further comprises a transducer configured to measure vibrations in the cuff.

[0179] As shown in FIG. 1 1 , in an example, the BP Unit 1 100 includes a housing 1 102 including a display 1 104, an input device 1 106, a storage compartment 1 108 which may be sealed with a cover 1 1 10, a pump and a pressure gauge (located within the housing 1 102). The BP Unit 1 100 further includes a cuff 1 1 12 which may be held in the storage compartment 1 108 while not in use. In an example, the cuff 1 1 12 is removable from the BP Unit 1 100 and may be replaced with a cuff 1 1 12 of a different size so as to ensure the cuff 1 1 12 is properly sized for a particular patient. In an example, the BP Unit 1 100 further includes a transducer or oscillometer (not shown) located in the cuff 1 1 12 and configured to generate a signal representative of the vibrations in the cuff 1 1 12 and enable the determination as to whether blood is flowing through arteries in patient's arm.

[0180] In an example, BP Unit 1 100 is operated by wrapping the cuff around a patient's upper arm. In an example, a signal provided by the input device 1 106 indicates that the BP Unit 1 100 should begin taking measurements. The pump increases the pressure in the cuff 1 1 12 until the microcontroller determines that the pressure in the cuff has reached a target level, before gradually decreasing the pressure in the cuff while the pressure gauge records the pressure in the cuff 1 1 12. In an example, the target pressure is approximately 20mm Hg above systolic pressure for the patent. In an example, the display 1 104 graphically displays the current blood pressure reading, along with an indication as to whether the measurement is complete. In an example, the display 1 104 provides simultaneous readout of systolic/diastolic pressure and pulse rate. In an example, the BP Unit 1 100 provides alert(s) to the user if it detects an irregular heartbeat.

[0181 ] Other Medical Devices

[0182] As will be understood by one of skill in the art, other specialized medical devices may be adapted for use with the system 10, 12, 14 disclosed herein, either by creating a specialized version of the medical device or through the use of an adapter, as described herein. Additional medical devices, including but not limited to those shown in FIG. 3, are also contemplated. [0183] Room Automation

[0184] Equipment will now be discussed for automating a patient's environment, such as a patient's room, for use in a system 10, 12, 14 in accordance with an example disclosed herein.

[0185] Many variables relating to a patient's environment can typically be controlled by a physician located proximate to a patient, particularly in a controlled setting such as a hospital room. The intensity of the lights, the temperature of the room, the position of the bed, and other sources of noise such as a television (TV), fan, or air conditioning unit may all be controlled by such a physician. However, these variables typically require adjustment by a person physically present in the room. Accordingly, a need exists for a physician located remotely from a patient to be able to exercise similar control using telemedicine. Further, in the event that a physician and a patient are interacting using videoconferencing as described herein, it is advantageous for the physician to be able to adjust the room conditions to create an optimal environment for such interaction. For example, it may be desirable to eliminate all sources of background noise and increase the intensity of the lighting for the duration of the videoconferencing. Such control is provided to a remotely located physician by room automation equipment.

[0186] In an example, the system 10, 12, 14 interacts with standard room

automation equipment to allow a remotely located individual to control the room's conditions. In an alternative example, customized room automation equipment is provided.

[0187] With reference to FIG. 12, a block diagram illustrating several room automation modules is depicted. As shown in FIG. 12, in an example, a lighting and room automation unit 1202 ("Automation Unit") controls a plurality of separate devices, including a television (TV) 1204 (using a TV Module), lighting 1206 (using a Lighting Module), a bed 1208 (using a Bed Module), a fan 1210 (using a Fan Module), and an air conditioner 1212 (using an Air Conditioning Module).

[0188] The Automation Unit 1202 may include a microcontroller and a

communication unit, such as a ZigBee unit, to enable the Automation Unit 1202 to communicate with the base station 106, server 102, or other computing devices. The Automation Unit may include an additional one or more automation communication units adapted to communicate with the room automation equipment. For example, an automation communication unit may comprise an infrared (IR) emitter and/or receiver, thereby enabling interaction with a standard TV IR receiver without the need for a separate TV Module. Alternatively, an automation communication unit may comprise a wireless or wired transmitter, such as a ZigBee or Bluetooth unit. Each room automation device, such as the TV Module, Lighting Module, etc., may include a corresponding automation communication unit. In this way, the Automation Unit may communicate with each of the room automation devices directly. The Automation Unit may transmit information regarding the current conditions of the room, such as the lighting level, temperature, fan speed, and whether the TV is currently on and what channel is being watched. The Automation Unit may receive commands indicating changes that should be made to the room automation equipment, such as turning off the TV or reducing the fan speed. In an example, the Automation Unit is incorporated into the base station.

[0189] The Lighting Control Unit 1206, for example, may include a microcontroller and a lighting control unit communicatively coupled with an automation communication unit in the main Automation Unit. In an example, the Lighting Control Unit may further comprise a mechanism for adjusting the room lights, such as a dimmer switch connected in series with the room light's power supply. By adjusting the level of power supplied to the room lights, the level of light in the room may be controlled. As will be understood by one of skill in the art, similar devices may be used to control other systems in the room. In an example, specialized devices (such as a specialized bed, TV, fan, etc.) comprise sensors, a microcontroller, and a communication unit and transmit the device's status and receive commands from the Automation Unit 1202.

[0190] Alarm and Patient Monitoring System

[0191 ] Equipment for monitoring a patient remotely for use in the system 10, 12, 14 disclosed herein will now be discussed.

[0192] Typically, a care provider such as a doctor or nurse must be physically present in a patient's room in order to monitor the patient. For example, it may be desirable to monitor whether a patient has moved or the status of a patient's vital signs. When a patient begins moving or has a significant change in status, a health care provider may need to take steps to adjust the patient's treatment or perform additional tests. In order to better enable treatment and monitoring by a remotely located physician, devices for monitoring a patient remotely are needed.

[0193] In an example, the system 10, 12, 14 disclosed herein provides remote monitoring and automated alerts when a patient's status changes.

[0194] With reference to FIG. 13, such an alarm and monitoring system may include several components to comprehensively monitor a patient's status. As shown in FIG. 13, the alarm and monitoring system 1300 may include a central controller 1302. In an example, this controller is implemented in the base station 106. In an alternative example, this controller is a separate piece of hardware and includes a microcontroller and at least one communication interface for interacting with other devices. The system 1300 may include one or more motion detectors 1304 to monitor patient movement. For example, a motion detector 1304 may include a sensor such as an IR sensor or an ultrasonic sensor to detect movement. Once movement is detected, the motion detector may notify the controller, which may then send an alert to the base station 106, a server 102, the mobile device 104', or another computing device. Alternatively, the motion detector may itself provide a notification. Such notification may be sent to a remotely located physician, for example, using the software as discussed herein, or may notify a health care provider in proximity to the patient.

[0195] Similarly, a sensor 1306 may be attached to a patient's body, such as a patient's wrist or fingers, so as to detect patient movements. In an example, a sensor 1308 is configured to monitor a patient's vital signs, such as a patient's heartbeat, and provide an alert based on a change in patient status. Alternatively, standard medical equipment such as a heart rate monitor may be employed, with a device adapted to detect an alert such as an audible alert. Upon detecting an audible alert, a notification may be sent via the base station to the server 102 or a remote computing device. In an example, a single device attached to a patient's wrist or finger comprises multiple sensors and is configured to monitor both movement and a patient's vital signs. [0196] In an example, an RFID tag is attached to a patient. Sensors are located in one or more locations; for example, sensors may be located in multiple rooms in a treatment facility. The RFID tag may be used to track a patient's movements through the treatment facility. In an example, sensors are located at one or more pieces of medical equipment and are used to identify the patient being examined by the medical equipment. In an example, RFID tags are attached to containers of medication and are used to track the location of the containers within the treatment facility.

[0197] By using monitoring and alarm systems in accordance with examples disclosed herein, a single nurse or physician may monitor multiple patients at once.

[0198] Other alerts that are contemplated may include reminders for the patient using the system 10, admission alerts using the system 14, hand off alerts using the system 12, alerts to primary care physicians after a patient has been admitted using the system 14, or any other notifications described herein.

[0199] Equipment Designs

[0200] Various examples of equipment designs in accordance with examples disclosed herein will now be discussed. In an example, the equipment such as the base station 106 is portable. The equipment may be adapted to include a trolley or backpack so as to enable easy transportation.

[0201 ] A device may include one or more wheels to provide movement. These wheels may be operated by one or more servomotors, enabling the wheels to turn independently. Further, as shown in FIGS. 12-19, the device may include a camera, a microphone, a screen, and speakers. The device may be integrated with the base station 106 described herein. The device may include one or more compartments to store additional devices, medications, or other objects. In an example, the video camera may rotate independently and includes a zoom lens. The device may be controlled remotely, for example, by a physician using the various GUIs disclosed herein. Alternatively, the device may be automated or controlled by a program running on either the device or another computing device, such as the server 102. [0202] The device may include a camera and screen. The device may include a height adjuster. The height adjuster may be located on the bottom surface of the device. The device may include an area for storage. The device may include lighting.

[0203] The device may be configured so as to fit into a backpack. The device may include a camera and a screen. While not in use, the camera and screen may be contained inside the device. The camera and screen may then fold out, be uncovered, or otherwise be removed from the device when in use. The device may include one or more compartments for storage. In an example, the device is integrated into a backpack. The device may be configured to interact with one or more external add-on modules. These modules may increase the functionality of the device.

[0204] Software

[0205] Software for use with a system 10, 12, 14 disclosed herein will now be discussed. As discussed herein, the software may run locally on one or more computing devices or may be transmitted to a computing device from a remote server. The software may enable communication using text, audio, and/or video between individuals located in separate locations. Further, the software may provide for the exchange of other information, such as images comprising the results of medical tests. In example various examples, the software applications described herein may be implemented as instructions carried out by one or more hardware devices, as logical circuits or specialized hardware devices, or by any combination of the foregoing.

[0206] One example of the software is the DICOM viewer. A related software component in accordance with an example disclosed herein may operate on a portable device such as a smartphone or iPhone. This related sotware may contain features similar to the DICOM viewer, and additionally may include a list of patients customized for each doctor, a barcode scanner, an image scanner and data extractor (to extract data surrounding a barcode), and encrypted communications including video, audio, and text between devices. This software may be integrated with existing billing systems for insurance providers. For example, the software may allow a doctor to enter patient identifying information, such as an SSN or a barcode on a health insurance card, enter information regarding the services provided by the doctor to the patient, and directly submit a bill to the patient's health insurance provider from within the application.

[0207] Another software component is each of the directories disclosed herein.

[0208] One or more of the software components may include a universal uploader module, which may access medical information stored on a plurality of formats and transmit that information to the server 102 to be added to a database, which may then be accessed using one or more of the other software components. For example, EMR or DICOM files may be collected using the universal uploader so as to allow a doctor located remotely to quickly and securely access the information.

[0209] One or more of the software components may include a diagnosis tracker. The diagnosis tracker allows a doctor to track his patient's symptoms and compare them to those commonly associated with one or more diagnoses. One or more software components may be configured to receive alerts, such as those originating from a patient monitoring system. One or more of the software components may allow a doctor to interact with remotely located medical equipment, sending commands and receiving information from the equipment. One or more of the software components may allow a doctor to access a patient's EMR and/or update a patient's EMR, based on new developments.

[0210] As mentioned herein, a single electronic health record system is provided for integrating with the various medical equipment and computing devices. An electronic health record is a digital collection of patient information compiled at one or more meetings in any care delivery setting. The electronic health record provides a web browser and/or application-based system available on multiple platforms which provides access to electronic health records. The electronic health record enables information to be quickly and seamlessly shared between patients, physicians, billers, pharmacists, treatment facilities, and integrated medical equipment. In an example, electronic health record enables a physician to electronically prescribe medication to patient based on a remove evaluation performed by the physician. In an example, the software is configured to permit a physician to refer a patient to another physician or consult with another physician for a second opinion, request and review the results of lab tests or imaging tests performed at a remove medical facility, bill a patient for services rendered, schedule appointments or evaluations that may be conducted in person or remotely, access electronic patient medical histories, and securely communicate with a patient using video, audio, and text communications. An example of an example use of the software is discussed below, with reference to FIG. 14. In an example, the software may be secured so as to be compliant with the Health

Insurance Portability and Accountability Act ("HIPAA") in protecting personal health information ("PHI").

[021 1 ] In an example, a secure portal is provided for enabling remote doctor/patient interaction. The secure portal combines high-quality audio and video conferencing, as discussed herein, with the capability to send secure textual or graphical information. Information (e.g., data files generated by medical equipment) may also be exchanged.

[0212] In an example, software modules are configured to provide automated alerts and/or automatically schedule and provide a remote consultation between a patient and a physician if the patient's vitals (e.g., blood pressure, weight, or blood oxidation) crosses a predetermined "normal" value. By way of example, for a patient using the BP Unit discussed above, the software may be configured to obtain a measurement of the patient's blood pressure periodically (e.g., once per day or once per hour). This measurement is recorded using a server, as described above. If at any point the patient's measured blood pressure drops below a predefined limit, the server is configured to immediately send an alert to the patient and/or physician (e.g., using a secure text message sent via TiaMD). The software can schedule a remote

consultation between the doctor and physician for the next morning, which may be conducted using the software and specialized hardware described herein.

[0213] Examples of Use

[0214] In order to more fully explain the examples disclosed herein, the following illustrative examples are provided.

[0215] As shown in FIG. 14, in an exemplary example, a method of providing telemedicine coordinates interactions between a physician 1401 , a patient, a pharmacist, and/or a billing department. The method begins when a patient 1402 seeking treatment registers 1404. Based on a preliminary screening and a review of the patient's current medical history 1406, an evaluation (also termed an encounter 1408) is scheduled. If necessary, a physician 1401 is scheduled to be available during the encounter 1408, either in the same physical location or in a different physical location. The appointment is created 1410 and may be viewed using the system by either the patient 1402 or physician 1401 . During the encounter 1408, the patient is examined. In an example, the physician interacts with the patient remotely. The physician may request that the patient's vital information be measured 1412 and/or that one or more procedures 1414 (e.g., a blood test) be performed. Using the healthcare professional system 12, the results of the encounter are recorded in the patient's medical history 1406, any necessary prescriptions are sent to a pharmacist 1403, and any resulting charges for the encounter 1408 (e.g., room fee, nursing fee, etc.) are compiled into a central database or fee sheet. Similarly, the charges for any procedures 1414 or prescriptions filled by the pharmacist 1403 are compiled on the fee sheet 1416. The patient 1402 may receive the bill using the patient system 10, and can provide a single payment 1418 to a payment processor 1420, which is distributed to the physician 1401 , pharmacist 1403 and/or a treatment facility as needed. The method ends at step 1422, as the treated patient leaves with access to his or her medical records, any necessary prescriptions, and the ability to easily register for further treatment in the future.

[0216] With reference to FIG. 15, a flow chart depicting the interactions between individuals and the various components of the systems 10 and 12 in accordance with an example is provided. As shown, a patient 1502 may use the patient portal 1504 (e.g., the records graphical user interface 20 of the patient system 10) to access information previously collected, which is stored on a server 1506 (e.g., the patient's medical records or a directory of physicians able to provide treatment, diagnosis, or assistance to the patient). New information may be collected from the patient in several ways: first, the patient may visit a treatment facility, where medical procedures (e.g., x-ray, EKG) are performed. The results of these tests or procedures are recorded by a DICOM machine 1508 and uploaded to a server 1512 as DICOM files 1510. Alternatively, a patient may use a CD uploader 1514 to upload DICOM files previously generated from past procedures to the server 1512. Second, the patient can use specialized medical equipment 1516 such as that discussed above (e.g., the Height Unit, Weight Unit, BP Unit) to directly upload new information (e.g., patient vital signs or test results) to the server 1512. This equipment 1516 may be located in the patient's home 1518, at a treatment facility 1520 such as a clinic or hospital, or at another location 1522 such as a nursing home. Finally, the patient can directly create files such as video or audio recordings 1524 (for example, using the patient's own personal computer or other computing device 1 10') which may be loaded onto the server 1512. A doctor 1528 may then access all of the information stored on the server 1512 using his/her mobile device 104'. That same doctor 1528 may consult with a colleague 1542, interact with the patient 1534, and interact with the biller 1538. The servers 1506 and 1512 may be the same server and the patients 1502 and 1534 may be the same patient, thereby allowing a patient to access all of his or her information at any time and interact with his or her physician directly at any point.

[0217] As an additional illustrative example, equipment in accordance with an example may be carried onboard an aircraft. A base station may be integrated into the aircraft's systems or may be a stand-alone unit. As described above, the base station may contain a communication module capable of accessing a WAN such as the Internet, for example, by using a satellite connection. The base station may further comprise a video camera, microphone, display screen, and speakers. Accordingly, were a medical emergency to occur while the aircraft was in flight, the base station could be used to allow a doctor not present on the aircraft to examine, diagnose, and recommend treatment for the afflicted person.

[0218] Similarly, in another example, equipment in accordance with an example of the present invention may be transported to remote areas where trained health care providers are uncommon or unavailable. The equipment may contain multiple communication devices so as to be operable in a variety of circumstances. The equipment may contain a cellular antenna compatible with a variety of SIM cards, a satellite connection, a radio, or other communication devices.

[0219] A device in accordance with an example includes software for automatically collecting a patient history and performing an initial examination of the patient. The device may include a video camera, microphone, and/or other sensors such as ultrasonic sensors. The device may further include a video screen and speakers. The device may be programmed to display an animation which asks the patient a series of questions, such as "What is your name?" and "How old are you?" The animation may further instruct the patient to perform certain movements, such as raising her arms above her head. The device may record the patient's answers using video, audio, and the data collected by the one or more sensors. After the information is collected and stored, it may be transmitted to a server or other computing device for review by a doctor. In this way, the doctor can quickly receive comprehensive information about a patient without needing to spend time performing the initial examination of the patient. Further, the software may automatically screen for serious conditions that require immediate medical attention, such as traumatic injuries, and prioritize treatment for such patients.

[0220] It is to be understood that any of the systems (e.g., 10, 12, 14 and/or others) disclosed herein may be integrated together in an overall healthcare system.

[0221 ] Reference throughout the specification to "one example", "another example", "an example", and so forth, means that a particular element (e.g., feature, structure, and/or characteristic) described in connection with the example is included in at least one example described herein, and may or may not be present in other examples. In addition, it is to be understood that the described elements for any example may be combined in any suitable manner in the various examples unless the context clearly dictates otherwise.

[0222] In describing and claiming the examples disclosed herein, the singular forms "a", "an", and "the" include plural referents unless the context clearly dictates

otherwise.

[0223] While several examples have been described in detail, it is to be understood that the disclosed examples may be modified. Therefore, the foregoing description is to be considered non-limiting.

Claims

What is claimed is:

1 . A healthcare professional system, comprising:

a mobile device, including:

a display for presenting a plurality of graphical user interfaces associated with a charge tracker workflow, the plurality of graphical user interfaces including:

a rounding list graphical user interface;

a patient health record graphical user interface;

a coding graphical user interface; and

a billing graphical user interface; and

a user input device for:

accessing a patient rounding list and creating a patient encounter using the rounding list graphical user interface;

recording patient encounter information using the patient health record graphical user interface;

requesting a code using the coding graphical user interface; and initiating transmission of a bill associated with the patient encounter to a billing agency using the billing graphical user interface.

2. The healthcare professional system as defined in claim 1 wherein the mobile device further comprises a camera accessible by the billing graphical user interface.

3. The healthcare professional system as defined in claim 1 , further comprising a healthcare professional server in communication with the mobile device, the healthcare professional server having a memory that stores the patient rounding list and patient health records.

4. The healthcare professional system as defined in claim 1 , further comprising a billing agency server in communication with the mobile device, the billing agency server to receive the bill.

5. The healthcare professional system as defined in claim 1 wherein the rounding list graphical user interface includes:

a dictation tool; and

a transcription tool.

6. The healthcare professional system as defined in claim 1 wherein the plurality of graphical user interfaces further includes a favorites graphical user interface that provides user-defined dashboard reports.

7. The healthcare professional system as defined in claim 1 , further comprising a virtual scribe having real-time and secure access to the patient encounter

information.

8. An emergency response system, comprising:

a first mobile device including:

a one touch medical emergency connection button;

wireless audio and video connection capability;

secure texting capability; and

customizable rules for sending and receiving broadcast messages, group calls, and combinations thereof; and

a communication hub to receive a signal in response to the activation of the one touch medical emergency connection button of the first mobile device, and including:

an integrated scheduler with information for a first on call doctor, and a second on call doctor; and

protocol for:

first attempting to connect the first mobile device with a mobile device of the first on call doctor; and

upon recognizing a failure to connect the first mobile device with the mobile device of the first on call doctor, then attempting to connect the first mobile device with a mobile device of the second on call doctor.

9. The emergency response system as defined in claim 8 wherein: the medical emergency is a stroke;

the first on call doctor is a first on call vascular doctor, a first on call neurological doctor, or both; and

the second on call doctor is a second on call vascular doctor, a second on call neurological doctor, or both.

10. The emergency response system as defined in claim 8, further comprising: a registration module operatively connected to the communication hub; and an admission, discharge, and transfer system operatively connected to the communication hub.

1 1 . The emergency response system as defined in claim 8 wherein the one touch medical emergency connection button transmits an automated alert with a location of the first mobile device to the communication hub.

12. The emergency response system as defined in claim 8 wherein the mobile device of the first on call doctor or the second on call doctor includes:

a digital imaging and communications in medicine viewer; and

an electronic prescription platform.

13. A method, comprising:

recognizing that an incoming signal is associated with a one touch medical emergency connection button;

identifying, through an integrated scheduler, information for a first on call doctor, and a second on call doctor; and

sequentially attempting to connect a first mobile device, from which the incoming signal is received, with a mobile device of the first on call doctor, or the second on call doctor until a connection is established.

14. The method as defined in claim 13, further comprising determining a type ergency associated with incoming signal prior to identifying the on call doctors.

15. The method as defined in claim 14 wherein:

the type of emergency is a stroke;

the identifying involves identifying information for a first on call vascular doctor, a first on call neurological doctor, a second on call vascular doctor, and a second on call neurological doctor; and

the sequentially attempting involves sequentially attempting to connect the first mobile device with a mobile device of the first on call vascular doctor, or the first on call neurological doctor, or the second on call vascular doctor, or the second on call neurological doctor until the connection is established.

16. A patient system, com

a mobile device, including:

a display for presenting a plurality of graphical user interfaces, each of which is associated with at least one patient related workflow, the plurality of graphical user interfaces including:

an appointment graphical user interface, including an appointment scheduling workflow;

a medication graphical user interface including a medication reminder alert;

a prescription graphical user interface including a prescription refill workflow;

a records graphical user interface; and

a personal health graphical user interface; and a user input device for initiating the at least one of the patient related workflows.

17. The patient system as defined in claim 16 wherein the plurality of graphical user interfaces further includes a home graphical user interface including:

an appointment menu; a medication menu;

an emergency call menu;

a plurality of vital icons; and

a tab bar including a home icon, an appointment icon, a records icon and a my health icon.

18. The patient system as defined in claim 16 wherein the mobile device further comprises a digital imaging and communications in medicine viewer.

19. The patient system as defined in claim 16 wherein the plurality of graphical user interfaces further includes a payment graphical user interface.

20. The patient system as defined in claim 16, further comprising medical equipment in communication with the mobile device.