Transfer device and control system

Through the adoption of distributed control systems, the problems of high cost and insufficient automation capabilities of traditional control systems are solved, the safety and efficiency of automated transfer operations are achieved, and patient transfers of different body types and states are adapted to improve signal integrity and system reliability.

CN118946336APending Publication Date: 2024-11-12ABLE INNOVATIONS INC
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202380030905.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-03-31
Filing Date
2023-03-30
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

Traditional control systems for transfer devices have high costs, design compromises, lack of modularity and adaptability, signal management and integrity, resulting in limited automation and control capabilities, relying on manual user control and may be brittle or fragile. The object causes damage.

Method used

Adopt a distributed control system, using multiple subsystem controllers to work in concert with the system processor, realize automatic and semi-autonomous operation, reduce costs through distributed architecture, improve modularity and adaptability, improve signal integrity, and pass the manager The system integrates user input and sensor information to make decisions and actions.

Benefits of technology

The safety and efficiency of automated transfer operations are achieved, the risk of failure is reduced, and the transfer of patients of different body types and states is adapted to improve signal integrity and system reliability, and the dependence on users is reduced.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118946336A_ABST
    Figure CN118946336A_ABST
Patent Text Reader

Abstract

The present disclosure relates to a transfer device, such as a patient transfer device, comprising: a device body; the transfer platform is supported by the device main body; a plurality of subsystems; a plurality of subsystem controllers, each subsystem controller configured to control an operation of one of the plurality of subsystems; and a system processor in communication with the plurality of subsystem controllers. The transfer platform has at least one conveyor belt configured to move an object. Each subsystem is configured to implement a function of the transfer device. The system processor is configured to monitor and communicate with the plurality of subsystem controllers, receive operator input from a transfer device operator, make decisions regarding a transfer operation based on the input received from the transfer device operator and / or the input received from the plurality of subsystem controllers, and send commands to the plurality of subsystem controllers to complete the various transfer operation routines.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 362,301, filed on March 31, 2022, and entitled “Distributed Control System for a Transfer Device,” under 35 U.S.C. §119(e), which is hereby incorporated by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to transfer devices for moving objects, and more particularly to control systems and methods for such transfer devices. Background Art

[0004] The transfer device generally has a device body and a transfer platform configured to move the object. The transfer device can be controlled by a control system, for example, to control the movement of the transfer platform when moving the object or patient.

[0005] According to conventional approaches, control systems for transfer devices may have several disadvantages. For example, control systems (i) may be expensive, (ii) may involve various design compromises, (iii) may lack modularity, scalability, and adaptability, and (iv) may suffer from poor signal management and integrity.

[0006] In addition, the control system may have limited automation and control capabilities, thereby relying on manual user control and intervention. Unfortunately, such manual user control and intervention can be cumbersome and may lead to difficulties, such as variations in user interaction and interpretation. In situations where the object is fragile or fragile, especially in the case of transferring a patient who may be frail and / or immobile, incorrect input and control commands from the user may cause serious injury or damage to the patient or object being transferred.

[0007] Therefore, the conventional method still has many deficiencies. The purpose of the disclosed technology is to improve the conventional method to solve or alleviate some or all of the above-mentioned shortcomings. Summary of the invention

[0008] The disclosed technology provides a transfer device for moving an object and related control systems, devices and methods. One aspect of the disclosed technology includes a transfer device with a control system. In various specific implementations, the transfer device is configured to move a patient and therefore may be referred to as a patient transfer device in some cases. The transfer device according to various specific implementations may have architectural variations, but generally includes a body with an actuator, a transfer platform, and a conveyor belt or multiple conveyor belts that are operably configured to move an object such as a patient. In some cases, various components and / or functions of the transfer device may be considered to be part of one or more operating subsystems of the transfer device.

[0009] The control system has a system processor that maintains supervision of a plurality of subsystem controllers that communicate with the system processor. In some cases, the control system is referred to as a distributed control system because control of the transfer device is distributed between the system processor and the plurality of subsystem controllers. Each subsystem controller is configured to communicate with and / or control various components to implement one or more functions of the transfer device. In some cases, the subsystem controller may be considered to be part of and / or control one of the operating subsystems of the transfer device.

[0010] The system processor is configured to perform various activities depending on the state of the transfer device and the desired mode of operation. In some examples, the system processor is configured to monitor and communicate with one or more of the subsystem controllers. According to various specific implementations, the system processor is configured to perform specific operations or actions by loading and executing instructions stored in one or more memory devices. The system processor executing the instructions causes the control system and / or the transfer device to perform the desired actions.

[0011] According to various specific implementations, the system processor is configured with instructions including preloaded, adaptable and interactive subroutines and algorithms. In some instances, the instructions configure the system processor to take actions based on information collected or transmitted from the subsystem controller. For brevity and convenience, the system processor is sometimes described as performing various actions. Such references mean that the system processor is configured with appropriate instructions for execution by the system processor. In addition, the term "manager system" is sometimes used herein to refer to the system processor and various instructions stored in memory and / or the system processor that operates according to various instructions (e.g., a collection of software applications running on the system processor) and is therefore configured to perform corresponding activities.

[0012] Compared to using a single microcontroller, utilizing multiple subsystem controllers can result in reduced costs, avoidance of design compromises, and increased modularity, which in turn can enable scalability and adaptability. Moreover, in various implementations, one or more of the subsystem controllers can be located in different areas of the transfer device (e.g., not all in a single location), thereby providing a physically distributed control system. Such placement can allow various subsystem controllers to be located near specific sensors and / or actuators so that signals can be sent and received over shorter distances, which can improve signal integrity and mitigate noise.

[0013] Various specific implementations of the distributed control system disclosed herein enable automatic and semi-autonomous operation. In such cases, various subsystem controllers can work together to automatically perform patient transfers without user intervention. Depending on the specific implementation, the distributed control system may include various subsystem controllers. In various cases, the distributed control system has a system processor that is configured with instructions to implement an abstract operating system and a transfer program that serves the purpose of collecting, interpreting and sending commands on behalf of a human operator (also referred to herein as a "user"). In such cases, the manager system (i.e., a system processor programmed with specific instructions) can be configured to autonomously make decisions and send commands based on information received from the operator and from one or more subsystem controllers. The subsystem controllers may include, but are not limited to, a power system controller, a transfer operation controller (e.g., at least an operating platform and a conveyor belt), and a lift and tilt actuator controller. It should be understood that additional proximity sensors and / or peripheral devices may also be included in a typical configuration of such a transfer device and control system.

[0014] Various implementations of the disclosed technology include a transfer device and / or distributed control system having one or more of the following aspects and / or features. In some implementations, the manager system is configured to perform various operations based on operator input of transfer parameters (e.g., subject or patient characteristics, such as, for example, height and body mass index). Other inputs may include parameters of a support surface (e.g., a bed), such as the width and type of mattress (e.g., an air mattress or a foam mattress). In various cases, the manager system may execute routines to enable coordinated operation of multiple subsystem controllers, such as, for example, coordination and unification of operating states. In some cases, the manager system may perform protection and security routines to identify device-wide errors or faults and transmit them to the required subsystem controllers, thereby allowing the subsystem controllers to take corresponding actions, such as, for example, stopping a motor. In some cases, the manager system may centralize various device-level subroutines. As an example, the manager system may perform security protection on the transfer device, including preventing unauthorized access and / or inappropriate commands from being sent directly to the subsystem controllers if a security breach (e.g., a hacking incident) occurs.

[0015] A method of operating a transfer device is also disclosed. In various specific implementations, the transfer device has a device body, a transfer platform, at least one conveyor belt, and a distributed control system, the distributed control system including a manager system and a plurality of subsystem controllers. The manager system includes a system processor and executable instructions stored in a physical non-transitory medium, the executable instructions causing the system processor to relay information to the subsystem controller, record and transmit the obtained information, and send actions and / or requests to the subsystem controllers in the distributed control system.

[0016] According to various aspects, another method of operating a transfer device includes receiving one or more images from at least one imaging device and processing the images to determine at least one variable associated with transfer of an object by the transfer device.

[0017] Also disclosed is a non-transitory computer-readable medium having statements and instructions recorded thereon that, when executed by a system processor of a transfer device, configure the system processor to implement one or more of the various systems and one or more of the methods disclosed herein.

[0018] Examples of various specific implementations of the disclosed technology include, but are not limited to, the following:

[0019] In Example 1, a transfer device includes: a device body; a transfer platform supported by the device body, the transfer platform including at least one conveyor configured to move an object onto the transfer platform and / or away from the transfer platform; a plurality of subsystems, each subsystem being configured to implement a function of the transfer device; a plurality of subsystem controllers, each subsystem controller being configured to control the operation of one of the plurality of subsystems; and a system processor communicating with the plurality of subsystem controllers, the system processor being configured to: monitor and communicate with the plurality of subsystem controllers, receive operator input from a transfer device operator, make decisions regarding transfer operations based on input received from the transfer device operator and input received from the plurality of subsystem controllers, and send commands to the plurality of subsystem controllers.

[0020] In embodiment 2, the transfer device according to embodiment 1, wherein two or more of the plurality of subsystem controllers are located in different areas of the transfer device near one or more sensors and / or actuators.

[0021] In Example 3, the transfer device according to Example 1 or Example 2, wherein the system processor and the plurality of subsystem controllers are configured to operate together to automatically perform the patient transfer without user intervention.

[0022] In embodiment 4, according to any one of embodiments 1 to 3, the system processor is configured to control a human machine interface (HMI) of the transfer device.

[0023] In embodiment 5, according to the transfer apparatus according to any one of embodiments 1 to 4, the plurality of subsystem controllers include a subsystem controller configured to control the transfer of the object.

[0024] In Example 6, according to the transfer device of Example 5, the distributed control system is configured to receive the tension and displacement of at least one conveyor belt and the position and speed of the transfer platform for use in the method of transferring a patient.

[0025] In Example 7, according to the transfer device of any one of Examples 1 to 6, the plurality of subsystem controllers include a subsystem controller configured to adjust the height and angle of the transfer platform and / or the transportation of the transfer device.

[0026] In Example 8, according to any one of Examples 1 to 7, the plurality of subsystem controllers include a subsystem controller configured to control one or more peripheral subsystems of the transfer apparatus that do not participate in the movement of the transfer platform.

[0027] In embodiment 9, the transfer device according to any one of embodiments 1 to 8, wherein the plurality of subsystem controllers include a subsystem controller configured to control power delivery to electronic components of the distributed control system and to actuators of the transfer device.

[0028] In Example 10, a transfer device according to any one of Examples 1 to 9, wherein the plurality of subsystems are configured to implement one or more of the following: (i) transferring an object, (ii) adjusting the height and angle of a transfer platform and / or transporting the transfer device, (iii) controlling peripheral devices of the transfer device that are not involved in the movement of the transfer platform, (iv) providing device safety, and (v) controlling power delivery to electronic components of a distributed control system and to actuators of the transfer device.

[0029] In embodiment 11, according to any one of embodiments 1 to 10, the system processor is configured to establish a secure connection to an external network to upload captured images, diagnostic data and / or download firmware changes.

[0030] In embodiment 12, according to the transfer device of embodiment 11, the external network is an intranet configured to facilitate communication between multiple transfer devices.

[0031] In embodiment 13, according to the transfer device of embodiment 11, the external network is the World Wide Web.

[0032] In Example 14, a transfer device according to any one of Examples 1 to 13, wherein the system processor communicates with an imaging subsystem including at least one imaging device, and wherein the system processor is configured to receive at least one captured image from the at least one imaging device, and use image processing of the captured image to determine at least one variable, so that the at least one variable is related to the transfer of the object by the transfer device.

[0033] In Example 15, the transfer device according to Example 14, wherein the system processor is configured to receive multiple captured images forming a video feed from at least one imaging device, and use image processing of the video feed to determine at least one variable, so that the at least one variable is related to the transfer of the object by the transfer device.

