Patient support device with user interface

Abstract

A system and method for addressing an error condition of a medical device includes a medical device, a mobile device, and a host computer. The medical device generates machine-readable code that is read by the mobile device, and the remote computer hosts a uniform resource locator (URL) associated with the machine-readable code to enable the mobile device to access the URL.

Description

Cross - Reference to Related Applications

[0001] This application claims priority to U.S. Provisional Application No. 63 / 381,669, filed on October 31, 2022, under 35 USC § 119(e), which is hereby incorporated by reference in its entirety. Technical Field

[0002] The present disclosure relates to systems that allow a user to access information specific to the operating condition of a medical device from a location remote from the medical device. More specifically, the present disclosure relates to the automatic display of codes that are used by a user to access interactive troubleshooting tools from a remote computer. Background Art

[0003] As patient support systems, such as hospital beds with therapeutic mattresses, become increasingly complex, the knowledge required to operate the functional systems correctly is also increasing. In addition, as the functions of patient support systems expand, concerns about non - professionals interfering with the treatment provided by patient support systems are also increasing. The balance between ease of use for caregivers and the ability to resolve detailed errors is an important part of the development of user interfaces for patient support systems and patient support surfaces.

[0004] In a healthcare environment, caregivers are exposed to various medical and patient care devices, such as hospital beds, patient lifts, intravenous (IV) pumps, vital sign monitors, treatment delivery devices, etc. To control each of these patient care devices, caregivers must touch or otherwise contact the user input portions of each individual patient care device, such as buttons, knobs, and touchscreens. Caregivers also touch other types of devices present in the ward environment, such as blinds, thermostats, and light switches.

[0005] Whenever a caregiver touches a surface within a ward, there is a risk that the caregiver will be infected by germs or bacteria, and there is a risk that the caregiver will contaminate the surface with germs or bacteria. Therefore, it would be beneficial to reduce the number of surfaces that a caregiver needs to touch to control multiple devices in a ward environment.

[0006] Currently, patient support systems use paper - printed user manuals for hospital staff to refer to. Since these manuals may be difficult to find in a hospital, "help" screens have been adopted in patient support systems with graphical interfaces. This can be problematic because help screens typically require a large amount of memory. Summary of the Invention

[0007] The present disclosure includes one or more of the features described in the appended claims and / or the following features: These features may singly or in any combination include patentable subject matter.

[0008] According to a first aspect of the present disclosure, a system includes a medical device, a mobile device, and a remote computer. The medical device includes a control system that includes a user interface having at least one display and at least one controller. The controller includes a processor and a storage device that includes instructions that, when executed by the processor, cause the controller to transmit an error condition to the user interface. The user interface includes a processor and a storage device that includes instructions that, when executed by the processor, cause the user interface to display a machine-readable code associated with a Uniform Resource Locator (URL). The mobile device includes a camera, a processor, and a storage device that includes instructions that, when executed by the processor, cause the camera to detect a machine-readable marker and cause the camera to automatically connect to the Internet and direct an Internet browser of the mobile device to the URL associated with the machine-readable marker. The remote computer hosts an interactive menu-driven web page associated with the URL associated with the machine-readable marker. The mobile device is configured to display the menu-driven web page such that a user can interact with the menu-driven web page via a browser on the mobile device, and the menu-driven web page is operable to provide information specific to the error condition, which is transmitted to the user interface to allow the user to identify and resolve the error condition.

[0009] In some embodiments of the first aspect, the medical device is a patient support device.

[0010] In some embodiments of the first aspect, the error condition is associated with a module of the medical device.

[0011] In some embodiments of the first aspect, the user interface of the medical device is operable to display a help key, and when the help key is activated during an error condition, the machine-readable code generated by the user interface is associated with a specific error condition.

[0012] In some embodiments of the first aspect, a text box for identifying the error condition is displayed on the user interface before the help key is activated.

[0013] In some embodiments of the first aspect, the machine-readable marker includes a Quick Response (QR) code.

[0014] In some embodiments of the first aspect, the machine-readable marker includes a barcode.

[0015] In some embodiments of the first aspect, the machine-readable marker includes text that is both machine-readable and human-readable.

