Improvements for wireless connection and monitoring of processing of wireless medical devices
By installing sensors and electronic processors on medical devices, monitoring transportation and processing conditions, and ensuring wireless connectivity with autonomous robots or remediation instructions, solving equipment damage and data loss problems, reducing maintenance costs and improving connection stability and Operator training effect.
Patent Information
- Application Number
- CN202380033231.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-26
- Filing Date
- 2023-04-03
- Publication Date
- 2024-11-29
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
Medical devices are easily damaged when wireless connections are lost or improperly processed, resulting in data loss and increased repair costs, and it is difficult to maintain a stable connection when used in areas with insufficient Wi-Fi coverage.
Using a system including sensors and electronic processors to monitor the transportation and processing of medical equipment, detect shocks, handle improper events, and ensure wireless connection between the equipment and the hospital network through autonomous robots or remedial instructions, providing real-time data transmission and operator training .
Reduces the possibility of medical equipment being damaged during transportation, reduces maintenance costs, ensures secure data transmission and reliable equipment connection, and improves operator training results.
Smart Images

Figure CN119053520A_ABST
Abstract
Description
Technical Field
[0001] In summary, the following content involves medical device tracking technology, medical device processing technology, real-time location system (RTLS) technology, Wi-Fi connection analysis technology, and related technologies. Background Art
[0002] Wireless connections between medical devices such as image acquisition sensors (e.g., digital X-ray detector boards or local MRI coils) and a host computer (e.g., a digital X-ray system or an MRI scanner) are sometimes used. These wireless connections enable more flexible positioning of the data acquisition sensor during an examination. In addition, the sensor can be easily connected to multiple host systems at different locations in the clinical field. Similarly, mobile medical imaging devices (such as mobile C-arms or mobile digital X-ray systems) can be used in various locations within a single hospital. However, in remote areas where hospital network access is poor or non-existent, thereby limiting connectivity and data transfer, such wireless connections may be detrimental rather than beneficial. Mobile medical devices (such as mobile C-arm systems) are operated in a variety of locations, which makes it difficult or impossible to send acquired image data and / or log information directly to local IT systems. Although this situation can be alleviated to some extent by including an on-board data storage buffer in the medical device, this solution may be less than satisfactory. The capacity of such a storage buffer is limited, which in turn limits the time the medical device can be out of range of the Wi-Fi network before medical data is lost.
[0003] Additionally, due to events such as temporary power outages, storage buffers may lose stored data, again resulting in loss of medical data. As time out of range increases, such losses due to buffer failures become more problematic again, as more data will be lost in such failures. In some cases, these considerations may lead medical device manufacturers to choose not to include wireless connectivity in devices where reliable communication connectivity is important, such as in medical devices that may transmit life-critical medical data.
[0004] Medical devices can also be easily damaged when not handled with care. Often, careful handling according to the manufacturer's specifications can prevent operator misuse that can damage a medical device, while improper handling can result in expensive repair or replacement costs. Warranty violations due to operator misuse can result in customer dissatisfaction or high service costs at sites where carelessness or inadequate training has occurred.
[0005] Expensive medical equipment can lead to high service and maintenance costs when operators are not properly trained or when the equipment is misused. Examples include carrying mobile or connectable equipment, such as mobile X-ray detectors, magnetic resonance (MR) coils, or computed tomography (CT) phantoms, without necessary precautions, i.e., keeping hands on the equipment, not running, etc. Other examples of improper handling may include not using designated straps or other support components when transporting heavy medical equipment, or allowing Wi-Fi-enabled devices to be moved out of range of the hospital Wi-Fi access point (AP).
[0006] In summary, while mobile and / or cordless medical devices have a wide range of advantages, the beneficial portability of such devices also makes them susceptible to damage during transportation, or malfunctioning due to loss of wireless connectivity when transported to locations with insufficient Wi-Fi service coverage.
[0007] The following discloses certain improvements that overcome these and other problems. Summary of the invention
[0008] In one aspect, a system for evaluating and / or providing wireless communication between a medical device and a hospital wireless network is disclosed. The system includes an electronic processor and a memory storing instructions that can be read and executed by the electronic processor to: determine whether a radio unit of the medical device has a wireless connection; and in response to the determination that the radio unit of the medical device does not have a wireless connection, perform a remedial action.
[0009] In another aspect, a system for evaluating and / or providing wireless communication between a medical device and a hospital wireless network is disclosed. The system includes an autonomous robot having an electronic processor and a memory, the memory storing instructions that can be read and executed by the electronic processor to perform the following operations: determine whether a radio unit of the medical device has a wireless connection; and in response to the determination that the radio unit of the medical device does not have a wireless connection, perform a remedial action, wherein the remedial action includes autonomously moving the robot toward the medical device, and establishing a connection with the radio unit of the medical device via at least one radio unit of the autonomous robot, acquiring medical and / or operational data generated by the medical device via the established wireless connection, and transmitting the acquired medical and / or operational data to the hospital wireless network via at least one radio unit of the autonomous robot.
[0010] In another aspect, a medical device includes: a medical device; one or more sensors (14) configured to monitor transportation of the medical device; and at least one electronic processor (16, 18) programmed to: detect a time-stamped transportation event based on sensor data acquired by the one or more sensors; and perform a remedial action in response to the detected time-stamped transportation event.
[0011] In another aspect, a medical communication system for providing wireless communication between a medical device and a hospital Wi-Fi network is disclosed. The system includes a radio system including a Wi-Fi radio unit and a non-Wi-Fi radio unit, as well as an electronic processor and a memory, the memory storing instructions that can be read and executed by the electronic processor to perform the following operations: establish a wireless connection with a non-Wi-Fi radio unit (44) of a medical device via the non-Wi-Fi radio unit; obtain medical and / or operational data generated by the medical device via the established wireless connection; and transmit the obtained medical and / or operational data to the hospital Wi-Fi network (52) via the Wi-Fi radio unit. In some embodiments, the medical communication system includes an autonomous vehicle.
[0012] One advantage resides in reducing the likelihood of damage to the portable medical device during transportation.
[0013] Another advantage resides in providing practical real-time operator training on handling sensitive portable medical devices.
[0014] Another advantage resides in reducing maintenance costs for medical facilities to repair medical equipment over time.
[0015] Another advantage resides in identifying patterns of misuse of a medical device, for example, enabling targeted remedial training regarding device handling.
[0016] Another advantage resides in collecting location data of medical devices and electronically connecting the devices via a network.
[0017] Another advantage resides in improved Wi-Fi connectivity between medical devices to maximize device operability.
[0018] A given embodiment may provide none, one, two, more, or all of the aforementioned advantages, and / or may provide other advantages that will be apparent to one of ordinary skill in the art upon reading and understanding the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS
[0019] The disclosure may take form in various components and arrangements of components, and in various steps and arrangements of steps.The drawings are only for illustrating the preferred embodiments and are not to be construed as limiting the disclosure.
[0020] Figure 1 An illustrative apparatus for monitoring a medical device according to the present disclosure is schematically shown.
[0021] Figure 2 Shows Figure 1 An exemplary flow chart operation of a system.
[0022] Figure 3-5 Shows Figure 1 Other embodiments of the device. DETAILED DESCRIPTION
[0023] The following relates to monitoring the handling of medical devices. Certain types of medical imaging devices, such as X-ray detector plates, local MR coils, and CT imaging phantoms, are transported or handled by imaging technicians or other medical professionals. Many of these types of devices are heavy and can be easily damaged if dropped, hit against a wall, or otherwise subjected to sudden impact. The devices may include handles or support straps to reduce the likelihood of such impacts. However, these features may not be available, and / or the medical professional may be careless when handling the device, such as running with the device. Impact damage to medical imaging devices may result in unnecessary warranty claims and customer dissatisfaction.
[0024] In some embodiments, sensors are added to the portable medical device and / or the strap or handle used to transport the device, the sensors being designed to detect improper handling of the device. Such sensors may include: accelerometers or other motion sensors for detecting movement of the device and / or impact thereon; pressure sensors on the handles for detecting whether the handles are used during transport; proximity sensors attached to the device and the transport strap, respectively, to verify whether they are close to each other during transport; connection sensors for detecting whether the transport strap is physically connected to the device, vital sign sensors (e.g., heart rate, body temperature, or blood pressure) for detecting the physical condition of the person transporting the device, and the like. The sensors are designed to generate time-stamped data.
[0025] In addition, the electronic processor receives data from the sensors and may also receive other log information, such as machine logs, to detect when the equipment is transported or used. Optionally, the time-stamped sensor data can be associated with the location of the personnel provided by the hospital's real-time location system (RTLS) to associate the mishandling event with a specific individual. Based on the sensor (and optional log and RTLS) data, the processor determines (1) a shock event; and (2) a mishandling event.
[0026] Shock and mishandling event detection (or more generally, detected shipping events) can have a variety of uses, such as determining whether a repair should be covered under warranty or is due to device misuse, or triggering a service call to ensure that the device is fully functional.
[0027] Detectable mishandling events include impact events as well as other types of improper handling, such as not using the handles or straps, running with the device, etc. A single severe mishandling event detected may immediately trigger a warning. For example, if the accelerometer detects that the device is moving, but the handle sensor does not detect that the handle is being used, a warning may be issued to carry the device by the handle (e.g., by an illuminated or flashing LED indicator on the handle, or an electronic voice warning in English or other locally used natural language issued by a speaker integrated with the device). A pattern of (potentially less severe) mishandling events may prompt hospital administrators to recommend remedial training to employees. If RTLS data can be used to identify mishandling events for a specific individual, a recommendation for retraining may be targeted to that specific individual.
[0028] In one variant (not necessarily exclusive) embodiment, a severe mishandling incident associated with damage to equipment may be grounds for denying warranty coverage to repair that damage (subject to the relevant contractual warranty terms).
[0029] Other types of transportation issues for portable medical devices may be related to transporting a Wi-Fi equipped portable medical device to a location with insufficient Wi-Fi coverage. While this typically does not result in damage to the device, it may result in failure or loss of medical data, which may adversely affect the medical services provided. The following also addresses these types of transportation issues by disclosing remedies for situations where the portable medical device is out of Wi-Fi range. Loss of Wi-Fi connectivity may result from moving the device to a location that is not covered by a Wi-Fi network due to gaps in the Wi-Fi access point (AP) layout, or from the medical device being taken outside of the hospital (e.g., outside a hospital building). In other use cases, portable medical devices may be deployed at disaster locations or other temporary locations supported by portable Wi-Fi hotspots with limited coverage.
[0030] In some embodiments, a mobile robot with an onboard Wi-Fi AP and autonomous navigation can be programmed to follow a portable medical device. The robot includes a data storage device and can therefore receive wireless data from the medical device. Then, at time intervals, the robot can move to a location with central Wi-Fi access to send the stored data to the hospital network. In some embodiments, a group of such mobile robots is provided, as well as a central controller that can intelligently deploy the robot when the mobile medical device falls off the network (or in preventive mode, has a weak Wi-Fi signal). The mobile robot can be a wheeled vehicle, or in an outdoor environment, it can be an unmanned aerial vehicle (UAV).
[0031] In other embodiments, the mobile robot is omitted, and instead the mobile medical device itself is programmed to detect a weak or lost Wi-Fi connection and provide remedial instructions, such as: "Weak Wi-Fi connection - please move this device to another location to perform this procedure!"
[0032] Reference Figure 1 , showing a medical device 10 for monitoring the processing of a medical device and analyzing the Wi-Fi connection of the medical device. The device 10 includes a portable medical device 12 (in Figure 1 Schematically shown as a box in FIG. ; see also the description later in this article Figure 3 and Figure 4 The portable medical device 12 may include any suitable portable medical device, such as an IV pump, a patient bed, an X-ray detector plate, a local MR coil, a CT imaging phantom, etc. Figure 1 Also shown is one or more sensors 14 ( Figure 1 ), which is configured to monitor the transport of the portable medical device 12. Examples of sensors 14 are described in more detail below, but in some brief non-limiting examples, may include an inertial measurement unit (IMU) for detecting transport events (such as impact or excessive transport speed), sensors for detecting transport events (such as (not) using transport hardware (such as handles or slings), etc. In some embodiments, one or more sensors 14 may include or operate in conjunction with a real-time location system (RTLS) that is configured to perform tracking of the portable medical device 12.
[0033] The apparatus 10 also includes an electronic processing device 16, 18 (such as a server computer 16, a workstation or a smart tablet computer 18, various combinations thereof), or more generally a computer. The server computer 16 may include multiple server computers, for example interconnected to form a server cluster, cloud computing resources, etc., to perform more complex computing tasks. The workstation 18 and / or the server computer 16 include typical components such as an electronic processor 20 (e.g., a microprocessor), at least one user input device (e.g., a mouse, keyboard, trackball, a device with an embedded screen such as a tablet computer, a smart phone, a smart watch, an alternative reality / virtual reality headset or goggles, etc.) 22 and a display device 24 (e.g., an LCD display, a plasma display, a cathode ray tube display, etc.). In some embodiments, the display device 24 may be a separate component from the workstation 18, or may include two or more display devices.
[0034] The electronic processor 20 is operably connected to one or more non-transitory storage media 26. As non-limiting illustrative examples, the non-transitory storage media 26 may include one or more of a disk, RAID or other magnetic storage media; a solid state drive, a flash drive, an electrically erasable read-only memory (EEROM) or other electronic memory; an optical disk or other optical storage; various combinations thereof; etc.; and may be, for example, network storage, an internal hard drive of the workstation 18, various combinations thereof, etc. It should be understood that any reference to one or more non-transitory media or media 26 herein should be broadly interpreted to include a single medium or multiple media of the same or different types. Likewise, the electronic processor 20 may be embodied as a single electronic processor or two or more electronic processors. The non-transitory storage medium 26 stores instructions executable by at least one electronic processor 20. The instructions include instructions to generate a visualization of a graphical user interface (GUI) 28 for display on a display device 24.
[0035] The non-transitory computer-readable medium 26 (or the server computer 16) stores instructions that can be read and executed by at least one electronic processor 20 (or the server computer 16) to perform the following operations: (i) detect a time-stamped transport event based on sensor data acquired by one or more sensors 14, and (ii) perform a remedial action in response to the detected time-stamped transport event. The remedial event can range from recording the transport event to active remediation, such as issuing a warning in response to detected improper handling of the portable medical device 12.
[0036] In an exemplary embodiment, the sensor 14 includes an inertial measurement unit (IMU) placed on or in the portable medical device 12. The IMU sensor 14 may include an accelerometer, a gyroscope, a magnetometer, etc. The server computer 16 is then programmed to detect a time-stamped transportation event including a time-stamped impact event in which the portable medical device 12 is subjected to an impact, and the remedial action performed in response to the detected time-stamped impact event includes at least recording the time-stamped impact event.
[0037] In another exemplary embodiment, the sensor 14 includes a position sensor and a handle use sensor, wherein the position sensor is placed on or in the portable medical device 12, and the handle use sensor is placed on the transport handle 13 of the portable medical device 12 (at Figure 1 The server computer 16 may be a computer system that includes a position sensor 14 and a handle sensor 15. The position sensor 14 may be an IMU sensor, a radio frequency identification (RFID) tag, an infrared tag, etc., used with RTLS to track the location of the portable medical device 12. The handle sensor 14 may include a pressure sensor, a capacitive touch sensor, a strain gauge, an optical sensor, etc. The server computer 16 is then programmed to detect a timestamped transportation event including a timestamped handle non-use event in which the handle usage sensor 14 does not detect the use of the transportation handle 13 while the position sensor 14 detects the transportation of the portable measuring device 12.
[0038] In another exemplary embodiment, the sensor 14 includes a proximity sensor including a first sensor component and a second sensor component, the first sensor component being placed on or in the portable medical device 12 and the second sensor component being placed on the device support component 15 (e.g., Figure 1 The device support assembly 15 is configured to be detachably connected to the portable medical device 12 and to support the portable medical device 12 on a support belt (schematically shown as a curve in FIG. 1 ). The first sensor assembly and the second sensor assembly are configured to detect whether the first sensor assembly and the second sensor assembly are close to each other. Then, the server computer 16 is programmed to detect a time-stamped transportation event including a time-stamped support device non-use event, in which the proximity sensor 14 does not detect the mutual proximity of the first sensor assembly and the second sensor assembly while the position sensor 14 detects the transportation of the portable measuring device 12.
[0039] In another exemplary embodiment, the sensor 14 includes a connection sensor configured to detect whether a detachable device support assembly (e.g., support strap 15) is connected to the portable medical device 12. The position sensor 14 is placed on or in the portable medical device 12. The server computer 16 is then programmed to detect a time-stamped transport event including a time-stamped support device non-use event in which the connection sensor 14 does not detect that the detachable device support assembly 15 is connected to the portable medical device 12 while the position sensor 14 detects transport of the portable medical device.
[0040] In another exemplary embodiment, the sensor 14 includes a position sensor that is placed on or in the portable medical device 12. The server computer 16 is then programmed to detect time-stamped transport events including time-stamped transport speed exceeding events in which the position sensor 14 detects that the portable measurement device 12 is being transported at a speed greater than a speed limit (i.e., a maximum acceptable transport speed of the device 12 as predefined in the device operating manual, hospital regulations, or other authoritative source).
[0041] In another exemplary embodiment, the sensors 14 include a vital sign sensor configured to measure a person's vital signs, a device location sensor placed on or in the portable medical device 12, and a person location sensor configured to be worn by a person. The server computer 16 is then programmed to detect a time-stamped transportation event including a time-stamped physiological stress event in which the device and person location sensors 14 detect that the person and the portable medical device 12 are moving together, and the vital sign sensors 14 detect that the person is under physiological stress. For example, this can detect a situation in which a person attempts to move a heavy portable medical device 12 when the heavy device 12 should only be moved by a team of two.
[0042] In another exemplary embodiment, the sensor 14 includes an audible and / or visual alarm (e.g., a sound, a visual message, a flashing light, etc.) placed on the portable medical device 12. The server computer 16 is then programmed to perform a remedial action including activating the audible and / or visual alarm 14. In some embodiments, the sound may be a pre-recorded or electronically generated natural language voice warning in English or another natural language. Such a voice warning is expected to be a particularly effective remedial action because it effectively provides a disembodied voice that warns of improper treatment in real time.
[0043] In another example embodiment, the server computer 16 is programmed to perform a remedial action including recording a time-stamped transportation event annotated with the spatial location at which the time-stamped transportation event occurred. The spatial location is determined based on an RTLS including a sensor 14 in communication with the server computer 16. (Such remedial actions can be easily combined with the remedial actions for real-time alerts described above).
[0044] In another example embodiment, the portable medical device 12 is Wi-Fi enabled, and the sensor 14 includes a sensor configured to detect a time-stamped transportation event including a time-stamped loss of Wi-Fi connectivity of the portable medical device 12. The server computer 16 is then programmed to perform a remedial action in response to the detected time-stamped loss of Wi-Fi connectivity, the remedial action including caching the Wi-Fi communications of the portable medical device 12 in the data store 32 of the portable medical device 12.
[0045] In another example embodiment, the portable medical device 12 is Wi-Fi enabled, and the sensor 14 includes a Wi-Fi enabled mobile robot configured to connect via Wi-Fi with the portable medical device 12. The server computer 16 is then programmed to detect a time-stamped transportation event including a time-stamped loss of Wi-Fi connection between the portable medical device 12 and the Wi-Fi enabled mobile robot 14, and to perform a remedial action including moving the Wi-Fi enabled mobile robot 14 to a location closer to the portable medical device 12.
[0046] These are merely illustrative examples and should not be construed as limiting.
[0047] refer to Figure 2 , and continue to refer to Figure 1 , the electronic processing device 18 or the server computer 16 (or a combination of both) is configured as described above to perform the method or process 100 for monitoring the user's handling of the medical device. The non-transitory storage medium 26 (or the server computer 16) stores instructions that can be read and executed by at least one electronic processor 18 (or the server computer 16) to perform the disclosed operations, including performing the method or process 100. In some examples, the method 100 can be performed at least in part through cloud processing.
[0048] At operation 102, data is received from one or more sensors 14 affixed to one or more medical devices (e.g., portable medical devices 12). In some embodiments, the data includes time-stamped data. In other embodiments, the data includes log data from the portable medical devices 12. In further embodiments, the data includes location data from the portable medical devices 12.
[0049] At operation 104, at least one of the following is determined: (i) a shock event for one of the medical devices 12 and (ii) a mishandling event for one of the medical devices 12. In one example embodiment, the received time-stamped data may be correlated with location data provided by an RTLS including the sensor 14. The shock event and / or the mishandling event may be determined based on the correlation. In another example embodiment, the shock event and / or the mishandling event may be determined based on log data from the medical device 12.
[0050] At operation 106, a warning and / or recommendation may be output on the electronic processing device 18. In one example, a user interacting with the medical device 12, determined by the location data for which a plurality of mishandling events were determined, may be recommended to an administrator. The recommendation may include conducting a training course for the medical device 12 for which a plurality of mishandling events were determined. In another example, a warning is issued to the user of the medical device 12 for which a mishandling event was determined. In another example, a service call may be triggered for the medical device 12 for which at least one of an impact event or a mishandling event was determined. These are merely illustrative examples and should not be construed as limiting.
[0051] Continue to refer Figure 1 and Figure 2 , the electronic processing device 18 or the server computer 16 (or a combination of both) is configured as described above to perform a method or process 200 for detecting a Wi-Fi connection of a medical device (e.g., a portable medical device 12). The non-transitory storage medium 26 (or the server computer 16) stores instructions that can be read and executed by at least one electronic processor 18 (or the server computer 16) to perform the disclosed operations, including performing the method or process 200. In some examples, the method 200 can be performed at least in part through cloud processing.
[0052] like Figure 2As shown, method 200 may be performed in conjunction with method 100. For example, the remedial action in operation 104 may include restoring a weak or lost Wi-Fi connection of the medical device 12. At operation 202, a weak or lost Wi-Fi connection to a central Wi-Fi access point (AP) 30 is detected. At operation 204, remedial instructions may be provided to restore the weak or lost Wi-Fi connection (e.g., "Weak Wi-Fi connection—Please move this device to another location to perform this procedure!").
[0053] Example
[0054] The following examples describe the apparatus 10 in more detail. In a first embodiment, a monitoring device including one of the sensors 14 is worn by a medical device operator and motion data is collected using the accelerometer sensor 14. This information can be analyzed by an algorithm to identify any sudden changes in acceleration for fall and collision detection. In another embodiment, the information from the monitoring device is compared with log information from the medical device 12 itself. Typically, expensive medical devices (such as mobile X-ray detectors or MR coils) have integrated impact sensors 14 to identify severe impacts to the medical device 12. In this case, the timestamp of the identified collision detection from the user's monitoring device can be aligned with the corresponding signal from the impact sensor of the medical device 12. The data from the user's monitoring device before and after the event can then be processed to identify any misuse of the medical device 12, such as running while carrying the medical device 12 or carrying it with only one hand on the handle 13 (see next example).
[0055] In another embodiment, if Figure 3 As shown, a medical device 12 (such as an X-ray detector board) has a monitoring device 14, which is integrated into the handle 13 of the medical device 12 itself, and measures the operator's hands on the handle 13 attached to the medical device 12 with a contact sensor 14. The monitoring device 14 can share part of its log information with another monitoring device 14 that can be worn by the user (for example, if both contact sensors 14 measure a signal, it indicates the state of the user carrying the medical device 12 with both hands). In addition, any of the monitoring devices 14 can trigger an alarm, such as a sound, vibration, or light signal to notify the user of the error handling of the medical device 12. In a variation of this embodiment, the contact sensor 14 is replaced by a near field communication (NFC) sensor 14 to measure the proximity of the user's monitoring device 14 to the monitoring device 14 attached to the medical device 12.
[0056] In another embodiment, if Figure 4As shown, for a medical device 12 such as an X-ray detector board, one monitoring device 14 is attached to a belt 15, another monitoring device 14 is worn by an operator, and a third monitoring device 14 is attached to the medical device 12. The belt 15 can be attached to the operator and connected to the medical device 12 via a mechanical connector (screws, hook and loop, snap connector, etc.). The algorithm processes the log information from all three monitoring devices 14 to verify that the belt 15 is worn and connected to the medical device 12, otherwise it will log and sound an alarm. When the belt 15 is successfully connected or disconnected, the connector 34 sends a signal to at least one monitoring device 14. Similarly, the monitoring devices 14 can be configured to measure the proximity of each other, thereby triggering a signal when the belt 15 is put on or taken off.
[0057] In another embodiment, a monitoring device 14 (usually a monitoring device carried by an operator) is connected to other monitoring devices 14 (usually attached to or a part of a medical device 12) to collect log information, and upload the data to a remote host (i.e., a server computer 16) for further processing. On the server computer 16, log information from multiple users of different clinical sites is collected and analyzed. The analysis includes, for example, an evaluation of the average motion speed of each single user and statistical measures (e.g., standard deviation, percentile, etc.) of all user groups connected to the server computer 16. In this way, normal operating conditions can be derived for single user parameters (such as average user motion) to identify any atypical situations (e.g., a user running at a fast pace, rather than walking at a speed close to the average speed). In addition, by comparing with the statistical distribution derived from a peer user group, recommendations that individual users need to pay attention to (e.g., users usually walk at a much faster speed than their peers) can be derived. This information can be sent back to the monitoring device 14 and displayed as a recommendation, warning, or alarm. Thus, improved personalized training of medical staff may be planned and provided based on analysis of log information from the acquired data.
[0058] Other user parameters to be analyzed may include heart rate, body temperature, blood pressure, grip strength, vertical and horizontal acceleration, etc. Furthermore, user parameters may also include device specific settings commonly used by the operator, such as, for example, the applied X-ray dose or the selected X-ray tube settings during a CT or X-ray examination.
[0059] In another embodiment, the processing of the data is at least partially calculated on the monitoring device 14. For example, statistics and limits for atypical situations are stored on the monitoring device 14 and can be updated via the server computer 16 when new data is available. The generation of alerts and the derivation of user recommendations are calculated directly on the monitoring device 14. In this way, it is possible to trigger an alert immediately upon detection of a threshold exceeding certain limits, without the need for a connection to the server computer 16.
[0060] Another cause of malfunction of mobile and / or cordless medical devices is when transported to a wireless (e.g. Wi-Fi or Bluetooth) TM ) When the wireless connection is lost in a location with insufficient service coverage. In addition, some devices that might benefit from wireless connectivity may not include this feature due to concerns about its reliability. For example, if a medical device transmits life-critical data, making the loss of connectivity particularly problematic, the device manufacturer may choose to forgo wireless connectivity altogether and use only a wired data connection, such as wired Ethernet.
[0061] Figure 5 An apparatus 300 is shown that provides a wireless connection with improved reliability. Figure 5 The illustrative apparatus 300 includes a robot 40 (in a first room R1) having a Wi-Fi radio unit 42 wirelessly connected to a first medical device 12 (in a second room R2) and a second medical device 12' (in a third room R3). The robot 40 suitably includes a motor or other propulsion system and is designed to move autonomously. For example, the robot 40 suitably has optical, electromagnetic, and thermal sensors 50 to identify obstacles and identify their positions on a positioning map. For example, the sensor 50 may include a proximity sensor (such as a LIDAR sensor, a thermal sensor, etc.) to detect proximity to an object so as to avoid them. If the hospital has a real-time location service (RTLS), the sensor 50 may also include an RF tag or other sensor capable of location tracking via RTLS, which in combination with an electronic map of the hospital (typically included in the RTLS) can be used to facilitate navigation of the robot 40. These are merely non-limiting illustrative examples. The robot 40 may also include rubber bumpers or the like to limit damage if it does collide with a person or object, and may include a visible light (optionally flashing) and / or an audible beacon (e.g., a buzzer) to alert medical personnel of the robot 40, particularly when it is in motion.
[0062] The robot 40 (or a server computer 16 wirelessly connected to the robot via a Wi-Fi radio 42) may also include scheduler software that may be configured to link with one or more designated mobile medical devices 12 to follow the mobile medical device 12 whenever the mobile medical device 12 moves to a new location, position itself relative to the mobile medical device 12 to maximize the Wi-Fi signal between the robot 40 and the Wi-Fi radio 44 connected to the medical device 12, collect image data directly via the WiFi connection between the radios 42 and 44 after acquisition has been performed, collect log information from the image sensor 14 at a predefined cadence, upload data files to the medical device 12 (e.g., software or firmware updates for software components, updates to pre-trained neural networks, etc.), navigate and move toward the server computer 16 to upload collected data or download new software updates for distribution to remote systems, etc. In order for the robot 40 to locate the medical device 12 (and follow it if the medical device 12 is moved while the robot is wirelessly connected to it), various methods may be used. For example, if RTLS is available, both the robot 40 and the medical device 12 may include RF tags or the like to enable them to be tracked by RTLS, and the robot 12 may then access the RTLS to keep track of the location of the medical device 12 to which it is assigned. (In some such embodiments, the robot 40 itself may act as a location node for the RTLS.) Additionally or alternatively, the medical device 12 may include a non-RTLS tag (i.e., a locator tag not used by RTLS) that the robot 40 may directly detect to enable the robot 40 to locate and follow the medical device 12. As another tracking method, the signal strength of the wireless communications between the Wi-Fi radio units 42 and 44 of the robot 40 and the medical device 12 may be used.
[0063] Thus, the robot 40 in the above example acts as a mobile Wi-Fi access point (AP) to ensure Wi-Fi connectivity for the medical device 12 even if it moves to an area where Wi-Fi coverage is poor or non-existent. Generally speaking, medical and / or operational data generated by the medical device 12 is transmitted via the robot to the server computer 16, and in various embodiments, more specifically, using a database hosted on the server computer 16 (such as a patient's electronic health record (EHR), a radiology database (such as a picture archiving and communication system (PACS)), etc.). Data transmission to the hospital network is performed via a suitable wireless network of the hospital, such as the hospital Wi-Fi network 52 (although hospital wireless networks 52 other than Wi-Fi networks are also contemplated). Note that although the hospital Wi-Fi network 52 is Figure 5The hospital network 52 is represented schematically by a single illustrated Wi-Fi access point (AP) 52, but this is for ease of illustration and more typically the hospital network 52 will include multiple Wi-Fi APs distributed across the floors of the hospital to provide Wi-Fi coverage over most (but not necessarily all) areas of the hospital.
[0064] In the above example, the robot 40 suitably has a single radio unit 42 (e.g., a Wi-Fi radio unit) that provides both a wireless connection to the medical device 12 and a wireless connection to the hospital wireless network 52. In another example, if the medical device 12 has a type or protocol of wireless connection other than Wi-Fi, the robot 40 can again serve as a bridge between the medical device 12 and the hospital Wi-Fi system. In other words, in these embodiments, the Wi-Fi radio unit 44 of the medical device 12 is replaced by another type of radio unit, such as Bluetooth. TM Radio unit, Zigbee TM In these embodiments, the robot 40 includes a Wi-Fi radio unit 42 as described to communicate with the hospital Wi-Fi network 52, and also includes a second radio unit (not shown) configured to communicate via the communication type or protocol of the medical device 12 (e.g., Bluetooth TM or Zigbee TM ) to communicate. In these embodiments, the robot 40 thus acts as a Bluetooth TM or Zigbee TM or other non-Wi-Fi protocols and a mobile wireless bridge between the Wi-Fi hospital network 52. The advantages of these embodiments are that Bluetooth TM or Zigbee TM Or other non-Wi-Fi protocols may be short-range protocols (ie, shorter distances than Wi-Fi) and may therefore operate at lower power with less potential for radio frequency interference between medical devices.
[0065] It will also be understood that these embodiments may be implemented with a system having two radio units (e.g., Wi-Fi for communicating with the hospital wireless network 52 and Bluetooth for communicating with the medical device 12). TM or Zigbee TM The wireless relay device may be implemented as a fixed device (such as a radio unit) instead of the robot 40. For example, such relay devices may be strategically distributed in various areas of a hospital where medical devices using non-Wi-Fi protocols are to be used.
[0066] In any of these embodiments, the robot 40 provides improved reliability for wireless connections of the medical device 12. Thus, the need to temporarily store medical and / or operational data in an onboard storage buffer (e.g., such as flash memory) of the medical device 12 is reduced or eliminated.
[0067] Figure 5 The movement of the robot 40 equipped with the first Wi-Fi radio unit 42 is schematically illustrated by schematic trajectory 54. For the illustrative example, the robot 40 begins its path at a location near the server computer 16 (as shown) or at some other central location or warehouse where the robot places itself when not in use, providing wireless bridging for wireless medical devices. (In this regard, it should be noted that although the illustrative example Figure 5 A single robot 40 is shown schematically at different locations along a trajectory 54, but more generally, there may be a group of such robots providing wireless bridging for multiple medical devices simultaneously). In the illustrative trajectory 54, the robot starts and moves from its warehouse location to locate (and, if necessary, follow) a medical device 12 for data collection in a first room R1. The robot 40 can be configured to follow the first medical device 12 to a second room R2 with a Wi-Fi radio unit 44, and position itself to maximize the Wi-Fi signal and collect data from the first medical device 12. The robot 40 can also be configured to visit several medical devices 12 at different locations, for example, after the first medical device 12 is used, the robot 40 can be reassigned to the second medical device 12', and in response to the reassignment, the robot 40 is configured to move to a third room R3 to connect with the Wi-Fi radio unit 46 of the second medical device 12' to collect data therefrom.
[0068] When providing wireless bridging for the medical device 12, the robot 40 may or may not maintain a continuous Wi-Fi connection with the hospital Wi-Fi network 52. Generally, when providing wireless bridging, it is advantageous for the robot 40 to maintain a Wi-Fi connection with the hospital Wi-Fi network 52, because in this case, the medical and / or operational data generated by the medical device 12 can be immediately transmitted to the appropriate database, such as the patient's EHR, radiology database (such as PACS), etc. In this way, there is no data transmission delay, and there is no risk of buffered data loss (because the data is not buffered, but transmitted immediately). Maintaining a continuous Wi-Fi connection can be achieved in many cases. For example, if the Wi-Fi radio unit 42 of the robot 40 has a larger range than the Wi-Fi radio unit 44 of the medical device 12, it may be able to maintain a connection even in an area where the medical device 12 loses such a connection. In another approach, the robot 40 can strategically position itself in an intermediate position between the nearest hospital network AP 52 and the medical device 12 to maintain a Wi-Fi connection with both. The wireless radio unit 44 of the medical device 12 is a non-Wi-Fi radio unit (e.g., Bluetooth TM or Zigbee TM Radio unit), the robot 40 can provide a wireless bridge provided in a location with strong hospital Wi-Fi coverage (however, in such an embodiment the medical device cannot be used directly because it has a non-Wi-Fi radio unit).
[0069] However, in some embodiments, it is contemplated that the robot 40 provides wireless connectivity for the medical device 12 at locations where the robot 40 itself cannot maintain a Wi-Fi connection. In this case, the robot 40 appropriately includes a data buffer (e.g., flash memory), and the medical device 12 also includes a data buffer. The robot 40 uses its connection to the medical device 12 (Wi-Fi or non-Wi-Fi, depending on the embodiment) to collect and store medical and / or operational data from the medical device. At certain time intervals, the robot 40 interrupts the wireless connection with the medical device 12 and autonomously moves to a location where the robot 40 regains a Wi-Fi connection with the hospital Wi-Fi network 52, and transmits the medical and / or operational data stored in the robot's data buffer to an appropriate database via the hospital network 52. The robot 40 then moves back to a location close to the medical device 12 and reestablishes a wireless connection with the medical device 12 to resume collecting medical and / or operational data from the medical device 12. During the time interval during which the robot 40 interrupts the wireless connection with the medical device 12, the medical device 12 temporarily stores the medical and / or operational data it generates in its own data buffer. This approach reduces the amount of medical and / or operational data in the temporary buffer, thereby reducing data latency, enabling the use of a smaller data buffer in the medical device 12, and reducing the extent of data loss when the data buffer of the medical device 12 loses stored data.
[0070] In the illustrative example, the robot 40 comprises a ground vehicle, such as wheels or tracks for autonomous movement on floors of hospital corridors and rooms, etc. In another embodiment, the robot 40 comprises an unmanned aerial vehicle (UAV), such as an airborne drone, having navigation sensors 14 that allow positioning and movement in 3D space. Such an embodiment may be useful, for example, in situations such as mobile emergency medical facilities deployed in disaster locations.
[0071] In another embodiment, the robot 40 is configured to automatically follow the medical device 12 and reposition itself to extend and maximize the Wi-Fi connection between the medical device 12 and the local hospital IT network 52. If the robot 40 detects that the medical device 12 is moving too far from the Wi-Fi AP 30, and the robot 40 itself cannot continue to connect to the local hospital IT network 52, it will request another similar robot 40 to fill the gap. In this way, multiple robots 40 will be lined up to provide uninterrupted Wi-Fi connections for the medical devices 12.
[0072] In another embodiment of the robot 40, the server computer 16 has an orchestration mechanism that can track multiple robots 40 in the hospital. If the range of the current robot 40 has been maximized and a particular hospital area is not covered, the orchestration software in the server computer 16 can direct the deployment of an additional number of robots 40. The number of additional robots 40 to be deployed can then be decided based on the hospital area and the number of medical devices 12 present in the hospital.
[0073] In another embodiment, the medical devices 12 are stationary and the robot 40 navigates to the stationary medical devices 12 on a fixed schedule to collect data (image data, log information, etc.). The robot 40 can be configured to collect data from multiple medical devices 12 upon request while it is en route to the next waypoint, which can be a stationary or mobile medical device 12 or a server computer 16, where the data is downloaded for further data storage (e.g., picture archiving and communication system (PACS) database, maintenance database, etc.) and processing (e.g., image analysis, alarm scoring, etc.).
[0074] In another embodiment, processing of the data (e.g., computer-aided decision algorithms, image quality analysis, analysis of log files, etc.) is performed on the robot 40, and the generated results are sent along with the collected data to the server computer 16. In this way, proprietary algorithms that rely on vendor-specific imaging system information can be applied to the data before it is sent to the PACS.
[0075] In another embodiment, the robot 40 moves on a rail system or similar safety guard system to facilitate navigation on a predefined route arranged by a rail / safety guard system (electromagnetic coils in the ground, etc.). In this way, the requirements for the conflict detection sensor 14 can be relaxed. In another variation, the rail system can include overhead transport (OHT), and the robot 40 then appropriately includes an OHT vehicle running on the OHT. Such OHT systems are sometimes used in complex manufacturing sites such as semiconductor manufacturing facilities, so vehicle transportation coordination and collision avoidance techniques used in manufacturing OHT systems can be easily applied. The advantage of OHT is that the robot 40 is located above the medical staff, thereby greatly reducing or eliminating the possibility of conflict with medical staff, equipment, etc. again. In addition, the robot 40 can be operated in manual mode, that is, the robot 40 is moved and repositioned by an operator. In another contemplated embodiment, a technician from a given institution uses a device with augmented reality (AR) capabilities like a smartphone or tablet to pre-map the route of interest of the robot 40.
[0076] Since the robot 40 may be out of range of the hospital Wi-Fi network 52, it should generally be able to operate autonomously to locate the medical device 12 or 12' to which it is assigned, establish wireless communication with the assigned medical device, and (in some embodiments) in parallel transmit medical and / or operational data received from the assigned medical device to the hospital Wi-Fi network 52, and (in some embodiments) temporarily store the received medical and / or operational data in a data buffer (e.g., flash memory) of the robot 40, and occasionally interrupt the wireless connection with the medical device 12 and go to a location with hospital Wi-Fi access to transmit the stored data to the network and return to the medical device to re-establish wireless communication therewith. Therefore, the robot 40 appropriately includes Figure 5 Components not shown, such as an on-board electronic processor (e.g., a microprocessor or microcontroller) and on-board memory (e.g., flash memory, read-only memory, electrically erasable read-only memory, etc.), store instructions that can be read and executed by the electronic processor to control the robot 40 (including controlling at least one radio unit 42) to perform these autonomous functions.
[0077] In a more general embodiment, an electronic processor is provided, and a memory storing instructions readable and executable by the electronic processor to: determine whether a radio unit 44 of a medical device 12 has a wireless connection, and in response to the determination that the radio unit 44 of the medical device 12 does not have a wireless connection, perform a remedial action. In the previously described embodiment, the electronic processor and memory are onboard the robot 40, and the remedial action entails controlling the robot 40 to autonomously move the robot toward the medical device 12 and establish a wireless connection with the radio unit 44 of the medical device via at least one radio unit 42 of the autonomous robot 40; acquiring medical and / or operational data generated by the medical device via the established wireless connection; and transmitting the acquired medical and / or operational data to the hospital wireless network 52 via at least one radio unit of the autonomous robot.
[0078] In another embodiment, the electronic processor and memory are integrated into the medical device 12 itself, and the instructions program the electronic processor of the medical device 12 to use the Wi-Fi or other wireless radio unit 44 of the medical device 12 to detect Wi-Fi (or other wireless) signal strength when the medical device 12 is moved to a new location. Based on this tracking, it is determined whether the medical device 12 has a wireless connection (wherein not having a wireless connection corresponds to not having a wireless connection at all, or having a weak wireless connection that is insufficient to reliably transmit the acquired medical and / or operation data to the hospital wireless network 52). In response to determining that the radio unit 44 does not have a wireless connection, the remedial action can appropriately suggest moving the medical device 12 to a location with stronger signal strength. The medical device 12 can indicate, for example, on a display of the medical device (or, in another embodiment, on a display of a mobile phone or other mobile device carried by a hospital staff member who transports the medical device 12) where the medical device 12 should be moved to ensure wireless connection. The hospital staff can then move the medical device 12 to that location. In another variation, the medical device 12 can relay the notification to the individual (e.g., hospital staff) responsible for relocating the device. Such a notification may indicate that the device's location needs to be updated, or the notification may also relay information about a recommended updated location for the medical device that will establish (or improve) a Wi-Fi signal connection.
[0079] In a variant embodiment, if a map of Wi-Fi access points APs is available along with RTLS tracking of the medical device 12 (e.g., via an RTLS tag on the medical device 12) (or another location tracking system such as a global positioning system (i.e., GPS)), then the determination that the radio unit 44 in the medical device 12 does not have wireless connectivity may be based on whether the RTLS tracked location of the medical device 12 is within the operating range of at least one Wi-Fi AP as indicated by the Wi-Fi AP map. If it is determined that the medical device 12 does not have wireless connectivity, the notification may suggest moving the medical device 12 to the nearest location within the operating range of the at least one AP.
[0080] The apparatus 10 may be applied to a mobile medical device 12 having a wirelessly connected sensor 14 (eg, a Wi-Fi ultrasound probe, a Wi-Fi X-ray detector, etc.) in order to optimize the connectivity and operability of the mobile medical device 12 .
[0081] Furthermore, the apparatus 10 may be applied to any mobile medical device 12 that collects data to ensure timely transmission of the data to a local PACS.
[0082] Finally, the apparatus 10 may be used generally with both mobile and stationary medical devices 12 to periodically collect data from the medical devices 12 without relying on the medical devices 12 being connected to a local hospital network 52 .
[0083] The present disclosure has been described with reference to the preferred embodiments. After reading and understanding the above specific embodiments, others may make modifications and changes. It is intended that the exemplary embodiments be interpreted as including all such modifications and changes as long as they are within the scope of the appended claims or their equivalents.
Claims
1. A system (300) for evaluating and / or providing wireless communication between a medical device (12, 12') and a hospital wireless network (52), the system comprising: Electronic processors; as well as A memory storing instructions readable and executable by the electronic processor, the instructions for performing the following operations: determining whether a radio unit (44) of the medical device has a wireless connection; and Responsive to the determination that the radio of the medical device does not have a wireless connection, performing a remedial action.
2. The system (300) according to claim 1, further comprising: At least one autonomous robot (40) comprising at least one radio unit (42) and said electronic processor and said memory storing instructions readable and executable by said electronic processor, wherein said remedial action comprises: autonomously moving the robot toward the medical device and establishing a wireless connection via the at least one radio unit of the autonomous robot with the radio unit (44) of the medical device; acquiring medical and / or operational data generated by the medical device via the established wireless connection; and The acquired medical and / or operational data is transmitted to the hospital wireless network (52) via the at least one radio unit of the autonomous robot.
3. The system according to claim 2, wherein: The at least one radio unit (42) of the robot includes a non-Wi-Fi radio unit and a Wi-Fi radio unit, the non-Wi-Fi radio unit is configured to establish the wireless connection with the radio unit (44) of the medical device (12), and the Wi-Fi radio unit is configured to transmit the acquired medical and / or operational data to the hospital wireless network (52).
4. The system according to claim 2, wherein: The at least one radio unit (42) includes a single radio unit configured to both establish the wireless connection with the radio unit (44) of the medical device (12) and transmit the acquired medical and / or operational data to the hospital wireless network (52).
5. The system according to any one of claims 2 to 4, wherein: The on-board memory stores instructions readable and executable by the electronic processor, the instructions being used to control the robot (40) to acquire the medical and / or operational data generated by the medical device (12) via the established wireless connection, and in parallel transmit the acquired medical and / or operational data to the hospital wireless network (52).
6. The system according to any one of claims 2 to 5, wherein: The on-board memory stores instructions readable and executable by the electronic processor, the instructions for controlling the robot (40) to perform at least one iteration of: (i) acquiring medical and / or operational data generated by the medical device via the established wireless connection when the robot is not connected to the hospital wireless network (52); and disconnecting the wireless connection with the radio unit (44) of the medical device and then moving away from the medical device, and transmitting the acquired medical and / or operational data to the hospital wireless network (52) when the robot is not connected to the radio unit of the medical device.
7. The system (300) of claim 1, wherein: The medical device 12 includes the electronic processor and the memory, and the remedial action includes outputting at least one of: (i) an indication that the medical device 12 does not have a wireless connection and / or (ii) a recommendation of a location to which the medical device can be moved to provide a wireless connection.
8. The system (300) of claim 7, wherein: The determination as to whether the radio unit (44) of the medical device (12) has a wireless connection is based on a measurement of a wireless signal strength determined using the radio unit of the medical device, the wireless signal strength being received by the radio unit of the medical device.
9. The system (300) according to one of the claims 7, wherein: The determination as to whether the radio unit (44) of the medical device (12) has a wireless connection includes: using a location tracking system to determine a current location of the medical device (12); and The current location is compared to a map of Wi-Fi access points to determine whether the radio unit of the medical device has a wireless connection to at least one Wi-Fi access point.
10. A medical device (10), comprising: Medical equipment (12); one or more sensors (14) configured to monitor transportation of the medical device; as well as At least one electronic processor (16, 18) programmed to: detecting a time-stamped transportation event based on sensor data acquired by the one or more sensors; as well as Remedial action is performed in response to the detected time-stamped transportation event.
11. The medical device (10) according to claim 10, wherein: The one or more sensors (14) include an inertial measurement unit (IMU) disposed on or in the medical device (12); and the at least one electronic processor (16, 18) is programmed to: The time-stamped transport event is detected to include a time-stamped impact event in which the portable medical device is subjected to an impact, and the remedial action performed in response to the detected time-stamped impact event includes at least recording the time-stamped impact event.
12. The medical device (10) according to any one of claims 10-11, wherein: The medical device (12) is portable, and the one or more sensors (14) include: a position sensor disposed on or in the portable medical device (12); and a handle use sensor placed on or in a transport handle (13) of the medical device and configured to detect use of the transport handle; wherein the at least one electronic processor (16, 18) is programmed to: The time-stamped transport event is detected including a time-stamped handle non-use event in which the handle use sensor does not detect use of the transport handle while the position sensor detects transport of the portable measurement device.
13. The medical device (10) according to any one of claims 10-11, wherein: The medical device (12) is portable, and the one or more sensors (14) include: A proximity sensor, comprising a first sensor component and a second sensor component, wherein the first sensor component is placed on or in the portable medical device, and the second sensor component is placed on a device support component (15), wherein the device support component (15) is configured to be detachably connected to the portable medical device and to support the portable medical device, wherein the first sensor component and the second sensor component are configured to detect whether the first sensor component and the second sensor component are close to each other; and a position sensor disposed on or in the portable medical device; wherein the at least one electronic processor (16, 18) is programmed to: The time-stamped transport event is detected including a time-stamped support device non-use event in which the proximity sensor does not detect the first sensor assembly and the second sensor assembly being in proximity to each other while the position sensor detects transport of the portable measuring device.
14. The medical device (10) according to any one of claims 10-11, wherein: The one or more sensors (14) include: a connection sensor configured to detect whether a detachable device support assembly (15) is connected to the portable medical device (12); and a position sensor disposed on or in the portable medical device; wherein the at least one electronic processor (16, 18) is programmed to: Detecting the time-stamped transport event including a time-stamped support device non-use event, in which the connection sensor does not detect that the detachable device support assembly is connected to the portable medical device while the position sensor detects transport of the portable medical device.
15. The medical device (10) according to any one of claims 10 to 13, wherein: The medical device (12) is portable, and the one or more sensors (14) include: a position sensor placed on or in the portable medical device (12); wherein the at least one electronic processor (16, 18) is programmed to: The time-stamped transportation events are detected including a time-stamped transportation exceeding event in which the position sensor detects that the portable measurement device is being transported at a speed greater than a speed limit.
16. The medical device (10) according to any one of claims 10 to 15, wherein: The medical device (12) is portable, and the one or more sensors (14) include: a vital sign sensor configured to measure a person's vital signs; a device location sensor disposed on or in the portable medical device (12); and a person position sensor configured to be worn by the person; wherein the at least one electronic processor (16, 18) is programmed to: detecting the time-stamped transportation event including a time-stamped physiological stress event in which the device and the person position sensor detect that the person and the portable medical device are moving together, and The vital signs sensor detects that the person is under physiological stress.
17. The medical device (10) according to any one of claims 10 to 16, further comprising: an audible and / or visual alarm (14) disposed on the portable medical device (12); wherein the at least one electronic processor (16, 18) is programmed to: The remedial action is performed including activating the audible and / or visual alarm.
18. The medical device (10) according to any one of claims 10 to 17, wherein: The at least one electronic processor (16, 18) is programmed to: Performing the remedial action includes recording the time-stamped transportation event, the time-stamped transportation event being annotated with a spatial location at which the time-stamped transportation event occurred, the spatial location being determined based on a real-time location service (RTLS) (14) in communication with the at least one electronic processor.
19. A medical communication system (300) for providing wireless communication between a medical device (12, 12') and a hospital Wi-Fi network (52), the system comprising: A radio system (42) comprising a Wi-Fi radio unit and a non-Wi-Fi radio unit; as well as An electronic processor and a memory storing instructions readable and executable by the electronic processor to: establishing a wireless connection with a non-Wi-Fi radio unit (44) of the medical device via the non-Wi-Fi radio unit; acquiring medical and / or operational data generated by the medical device via the established wireless connection; and The acquired medical and / or operational data is transmitted to the hospital Wi-Fi network (52) via the Wi-Fi radio unit.
20. The medical communication system (300) according to claim 19, wherein: The medical communication system includes an autonomous vehicle (40).