[0034] In Example 16, according to any one of Example 14 or Example 15, the subsystem controller is configured to determine at least one variable using processing of at least one captured image, so that the at least one variable is related to the transfer of the object by the transfer device.

[0035] In Example 17, according to the transfer device of Example 16, the at least one variable includes the mass and / or volume of the object.

[0036] In Example 18, the transfer device according to Example 16 or Example 17, wherein the at least one variable includes the position and / or orientation of the object.

[0037] In Example 19, the transfer device according to any one of Examples 16 to 18, wherein the system processor is configured to assess the risk of damage to the subject based on at least one variable.

[0038] In Example 20, according to any one of Examples 16 to 19, the system processor is configured to determine parameters and / or limitations of the transfer object of the transfer device based on at least one variable.

[0039] In Example 21, the transfer device according to Example 20, wherein the system processor receives feedback from at least one of the subsystem controllers regarding the forces measured during the transfer of the object, and the system processor is configured to adjust the parameters and / or limits based on the feedback.

[0040] In embodiment 22, the transfer device according to any one of embodiments 16 to 21, wherein the system processor is connected to a persistent memory configured to record the video or image feed for future playback.

[0041] In Example 23, according to any one of Examples 16 to 21, the system processor is configured to establish an external data connection and is configured to send the image or video feed to an external receiving unit for monitoring and observation through the external data connection.

[0042] In embodiment 24, a method for execution by a system processor of a transfer device, the transfer device comprising a device body and a transfer platform configured to move an object, the method comprising: receiving at least one image from at least one imaging device, using image processing of the at least one image to determine at least one variable, so that the at least one variable is related to the transfer of the object by the transfer device.

[0043] In Example 25, the method according to Example 24, wherein at least one variable includes the mass and / or volume of the object.

[0044] In Example 26, a method according to Example 24 or Example 25 is provided, wherein at least one variable includes a position and / or orientation of the object.

[0045] In Example 27, the method according to any one of Examples 24 to 26 further comprises: assessing the risk of impairment of the subject based on the at least one variable that has been determined.

[0046] In Example 28, the method according to any one of Examples 24 to 27 further comprises: determining parameters and / or limitations of the transfer object of the transfer device based on the at least one variable that has been determined.

[0047] In Example 29, the method according to Example 28 further includes: receiving feedback about the forces measured during the transfer of the object, and adjusting the parameters and / or limits based on the feedback.

[0048] In Embodiment 30, the method according to any one of Embodiments 24 to 29 further comprises: recording at least one image for future playback.

[0049] In Example 31, according to any one of the methods of Examples 24 to 30, it further includes: establishing an external data connection, and sending at least one image to an external receiving unit for monitoring and observation through the external data connection.

[0050] In embodiment 32, a non-transitory computer-readable medium has statements and instructions recorded thereon, which when executed by a system processor of a transfer device configures the system processor to implement the method according to any one of embodiments 24 to 31.

[0051] In Example 33, an apparatus comprises: any combination of parts or components as described and / or depicted herein.

[0052] In Example 34, a method comprising: any steps or any combination of steps as described and / or depicted herein.

[0053] In embodiment 35, a non-transitory computer-readable medium having statements and instructions recorded thereon, which when executed by a processor of a device configures the processor to implement a method including any combination of steps or steps as described and / or depicted herein.

[0054] Other aspects and features of the disclosed technology will become apparent to those of ordinary skill in the art upon reading the following description of various embodiments of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] Embodiments will now be described with reference to the accompanying drawings, in which:

[0056] Figure 1 is a block diagram of a distributed control system for a transfer device according to various implementations;

[0057] FIG. 2A to FIG. 2C is a schematic diagram of an example transfer apparatus according to various implementations;

[0058] FIG. 3A to FIG. 3B is a block diagram of a distributed control system for a transfer device according to various implementations;

[0059] FIG. 4A to FIG. 4I are various views of example user interface controls for a human machine interface (HMI) of a transfer device according to various implementations;

[0060] Figure 5A is a flow chart of a method for transferring an object using a transfer device according to various implementations;

[0061] Figure 5B is a flow chart of a method for transferring an object using a transfer device including image processing according to various implementations;

[0062] Figure 5C is a flow chart of an image analysis method according to various specific implementations;

[0063] Figure 5D is a flow chart of a method for estimating the mass and volume of a patient according to various implementations;

[0064] Figure 5E is a flow chart of a method for performing image-based metastasis risk assessment according to various implementations;

[0065] Fig. 5F is a flow chart of a method of relaying identified risks and other information to a user of a transfer device according to various implementations;

[0066] Figure 6 is a perspective view of a transfer device with an imaging system according to various implementations;

[0067] Figure 7 is a block diagram of a distributed control system for a transfer device according to various implementations;

[0068] Fig. 8A is a flow chart of a method for aligning a transfer device according to various implementations;

[0069] Figure 8B is a flow chart of a method for detecting contact between a device transfer platform and a support surface according to various implementations;

[0070] Figure 8C is a flow chart of a method for determining a characteristic of a support surface according to various implementations;

[0071] Fig.8D is a flow chart of a method for detecting an obstacle according to various specific implementations; and

[0072] Fig. 8E is a flow chart of a method for adjusting a position of an object on a transfer device according to various implementations.

[0073] Fig.8F is a series of diagrams illustrating different scenarios for adjusting the position of an object on a transfer device according to various implementations. DETAILED DESCRIPTION

[0074] First, it should be understood that although illustrative implementations of one or more embodiments of the present disclosure are provided below, the disclosed techniques can be implemented using any number of techniques, whether currently known or existing. The present disclosure should in no way be limited to the illustrative implementations, drawings, and techniques shown herein, including the exemplary designs and implementations shown and described herein, but may be modified within the scope of the appended claims and the full scope of their equivalents.

[0075] As noted above, one aspect of the disclosed technology provides transfer devices, systems, and methods for moving objects such as, for example, patients. As used herein and described with reference to the accompanying drawings, this aspect of the disclosure is often referred to as transfer device 200, patient transfer device 200, and variations thereof. Another aspect of the disclosed technology provides devices, systems, and methods for controlling transfer device 200. As used herein and described with reference to the accompanying drawings, this aspect of the disclosure is often referred to as control system 100, distributed control system 100, and variations thereof. It should be understood that the use of such terms to refer to these aspects of the disclosure is for brevity and convenience, and is in no way intended to be limiting to any particular form.

[0076] According to various specific implementations, the architecture of the transfer device may vary, but generally includes a body together with an actuator, a transfer platform, and a conveyor belt or multiple conveyor belts that are operably configured to move objects. In various specific implementations, the control system of the transfer device includes a system processor that communicates with multiple subsystem controllers. Each subsystem controller is configured to communicate with various components and / or control various components to implement one or more functions of the transfer device. In some cases, the components and functions of the transfer device can be considered to belong to one or more operating subsystems of the transfer device. In such cases, one or more subsystem controllers can be considered to be part of one of the operating subsystems and / or control one of the operating subsystems.

[0077] First reference Figure 1 , a block diagram of a distributed control system 100 for use with a transfer device 200 according to various implementations of the disclosed technology is shown. The distributed control system 100 has a system processor 110 coupled to a plurality of subsystem controllers 120, which are connected to the distributed control system 100 in accordance with various implementations of the disclosed technology. Figure 1 1 through 2 are depicted as first through Nth subsystem controllers. Each subsystem controller 120 according to these specific implementations is configured to implement functions of the transfer device 200, such as, for example, operation of a transfer sequence, control and monitoring of power systems, patient monitoring, movement of the transfer device (including lifting, tilting, and / or transporting), and equipment safety. The system processor 110 is configured to monitor and communicate with the subsystem controllers 120, among other things.

[0078] According to various implementations, the system processor 110 includes or is coupled to one or more physical non-transitory computer-accessible or readable storage devices, also referred to herein as "memory" and "memory devices". The memory may be implemented using any suitable memory technology, which may include, for example, temporary and longer-term configurations, volatile and non-volatile configurations, and solid-state and / or other physical formats. Examples of possible memory include random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), magnetic hard disks, optical disks, floppy disks, flash memory, electrically programmable memory (EPROM) and electrically erasable programmable (EEPROM) forms of memory, as well as other forms known in the art.

[0079] The memory device coupled to the system processor 110 contains instructions for configuring the system processor 110 to perform specific operations or actions by loading and executing the instructions. The system processor 110 executing the instructions causes the control system 100 and / or the transfer device 200 to perform the desired actions. References herein to the system processor 110 performing various activities mean that the system processor 110 is configured with the corresponding instructions for execution. As noted above, for convenience, the term "manager system" is used herein to refer to the system processor 110 and the various instructions stored in the memory and / or the system processor actively operating according to the various instructions (e.g., a collection of software applications stored in the memory and running on the system processor).

[0080] In various implementations, the manager system collects and interprets information from user input and subsystem controllers 120 to analyze and compute and automatically make decisions, and then coordinates and commands actions for subsystem controllers 120. In some implementations, the manager system collects information from subsystem controllers 120 and passes the information to other subsystem controllers 120. In various implementations, the manager system monitors the status and performance of subsystem controllers 120.

[0081] In some specific implementations, one or more of the subsystem controllers 120 are located in different areas of the transfer device (e.g., not all in a single location), thereby providing a physically distributed control system. Such placement allows various subsystem controllers to be located near various sensors and / or actuators so that signals can be sent and received over a shorter distance, which can improve signal integrity and mitigate noise. As an example, a specific subsystem controller may be physically located in an area shared by multiple components of a specific subsystem of the transfer device in some cases. As another example, in some cases, a transport controller that controls drive wheel and non-drive wheel motors and sensors is located in the base of the transfer device. The position of the controller in the base allows the wiring between the upper and lower components of the transfer device to be reduced. As another example, in some cases, a precision analog-to-digital conversion system controller is located close to a load cell, which is used to measure the transient force on the lifting actuator of the device. Such placement is advantageous because the raw electrical signal of the load cell is a very small voltage and is highly susceptible to noise.

[0082] Thus, the disclosed implementation of the distributed control system 100 differs from a centralized control system in which processing is typically located in one area. As described below, a distributed control system 100 configured with multiple subsystem controllers 120 in a decentralized manner (e.g., with one, two, or more subsystem controllers 120 located in different portions of a transfer device associated with various functions) may provide several potential benefits over utilizing a centralized control system in one area.

[0083] In various cases, the first potential benefit of utilizing multiple subsystem controllers 120 is reduced cost. Processors such as microcontroller units (MCUs) are often limited in how many general purpose inputs / outputs (GPIOs) they have. A single MCU may have enough GPIOs to handle all functions of the transfer device 200, but the single MCU may be expensive. In various specific implementations, each subsystem controller 120 is dedicated to the function of the transfer device. Therefore, it is possible to reduce the cost of each subsystem controller 120 by having reduced performance specifications (e.g., such as fewer GPIOs), so that the total cost of all subsystem controllers 120 can be lower than the cost of a single MCU with enough GPIOs to handle all functions.

[0084] The second potential benefit of utilizing the subsystem controller 120 is to avoid design compromises in various specific implementations. Due to a limited number of GPIOs or other specifications, attempts to use a single MCU may result in various design compromises. Various customizations or compromises made to address a limited number of GPIOs or other specifications may present difficulties. At the same time, in various cases, the specifications of the subsystem controller 120 may be sufficient to avoid any such design compromises. In addition, if many sensors and control inputs can be managed, a single MCU architecture may also have a relatively higher application cycle execution time than in a distributed control system. For example, a specific implementation of a distributed control system includes a plurality of subsystem controllers 120 working in coordination, each of which has a shorter application cycle execution time than in a single MCU architecture. The subsystem controllers 120 may communicate as needed between the distributed control system 100, thereby providing overall improved responsiveness and agility when compared to a system based on a single MCU architecture.