[0016] According to a second aspect of the present disclosure, a system includes a medical device and a remote computer. The medical device includes a control system that includes a user interface having at least one display and at least one controller. The controller includes a processor and a storage device that includes instructions that, when executed by the processor, cause the controller to transmit an error condition to the user interface. The user interface includes a processor and a storage device that includes instructions that, when executed by the processor, cause the user interface to display a machine-readable code associated with a Uniform Resource Locator (URL). The remote computer hosts an interactive menu-driven web page associated with the URL associated with the machine-readable label. When the URL is accessed via an Internet browser, the Internet browser displays the menu-driven web page to enable a user to interact with the menu-driven web page via the browser, and the menu-driven web page is operable to provide information specific to the error condition, which is transmitted to the user interface to allow the user to identify and resolve the error condition.

[0017] In some embodiments of the second aspect, the medical device is a patient support device.

[0018] In some embodiments of the second aspect, the error condition is associated with a module of the medical device.

[0019] In some embodiments of the second aspect, the user interface of the medical device is operable to display a help key, and when the help key is activated during an error condition, the machine-readable code generated by the user interface is associated with a specific error condition.

[0020] In some embodiments of the second aspect, a text box for identifying the error condition is displayed on the user interface before the help key is activated.

[0021] In some embodiments of the second aspect, the machine-readable code includes a Quick Response (QR) code.

[0022] In some embodiments of the second aspect, the machine-readable code includes a barcode.

[0023] In some embodiments of the second aspect, the machine-readable code includes text that is both machine-readable and human-readable.

[0024] According to a third aspect of the present disclosure, a method for resolving an error condition of a medical device includes: generating a human-readable marker of the error condition on a display of the medical device. The method further includes: in response to an input from a user activating a help function when the error condition is displayed, generating a machine-readable code on the display of the medical device, the machine-readable marker corresponding to a Uniform Resource Locator (URL) associated with a specific error condition. The method further includes: reading the machine-readable code using an optical detector configured to cause an Internet browser to be opened and directed to the URL. The method further includes: displaying a menu-driven web page associated with the URL on the Internet browser. The method further includes: providing error condition-specific information through the menu-driven web page.

[0025] In some embodiments of the third aspect, the machine-readable marker includes a Quick Response (QR) code.

[0026] In some embodiments of the third aspect, the machine-readable marker includes text that is both machine-readable and human-readable.

[0027] In some embodiments of the third aspect, the error condition is associated with a module of the medical device.

[0028] In some embodiments of the third aspect, in the absence of an error condition, activation of the help function generates a machine-readable marker that directs to a URL associated with a menu-driven screen that provides general user information for the medical device.

[0029] In some embodiments of the third aspect, the optical detector includes a smart phone.

[0030] Additional features that may be included, either alone or in combination with any other one or more features, such as those listed above and / or those listed in the claims, may include patentable subject matter, and will become apparent to those skilled in the art after considering the following detailed description of various embodiments that illustrate the presently contemplated best mode of carrying out the embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] The detailed description refers specifically to the drawings, in which:

[0032] Figure 1 is a schematic diagram of a system including a patient support device, a mobile computing device, and a network connected to a hospital information system and the Internet;

[0033] Figure 2 is described in the present disclosure Figure 1 block diagram of aspects of the system;

[0034] Figure 3 Is Figure 1 And Figure 2 An illustration of a user screen on a display of a patient support device, Figure 3 Showing that the help key on the display according to the present disclosure is actuated;

[0035] Figure 4 Is an illustration of one embodiment of a screen that can be displayed in response to the actuation of the help key;

[0036] Figure 5 Is an illustration of a second embodiment of a screen that can be displayed in response to the actuation of the help key;

[0037] Figure 6 Is an illustration of a second embodiment of a screen that can be displayed in response to the actuation of the help key;

[0038] Figure 7 Is when Figures 4 to 6 One of the displays shown in enters the mobile device, an illustration of a menu displayed on the mobile device generated;

[0039] Figure 8 Is Figure 7 Information displayed on the mobile device when the button therein is activated;

[0040] Figure 9 Is a flowchart showing the process of the steps of the present disclosure when a user searches for reference information.

[0041] Figure 10 Is a flowchart showing the process of the steps of the present disclosure when a user resolves an error condition on a patient support device. Detailed Description