[0085] In various specific implementations, the third potential benefit of using the subsystem controller 120 is modularity, which in turn can achieve scalability and adaptability. In various specific implementations, since each subsystem controller 120 is dedicated to the function and / or subsystem of the transfer device 200, it is possible to add or remove the function and / or subsystem by adding or removing the subsystem controller associated with the function and / or subsystem. This can achieve customization of the transfer device 200, such as upgrading or simplifying one or more functions depending on the customer's request or budget. For example, if the transfer MCU is to be improved, but the human-machine interface is not improved, then only the transfer MCU will need to be changed. It should also be noted that there may be challenges that are difficult to deal with in modifying or redesigning existing controllers. In various specific implementations of the disclosed technology, additional and / or new functions can be added to the transfer device by allowing the transfer device 200 to communicate with common components such as the system processor 110. In addition, in the case of repairing or maintaining a given function, the subsystem controller 120 associated with the given function can be exchanged or replaced without affecting other functions, which can reduce downtime.

[0086] The fourth potential benefit of utilizing multiple subsystem controllers 120 is improved signal management and integrity in various situations. There are physical / electrical challenges associated with the collection, interpretation and management of sensor signals and the output of command signals to actuators (e.g., motors, brakes, etc.). In various specific implementations, it is possible to distribute the subsystem controllers 120 in a manner located near the relevant subsystems, sensors, and / or actuators so that signals can be sent and received over a shorter distance, which can improve signal integrity and mitigate noise. Signal integrity can also be improved by utilizing more specialized processors for specific subsystems, which may not be ideal for the rest of the system. For example, a processor that specializes in analog-to-digital conversion (ADC) for sensor docking can provide high-fidelity conversion. However, in addition to this task, the ADC processor has limited functional capabilities, and therefore separating the conversion from future operations allows these signals to be then transmitted to another processor that specializes in digital signal processing and analysis or other operations that need to be performed, for example.

[0087] In some implementations, in addition to the potential benefits described above, the distributed control system 100 can also enhance the efficiency and effectiveness of the transfer device 200 by, for example, enabling autonomous and automatic operation of the transfer device while ensuring patient and user safety. In some implementations, the distributed control system 100 reduces the likelihood that if one portion of the transfer device malfunctions or fails, the distributed control system 100 will not fail, the transfer device will not be damaged, and the patient will not be in danger.

[0088] exist Figure 1 In a specific implementation, the subsystem controller 120 includes a first subsystem controller, a second subsystem controller, and a third subsystem controller. However, more generally, the subsystem controller 120 may include two or more subsystem controllers, up to N subsystem controllers, as will be readily understood. In various cases, the number of subsystem controllers 120 depends on how many functions of the transfer device 200 exist according to the specific implementation. In various cases, each subsystem controller 120 may be considered to be part of the operating subsystem of the transfer device 200 and / or control the operating subsystem of the transfer device. Different types of transfer devices 200 may differ in the various subsystems and associated functions that exist. Moreover, the same type of transfer devices 200 may also differ in the various functions provided. For example, even if the first transfer device and the second transfer device belong to the same type, a subsystem or function may be enabled for the first transfer device, but disabled for the second transfer device. Therefore, the modular nature of the subsystem controllers, functions, and subsystems means that they can be selectively enabled or disabled in various cases.

[0089] It should be understood that the distributed control system 100 is applicable to any suitable transfer device 200 having a device body and a transfer platform capable of moving an object or patient. Such movement generally involves a change in the physical state of the object or patient. The change in physical state may include a change in position (e.g., moving the object or patient from one position to another) and / or a change in orientation (e.g., rotating the object or patient 90°). Therefore, as used herein, "patient transfer" performed by a transfer device does not necessarily mean that the patient must change position, particularly when the patient's orientation is transferred from a first orientation to a second orientation (e.g., rotating from being on the left shoulder to being on the stomach). In various specific implementations, the transfer platform can be conveyor-based in that the transfer platform is equipped with a conveyor belt. There are many possibilities. To illustrate this point, refer to FIG. 2A to FIG. 2C , which are schematic diagrams of an example transfer device 200 in which the distributed control system 100 may be implemented.

[0090] Figure 2A One possible transfer device 200 according to various implementations is shown having a platform plate which is a transfer platform 202. The platform plate has bidirectional functionality (i.e., can move in two directions) to move a patient 10 from a first position 20 on one side of the transfer device 200 to a second position 30 on the other side of the transfer device 200. The transfer device 200 is conveyor-based in that the platform plate is equipped with a conveyor belt.

[0091] Figure 2B Another possible transfer device 200 is shown according to various implementations. The transfer device has platform segments instead of platform plates, so that the platform segments are used to "build" a transfer platform 202. The transfer platform 202 also has bidirectional functionality to move a patient 10 from a first position 20 on one side of the transfer device 200 to a second position 30 on the other side of the transfer device 200. The transfer device 200 is conveyor-based in that the transfer platform formed by the platform segments is equipped with a conveyor belt.

[0092] Figure 2C Another possible transfer device 200 is shown, which in various embodiments has a platform plate without bidirectional functionality. The platform plate is a transfer platform 202, but can only extend in one direction. The transfer device 200 is based on a conveyor belt, because the platform plate is equipped with a conveyor belt.

[0093] FIG. 2A to FIG. 2CThe transfer device 200 can be used to transfer a patient 10 from an initial starting position on a surface to a platform of the device, and then move the patient 10 again to the same or a different desired surface. For example, the articulated platform can be extended to a position underneath the patient 10 to be transferred - for example, between the patient 10 and the surface supporting the patient 10 - and then retracted with the patient 10 supported by the transfer belt and the transfer platform so that the patient 10 is positioned above the main body of the device. Additionally or alternatively, the transfer platform can be extended to transfer a patient 10 positioned above the main body of the device (i.e., supported on the transfer belt) to a remote surface.

[0094] Although the transfer device 200 is specifically described as being associated with and used in the context of transferring human subjects (e.g., individuals with reduced, limited, or incapacitated mobility, able-bodied individuals, unconscious individuals, incapacitated individuals, etc.), it should be understood that the transfer device 200 may alternatively be used to transfer other objects, such as those that are large, bulky, fragile, and / or difficult to grasp and move. For example, the transfer device 200 may be adapted and / or adapted for use in transferring livestock or domestic animals, undomesticated animals (e.g., in a zoo or wildlife care facility), human corpses (e.g., in a funeral home morgue), inanimate objects (e.g., in courier, freight, and / or logistics operations), etc.

[0095] In various specific implementations, in addition to FIG. 2A to FIG. 2C Transfer devices other than the ones shown are possible. Specific implementations of the distributed control system 100 are applicable to any suitable transfer device 200 having a transfer platform 202 capable of moving an object, whether or not the transfer platform supports bidirectional functionality or unilateral functionality, and whether or not the transfer platform is implemented using plates, segments, and / or other components. Additional examples of suitable transfer devices 200 that may be adapted for use in accordance with the present disclosure are described in international patent application PCT / CA2022 / 050044, entitled “Devices and Methods for Transferring an Object,” filed on January 12, 2022 and published as WO 2022 / 150915A1 on July 21, 2022, which is hereby incorporated herein by reference in its entirety.

[0096] Return to reference Figure 1In some implementations, the system processor 110 is a central processing unit (CPU), although other processors such as, but not limited to, MCUs, field programmable gate arrays (FPGAs), and application specific integrated circuits (ASICs) are possible. In some implementations, the system processor 110 includes a primary processor and a redundant processor, which can be a backup processor in the event of failure of the primary processor. In various cases, the system processor 110 includes or is coupled to one or more memory devices that contain instructions for configuring the system processor 110 to perform specific operations or actions. As noted elsewhere, the configuration of the system processor 110 with various instructions provides a manager system capable of, among other things, monitoring and communicating with the subsystem controllers 120. In some implementations, in addition to monitoring and communicating with the subsystem controllers 120, the manager system also supports a human-machine interface.

[0097] According to various specific implementations, one or more of the subsystem controllers 120 are implemented using an MCU, although other processors including but not limited to CPUs, FPGAs, and ASICs are also possible. In various cases, the subsystem controller 120 also includes one or more memory devices that include a processor and / or are coupled to a processor. In such cases, the memory stores instructions that configure the processor to perform one or more tasks.

[0098] There are many possibilities for the various functions and / or subsystems handled by the subsystem controller 120. Examples include, but are not limited to, actuation and control of the transfer platform and transfer belt; a human machine interface 320 (HMI) for the transfer device; lifting, tilting or other forms of positioning and position determination; transportation of the transfer device; management and control of peripheral devices of the transfer device; and power delivery and management of the transfer device. Further example details are provided below with reference to the accompanying drawings. Note that additional and alternative functions are possible.

[0099] According to various implementations, the manager system may be configured to make decisions or execute predetermined routines based on a combination of user input, external sensory input, and / or information obtained from subsystem controllers. In such cases, the manager system will automate various system and / or subsystem routines, thereby reducing the need for an operator. Automated routines may include, for example, providing an operator or user with pre-loaded transfer routines, automatically enabling cleaning cycles, maintaining device-level authorization and defensive security, or performing staging and device setup routines before or after a transfer is completed.

[0100] A potential benefit of such a manager system in various implementations would be to provide for scalability of the manager system without requiring code changes on one or more subsystem controllers. For example, multiple configuration and / or transfer programs could be easily uploaded, adapted, and / or adjusted by a technician and / or operator to change the configuration and behavior of the device. This approach would greatly simplify the management and organization of coordinates, parameters, and other variables associated with the execution of specific subroutines of a transfer (e.g., a turn operation and a transfer operation).

[0101] Now turn to FIG. 3A to FIG. 3B , an example of a distributed control system 100 according to various specific implementations will be described. The distributed control system 100 can be implemented in any suitable transfer device, such as FIG. 2A to FIG. 2C An example of a transfer device 200 is shown. It should be understood that FIG. 3A to FIG. 3B The examples of the distributed control system 100 are exemplary implementations and are not intended to be limiting. Other variations of the distributed control system are possible and within the scope of the present disclosure.

[0102] In these and other implementations, the distributed control system 100 has a system processor 110 coupled to a plurality of subsystem controllers 120. The subsystem controllers 120 are configured to implement various functions of the transfer device, as described in further detail below. In various implementations, the system processor 110 is configured to monitor and communicate with all of the subsystem controllers 120.

[0103] like Figure 3A As shown, in some cases, the system processor 110 communicates with multiple subsystem controllers 120. In various cases, the system processor 110 can be implemented by a variety of hardware, software and / or firmware. In some cases, the system processor 110 is configured with instructions for performing one or more activities and may also be referred to as a manager system as previously indicated. The subsystem controller 120 may be implemented by a variety of computing devices (e.g., one or more processors, controllers, and / or memory devices with instructions for configuring the processors or controllers) that meet the requirements of the various functions of the transfer device and are further described elsewhere herein. As previously indicated, the system processor 110 may communicate with a variety of subsystem controllers 120 depending on the specific implementation. An example of hardware utilized for the duties of the subsystem controller may be a microprocessor or microcontroller having a reduced instruction set computer (RISC) architecture. Depending on the requirements, the computer may have various processing capabilities and have a commonly used data bus configuration, such as an 8-bit to 64-bit architecture.

[0104] Figure 3AOne possible example is shown in which the control dispensing system 100 includes a system processor 110 and seven subsystem controllers 120 that interface with and control one or more operating subsystems of the transfer device. It should be understood that although this example shows seven specific subsystem controllers 120, a specific implementation of the control dispensing system 100 may have fewer than seven or more than seven subsystem controllers 120. In addition, a specific implementation may include Figure 3A Some, all, or none of the specific examples shown in .

[0105] In some implementations, one of the subsystem controllers 120 is a transfer controller 321. In various cases, the transfer controller 321 is responsible for controlling all of the subsystems 340 that directly perform the transfer of an object or patient. For example, the transfer controller 321 can control the movement of the transfer platform and any conveyor belts through external sensors and motors. In various cases, user input is received by the HMI 320 and transmitted to the system processor 110. The system processor 110 (e.g., a manager system) then passes the user commands to the transfer controller 321. In some implementations, the system processor 110 determines the optimal parameters for the transfer function without specific user input, and passes specific movements and state changes of the transfer platform and transfer belts to the transfer controller 321. The transfer controller 321 then controls one or more transfer subsystems 340 to cause the movements and state changes.