[0042] Referring to Figure 1 , a medical device is disclosed as a patient support device 10, which is exemplarily implemented as a hospital bed 10. In other embodiments, the medical device can be implemented as a medical and patient care device, such as a patient lift, an intravenous (IV) pump, a vital signs monitor, a treatment delivery device, etc. The hospital bed 10 includes an arm assembly 38 located above the head for providing support to a patient interface device 40. Figure 1The views shown are generally taken from a position oriented at the left foot end of the hospital bed 10. For purposes of orientation, the discussion of the hospital bed 10 will be based on the orientation of a patient supported in the supine position on the hospital bed 10. Thus, the foot end 12 of the hospital bed 10 refers to the end that is closest to the feet of the patient when the patient is supported in the supine position on the hospital bed 10. The hospital bed 10 has a head end 14 opposite the foot end 12. The left side 16 refers to the left side of the patient when the patient is lying in the hospital bed 10 in the supine position. The right side 18 refers to the right side of the patient. When referring to the longitudinal length of the hospital bed 10, the longitudinal length of the hospital bed 10 refers to the direction represented by a line that generally extends between the head end 14 and the foot end 12 of the hospital bed 10. Similarly, the lateral width of the hospital bed 10 refers to the direction represented by a line that generally extends between the left side 16 and the right side 18.

[0043] The hospital bed 10 includes a base frame 20 that supports a lift system 22. The lift system 22 engages a base and an upper frame 24 such that the lift system 22 moves the upper frame 24 vertically relative to the base frame 20. The lift system 22 includes a head end link and a foot end link (not shown) that can be operated independently and can be operated to move the hospital bed 10 to a reclined position, i.e., a position where the head end 14 of the upper frame 24 is positioned lower than the foot end 12 of the upper frame 24. The hospital bed 10 can also be moved to a reverse reclined position, where the foot end 12 of the upper frame 24 is positioned lower than the head end 14 of the upper frame 24. The upper frame 24 supports a load frame and a pivotable deck portion as known in the art.

[0044] The foot panel 26 (sometimes referred to as a footrest) is supported by the deck and extends vertically at the foot end 12 of the hospital bed 10. The head panel 28 (sometimes referred to as a headboard) is positioned at the base frame 20 and extends vertically to form a barrier at the head end 14 of the hospital bed 10. The left head side rail 30 is supported by the deck and is movable between Figure 1 the raised position shown and a lowered position as known in the art. The right head side rail 32 is also movable between Figure 1 its raised position and a lowered position. The left head side rail 30 exemplarily includes a user interface 46 that includes a keyboard 48 and a touch screen interface 50.

[0045] The hospital bed 10 further includes a left foot side guardrail 34 and a right foot side guardrail 36, and each of the left foot side guardrail 34 and the right foot side guardrail 36 is supported by an upper frame 24. Each of the side guardrails 30, 32, 34, and 36 can be operated to be lowered to a position below the upper surface of the corresponding bedplate portion. It should be noted that when the head portion of the bedplate is moved, the head side guardrails 30 and 32 move with the bedplate so that the head side guardrails 30 and 32 maintain their relative positions with respect to the patient. The arm assembly 38 located above the head is supported by an upright structure 42. The mattress 44 is supported on the bedplate and can move with the bedplate, as is known in the art.

[0046] The hospital bed 10 is part of an information management system 100 that includes an optical reader device, which is shown as a mobile device 52 that is implemented as a smartphone. However, the mobile device can be implemented as a tablet computer, a personal digital assistant, a smartphone, or a laptop computer. The information management system 100 further includes a network 54 that is connected to the hospital bed 10, as well as a hospital information system 56 and the Internet 58. The mobile device 52 can communicate with the Internet in any of a variety of known ways. For example, access to the Internet can be achieved by using any one or more communication technologies (e.g., wired or wireless communication) and associated protocols (e.g., Ethernet, WiMAX, 3G, 4G LTE, 5G, etc.) for enabling such communication. A remote computer 94 is also connected to the Internet 58 and can use any of the above communication technologies or other suitable communication technologies. The remote computer 94 hosts a Uniform Resource Locator (URL) page according to the present disclosure and can be accessed by other components of the system 100 via the Internet 58. In some embodiments, the remote computer 94 can be directly accessed by other components of the system 100 via the network 54.