[0106] As noted above, in various cases, user input is received by the HMI 320. As will be discussed in further detail, in various implementations, the HMI 320 may also display information to a user or operator using one or more displays or other output devices. In some implementations, the transfer device 200 may have one, two, or more separate HMI devices. As an example, Figure 3A The control system 100 is shown to include both a front-end HMI 320a and a back-end HMI 320b, with reference to the physical locations of the HMI devices 320a, 320b located in front of and behind the transfer device 200, respectively. As another example, Figure 3B A control system 100 is shown including both a front-end HMI 320a and a back-end HMI 320b and another HMI 320 integrated within a computing device 300 having a system processor 110. For convenience, references herein to HMI 320 also apply to front-end HMI 320a and back-end HMI 320b unless otherwise specified or understood.

[0107] Although not required, in various circumstances, one or more HMIs 320 may operate as a subsystem and / or subsystem controller. Figure 3A, each HMI 320 a , 320 b is shown as including a subsystem controller 120 . Figure 3B The example in shows that in some cases, each HMI 320, 320a, and 320b operates as a separate subsystem controller 120. In some cases, a single subsystem controller may control two or more HMIs (e.g., HMI 320a, 320b). As another example, in some cases, the system processor 110 or another subsystem controller may control one or more of the HMIs 320. Other configurations are also possible depending on the specific implementation.

[0108] Continue to refer Figure 3A In some implementations, one of the subsystem controllers 120 is a lift and tilt controller 322 that interfaces with and controls one or more lift / tilt subsystems 341. In various implementations, the lift and tilt controller 322 allows a user to adjust the height and angle of the transfer platform. In various cases, the user input is received by the HMI 320 and passed to the lift and tilt controller 322. In some implementations, the system processor 110 determines the optimal height and angle of the transfer platform independent of the user input and passes the height and angle to the lift and tilt controller 322. The lift and tilt controller 322 then controls various actuators and sensors within one or more subsystems 341 to make the desired height and angle adjustments.

[0109] In some implementations, one of the subsystem controllers 120 is a transport controller 323. In various implementations, the transport controller 323 allows a user to drive the transfer device 200 from one location or room to another using one or more transport subsystems 342, including a driven wheel or wheels that accept inputs for acceleration, steering, and braking. In various cases, the user input is received by the HMI 320 and passed to the transport controller 323 by the manager system (e.g., the system processor 110). In some implementations, the system processor 110 determines the best path to transport the transfer device or intervenes on behalf of the user to maintain safety or automate the transportation of the transfer device through direct communication with the transport controller 323.

[0110] Continue to refer Figure 3A In some implementations, one of the subsystem controllers 120 is a peripheral device controller 324. According to some implementations, the peripheral device controller 324 interfaces with and controls one or more peripheral subsystems 343, which include various sensors and / or actuators for controlling peripheral devices that are not involved in the actual movement of the transfer device for patient transfer.

[0111] In some implementations, one of the subsystem controllers 120 is a power system controller 325, which in some cases controls the delivery of power to all electronic components of the distributed control system 100 and to the actuators of the transfer device 200. In addition, in various cases, the power system controller 325 communicates with and provides power to the other subsystem controllers 120 and the system processor 110 and in some cases the imaging subsystem 333. In some implementations, it may also provide power to an Internet of Things (IOT) gateway 331. It should be understood that although this example involves an IOT gateway 331, the external connection of the distributed control system 100 may also be another form of networking device, such as, for example, an intranet, a wireless access point, or a cellular modem.

[0112] In some implementations, the distributed control system 100 implements a controller area network bus (CAN bus) network to allow one or more of the subsystem controllers 120 within the distributed control system 100 to communicate with each other without a host computer or complex dedicated wiring. This makes it possible for the subsystem controllers 120 to communicate directly with each other without the involvement of the system processor 110. That being said, in various implementations, the system processor 110 may act as a link or intermediary between the subsystem controllers 120. It should be understood that although a CAN bus network is shown in this example, any communication network that is feasible for distributed computing can be utilized. Examples of possible communication networks include, but are not limited to, Recommended Standard 232 (RS232), Serial Peripheral Interface (SPI), and Transmission Control Protocol (TCP). It should also be understood that multiple parallel or sequential communication networks can be implemented by the subsystem controller 120. The subsystem controller may also have a communication network implemented internally that does not communicate with the system processor 110.

[0113] According to various implementations, the system processor 110, the transfer controller 322, the transport controller 323, the peripheral device controller 324, and the power system controller 325 operate together to implement basic operations and additional functionality of the transfer device 200. In some cases, the basic operations may, for example, include height adjustment (e.g., lift / lower), angle adjustment (e.g., left upper / left lower tilt, right upper / right lower tilt, front upper / front lower tilt), pick up from the left, pick up from the right, drop down to the left, and drop down to the right. In some cases, the additional functionality may include various features in addition to the basic operations. Further details of the system processor 110, the lift and tilt controller 322, the transport controller 323, the peripheral device controller 324, and the power system controller 325 are provided below.

[0114] As noted above, in some implementations, the HMI 320 includes an output device that provides feedback to the user. Such feedback may include the status of the transfer device, thus allowing the user to monitor the operation of the transfer device. Although the output device typically includes a display screen, it should be noted that it may additionally or alternatively include other types of output devices. Examples include, but are not limited to, an audio speaker device for communicating status by voice. FIG. 4A to FIG. 4I Further details are provided regarding user interface controls for HMI 320 according to various implementations.

[0115] In some specific implementations, user input is received by HMI 320 and is passed to transfer controller 321 from system processor 110 to determine the direction of the transfer platform and how the conveyor belt extends for picking up and putting down. The relationship between the transfer platform and the conveyor belt determines how the patient moves. In some transfer operations, this relationship can be configured so that the patient has zero speed relative to the speed of the conveyor belt during picking up and putting down. Ensure that this kinematic relationship between the conveyor belt and the patient minimizes the risk of any shear movement of the conveyor belt to the patient's clothing or skin. Especially when the transfer platform is extending to reach below the patient, and when it is retracting so as to put down, this configuration can improve the patient's comfort and overall experience. In some specific implementations, the transfer device is bidirectional, which means that the transfer controller 321 can guide the transfer platform to perform transfer operations on the left and right sides of the transfer device or move away from the transfer device.

[0116] As noted above, in some specific implementations, the transfer controller 321 controls the movement of the transfer platform and any conveyor belt by sensors and motors. In some specific implementations, this includes an encoder for sensing motor speed, a linear displacement sensor for measuring conveyor belt tension, and a positioning sensor for determining the position of the transfer platform. In some specific implementations, the transfer controller 321 is pre-programmed with a monitored predetermined limit or safety threshold about a transfer parameter. For example, on a transfer device 200 with an open-end conveyor belt, the transfer controller 321 can know the length of the conveyor belt required for a single transfer, and the transfer platform and conveyor belt can be offset and automatically reset to a default position, so as to prepare for subsequent or continuous transfer. In some specific implementations, the transfer controller 321 receives a reading from a device positioning sensor to determine whether the transfer platform is in situ, extended or dislocated.

[0117] In some implementations, the transfer controller 321 is configured to include several automated features that can improve the overall performance of the transfer device. For example, the transfer controller 321 can be configured to automatically send requests directly to other subsystem controllers (such as the lift and tilt controller 322 and the transport controller 323) to directly request to adjust the global positioning of the transfer device (e.g., vertical height, tilt angle, and position in the room) based on the patient's support surface (e.g., bed, stretcher) and the patient's position to ensure correct positioning before starting the transfer sequence. In some cases, the transfer controller 321 can use measurements taken from load sensors by other subsystem controllers 120 to sense the appropriate force / interaction between the support surface and the transfer platform, thereby enabling the transfer controller 321 to determine the global positioning. In some implementations, these automated features are included in the system processor 110 instead of the transfer controller 321.

[0118] In some implementations, the transfer controller 321 can automatically tune device parameters and / or limits (e.g., platform speed, conveyor speed) based on patient size (e.g., height and weight). Implementing sensor fusion to combine all relevant data (patient size, patient position) can enable parameters and / or limits to be appropriately determined for each patient. This can enable the transfer device to transfer anyone, regardless of their size and weight. Figure 5A and Figure 5B Further details are provided on how the transfer controller 321 autonomously tunes and configures device parameters and / or limits.

[0119] In some implementations, to ensure patient safety during the transfer process, the transfer controller 321 implements an error handling system that can automatically abort and stop any unsafe actions. In some implementations, the transfer controller 321 also facilitates device assistance services, whereby the transfer controller 321 automatically repositions the transfer device or a subsystem of the transfer device to allow a technician or other person to easily access the transfer device or a subsystem of the transfer device.

[0120] As noted above, the lift and tilt controller 322 allows the user to adjust the height and angle of the transfer platform. In some implementations, the adjustable angles include a tilt angle that enables the transfer platform to tilt laterally, such that the left and right sides can tilt up and down, for example, + / -5 degrees, and a Trendelenburg angle that enables the transfer platform to tilt longitudinally, such that the head and foot ends can tilt up and down, for example, + / -10 degrees. In various implementations, the height, tilt angle, and Trendelenburg angle can be changed at any point during the transfer. These changes can be automatically initiated by the lift and tilt controller 322, another subsystem controller 120, or requested by the system processor 110.

[0121] In some implementations, the lift and tilt controller 322 utilizes limit switches and feedback from Hall effect sensors to drive the four linear actuators. If the current sensing software limit is exceeded, the lift and tilt controller may decide to disable the linear actuators and halt the transfer operation. In some implementations, thresholds for the maximum tilt angle and the maximum Trendelenburg angle are also defined within the lift and tilt controller 322 to prevent excessive tilting of the transfer platform, which may be unsafe for the patient.

[0122] In some implementations, as noted above, the transport controller 323 controls the transport of the transfer device. In some implementations, the transport controller 323 implements a propulsion system that controls motors that move the transfer device, thereby enabling assisted transport of the transfer device based on gestures or input commands from a user through the HMI 320. In some implementations, the transport controller 323 can be equipped with additional sensors and data inputs to enable automated transport of the transfer device 200. In such implementations, those familiar with automated vehicle navigation will appreciate that additional controllers can be integrated to enable technologies such as, for example, simultaneous positioning and mapping or GPS (Global Positioning System).

[0123] As noted above, the peripheral device controller 324 interfaces with one or more peripheral subsystems that include various sensors for detecting and controlling matters that are not involved in the actual movement of the transfer device for patient transfer. In some implementations, the peripheral device controller 324 communicates with sensors for detecting patient size and position. In some implementations, sensors within the lift / tilt subsystem 341 within the transfer device are capable of measuring the patient's weight, and distance sensors within the peripheral subsystem 343 (such as time-of-flight, infrared, or ultrasonic sensors) are mounted on the transfer device for monitoring patient positioning during transfer by measuring the distance between the sensor and the patient. In some implementations, the peripheral device controller 324 may provide the acquired data directly to the transfer controller 321 so that the transfer controller 321 can customize and determine device parameters and / or limitations for each patient. It should be understood that this is an example of such an implementation, but the configuration of the subsystem controller 120 and the system processor 110 is intended to be adaptable so that individual sensory inputs can be positioned throughout the transfer device in such a way as to optimize and achieve the most advantageous overall configuration. Reference Figure 5A and Figure 5B Further details are provided on how the transfer controller 321 automatically tunes device parameters and / or limits.

[0124] In some implementations, the peripheral device controller 324 provides safety features to the distributed control system 100 (e.g., alone or in combination with the peripheral subsystem 343) to ensure patient and user safety. These safety features may include one or more of guardrail sensing, support surface proximity sensing, wheel lock sensing, patient position sensing on the platform, and service coverage intrusion detection. According to various implementations, the guardrail sensing system detects the position of the guardrail. If the guardrail is up, the sensor is turned on, and if the guardrail is lowered, the sensor is turned off. In various cases, the state of the sensor is communicated to the rest of the distributed control system 100. In various implementations, if the sensor is off, transfer is not allowed because this means that the patient side guardrail is lowered.

[0125] According to various implementations, the sensor for support surface proximity sensing detects the presence of a patient support surface, such as a bed, and measures the distance between the device and the support surface to ensure that the device is sufficiently close to the support surface. If the support surface is not detected or the device is too far from the support surface, the peripheral device controller 324 will not allow the transfer device 200 to perform any patient transfer movement for patient safety.

[0126] In some implementations, the peripheral device controller 324 implements a wheel lock system to detect whether the wheels of the transfer device are locked or unlocked, and if the wheels are not locked, the transfer will not be allowed.

[0127] In some implementations, the peripheral device controller 324 interfaces with sensors in one or more peripheral subsystems 343 for detecting the position and orientation of the patient when positioned above the body of the transport device. The sensors can detect whether the patient is obstructing the bed rails and whether the patient is fully supported by the body of the device. The peripheral device controller 324 communicates this sensor information to the system processor 110, which can inform the user to take corrective action via the HMI 320, or to the transfer controller 321 to automatically adjust the patient's position within the body of the device.

[0128] In some implementations, the peripheral device controller 324 interfaces with sensors in one or more peripheral subsystems 343 for detecting service coverage intrusions, such as if someone were to open a panel or cover on a transfer device. This detection can be communicated to the power system controller 325 in various circumstances so that the power system controller 325 can shut off high power to the actuators of the transfer device. In such circumstances, normal applications can be disabled and the transfer device can be repaired.

[0129] As noted above, the power system controller 325 controls the delivery of power to the electronic components of the distributed control system 100 and to the actuators of the transfer device. In some implementations, the power system controller 325 controls the delivery of power to the actuators of the transfer device through a contactor switch that is configured to power on and off the motor drive. In some implementations, the power system controller 325 operably controls an electronic circuit board that has individually selectable and switchable power outputs for delivering energy (e.g., 12V) to one or more of the subsystem controllers 120. In some implementations, the power system controller 325 has sufficient power connections to monitor all voltages and currents on the power rails in the transfer device, although in some cases it may monitor less than all power levels. In some cases, the sensor may additionally monitor the total current in the transfer device.

[0130] In some implementations, the power system controller 325 is coupled to one or more power subsystems 325a, which in some cases include a battery management system (BMS) that monitors and interacts with the batteries to gain insight into the battery status and health, such as charge level and any errors or problems. In some cases, the power system controller 325 can determine from the BMS when the battery needs to be charged, and thereafter de-energize the transfer device 200 so that the battery can be charged.

[0131] In some implementations, there are fans located within the transfer device 200 for cooling purposes, and the power system controller 325 controls activation of the fans. If the temperature within the transfer device 200 becomes too hot, the power system controller 325 will power on the fans to prevent overheating.

[0132] In some implementations, the transfer device 200 has two emergency stop (E-Stop) buttons, one at each end of the transfer device 200. In various situations, the E-Stop button can be pressed to immediately stop all actions. In some implementations, the power system controller 325 has an energy dump system that monitors the E-Stop status and ensures that the transfer device stops immediately when either E-Stop button is pressed.

[0133] In some implementations, the transfer device 200 additionally has a wired or wireless remote control. The remote control (sometimes referred to as a control pendant) enables the user to leave the device body and get closer to the subject (e.g., patient) for monitoring and observation purposes during the transfer process. In such implementations, the remote control may also have an emergency stop button.

[0134] In some implementations, the power system controller 325 ensures that the transfer device 200 stops immediately upon other various triggers. For example, upon a service coverage violation, the power system controller 325 can stop the transfer device. The service coverage violation can be detected by sensors in one or more peripheral subsystems 343, and the peripheral device controller 324 can signal the power system controller 325 with an indication of the service coverage violation.

[0135] In some implementations, the power system controller 325 has a notification or alarm system to communicate messages and status reports to the operator. An example of such a system is an audio alarm system, such as a buzzer, which provides an audio output to alert the user of any errors or possible safety hazards. It is readily understood that various alarm systems can be utilized, such as tactile alarms through the handle of the transfer device 200, indicator lights or LED bars, or audible sound alarms generated by the subsystem controller.

[0136] In some implementations, HMI 320 can include a display screen and / or other output devices for conveying information, as well as buttons and / or other input devices for receiving user input that can be forwarded to and processed by system processor 110 .

[0137] Continue to refer Figure 3A In some implementations, the control system 100 of the transfer device 200 is connected to a communication network (e.g., internal, local, external, etc.) to provide access to various types of data. As an example, in some cases, the distributed control system 100 is connected to the cloud network 332 via the IoT gateway 331. In such cases, developers can receive diagnostics about the performance of the transfer device, the real-time status of the transfer device, and can upload firmware changes to the transfer device. In some cases, users can receive data about the status of the transfer, the number of transfers completed, patient information (such as, for example, weight and location), and various other types of data.

[0138] like Figure 3AAs shown, in some specific implementations, the distributed control system 100 is docked with at least one imaging device or system 333. According to various specific implementations, the imaging device or system 333 can be considered as a device subsystem of the transfer device 100 without its own imaging subsystem controller. In such cases, the system processor 110 and / or one or more other subsystem controllers can communicate with the imaging device 333. In some cases, the imaging device or system 333 is considered to be an operating device subsystem including an imaging subsystem controller. In such cases, the imaging subsystem controller can communicate with the imaging subsystem, and the system processor 110 can communicate with the imaging subsystem controller and / or the imaging subsystem itself. By incorporating imaging into the transfer device, it is possible to allow more precise and accurate patient positioning and further patient monitoring. In some cases, the imaging device 333 can improve the patient support surface proximity sensing capability of the transfer device, preventing or mitigating the gap between the support surface and the transfer platform of the transfer device during the transfer operation. According to various specific implementations, the imaging device 333 may include a radar device, a sonar or ultrasound device and / or a camera (standard / stereo / depth) device. Combinations of imaging devices are also possible, including different types of imaging devices. For example, the distributed control system 100 can interface with both a radar device and a camera. In some implementations, the system processor 110 learns how to use the following reference Figure 5D The described images are processed to estimate the mass and / or volume of a patient.

[0139] Figure 3B In many ways Figure 3A A block diagram of a distributed control system 100 similar to the control system 100 described above. Unless otherwise indicated, Figure 3A The description of various aspects of the control system 100 in Figure 3B The control system 100 in FIG. Figure 3B As shown, in various implementations, the system processor 110 incorporates HMI 320 functionality that allows a user to interact with the transfer device 200. In such implementations, the system processor 110 may be incorporated as part of the computer 300 to take on the additional functionality. It should be understood that while the HMI 320 functionality is depicted as being bundled with the system processor 110 in this implementation, other subsystem controllers 120 may also be incorporated into the system processor 110 in a similar manner.

[0140] Reference now FIG. 4A to FIG. 4I , which illustrates a diagram of example user interface controls for the HMI 320 of the transfer device 200 according to various implementations. Figure 4AAn example location 402 of user interface controls on one end of the transfer device 200 is shown. Note that in some implementations, the other end of the transfer device 200 can have the same user interface controls. Figure 4B A close-up view of an example location 402 of an example component including a user interface control is shown. Figure 4B As shown, in various implementations, the user interface controls include a handheld controller 410 having a cable 420, a first keyboard 430, a second keyboard 440, and a display screen 450. Although the handheld controller 410 is wired using the cable 420, in other implementations, the handheld controller 410 is wireless, in which case the cable 420 may be omitted. Please note that the depicted components and their locations on the transfer device 200 are for illustration and are provided for exemplary purposes only. Other implementations are also possible.

[0141] FIG. 4C to FIG. 4E Details of a handheld controller 410 are shown according to various implementations. The handheld controller 410 has a membrane 411 for receiving user input, an emergency stop button 412 for immediately stopping all action, an indicator light 413 for providing user feedback, and a cable gland 414 for wired implementations. Figure 4F Details of the first keypad 430 are shown, including an up button 431 for raising the transfer device 200, a down button 432 for lowering the transfer device 200, a left tilt button 433 for tilting the transfer device 200 to the left, and a right tilt button 434 for tilting the transfer device 200 to the right. Figure 4G Details of a second keyboard 440 are shown, including four buttons 441 to 444 for selecting a depicted patient transfer, a work button 445 for continuing an already selected transfer, and a pause button 446 for pausing a transfer. Other user interface controls are possible in addition to or in lieu of the user interface controls shown in the figures.

[0142] Figure 4H and Fig. 4I Details of an HMI tablet 460 for use with the transportation device 200 are shown according to various implementations. Figure 4H A possible implementation of an HMI tablet computer 460 is shown, which can be removably mounted between the first keyboard 430 and the second keyboard 440 of the transfer device 200, replacing Figure 4A and Figure 4B Display screen 450 shown in the example shown in . Fig. 4I The HMI tablet 460 is shown mounted proximate a corner of the transfer device 200 according to various implementations. Of course, other locations and ways of mounting the HMI tablet 460 are possible in various implementations.

[0143] In some cases, incorporating some or all of the functionality of the HMI 320 into the HMI tablet 460 gives the operator increased mobility when operating the transfer device 200 without compromising the functionality of the HMI 320, for example by improving ease of use, compared to conventional hand-held designs. In some cases, the touch screen component of the HMI tablet 460 can be used when mounted to the transfer device 200 and when removed from the transfer device 200, at which point it can be used like a tablet. When mounted to the device, the HMI tablet 460 can also be plugged into its communication and power ports. In some cases, the HMI tablet can automatically charge its battery after being mounted, and can communicate with the device using physical wires. When the HMI tablet 460 is not plugged into or mounted to the device, the HMI tablet 460 relies on battery power and communicates with the transfer device 200 via a wireless communication connection (e.g., a Bluetooth connection).

[0144] According to various implementations, when the HMI is removed from the transfer device 200 and in "tablet mode," the operator will be able to change the orientation of the HMI screen for ease of use. In some cases, a hand strap may be attached to the back of the HMI for safety and to allow for a more secure grip. In some cases, the HMI tablet 460 may be used with an extension cord if the charge is insufficient, but the operator still wishes to utilize the tablet mode option. In such cases, the power and communication modes may be substantially the same as when the HMI tablet 460 is installed and inserted into the transfer device 200. In some cases, the accessibility and location of the HMI 320 on one or more sides (e.g., the front and back) of the transfer device 200 will still be applicable to the specific implementation of the HMI tablet 460.

[0145] According to various implementations, the HMI tablet 460 may also implement “find my tablet” functionality. For example, in some cases, the transfer device 200 includes a button located in the mounting area of ​​the lost HMI that can be pressed if the HMI tablet 460 is misplaced, which can send a command to the HMI tablet 460 that will cause the device to, for example, beep and flash lights to assist in locating the HMI tablet 460.

[0146] FIG. 5A to FIG. 5F2 is a flow chart illustrating various migration apparatus 200 routines according to various implementations. In various cases, a manager system (e.g., a system processor 110 configured with appropriate instructions) and / or one or more subsystem controllers 120 perform a routine or method, sometimes in conjunction with various user inputs and / or other conditions. According to various implementations, the migration routine may be enhanced for functionality, safety, or ease of use by adding additional subroutines that may run sequentially or in parallel with the migration operation. FIG. 5A to FIG. 5F Also included are examples of how these transfer routines can be improved and enhanced by adding electronic imaging to distributed control systems.

[0147] Figure 5A 5 is a flow chart of a method 500A for coordinating the transfer of an object (e.g., a patient) according to various implementations. At step 501, the manager system receives and processes information from the HMI 320 regarding user input regarding transfer parameters and initiates the transfer process accordingly. At step 502, the manager system signals the transfer controller 321 to extend the device platform toward the object.