[0047] Figure 2 A control system 66 for the hospital bed 10 is shown, and the control system 66 includes a controller 68 that includes a processor 70 and a storage device 72. According to the present disclosure, the operation of the hospital bed 10 is controlled by the processor 70, which executes instructions stored in the storage device 72 to implement the operation of the hospital bed 10. It should be understood that the control system 66 can include multiple controllers with specific functions, and the multiple controllers are distributed to separate controllers with specific functions for functional subsystems or modules of the patient support device 10. The multiple controllers can each communicate with each other via a network, and one or more of these controllers communicate with the network 54.

[0048] The control system 66 further includes a communication interface 74 that is operable to communicate with the network 54. The control system 66 further includes a user interface 46 that includes a display 86 and a plurality of user input parts 88. In some exemplary embodiments, the user interface 46 includes a display 50, which is exemplarily a touch screen display that allows a user to provide input through the display 50. The user interface 46 further includes a keyboard 48, which is shown as the user input part 48 in Figure 2 . The user interface includes a processor 76 and a storage device 78. The operation of the user interface 46 is controlled by the processor 76, which executes instructions stored in the storage device 78 to implement the operation of the user interface 46. The processor 76 of the user interface 46 can interact with the processor 70 of the controller 68 using any one of a variety of communication protocols known in the art, including but not limited to: Echelon, CAN, SPI, and LIN, or another suitable electronic communication protocol. In other embodiments, the communication can include circuitry that allows for a hardwired connection using an IEEE802.3 connection, an RS-232 compatible connection, an RS-483 compatible connection, or other protocols known in the art.

[0049] The mobile device 52 includes a communication interface 80, a processor 82, and a storage device 84. The operation of the mobile device 52 is controlled by the processor 82, which executes instructions stored in the storage device 84 to implement the operation of the mobile device 52. The mobile device 52 further includes a display 86, which is exemplarily a touch screen display that allows a user to provide input through the display 50. The mobile device 52 further includes a camera 90 and discrete user input parts 88. In some embodiments, the user input parts 88 can be omitted, and the user can use only the touch screen function of the display 86. It should be understood that in some embodiments, the communication interface 80 is operable to communicate via a wireless protocol, including IEEE802.11n (Wi-Fi), IEEE802.16e (WiMAX), mobile communication technologies such as 3G or 4G technologies, or other wireless technologies. In other embodiments, the communication interface 80 can include circuitry that allows the mobile device 52 to communicate via a hardwired connection using an IEEE802.3 connection, an RS-232 compatible connection, an RS-483 compatible connection, or other protocols known in the art.

[0050] The control system 66 of the hospital bed 10 may include a plurality of functional subsystems or modules known in the art. These subsystems may be complex subsystems that involve data sharing between the subsystems to control various functional aspects of the hospital bed 10. These subsystems / modules may encounter situations where the operation of the hospital bed 10 or the solution to an error condition within the hospital bed 10 may not be obvious to the user. The present disclosure relates to a system that provides the user with real-time access to operational information and troubleshooting functions while limiting the amount of information that must be stored on the hospital bed 10.

[0051] The touch screen 50 provides an interactive screen for the user that can be used to access useful information for the user related to the operation of the hospital bed 10 or any errors encountered by the hospital bed 10. For example, referring to Figure 3 , the screen 102 displayed on the touch screen 50 displays an error notification 104 that indicates that the module for the mattress 44 is in an error condition. The user can use his finger 96 to activate the help key or icon 106 (visible in Figure 4 ) to activate the help screen 108 (shown in Figure 4 ) that provides a machine-readable marker, such as a QR code 110, that the user can scan with the mobile device 52 to access reference materials from a URL on the Internet associated with the specific QR code 110. In some embodiments, the user interface 40 may include a touch screen similar to the touch screen 50, and when the user interface 40 is so equipped, the functions associated with the touch screen 50 may be available on the user interface 40.

[0052] Now referring to Figure 9 , a general process 112 for utilizing this method is shown. The user begins the process at step 114 and actuates the help key 106 at step 116. At step 118, the user interface 46 transmits this state to the controller 68, where at step 118, the controller 68 provides a value representing the help request and the controller 68 sends the value to the user interface 46. At step 120, the processor 76 of the user interface 46 processes the value and generates a QR code 110 specific to the value, and the QR code 110 is displayed on the screen 108.