[0148] While the device platform is extending toward the object, a parallel transfer performance activity 503 may be performed. For example, in some cases, the manager system may coordinate multiple subsystem controllers 120 to detect the supporting surface under the object in order to efficiently complete the transfer. Examples of such surface detection methods are further described in Figure 8B Another possible parallel activity involves the transfer controller 321 executing a method for detecting material obstructions as it extends the device platform. Examples of such material obstruction detection methods are further described in Fig.8D Another possible parallel transfer performance activity 503 is to coordinate multiple subsystem controllers 120 to optimize transfer efficiency 5031, such as coordinating transfer controller 321, lift and tilt controller 322, and peripheral device controller 324 to optimize the speed and path of the platform under the object. In various implementations, the manager system monitors the parallel transfer performance activity 503 and modifies the transfer behavior accordingly.

[0149] After the device platform 504 is extended below the object, the manager system coordinates with the HMI 320 to request confirmation from the user to proceed to the next transfer step, such as Transfer On in step 505. If confirmation is received at step 505, the manager system signals 506 the transfer controller 321 to move the object toward the device. Parallel activity step 503 is initiated again in parallel with step 506. According to various implementations, the manager system coordinates multiple subsystem controllers 120 to perform the method 506 of centering the object above the device base to prevent unsafe and uncomfortable conditions. Examples of such methods are further described in Fig. 8E .

[0150] At step 507, the manager system waits for the HMI 320 to communicate a user intent to move an object (e.g., a patient) away from the device. Upon receiving user input regarding the transfer parameters, the manager system sends a signal to the transfer controller 321 to move the object toward a subsequent support surface, which may be different or the same as the support surface to which the object was initially moved. When the transfer controller 321 moves the object onto the support surface, step 503 is performed again.

[0151] When the transfer controller 321 completes moving the object onto the support surface, the manager system waits for the HMI 320 to communicate user confirmation to complete the final step of the transfer process, which is described as retracting in step 509. When the confirmation is received, the manager system signals 510 the transfer controller 321 to retract the device platform from under the object and move the platform back to the center of the device. The parallel transfer activity 503 is performed again as the transfer controller 321 moves the platform toward the device. During this process, the manager system can initiate methods such as obstacle detection 800D to monitor for any displacement or position issues caused by obstacles that appear between the support surface and the device. When the platform returns to the center of the device, at step 511, the transfer is complete.

[0152] Figure 5B is a flow chart of a method 500B for coordinating the transfer of an object (e.g., a patient) using image processing according to various implementations. The transfer method 500B includes Figure 5A The transfer method 500A shown in FIG. Figure 5A The description of the transfer method 500B also applies to the various steps in the transfer method 500B. As with the transfer method 500A, the transfer method 500B begins with the user initiating a request for a transfer start operation 501. The manager system may also initiate a parallel performance activity 503 as previously described.

[0153] At the same time, the system processor 100 and / or the subsystem controller 120 are configured to initiate 512 the capture of an image of the object transfer. The term "image" is used herein to refer to a representation of an object, a support surface, and / or other environment external to the transfer device 200 sensed or otherwise acquired by the transfer device 200. Additionally, unless otherwise indicated, the terms "image," "image capture," "image data," and "imaging" are used herein to refer to both a static image and a series of continuous images forming a video.

[0154] It should be understood that image capture may encompass the collection of many forms of electromagnetic radiation, such as, but not limited to, the visible spectrum, infrared, and X-rays. In some cases, image capture may involve detecting sound waves, such as using sonar or ultrasound. Transfer device 200 may be configured with one or more techniques for capturing images. FIG. 3A to FIG. 3B As described, in various cases, the transfer device may include an imaging device 333, such as, for example, a radar device, a sonar or ultrasound device, and / or a camera (standard / stereo / depth) device. Combinations of two or more imaging devices are also possible, including different types of imaging devices. Examples of locations for image capture may include the device platform, the support surface, the surrounding environment of the device (i.e., the room), and the object (e.g., the patient).

[0155] After initiating 512 image capture, multiple parallel processes 513 may be performed based on the acquired images. In various implementations, adding image-based analysis may improve the safety and effectiveness of the transfer process. FIG. 5C to FIG. 5F Some examples of possible parallel processes 500C, 500D, 500E, and 500F are described. For example, Figure 5D and Figure 5E A method of analyzing captured images to generate additional information that assists other routines is presented. As an example, image analysis can be used to improve the accuracy of the extension device platform 502, such as in Fig. 8A 800A for aligning a transfer device. According to various implementations, image capture 512 may also be initiated in parallel during all other transfer steps. As another example, in some cases, analyzing the captured image (e.g., based on FIG. 5C to FIG. 5F ) may provide additional data for centering the object 506 as well as monitoring the new transfer area, detecting obstacles, and preventing unsafe conditions during the transfer operation.

[0156] Figure 5C FIG. 5 is a flow chart of a method 500C for performing image processing to determine at least one variable associated with the transfer of an object according to various implementations. The image processing method 500C may be performed by a manager system implemented by the system processor 110 of the distributed control system 100 shown in FIG. 3 . In various implementations, the manager system includes a machine learning algorithm to determine at least one variable. According to various implementations, Figure 5C Method 500C may be executed by any processor of transfer device 200 , including a processor that may not be part of distributed control system 100 .

[0157] like Figure 5B As shown, method 500C begins after image capture 512. A processor executing the method receives one or more captured images from at least one imaging device. As an example, the processor may receive a sequence of images forming a video feed. Figure 5C At step 532, the processor determines at least one variable using image processing of the captured image, such that the at least one variable is related to transfer of the object by the transfer device.

[0158] There are many possibilities for the at least one variable. In some implementations, the at least one variable includes the mass and / or volume of the object. In some implementations, the at least one variable includes the position and / or orientation of the object. In some implementations, the at least one variable includes the topography of the support surface, such as the size of the support surface, the smoothness of the support surface, or the orientation and slope of the support surface.

[0159] In some implementations, the processor assesses the risk of damage to the object based on at least one variable that has been determined. For example, the processor may determine that there is a risk of harm to the patient due to the patient's position or orientation (e.g., the patient is facing down), and therefore the patent transfer may be delayed or stopped. In other control algorithm implementations, the risk of damage to the object may be based on the probability of accidental collision or excessive force of the transfer device with the object being transferred. For example, by using a depth camera, the imaging system can predict the platform extension distance before the platform may interact with the patient, and adjust its extension path accordingly in terms of travel and height. Reference will be made to the following. Figure 5E An example of such a process is described in more detail.

[0160] In some implementations, the captured image (e.g., video feed) can be overlaid with desired assistance to the operator. Such assistance can include alignment assistance when driving the transfer device 200 during transport, alignment of the transfer device with a support surface, or alignment relative to an object being transferred. Examples of such overlaid positioning are depicted in Figure 6 .

[0161] In some implementations, a processor (e.g., a manager system, a subsystem controller, or another processor) records captured images (e.g., a video feed) for later playback. In some implementations, the processor establishes an external data connection and sends the images via the external data connection to an external receiving unit for monitoring and viewing (e.g., by a remote operator or user, or for analysis by a remote computer system).

[0162] According to various specific implementations, an imaging device 333 as a digital camera-based method (e.g., CMOS, CCD, infrared, depth camera) or a combination of digital cameras can be used to monitor and / or supervise the transfer of a patient (or other object). For safety purposes, the camera 333 can determine whether the patient is in a dangerous position (e.g., face down) and should not be transferred by the transfer device 200. During the process of the transfer, the camera 333 can monitor whether the patient becomes agitated, or whether the patient begins to move or roll to an unsafe position. In such cases, the manager system can intervene to take appropriate actions, such as stopping the transfer. If the captured image (e.g., video stream) is recorded during the transfer process, the method can also be used to serve as a data record for employee monitoring or insurance audit purposes. For example, if an accident occurs (e.g., a patient falls or is injured), the camera footage can be replayed as evidence of what happened during the incident.

[0163] In some implementations, the processor determines parameters and / or limits for transferring an object by the transfer device 200 based on the at least one variable that has been determined. For example, the processor may determine the parameters and / or limits based on the mass and / or volume of the object. In some implementations, the processor receives feedback about the force measured during the transfer of the object and adjusts the parameters and / or limits based on the feedback. Figure 5D Examples of such methods are described in more detail.

[0164] Figure 5D 5 is a flow chart of a method 500D for estimating mass and / or volume using image processing. The method may be executed by a processor, for example, by FIG. 3A to FIG. 3B In a particular implementation, the manager system executed by the system processor 110 includes a machine learning algorithm to predict quality and / or volume. More generally, Figure 5D The method may be performed by any processor of the transfer device, including a processor that may not be part of a distributed control system.

[0165] In various implementations, before the transfer sequence begins, the processor combines data obtained from sensors and cameras within the various subsystems of the transfer device 200 to estimate the mass and / or volume of the patient. After the user initiates the transfer request 501, image capture is initiated 512, and the processor performs a camera and distance sensor pre-assessment. For example, such a pre-assessment may include measuring the distance to the edge of the support surface or the first interaction with the patient. At step 513-10, the processor performs an image-based estimate of the patient's volume and mass according to the configuration of the algorithm. For example, in various cases, the processor estimates the weight of the object based on the count of object pixels and the object density.

[0166] In the example of transferring a patient, the density of a person is well defined. Therefore, in various cases, the processor counts the number of pixels that constitute the patient in the image and then determines the patient's body size in pixels. The processor is configured to estimate the patient's volume based on the pixel count and calculate the patient's estimated mass based on the patient's estimated volume and density. In some cases, the processor is configured to first convert the patient's body size in pixels into real-world dimensions (e.g., pixels per millimeter), then estimate the volume and / or subsequently calculate the mass. Accordingly, the processor (e.g., a manager system) can estimate the patient's total mass and weight distribution, and as a result of the prediction, it can also predict the expected forces on the platform and which positions will be subject to these forces during the platform extension process. The manager system can also use the patient's mass and weight distribution in combination with the supporting surface characteristics to predict the upward force on the platform. Such estimates are used to determine the transfer parameters and / or limitations of the transfer sequence.

[0167] During the transfer sequence, at step 513-11, the processor acquires data corresponding to the forces acting on the device platform and / or the device body downward (e.g., from the patient), upward (e.g., from the support surface), or in another direction from a data acquisition (DAQ) system, as well as the device platform extension distance, which will correspond to the volume and / or mass of the patient applying forces to the platform during various stages of the transfer process. The data from the DAQ system may, for example, include sensor data measured by the peripheral device controller 324 and / or the lift and tilt controller 322. At step 513-12, the processor analyzes the measured force data (e.g., from a force sensor attached to the platform structure or a load cell in the device base) to determine the force and extension for extending the platform under the patient based on the data from step 513-11. At step 513-13, the processor compares the force and extension distance from step 513-12 with the force and extension that would be expected based on the image-based estimate from step 513-10.

[0168] If the processor determines that the force and extension distance from step 513-12 are consistent with the expected force and extension distance within a defined tolerance (e.g., within + / - 5%), no changes are made to the configuration of the algorithm and the transfer sequence continues until it is completed. However, if the processor determines that the force and extension from step 513-12 are inconsistent with the expected force and extension within a defined tolerance, then at step 513-14, the processor adjusts the configuration of the algorithm and provides training data to the image weight estimation routine. This enables the transfer parameters and / or limits of the transfer sequence to be adjusted in real time for the current transfer sequence. Additionally or alternatively, adjustments to the configuration of the algorithm can achieve improvements to subsequent transfer sequences. Adjustments to the configuration of the algorithm may include modifying the expected platform extension force, conveyor belt tension, modifying the preset platform transfer height (e.g., to require compression into the support surface) or angle, to name just a few examples.