[0053] The QR code 110 is available for the user, and the user can use the camera 90 of the mobile device 52 to allow the mobile device 52 to read the QR code 110, as shown at step 122. The processor 82 of the mobile device 52 processes the QR code 110 and communicates with the Internet 58 via the link 92 (as Figure 1communicate as shown in FIG. to direct an Internet browser application on the mobile device 52 to access the URL associated with the QR code 110, as shown at step 124.

[0054] At step 126, the URL generates an interactive menu screen based on the activation of the help key 106, such as Figure 7 the menu screen 132 shown on the display 86 of the mobile device 52 in FIG., which the user uses to browse various topics that the user may be interested in. It should be understood that in some embodiments, the screen 132 may be only a display screen, and the help key 106 may be a discrete key present on the keyboard 48. Figure 8 The menu screen 132 of FIG. shows a plurality of selectable radio buttons 134, 136, 138, and 140 corresponding to the functions of the hospital bed 10, and the functions of the hospital bed 10 include "zero bed", "weigh patient", "exit bed", and "lock". At step 128, the user uses the interactive menu screen 132 to collect information. For example, use their finger 96 to interact with the menu screen 132 to activate the Figure 7 "lock" radio button shown in FIG., and the menu advances to Figure 8 the screen 142 shown in FIG., which provides the user with a quick reference to illustrate how the "lock" function of the hospital bed 10 works. It should be understood that the interactive menu at the URL can have any of a plurality of various branches and options to allow the user to browse information that helps operate the hospital bed 10 or provides information useful to the user. Once the user finishes interacting, the process 112 ends at step 130.

[0055] In addition to Figure 9 the embodiments of FIG., in some embodiments, the QR code 110 can be customized for a specific error condition, and Figure 10 another process 140 shown in FIG. can be used by the user to resolve a specific error code. For example, the mattress error code is given as ERROR101 in Figure 7 FIG.. Referring to the process 140, the process starts at step 144 and then advances to step 146, where an error code is generated. At step 148, the user actuates the help key 106, similar to the discussion above. At step 150, the user interface 46 transmits the activation of the help key 106 to the controller 68. However, since ERROR101 was active at that time, the controller 68 generates a help code associated with the specific error and transmits the value associated with the help code to the user interface 46. At step 152, the user interface 46 generates a QR code 110 associated with a specific URL for the specific error code that is ERROR101 in this example.

[0056] At step 154, the user uses the mobile device 52 to read the QR code 110, and at step 156, directs the Internet browser of the mobile device 52 to a URL specific to the error code. The URL in turn generates an interactive menu screen specific to the error code at step 158. Then, at step 160, the user uses the interactive menu to resolve the error condition. Once the error condition is resolved, the process ends at step 162.

[0057] It should be understood that in addition to Figure 4 the QR code 110 implementation, other machine and / or human-readable markings can be generated. In Figure 5 one implementation, a bar code 170 is displayed on the screen 172, and the bar code 170 provides a machine-readable marking similar to the function of the QR code 110. Similarly, in Figure 6 one implementation, a text code 176 is generated on the screen 174. Figure 6 The text code 176 in one implementation is both machine-readable and human-readable. Although the text code 176 can be operated to direct the Internet browser to a corresponding URL, the text of the text code 176 corresponds to an appropriate URL such that if a machine reader is not available, the user can type the appropriate URL address into the Internet browser.

[0058] Although this disclosure relates to specific implementations, those skilled in the art will understand that various changes in form and detail can be made without departing from the subject matter set forth in the appended claims. This disclosure is not limited to the disclosed implementations. Other modifications will be apparent to those skilled in the art upon reading this disclosure. These modifications may involve other features that are known in the art and can be used to replace or supplement the features described herein. In the claims, the wording "comprising" does not exclude other elements or steps, and the indefinite article "a" or "an" does not exclude a plurality.

Claims

1. A system, the system comprises: A medical device, the medical device includes a control system, the control system includes (i) a user interface having at least one display and (ii) at least one controller, the controller includes a processor and a storage device, the storage device includes instructions that, when executed by the processor, cause the controller to transmit an error condition to the user interface, the user interface includes a processor and a storage device, the storage device includes instructions that, when executed by the processor, cause the user interface to display machine-readable code associated with a Uniform Resource Locator (URL); A mobile device, the mobile device includes a camera, a processor and a storage device, the storage device includes instructions that, when executed by the processor, cause the camera to detect a machine-readable tag and cause the camera to automatically connect to the Internet and direct the Internet browser of the mobile device to the URL associated with the machine-readable tag; and A remote computer that hosts an interactive menu-driven web page associated with the URL associated with the machine-readable tag; wherein the mobile device is configured to display the menu-driven web page so that a user can interact with the menu-driven web page via the browser on the mobile device, the menu-driven web page is operable to provide information specific to the error condition, and the information is transmitted to the user interface to allow the user to identify and resolve the error condition.

2. The system according to claim 1, wherein, the medical device is a patient support device.

3. The system according to claim 1, wherein, the error condition is associated with a module of the medical device.

4. The system according to claim 1, wherein, the user interface of the medical device is operable to display a help key, and when the help key is activated during an error condition, the machine-readable code generated by the user interface is associated with a specific error condition.

5. The system according to claim 4, wherein, before the help key is activated, a text box for identifying the error condition is displayed on the user interface.

6. The system according to claim 4, wherein, the medical device is a patient support device.

7. The system according to claim 4, wherein, the error condition is associated with a module of the medical device.

8. The system according to claim 4, wherein, the machine-readable tag includes a Quick Response (QR) code.

9. The system according to claim 4, wherein, the machine-readable tag includes a barcode.

10. The system according to claim 4, wherein, the machine-readable tag includes text that is both machine-readable and human-readable.

11. A system, the system comprises: A medical device, the medical device including a control system, the control system including (i) a user interface having at least one display and (ii) at least one controller, the controller including a processor and a storage device, the storage device including instructions that, when executed by the processor, cause the controller to transmit an error condition to the user interface, the user interface including a processor and a storage device, the storage device including instructions that, when executed by the processor, cause the user interface to display machine-readable code associated with a Uniform Resource Locator (URL); and A remote computer that hosts an interactive menu-driven web page associated with the URL associated with the machine-readable marker; wherein, when the URL is accessed via an Internet browser, the Internet browser displays the menu-driven web page such that a user can interact with the menu-driven web page via the browser, the menu-driven web page being operable to provide information specific to the error condition, the information being transmitted to the user interface to allow the user to identify and resolve the error condition.

12. The system according to claim 11, wherein, the medical device is a patient support device.

13. The system according to claim 11, wherein, the error condition is associated with a module of the medical device.

14. The system according to claim 11, wherein, the user interface of the medical device is operable to display a help key, and when the help key is activated during an error condition, the machine-readable marker generated by the user interface is associated with the specific error condition.

15. The system according to claim 14, wherein, a text box for identifying the error condition is displayed on the user interface before the help key is activated.

16. The system according to claim 14, wherein, the medical device is a patient support device.

17. The system according to claim 14, wherein, the error condition is associated with a module of the medical device.

18. The system according to claim 14, wherein, the machine-readable marker includes a Quick Response (QR) code.

19. The system according to claim 14, wherein, the machine-readable marker includes a barcode.

20. The system according to claim 14, wherein, the machine-readable marker includes text that is both machine-readable and human-readable.

21. A method for resolving an error condition of a medical device, the method comprising: generating a human-readable marker of the error condition on a display of the medical device; in response to input from a user activating a help function when the error condition is displayed, generating machine-readable code on the display of the medical device, the machine-readable marker corresponding to a Uniform Resource Locator (URL) associated with the specific error condition; reading the machine-readable code using an optical detector configured to cause an Internet browser to be opened and directed to the URL; Display a menu-driven web page associated with the URL on the Internet browser; And Provide information specific to the error condition through the menu-driven web page.

22. The method according to claim 21, Wherein, The machine-readable mark includes a Quick Response (QR) code.

23. The method according to claim 21, Wherein, The machine-readable mark includes text that is both machine-readable and human-readable.

24. The method according to claim 21, Wherein, The error condition is associated with a module of the medical device.

25. The method according to claim 24, Wherein, In the absence of an error condition, activation of the help function generates a machine-readable mark that directs to a URL associated with a menu-driven screen that provides general user information for the medical device.

26. The method according to claim 21, Wherein, In the absence of an error condition, activation of the help function generates a machine-readable mark that directs to a URL associated with a menu-driven screen that provides general user information for the medical device.

27. The method according to claim 26, wherein the machine-readable mark includes a Quick Response (QR) code.

28. The method according to claim 26, Wherein, The machine-readable mark includes text that is both machine-readable and human-readable.

29. The method according to claim 26, Wherein, The error condition is associated with a module of the medical device.

30. The method according to claim 26, Wherein, The optical detector includes a smart phone.

Images