[0169] By improving the configuration of the algorithm over time, the actuator of the transfer device 200 can only use sufficient force that may be appropriate given the size (e.g., volume and / or weight) of the object (e.g., patient) being transferred. This can avoid situations where too much force is used, resulting in a transfer that is too rough or even dangerous, and situations where too little force is used, resulting in the transfer being performed unsuccessfully. Thus, the predictive algorithm can help improve, for example, patient comfort and satisfaction because it adjusts the transfer parameters and / or limits for each patient. Additionally, it is also a safety feature because the algorithm can prevent excessive force from being applied to small patients.

[0170] Figure 5E is a flow chart of a method 500E for assessing metastasis risk using image processing according to various specific implementations. The method may be executed by a processor, for example, by FIG. 3A to FIG. 3B In a specific implementation, the manager system executed by the system processor 110 includes a machine learning algorithm to determine the transfer risk. More generally, Figure 5E The method may be performed by any processor of the transfer device, including a processor that may not be part of a distributed control system.

[0171] like Figure 5EAs shown, method 500E begins after image capture 512. In various cases, the pre-segmentation step 513-20 involves an image-based analysis of patient position, facial and limb detection, distance of first interaction of the extension platform, approach angle, and possible obstacles on the support surface. Facial recognition, edge and object detection, and geometric transposition are examples of some methods that can be used to perform the analysis described in step 513-20. After this analysis, a patient orientation analysis 513-21 is performed, which may include analyzing the rotation of their body and the direction of their face. To achieve this, those skilled in the art will recognize that there are a variety of image analysis algorithms that can identify key body anatomical structures (e.g., arms, elbows, heads, etc.) in order to identify the orientation of the transferred patient (commonly referred to as the "pose" of the person in the image). In the event that the patient orientation analysis detects a problem (e.g., the transfer process begins with the patient facing down), the transfer is stopped 514.

[0172] If no problem is detected at step 513-21, the processor executes a real-time risk determination algorithm 513-22. In some cases, real-time risk determination involves comparing patient orientation, platform interaction, and detected forces to the same parameters expected from image analysis. Examples may include comparing the patient's starting orientation to the orientation and changes thereto during the transfer using the image analysis methods described above. Other examples may include, but are not limited to, analyzing the rate of change of the patient's orientation, analyzing the patient's facial expressions in an effort to detect levels of pain or agitation, and analyzing potentially relevant behaviors, such as improper body mechanics (e.g., a joint being pushed inappropriately or bent incorrectly due to the transfer process).

[0173] According to various implementations, combining these kinds of patient orientation analyses with the force and extension algorithms discussed above can generate a more refined and accurate risk analysis. For example, the forces experienced by the transfer device DAQ system during the "limb" portion of platform extension (e.g., outstretched arm) should be lower than the patient midplane where peak forces should be seen. Using these analyses, a real-time transfer risk analysis 513-23 can then be generated based on a predetermined risk curve that is determined as a reference for comparison. Once a problem is detected (i.e., the risk is outside of predetermined limits), the transfer is stopped 514. In other cases, the transfer is allowed to continue, and the method includes continuing to determine real-time risk 513-22.

[0174] Fig. 5Fis a flow chart of a method 500F of relaying identified risks and other information to a user or operator of a transfer device 200. The method may be performed by various processors, including, for example, the system processor 110 of the distributed control system 100 shown in FIG3 in coordination with the HMI 320. According to various implementations, the method begins by capturing one or more images 512, and then transmitting 513-30 the images to the HMI 320 display. The method 500F further includes overlaying the transfer platform and displaying the identified risks on the HMI display 513-31.

[0175] Figure 6 is a perspective view of a transfer device 200 with an imaging system according to various implementations. The transfer device 200 includes an imaging device 333 located at one end of the transfer device 200. In some cases, the imaging device 333 may be a radar device, a sonar or ultrasound device, and / or a camera (standard / stereo / depth) device. Figure 6 In the example shown in , the imaging device 333 captures an image of an area 600 adjacent to the transfer device 200. In some implementations, the captured image is displayed on the HMI 320 display 450 and / or the HMI tablet 460 for viewing by a device operator. Figure 6 An example of a captured image showing an obstacle 602 on the display 450 is shown. In some cases, the image is superimposed on the display 450 with desired assistance to the operator. Such assistance may include alignment assistance when driving the transfer device 200 during transport, alignment of the transfer device with a support surface, or alignment relative to an object being transferred.

[0176] Figure 7 is a block diagram of a distributed control system 100 for a transfer device 200 according to various implementations. The distributed control system 100 may be implemented in any suitable transfer device, such as any of the examples of transfer devices 200 discussed herein. It should be understood that the distributed control system 100 illustrates one specific implementation and is provided for exemplary purposes only. Other implementations of the distributed control system 100 are possible and within the scope of the present disclosure.

[0177] like Figure 7As shown, the distributed control system 100 has a system processor 110 coupled to a plurality of subsystem controllers 120. As should be appreciated, each of the subsystem controllers 120 is configured to implement the functionality of the transfer device 200. At the same time, the system processor 110 is configured to monitor and communicate with the subsystem controllers 120. According to various specific implementations, the distributed control system 100 is configured to interact with an environment 731, an object / patient 732, a user or operator 733, and a cloud network 332, among others. In some cases, the distributed control system 100 also has a redundant system processor 110a in case the system processor 110 fails.

[0178] The functions implemented by the system processor 110 and the subsystem controllers 120 may vary between various specific implementations. In some cases, the distributed control system 100 may include a Figure 7 3. In various cases, one or more of the system controllers control and / or are part of one or more corresponding operating subsystems of the transfer device as discussed above. Figure 7 In the example shown, the system processor 110 communicates with and oversees a plurality of subsystem controllers, including, for example, device failsafe 721, device monitoring 722, imaging 333, subject interaction 724, human machine interface 320, patient diagnostics 726, and connectivity kit 727. Additional and / or alternative operating subsystems and corresponding subsystem controllers 120 are possible in various implementations.

[0179] FIG. 8A to FIG. 8E Several examples of possible routines and decisions that the manager system is configured to perform in various implementations are shown. Unless otherwise specified, references to one or more subsystem controllers 120 refer to the use of one or more of the subsystem controllers 120 described herein, including references to FIG. 3A to FIG. 3B The examples shown and discussed are among other possible subsystem controllers 120. As an example, in some cases, the manager system collects and / or receives information from various sensors via one or more subsystem controllers 120, which optionally include a peripheral device controller 324, a transfer controller 321, a lift and tilt controller 322, a transport controller 323, and / or a power system controller 325. As another example, in some cases, the manager system directs and / or coordinates with the subsystem controllers to move or stop moving a portion of the transfer device 200. Such subsystem controllers 120 may include, for example, a peripheral subsystem controller 324, a transfer controller 321, a lift and tilt controller 322, a transport controller 323, and / or a power system controller 325, as appropriate.

[0180] Fig. 8A 8 is a flow chart of a method 800A for aligning a transfer device 200 according to various implementations. According to various implementations, the method 800A includes subroutines or autonomous operations that a manager system may execute to align a transfer device 200 relative to a support surface (e.g., FIG. 2A to FIG. 2C aligning the transfer device 200 with the support surface 20, support surface 30) in the transfer device 200. In steps 801 and 802, respectively, the manager system collects information from the HMI 320 to receive the user request, and collects information from the subsystem controller 120 to analyze and determine the position and orientation of the support surface 804, and identify any obstacles or obstructions 803.

[0181] The manager system makes decisions 805 and 806 based on its analysis in steps 803 and 804, and may deny 807 the user's request to align the device or continue with the alignment subroutine 800A. When the manager system decides to continue with the alignment 800A, it calculates a trajectory 808 through the floor to align the device and the support surface on the X-axis and Y-axis parallel to the floor, and commands the subsystem controller to advance 809 the transfer device 200 accordingly. The manager system collects further information 810, 811 to identify obstructions 812, and makes a decision 813 to continue or abandon the alignment subroutine 800A. When the manager system decides to continue with the alignment 800A, it commands the subsystem controller 120 to adjust 815 the height and angle of the transfer platform 202 on the Z-axis perpendicular to the floor so that the transfer is possible. In some implementations, the manager system may further query 817 the user or operator to confirm the alignment.

[0182] Figure 8B 800B is a flow chart of a method 800B for detecting contact between a device transport platform and a support surface according to various specific implementations. The method 800B includes subroutines or autonomous operations executable by a manager system to detect 800B contact between a transfer device 200 and a support surface. The manager system coordinates the subsystem controller 120 to lower 821 the transfer platform and read data 822 from a plurality of force sensors. The manager system then calculates 823 a reaction torque for the transfer device 200. One possible method of calculating the reaction torque involves calculating the sign and magnitude of the acceleration of the force sensed on the two lateral halves of the device, where the reaction torque acts along the longitudinal centerline of the device.

[0183] At step 824, the manager system determines whether the reaction torque is greater than a specified threshold tuned for the mass, static load, and dynamic load of the transfer device. One possible method of determining whether the reaction torque meets the threshold involves confirming that the sign of the acceleration of the force acting on the half of the device closest to the patient is opposite to the sign of the acceleration of the force acting on the opposite half of the device. In some embodiments, an approximate threshold for the reaction torque of the transfer device that has contacted the surface is 150% to 300% of the typical reaction torque of the same transfer device raised or lowered in the open air. However, this value may vary depending on the mechanical configuration of the particular transfer device. Therefore, in various embodiments, by determining a specific trigger threshold corresponding to a specific transfer device, method 800B can be used for different device mechanical architectures.

[0184] According to various implementations, a determination that the threshold has not been met causes the manager system to return to reading data 822 and calculating 823 the reaction torque until the threshold is met, or otherwise aborting the method. When the manager system determines that the reaction torque is greater than the threshold, the manager system makes a further determination 825 that a support surface has been detected. In such cases, the entire transfer process then continues. In some cases, the transfer process continues at step 826 by subsequently determining one or more characteristics of the support surface. In some cases, the manager system may search for multiple reaction torques that subsequently change direction in order to detect multiple contact points that increase support.

[0185] Figure 8C is used to determine the support surface (e.g., FIG. 2A to FIG. 2CFlowchart of method 800C for determining characteristics of support surface 20, support surface 30 in a patient's body. Method 800C includes subroutines or autonomous operations executable by a manager system to determine characteristics 800C of a support surface. As an example, in some cases, the manager system may determine characteristics including the width and type of mattress (e.g., air mattress or foam mattress). Method 800C includes the manager system coordinating various subsystem controllers 120 to lower the device transfer platform onto the support surface at step 832. The manager system also collects information from various subsystem controllers 120, including collecting force sensor data 833 and vertical displacement 834. In some cases, the manager system calculates 835 spring constants based on the collected data, and then applies the spring constants to subsequent transfer calculations 836 to inform the force analysis that should be applied during the transfer process, the required displacement in order to achieve the desired compression set point, and determine the expected force and displacement curve depending on the support surface change. This can be very useful in situations where the support surface is undergoing a large change (e.g., air mattress vs. foam) between patient transfers. Overall, this process provides the advantage of optimizing workflow by adjusting the transfer algorithm and optimizing transfer efficiency as well as patient comfort without requiring user input of the support surface type.

[0186] Fig.8D 800D is a flow chart of a method 800D for detecting an obstacle according to various specific implementations. The method 800D includes a subroutine or autonomous operation executable by a manager system to detect 800D material obstacles during a transfer. According to various specific implementations, the manager system coordinates with the transfer subsystem controller 321 to match the displacement of the conveyor belt with the displacement of the transfer platform according to the kinematic requirements of each stage of the transfer process. As an example, in some cases, the transfer controller 321 is configured to shift the conveyor belt by the same amount as the displacement of the transfer platform during a stage that requires an object (e.g., a patient) to be moved with the same displacement as the platform. Some examples include when an object is being moved onto the transfer device 100, after the platform is inserted under the object, and when the patient needs to be moved back on the support surface, they will be placed on the support surface. In another example, the transfer controller 321 is sometimes configured to shift the conveyor belt by twice the amount of the transfer platform displacement, such as during a transfer stage that involves the platform moving under the patient or removing itself from under the patient (i.e., picking up the patient from the support platform or placing the patient back on the support surface).

[0187] After determining the actual conveyor belt displacement, the manager system then determines 842 whether there is a displacement error. In some cases, determining the presence of a displacement error includes determining the difference between the expected conveyor belt displacement and the actual conveyor belt displacement. In some cases, a threshold is applied to the displacement difference, and an error occurs when the difference exceeds the threshold. According to various specific implementations, the threshold is selected based on the sensitivity requirements of the current transfer stage. For example, when transferring a patient to the device, the patient should not move significantly to avoid the risk of falling from the transfer device. In some cases, based on control limits, and as a general guide, the positioning of the conveyor belt relative to the platform can be between 1mm and 5cm, for example, which is considered safe. In other cases, in order to limit any shear forces generated by the relative speed mismatch between the patient and the transfer process (e.g., the platform is inserted under the patient), the conveyor belt must not "drift" beyond the range of approximately 1mm to 10mm to ensure that the patient does not feel any pushing sensation. In some cases, determining 842 that there is no error causes the manager system to coordinate with the transfer controller 321 to continue to control the conveyor belt and the platform. In some cases, the manager system determines 842 that there is a displacement error. In such cases, the manager system can infer 843 that a material obstruction has occurred, and in some cases report the obstruction and / or request instructions for the next action to take 844. In some implementations, the subroutine 800D can be performed by the transfer controller 321.

[0188] Fig. 8E 850E is a flow chart of a method 800E for adjusting the position of an object on a transfer device according to various specific implementations. The method 800E includes subroutines or autonomous operations executable by a manager system to adjust the position of an object (such as, for example, a patient) without the need for an imaging device such as a camera. At step 851, the manager system coordinates the subsystem controller 120 to transfer the object toward the center of the transfer device. At steps 852 and 853, the manager system collects data from multiple sensors from the subsystem controller 120 to monitor and compare the platform position and the object position, respectively. At step 854, the manager system uses the information from steps 852 and 853 to calculate the trajectory of the object and predict the final position of the object within the three sections of the device.

[0189] At step 855, the manager system coordinates the subsystem controller 120 to modify the transfer platform and conveyor kinematics based on the predicted final position from step 854. For example, assuming the position of the patient 10 is as follows Fig.8F Starting from any position in the platform 202 shown in step 860, if the predicted final position is located at Fig.8F82 of the transfer device 200 shown in step 861, the transfer process continues to move the patient 10 to the center of the platform 202 without interruption. As another example, if the predicted final position is located at Fig.8F 81 of the transfer apparatus 200 shown in step 862 of the present invention, the manager system signals the transfer controller 321 to continue moving the platform to the center of the transfer apparatus 200 and also moves the conveyor belt to adjust the patient's position to the center of the platform 202 and the transfer apparatus 200, thereby moving the patient 10 away from the edge of the apparatus. As another example, if the predicted final position is in the third section 83 of the transfer apparatus 202 that is farthest from the original patient 10 position, the manager system signals the transfer controller 321 to execute a zero relative velocity relative to the transfer apparatus 200 and thus maintain the position of the patient 10 in the center of the apparatus while moving the platform to the center of the transfer apparatus 200 as shown in step 862 of the present invention. Fig.8F The manager system may also signal the lift and tilt controller 322 to adjust the height and angle of the transfer device 200 to assist in adjusting the angle of approach and compression on the support surface to minimize elevation changes and any blunt force impacts of the patient 10. This in turn will improve efficiency, comfort, and reduce the likelihood of obstructions during the transfer process.

[0190] According to various implementations, the transfer device 200 and / or the distributed control system 100 may include one or more of the following aspects and features.

[0191] In some implementations, the distributed control system 100 can utilize logical data input and decision-making capabilities to eliminate variations in user interaction and interpretation, enabling the transfer device to easily and automatically complete a patient transfer.

[0192] In some implementations, the distributed control system 100 enables automatic and semi-autonomous operation. The transfer device 200 can be controlled by various control subsystems working in coordination to perform patient transfers without user intervention.

[0193] In some implementations, the distributed control system 100 achieves ease of use. A simple and efficient user interface can allow an operator to easily adjust the transfer platform and perform patient transfers.

[0194] In some embodiments, the distributed control system 100 implements basic operations including height adjustment (e.g., lifting / lowering), angle adjustment (e.g., tilting up / down left, tilting up / down right, tilting up / down front), picking up from the left, picking up from the right, lowering to the left, and lowering to the right.

[0195] In some implementations, the distributed control system 100 implements safety and reliability. For example, in some cases, the distributed control system can automatically stop any unsafe actions or transfers that could potentially cause harm to the patient or user, and will not start a transfer process if the patient or transfer device is not in the correct position.

[0196] In some implementations, the distributed control system 100 achieves a high system uptime (ie, it does not fail frequently). If a fault or failure occurs within the control system, patients are not harmed and the entire system is not paralyzed.

[0197] In some implementations, the distributed control system 100 implements adaptability so that patient transfer is possible for any patient, regardless of their size (i.e., weight and / or height). Patients can be picked up or lowered from any patient support surface (e.g., bed, stretcher), regardless of height, hardness, or surface material.

[0198] In some implementations, the distributed control system 100 implements fault monitoring and redundancy. By utilizing multiple MCUs, the system has built-in fault tolerance. If a single MCU fails, the entire system has the ability to monitor communications and determine whether a single controller has failed, or whether the entire system is down. In addition, by distributing the processing and decision making of the system, it can reduce the probability of errors in each subsystem by making the firmware easier to manage and subsystem unit testing more efficient than if one core MCU manages everything.

[0199] Many modifications and variations of the present disclosure are possible in light of the above teachings.It is therefore to be understood that within the scope of the appended claims, the present disclosure may be practiced otherwise than as specifically described herein.

Claims

1. A transfer device, comprising: Device body; a transfer platform supported by the apparatus body, the transfer platform comprising at least one conveyor belt configured to move objects onto and / or away from the transfer platform; a plurality of subsystems, each subsystem being configured to implement the function of the transfer device; a plurality of subsystem controllers, each subsystem controller configured to control operation of one of the plurality of subsystems; as well as a system processor in communication with the plurality of subsystem controllers, the system processor being configured to: monitoring and communicating with the plurality of subsystem controllers; receiving operator input from a transfer device operator; making decisions regarding the transfer operation based on input received from a transfer device operator and input received from the plurality of subsystem controllers; and A command is sent to the plurality of subsystem controllers.

2. The transfer device of claim 1, wherein two or more of the plurality of subsystem controllers are located in different areas of the transfer device proximate to one or more sensors and / or actuators.

3. The transfer device of claim 1 or claim 2, wherein the system processor and the plurality of subsystem controllers are configured to operate together to automatically perform a patient transfer without user intervention.

4. The transfer device according to any one of claims 1 to 3, wherein the system processor is configured to control a human machine interface (HMI) of the transfer device. 5 . The transfer apparatus according to claim 1 , wherein the plurality of subsystem controllers include a subsystem controller configured to control transfer of the object.

6. The transfer apparatus of claim 5, wherein the distributed control system is configured to receive the tension and displacement of at least one conveyor belt and the position and speed of the transfer platform for use in a method of transferring a patient.

7. The transfer device according to any one of claims 1 to 6, wherein the plurality of subsystem controllers include a subsystem controller configured to adjust the height and angle of the transfer platform and / or the transportation of the transfer device.

8. The transfer device according to any one of claims 1 to 7, wherein the plurality of subsystem controllers include a subsystem controller configured to control one or more peripheral subsystems of the transfer device that are not involved in the movement of the transfer platform.

9. The transfer device according to any one of claims 1 to 8, wherein the plurality of subsystem controllers includes a subsystem controller configured to control power delivery to electronic components of the distributed control system and to actuators of the transfer device.

10. A transfer device according to any one of claims 1 to 9, wherein the plurality of subsystems are configured to implement one or more of the following: (i) transferring an object, (ii) adjusting the height and angle of the transfer platform and / or transporting the transfer device, (iii) controlling peripheral devices of the transfer device that are not involved in the movement of the transfer platform, (iv) providing device safety, and (v) controlling power delivery to electronic components of the distributed control system and to actuators of the transfer device.

11. The transfer device of any one of claims 1 to 10, wherein the system processor is configured to establish a secure connection to an external network to upload captured images, diagnostic data and / or download firmware changes.

12. The transfer device of claim 11, wherein the external network is an intranet configured to facilitate communication between a plurality of transfer devices.

13. The transfer device according to claim 11, wherein the external network is the World Wide Web.

14. The transfer device of any one of claims 1 to 13, wherein the system processor is in communication with an imaging subsystem comprising at least one imaging device, and wherein the system processor is configured to receive at least one captured image from the at least one imaging device and to determine at least one variable using image processing of the captured image such that the at least one variable is related to transfer of an object by the transfer device.

15. The transfer device of claim 14, wherein the system processor is configured to receive a plurality of captured images forming a video feed from the at least one imaging device and to determine at least one variable using image processing of the video feed such that the at least one variable is related to transfer of an object by the transfer device.

16. A transfer device according to any one of claims 14 or claim 15, wherein the subsystem controller is configured to use processing of the at least one captured image to determine at least one variable such that the at least one variable is related to transfer of an object by the transfer device.

17. The transfer device of claim 16, wherein the at least one variable comprises the mass and / or volume of the object.

18. A transfer device according to claim 16 or claim 17, wherein the at least one variable comprises the position and / or orientation of the object.

19. The transfer device of any one of claims 16 to 18, wherein the system processor is configured to assess the risk of damage to the object based on the at least one variable.

20. The transfer device of any one of claims 16 to 19, wherein the system processor is configured to determine parameters and / or limitations for transfer of the object by the transfer device based on the at least one variable.

21. The transfer device of claim 20, wherein the system processor receives feedback from at least one of the subsystem controllers regarding forces measured during transfer of the object, and the system processor is configured to adjust the parameters and / or limits based on the feedback.

22. A transfer device according to any one of claims 16 to 21, wherein the system processor is connected to a persistent memory configured to record the video or image feed for future playback.

23. The transfer device according to any one of claims 16 to 21, wherein the system processor is configured to establish an external data connection and is configured to send the image or video feed through the external data connection to an external receiving unit for monitoring and observation.

24. A method for execution by a system processor of a transfer device, the transfer device comprising a device body and a transfer platform configured to move an object, the method comprising: receiving at least one image from at least one imaging device; At least one variable is determined using image processing of the at least one image such that the at least one variable is related to transfer of an object by the transfer device.

25. The method of claim 24, wherein the at least one variable comprises the mass and / or volume of the object.

26. A method according to claim 24 or claim 25, wherein the at least one variable comprises the position and / or orientation of the object.

27. The method according to any one of claims 24 to 26, further comprising: A risk of damage to the subject is assessed based on the at least one variable that has been determined.

28. The method according to any one of claims 24 to 27, further comprising: Parameters and / or limits for transferring the object by the transfer device are determined based on the at least one variable that has been determined.

29. The method of claim 28, further comprising: receiving feedback regarding forces measured during transfer of the object; as well as The parameters and / or limits are adjusted based on the feedback.

30. The method according to any one of claims 24 to 29, further comprising: The at least one image is recorded for later playback.

31. The method according to any one of claims 24 to 30, further comprising: Establish external data connections; as well as The at least one image is transmitted via the external data connection to an external receiving unit for monitoring and viewing.

32. A non-transitory computer readable medium having statements and instructions recorded thereon, which when executed by a system processor of a transfer device configure the system processor to implement the method of any one of claims 24 to 31.

33. An apparatus comprising: Any component or combination of components as described and / or depicted herein.

34. A method comprising: Any steps or combination of steps as described and / or depicted herein.

35. A non-transitory computer-readable medium having statements and instructions recorded thereon which, when executed by a processor of a device, configure the processor to implement a method comprising any combination of steps or steps as described and / or depicted herein.

Citation Information

Patent Citations

  • Devices and methods for transferring an object

    WO2022150915A1