Method and device for transporting functional devices in healthcare application ecosystems

The automation of functional device transportation in healthcare ecosystems using task-list-controlled transport devices addresses the inefficiencies and errors of manual methods, improving operational efficiency and patient safety.

WO2025132791A1PCT designated stage expired Publication Date: 2025-06-26VIGERES GMBH

Patent Information

Application Number
PCT/EP2024/087406
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-12-22
Filing Date
2024-12-19
Publication Date
2025-06-26

AI Technical Summary

Technical Problem

The transportation of functional devices in healthcare ecosystems is often manual, labor-intensive, and prone to errors, leading to inefficiencies and potential disruptions in patient care.

Method used

A computer-implemented method and system for automating the transportation of functional devices using specialized transport devices configured to engage with various devices, controlled by a task list that specifies target locations, and equipped with sensors for navigation and collision avoidance.

Benefits of technology

The solution reduces turnaround time for deploying and storing cleaned or maintained functional devices, minimizes human errors, and enhances operational efficiency in healthcare ecosystems, ensuring the safety and well-being of patients.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure EP2024087406_26062025_PF_FP_ABST
    Figure EP2024087406_26062025_PF_FP_ABST
Patent Text Reader

Abstract

The description specifies a computer-implemented method for transporting functional units in healthcare application ecosystems, comprising providing one or more transport devices in a healthcare application ecosystem, the one or more transport devices configured to engage with functional units deployed in the healthcare application ecosystem, accessing a task list, the task list including one or more tasks, each specifying a target location for a functional unit in the healthcare application ecosystem, and controlling the one or more transport devices according to the task list, including, for a task of the one or more tasks, selecting a transport device of the one or more transport devices for a functional unit specified in the task, engaging the transport device with the functional unit, and transporting the functional unit to the target location specified in the task using the transport device. Furthermore, a transport device and a system are defined.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] METHOD AND DEVICE FOR TRANSPORTING FUNCTIONAL DEVICES IN

[0002] HEALTHCARE APPLICATION ECOSYSTEMS

[0003] TECHNICAL FIELD

[0004] The disclosure relates to transporting functional devices in healthcare application ecosystems using transport devices. The disclosure may refer to a method for transporting functional devices in healthcare application ecosystems, a transport device, and a system for deployment of transport devices in one or more healthcare application ecosystems.

[0005] BACKGROUND

[0006] Healthcare application ecosystems typically require a number of apparatuses or devices that form functional devices, to ensure efficient and effective delivery of healthcare to patients. The functional devices, which may include everything from advanced medical equipment, emergency or evacuation equipment to fundamental apparatuses like patient beds, serve as the backbone of healthcare applications.

[0007] Despite their centrality in healthcare delivery, several challenges are associated with the use and management of functional devices. Functional devices, especially those like patient beds that have prolonged contact with individuals, are at high risk of harboring pathogens. Proper cleaning and sterilization are crucial to prevent cross-contamination between patients and staff. Further, routine wear and tear require constant attention. Any unexpected malfunction can disrupt care, and in critical cases, put lives at risk. The provision of functional devices may also impose logistical challenges since space is often limited in healthcare settings. Thus, efficiently storing and moving functional devices, including diagnostic and therapeutic devices, monitoring equipment, or beds, without causing disruption is a logistical concern. As a consequence, functional devices are frequently transported in healthcare application ecosystems.

[0008] Traditionally, the transportation of functional devices for cleaning, maintenance or storage purposes in healthcare application ecosystems has largely been a manual process. This involves a team of (facility) staff responsible for deploying, moving, cleaning, disinfecting, maintaining, storing, and returning these functional devices to facilities, patient or treatment rooms or storage areas. The manual processes can be labor-intensive and time-consuming. Besides, human error or inconsistency can lead to lapses in cleanliness, safety, and security standards.

[0009] The number of functional devices can vary widely in healthcare application ecosystems. With regard to beds and healthcare facilities, for example, smaller clinics or specialty care units may house only a few dozen beds, while large metropolitan hospitals can have upwards of a thousand beds. With such a vast number of beds, especially in bigger facilities, the logistics of ensuring every bed is cleaned and ready for patient use becomes an intricate task. This does not include the cleaning or maintenance process only, but it must be ensured that functional devices are transported safely without causing disruptions in the daily operations of the healthcare application ecosystems.

[0010] SUMMARY OF THE DISCLOSURE

[0011] In light of these challenges, there is a growing interest in finding more efficient, consistent, and automated approaches to manage automatic deployment and transportation of functional devices in healthcare application ecosystems.

[0012] The above-mentioned problems are solved by a computer-implemented method for transporting functional devices in healthcare application ecosystems, a transportation device, and a system according to the independent claims. Preferred embodiments are defined in the dependent claims.

[0013] A first aspect of the disclosure provides a method for transporting functional devices in healthcare application ecosystems, comprising providing one or more transport devices in a healthcare application ecosystem, the one or more transport devices configured to engage with functional devices deployed in the healthcare application ecosystem, accessing a task list, the task list including one or more tasks, each specifying a target location for a functional device in the healthcare application ecosystem, and controlling the one or more transport devices according to the task list, including, for a task of the one or more tasks, selecting a transport device of the one or more transport devices for a functional device specified in the task, engaging the transport device with the functional device, and transporting the functional device to the target location specified in the task using the transport device. Solutions according to the present disclosure reduce the turnaround time for deploying, storing or furnishing cleaned or maintained functional devices and minimize human errors. They enhance the operational efficiency of healthcare application ecosystems and ensure the wellbeing of patients.

[0014] The method may be a computer-implemented method. The method may be implemented in a computing device or on a system with one or more computing devices, including one or more processors or processing units (PUs) that may be coupled to each other or communicate with each other, and that may be configured to perform individual method steps. The one or more processors or PUs may implement hardware and / or software modules that execute the individual method steps. Examples may include a providing PU or provider; an accessing PU or interface; and / or a controlling PU or controller that may perform one or more steps of the method according to the first aspect or implementations of the first aspect.

[0015] Providing of transport devices may involve introducing or deploying specialized transport devices within the healthcare application ecosystem. The transport devices may be specifically designed or adapted to physically engage with various functional devices. Engagement could mean attaching, lifting, holding, or any other method of securing the functional device for transport. The type of engagement mechanism can vary based on the nature or type of the functional device. This may include one or more of clamps for heavy machinery, shelves or slots for devices, secure storage for delicate equipment, and similar, in any combination.

[0016] The task list may serve as a blueprint for the transport devices, guiding their operations. Entries in the task list could be generated via a user interface by personnel or could be generated in a (semi-) automated manner based on constraints and requirements of a management system, which could be similar to a Warehouse Management System (WMS) or an loT (Internet of Things) management system. Each task on the task list could provide instructions, including a target location for a particular functional device. The specificity of target locations can vary, including exact coordinates, such as geo-location coordinates or RFID-related locations, to more generic location descriptions, including indications of rooms, stations, or other areas in a healthcare facility of the healthcare application ecosystem. Transportation is achieved by identifying for a task an appropriate (or associated) transport device for a specific functional device specified in the task. The selection could be based on various factors such as a size of the functional device, its weight, delicacy, or a current location of available transport devices. Further, transport devices may be associated with a functional device, which may directly lead to selection of the associated transport device if the functional device is specified in a task of the task list. The selection may also be based on terrain conditions on a path of the transport device, such as outdoor conditions. In this case, the transport device may be selected based on whether the transport device is capable of traveling under the terrain conditions.

[0017] The transport device may be physically attached or secured to the functional device. This could involve mechanisms like robotic arms, lifting forks, clamps, connectors, or the like, in any combination. The transport device moves the engaged functional device to its target location as specified in the task. The transportation might involve navigating through the healthcare application ecosystem, avoiding obstacles, and ensuring safety and security of the functional device throughout the journey in the healthcare application ecosystem.

[0018] The method provides for an automated transportation of functional devices in healthcare application ecosystems based on task lists. Suitable transport devices are selected and scheduled to efficiently perform a task in a secure and reliable manner.

[0019] In a first implementation of the method according to the first aspect, the method further comprises analyzing the task list to generate a task allocation table for the one or more transport devices, wherein the task allocation table specifies tasks for the one or more transport devices, including respective functional devices and target locations as specified in the task list. Before any transport task is initiated, the task list may be analyzed. The analysis may involve assessing one or more of a priority of tasks, locations of functional devices, their target destinations, nature and type of the functional devices, and others, in any combination. The objective may be to allocate tasks in a manner that maximizes efficiency and minimizes redundancy or transport device downtime. Results of the analysis may be compiled into a structured format, which may be also referred to as a task allocation table. The task allocation table may represent a master plan or roadmap for the deployed transport devices in the healthcare application ecosystem for a given duration or set of tasks. The task allocation table may specify which transport device is tasked with which functional device and the target location for that func- tional device. For each transport device, the table may enumerate one or more of the tasks assigned to the transport device, respective functional devices that the transport device will transport, and the target locations of the functional devices from the original task list, ensuring that each transport device knows precisely where it needs to deposit each functional device. The task allocation table may represent an optimization layer, wherein based on an analysis of the task list, intricacies and details of each task are highlighted. Using this information, a detailed plan reflected in the task allocation table is established that dictates how each transport device will operate, ensuring tasks are completed in the most efficient manner possible.

[0020] In a further implementation of the method according to the first aspect, the method further comprises identifying dependencies in the task list and defining an order of the one or more tasks according to the dependencies. Before executing tasks, the task list may be reviewed to identify any dependencies that exist between individual tasks. A “dependency” may mean that one task relies on another task being completed first. For instance, a certain functional device may need to be transported for maintenance or cleaning, which may be specified in a first task, before the functional device is moved to a storage location or place of use, which may be specified in a second task. Dependencies can arise for a variety of reasons such as logistical requirements, operational constraints, or specific sequences needed for effective workflow. This introduces a critical layer of logistical intelligence, which ensures efficient and error-free task execution.

[0021] In a further implementation of the method according to the first aspect, the method further comprises determining an optimized route for the one or more transport devices based on current locations of the functional devices in the healthcare application ecosystem and target locations of the functional devices specified in the task list. The method may take into account where each functional device is currently situated in the healthcare application ecosystem. The current location of a functional device may either correspond to a location of the transport device if the transport device is coupled to the functional device, or an assigned transport device needs to first travel to the current location of the functional device to pick up the functional device. By knowing the starting point (current location of the functional device) and the ending point (target location), it becomes possible to calculate an efficient pathway. This may include factors, such as, distance, possible obstructions, and other concurrent movements in the healthcare application ecosystem. With the starting and ending points established, the method may then calculate the best route for the transport device to take. It is to be noted that the terms “best” or “optimized” do not necessarily mean a shortest path. It may refer to a most efficient route, considering one or more of the following factors, in any combination, such as a minimal traffic disruption, which takes into account that the route avoids congested areas in the healthcare application ecosystem to prevent slowdowns; safety, which may take into account that the route avoids areas where fragile items may be located or stored, or where personnel or patients may be present or active; energy efficiency, which may be important when transport devices are battery-operated; time efficiency, which may reduce transit time, especially during peak operational hours; and the like, in any combination. The determination of the optimized route may further incorporate real-time data from sensors or other devices in the healthcare application ecosystem.

[0022] In one embodiment, the transport unit and the functional device are connected with each other. For example, one or more of the transport units may be temporarily or permanently connected with corresponding functional devices, which may enable a self-automated functional device controlled by tasks. In this preferred embodiment, the transport device connected to the functional device may be directly selected to perform any task specifying the functional device. The selected transport device may directly engage with the functional device to initiate transport to the target location.

[0023] In a further preferred embodiment, the method further comprises navigating the transport device to a current location of the functional device. Initially, the selected transport device and the functional device specified in the task may not be connected or associated. Thus, the method may first determine a current location of the transport device and the current location of the functional device. The current locations of both devices can change. The current location of the transport device can be affected by navigation to the current location of the functional device. The current location of the functional device may be affected by manual movement or concurrent tasks. Accordingly, the transport device may continuously monitor its own location, update its location with a planned path to the functional device, and further monitor a current location of the functional device.

[0024] Preferably, said navigating includes using one or more sensors of the transport device to determine a current location of the transport device, and continuously adjusting a path of the transport device during navigation based on real-time feedback from the one or more sensors. The transport device may be equipped with the one or more sensors that constantly assess its current position within the healthcare application ecosystem. Sensors may include one or more of GNSS modules, inertial measurement units (IMUs), LiDARs or ultrasonic sensors, optical sensors, cameras, which can be, for example, used for visual SLAM (Simultaneous Localization and Mapping) to understand the transport device's current position relative to known or dynamically mapped landmarks in the healthcare application ecosystem. As the transport device moves towards its destination, the transport device may follow a pre-set path. Additionally or as an alternative, the transport device may continuously assess its environment and make decisions with respect to adjustment of the pre-set path on-the-go. The path can be adjusted based on several factors, including one or more of static or dynamic obstacles, like parts or elements of buildings and other construction parts, another moving objects or a person; changing environmental conditions, like a wet floor, which could influence the transport device's speed or direction to ensure safety; or re-routing considerations, which may take into account that a most direct path may not be the most efficient due to congestion or other traffic issues, in any combination. In case of re-routing, the transport device may determine alternate routes to reach its destination (faster or more safely). Real-time feedback from the one or more (onboard) sensors may provide the transport device with up-to-date information about its surroundings, enabling it to make path adjustments dynamically. The transport device may be provided with a strong sense of self-awareness and adaptability.

[0025] In a further implementation of the method according to the first aspect, said navigating includes detecting moving objects using proximity sensors of the transport device in real-time, dynamically estimating trajectories of the moving objects, and adjusting a path of the transport device in real-time based on the estimated trajectories to avoid collisions. Preferably, the one or more sensors of the transport device may include the proximity sensors. The proximity sensors may include any kind of sensors, capable of detecting objects in the vicinity of the device. Proximity sensors can include one or more of ultrasonic sensors, infrared sensors, or other types, in any combination. The proximity sensors may be (continuously or triggered by other sensors or constraints) active, by sending out signals and receiving reflections to ascertain the distance and direction of nearby objects. By determining how these reflections change over time, the transport device can identify not just stationary objects, but also those that are moving. Once a moving object is detected, the method may process data from the proximity sensors to estimate the moving object's current path or trajectory. By analyzing changes in the moving object's position and direction, the transport device may predict where the moving object is likely headed in the next moments and may establish the estimated tra- jectories. This may be used to understand where the object is now and where it will be in relation to the planned route of the transport device. The trajectory information of the moving objects can be used to calculate whether a collision is likely on the path of the transport device. In response, the method may re-route or adjust the path of the transport device if the likelihood surpasses a threshold. This may include a complete change in direction, a temporary halt, a change in speed, or a slight deviation from the planned path or other adjustments required to avoid collisions with the moving object. The decisions are preferably made in real-time. With its sensors, including the proximity sensors, the transport device always knows where it is and what's around it. If there's something in its way or if conditions change, the transport device can react in real-time, tweaking its path as needed. This ensures not just speed, but also safety, as the transport device moves around the healthcare application ecosystem.

[0026] In a further implementation of the method according to the first aspect, the method further comprises logging information including detected moving objects and their trajectories and adjustments of the path of the transport device, and communicating the information to a control system to establish patterns of movement and activity zones within the healthcare application ecosystem. The method may create a comprehensive record of dynamic movements and interactions within the healthcare application ecosystem, which, when relayed to a control system, facilitates better understanding of patterns of movement (or traffic patterns) and areas of high activity. The transport device may observe and log (significant) events, such as the detected moving objects and their trajectories. This may be combined with required adjustments of the path. By understanding patterns of movement and recognizing high-activity zones, strategies to reduce congestion or optimize storage placement can be implemented, resulting in smoother operations and reduced risks of accidents. The control system can use the provided information to update task lists or strategies dynamically, allowing transport devices to adjust to changes promptly. Over time, the method could employ predictive analytics to forecast potential bottlenecks or traffic issues before they occur. Furthermore, if a transport device consistently makes path adjustments in a specific zone, it might indicate issues with the environment or the transport device itself, prompting maintenance checks or further investigation. The communicated information can serve as feedback for continuous improvement processes, guiding updates to a control unit driving the transport devices and the physical layout or policies of the healthcare application ecosystem. In a further implementation of the method according to the first aspect, said engaging includes detecting an identification of the functional device using one or more sensors of the transport device and determining a type of the functional device using the identification. The transport device can use one or more sensors to detect identification markers or tags attached to the functional devices, such as RFID tags, NFC tags, barcodes, or QR codes that could be specifically customized for each functional device. For example, every functional device may be marked with an QR code, which will be red by the transport device to identify the type. Then, the transport device can start the engagement or docking procedure. These markers or tags can be placed in strategic locations on the functional device, such as near the handle or base, so that they can be easily scanned or read by the transport device's one or more sensors. Once the identification is confirmed, the transport device can access information associated with the functional device, such as its type, intended use, maintenance schedule, and transport preferences, to tailor its behavior accordingly. By leveraging these identifications and associated information, the transport device can optimize its performance and ensure safe and efficient transportation of functional devices throughout the healthcare application ecosystem. To ensure safe transportation and prevent damage or disruption, the transport device can employ various safety features and protocols such as speed limiters, collision avoidance systems, and sensitive braking systems. Accordingly, one or more features can be activated based on the type of functional device being transported, as determined by the identification. For example, if the functional device is a delicate medical instrument or a patient’s bed, having the functional device engaged, the transport device may slow down or stop entirely when approaching a busy area or another patient's bedside.

[0027] Preferably, RFID or QR tags, or any other kind of markers or tags can include pointers to local or remote information. Markers or tags can be used to retrieve specific information for a task, or information related to an objects tagged or marked using the tag or mark, respectively, or to any other local or remote object related to the tag or mark.

[0028] Preferably, at least some of the functional device and / or at least some of the transport devices, or any other kind of device or object, may have tags or markers, such as the aforementioned RFID or QR tags, or any other kind of markers or tags. This can be used to identify the marked or tagged devices or objects, and / or to retrieve information related to the device or objects and / or information related to connected or associated devices, objects or environment. In a further implementation of the method according to the first aspect, said engaging includes aligning the transport device with the functional device and engaging an interface portion of the transport device with the functional device. This contributes to securely transporting the functional device while minimizing the risk of damage or disruption. Said engaging may also be referred to as docking throughout the disclosure. The alignment of the transport device with the functional device can involve using sensors and cameras, both on the transport device and / or on the functional device, to accurately position the transport device relative to the functional device and then engaging the two devices via, for example, a mechanical interlock or magnetic attachment. By ensuring close fitting between the two devices, the transport device can maintain stability during transport and prevent the functional device from shifting or falling off during transit. Furthermore, the interface portion of the transport device can be designed to accommodate different types of functional devices and adapt to their unique form factors, thereby providing a flexible and versatile engagement or docking means for transportation of a wide range of functional devices in the healthcare application ecosystem.

[0029] In a further implementation of the method according to the first aspect, the interface portion has a form adapted to the form of at least a part of the functional device. By adapting the form of the interface portion to match the form of at least a part of the functional device, the transport device can achieve an even tighter fit and improved stability during transport. This adaptation can be achieved through various means such as molding or 3D printing the interface portion to conform to the shape of the functional device. Such customization can enhance the overall effectiveness of the transport device and enable it to handle a broader variety of functional devices with diverse form factors.

[0030] In a further implementation of the method according to the first aspect, said transporting includes adjusting, by an adaptive speed control system, a transport speed of the transport device based on a weight and size of the functional device. By considering the weight and size of the functional device being transported, the adaptive speed control system can dynamically adjust the transport speed to ensure a smooth and stable journey while avoiding potential damage or disruption. This could be used for transporting fragile or high-value functional devices, where slight changes of direction at a higher speed could result in significant damage or loss. This adds another layer of adaptability to the transport device, enabling it to tailor its performance to the specific needs of the healthcare application ecosystem and the functional devices being transported. In a further implementation of the method according to the first aspect, the method further comprises providing real-time feedback to the control system, including status and progress of transportation, and using the real-time feedback to dynamically adjust control of other transport devices. The real-time feedback may constitute a real-time feedback loop, which may help optimizing of the transport process and ensuring safe and efficient operations within the healthcare application ecosystem. By continuously monitoring the status and progress of transportation, the transport device can quickly respond to changes in the environment or unexpected events, such as obstacles or delays, and make adjustments to maintain optimal performance. Additionally or as an alternative, the real-time feedback loop can enable the transport device to adapt to the changing environment, leading to increased efficiency and reduced downtime. The ability to dynamically adjust control of other transport devices based on real-time feedback enables coordinating transport operations within the healthcare application ecosystem.

[0031] The term “real-time” as used throughout this disclosure can be defined as an immediate or near-immediate processing of information, typically involving a continuous flow of data and responses without noticeable delay. This can include decisions taken within a time duration of less than a threshold. Thus, the delay may be below a threshold. As an example, the threshold can be 1 second, 0.9 seconds, 0.8 seconds, 0.7 seconds, 0.6 seconds, 0.5 seconds, 0.4 seconds, 0.3 seconds, 0.2 seconds, 100 milliseconds, 50 milliseconds, or 10 milliseconds, or any other suitable threshold. Hence, any other threshold can be used to control an instant reaction of the method and of the transport device with respect to changing environments. In the context of the transport device, real-time feedback may refer to updates provided to the control system as the transport device moves through the healthcare application ecosystem, enabling prompt decisions and actions to address any issues or changes in the transport process or the environment. Real-time feedback or real-time can be achieved through various means, including multiple processing units, parallel processing, fasts networks and connectivity, designed to process or transport data below pre-set time constraints.

[0032] The term “dynamic” as used throughout this disclosure, for example, for dynamic adjustment of control of transport devices or dynamic estimation of trajectories of moving objects, can be defined as an ability of the transport device to continuously monitor its surroundings or environment, adapt to changing conditions, and / or adjust its behavior to maintain a defined per- formance. This may include adjusting a speed, trajectory, and orientation of the transport device based on factors such as the location of obstacles, the presence of people or vehicles, and the condition of the surrounding environment. By leveraging sensors, Al algorithms, and machine learning models, the transport device can continuously refine its behavior. This may minimize risks and maximize efficiency, creating a highly responsive and agile logistics network within the healthcare application ecosystem.

[0033] In a further implementation of the method according to the first aspect, the method further comprises, after reaching the target location, sending a task completion message to the control system. Preferably, this may further include disengaging of the functional device at the target location. By sending the task completion message to the control system, the transport device can effectively communicate its status and receive further instructions or assignments, for example, based on the task list. The transport device can contribute to maintaining records of completed transport tasks, which may optimize overall efficiency of the healthcare application ecosystem's logistics network. Moreover, this feature enables the transport device to transition (seamlessly) between different tasks, enhancing its flexibility and versatility within the healthcare application ecosystem.

[0034] In a further implementation of the method according to the first aspect, the method further comprises controlling the transport device to complete another task in the task list. By sequentially assigning tasks to the transport device and receiving confirmation of task completion, the control system can create a highly efficient and responsive logistics network that can adapt to changing conditions and priorities within the healthcare application ecosystem. This feature enables the transport device to maintain a steady workload and minimize downtime between tasks.

[0035] The term “functional device”, as used throughout this disclosure, encompasses a broad range of items in healthcare application ecosystems and may represent at least one apparatus, unit, or equipment for various functional tasks within the healthcare application ecosystem. Preferably, the functional device provides a function in the healthcare application ecosystem. Functional devices may comprise or be mounted on a frame, which enables transportation of the functional device. Functional devices may include, as an example, diagnostic, therapeutic or monitoring apparatuses, units, or equipment, such as instruments enabling determination of medical conditions, e.g., endoscopes, pumps, ventilators, nebulizers, and others, which direct- ly aid in the diagnosis, treatment and recovery of patients. Further functional devices may include beds, which may include standard patient beds, ICU beds, rescue beds, evacuation beds, or further specialized beds like orthopedic or birthing beds. However, it is to be understood that the disclosure is not limited to a particular type of functional device.

[0036] In a preferred embodiment, the functional device is a bed.

[0037] Embodiments of the present disclosure may also exclude certain types of functional devices, such as one or more of the afore-mentioned functional devices. A preferred embodiment may, for example, encompass functional devices, but may explicitly exclude functional devices for sitting, such as wheelchairs. Another preferred embodiment may encompass functional devices, but may explicitly exclude diagnostic, therapeutic, or monitoring apparatuses, units, or equipment as functional devices.

[0038] The healthcare application ecosystem(s) may be (an) application and deployment area(s) for functional devices in a healthcare context. This may include an outdoors application or deployment area, such as a rescue or evacuation site, which may involve one or more functional devices to rescue or evacuate individuals. The healthcare application ecosystem may also be linked to a facility, such as a healthcare facility or a plurality of healthcare facilities.

[0039] In a particularly preferred embodiment, the healthcare application ecosystem is (corresponds to) a healthcare facility. The healthcare application ecosystem may correspond to a healthcare facility. Accordingly, one embodiment of the method according to the first aspect may be defined as a method for transporting functional devices in healthcare facilities, comprising providing one or more transport devices in a healthcare facility, the one or more transport devices configured to engage with functional devices deployed in the healthcare facility, accessing a task list, the task list including one or more tasks, each specifying a target location for a functional device in the healthcare facility, and controlling the one or more transport devices according to the task list, including, for a task of the one or more tasks, selecting a transport device of the one or more transport devices for a functional device specified in the task, engaging the transport device with the functional device, and transporting the functional device to the target location specified in the task using the transport device. Healthcare facilities may include hospitals, retirement homes, clinics, outpatient clinics, and care centers, that may be equipped with a number of apparatuses or devices that represent the functional devices.

[0040] In another preferred embodiment, the healthcare application ecosystem may correspond to an evacuation or rescue area. Examples may include one or more of activity areas (skiing accidents on the slopes or hiking accidents in the mountains), disaster areas, emergency areas, military areas, crime or terrorist areas. This may encompass automated evacuation or rescue operations, such as automated transport of injured or wounded individuals, featuring automated transport devices with functional devices, such as automated transport beds, capable of navigating various (and challenging) terrains, such as off-road, mountainous, and disaster- prone areas. The combination of transport device with a bed may represent an automated (computerized) bed designed for efficiently transporting individuals in such environments. Preferably, the method involves using the automated bed to evacuate and rescue individuals from specified areas, wherein the design and operation of the automated bed may facilitate individuals' safe and speedy transportation.

[0041] A second aspect of the disclosure refers to a computer-readable storage medium. One or more computer-readable media may store instructions thereon that, when executed by one or more computing devices, configure the one or more computing devices to perform the method of the first aspect or one of the implementations of the first aspect. Preferably, the computer- readable storage medium stores program code with instructions that, when executed, configure at least one processor of the one or more computing devices to provide (or dispatch) one or more transport devices in a healthcare application ecosystem, the one or more transport devices configured to engage with functional devices deployed in the healthcare application ecosystem; access a task list, the task list including one or more tasks, each specifying a target location for a functional device in the healthcare application ecosystem; and control the one or more transport devices according to the task list, including, for a task of the one or more tasks, selecting a transport device of the one or more transport devices for a functional device specified in the task, engaging the transport device with the functional device, and transporting the functional device to the target location specified in the task using the transport device.

[0042] A third aspect of the disclosure refers to a computing device configured to perform the method according to the first aspect or one of the implementations of the first aspect. The compu- ting device may include one or more processors and a memory storing instructions that may be used to configure the one or more processors. Preferably, the device is configured to provide (or dispatch) one or more transport devices in a healthcare application ecosystem, the one or more transport devices configured to engage with functional devices deployed in the healthcare application ecosystem; access a task list, the task list including one or more tasks, each specifying a target location for a functional device in the healthcare application ecosystem; and control the one or more transport devices according to the task list, including, for a task of the one or more tasks, selecting a transport device of the one or more transport devices for a functional device specified in the task, engaging the transport device with the functional device, and transporting the functional device to the target location specified in the task using the transport device.

[0043] A fourth aspect of the disclosure provides a transport device, configured to engage with functional devices deployed in a healthcare application ecosystem. The transport device comprises a communication unit configured to receive a task from a task list specifying a target location for a functional device in the healthcare application ecosystem; a navigation unit configured to transport the functional device specified in the task to the target location specified in the task; and an interface portion configured to engage with the functional device.

[0044] The transport device of the fourth aspect may be configured to engage with functional devices deployed in the healthcare application ecosystem. The transport device is equipped with a communication unit that receives tasks from a task list, specifying the target location for a particular functional device within the healthcare application ecosystem. The navigation unit then transports the functional device to the designated location, while the interface portion engages with the functional device to facilitate secure and stable transport. This configuration enables the transport device to transport a wide range of functional devices, in an efficient and safe manner, each with their unique characteristics and requirements, thereby helping to streamline logistics operations within the healthcare application ecosystem and enhance patient care.

[0045] The transport device and its modules may be hardware or software components or a combination thereof. In particular the modules may include hardware controlled by software or firmware. Software updates can include new features, bug fixes, security enhancements, and performance improvements. For a plurality of transport devices, the software of a group of de- vices can be updated simultaneously using, for example, a software management system. In a fleet of transport devices, all devices may be updated or maintained at once to ensure consistency in performance and capabilities. This could be done remotely or through a central control system, such as the software management system. Firmware refers to a specific type of software that provides low-level control for the transport device's hardware. Firmware updates can improve the functionality and stability of the transport devices, fix hardware-related issues, or provide new hardware functionalities.

[0046] Device diagnostic and repair may involve checking the transport devices for any issues or malfunctions. Diagnostics can be run remotely or manually to assess the health of various components. If issues are detected, repairs can be either software-based (e.g., reconfiguring settings, updating software) or hardware-based (e.g., replacing a part).

[0047] Parameters of the transport device can be adjusted or set up using an interface or from a remote location. Remote configuration can be particularly useful for managing a fleet of devices where physical access to each device is not always feasible. This may include Parameter configuration can change operational settings, update routes for AGVs, adjust performance parameters, etc.

[0048] In a first implementation of the device according to the fourth aspect, the transport unit and the functional device are connected with each other. The connection can be a permanent physical connection between the transport unit and the functional device. By establishing the direct connection, the transport device can be efficiently assigned to specific functional devices within the healthcare application ecosystem, streamlining the distribution of tasks and maximizing resource utilization. This can lead to improvements in operational efficiency, as the transport device can be directly assigned with tasks relating to the (connected or associated) functional device. Moreover, the direct connection can enable the transport device to gather data about the assigned functional device, which may be used by a machine-learning approach to improve handling and control during transportation of the functional device.

[0049] In a further implementation of the device according to the fourth aspect, the navigation unit is configured to navigate the transport device to a current location of the functional device. In case the transport device and the functional device are not connected or coupled with each other, the navigation unit may guide the transport device to a current location of the assigned functional device according to the task list. By employing advanced navigation technologies such as GNSS, map-based routing, or sensor-assisted localization, the transport device can accurately determine its position and a current location of the functional device and navigate to the current location.

[0050] In a further implementation of the device according to the fourth aspect, said navigation unit is configured to use one or more sensors of the transport device to determine a current location of the transport device and continuously adjust a path of the transport device during navigation based on real-time feedback from the one or more sensors. The feature of using one or more sensors to determine the current location of the transport device and continuously adjust its path during navigation contributes to the transport device's autonomous capabilities. By leveraging sensors such as geo-location, cameras, lidar, or ultrasonic sensors, and others, in any combination, the transport device can gather real-time information about its surroundings and adjust its behavior accordingly, enabling the transport device to navigate through complex environments with precision. Moreover, the transport device can operate safely and efficiently within the healthcare application ecosystem, avoiding collisions with people, vehicles, or other obstacles, and minimizing the risk of damage or disruption to the functional devices it carries.

[0051] In a further implementation of the device according to the fourth aspect, the device further comprises proximity sensors, wherein the navigation unit is configured to detect moving objects using the proximity sensors in real-time, dynamically estimate trajectories of the moving objects, and adjust a path of the transport device in real-time based on the estimated trajectories to avoid collisions. By leveraging proximity sensors, the transport device can detect moving objects within its vicinity in real-time, estimating their trajectories and adjusting its own path accordingly to avoid potential collisions. The transport device can operate safely and efficiently within the healthcare application ecosystem, even in busy and dynamic environments, and ensures that it can respond rapidly to changes in its environment. The ability to dynamically estimate trajectories of moving objects and adjust the transport device's path in real-time may be based on algorithms for collision avoidance and traffic flow optimization.

[0052] In a further implementation of the device according to the fourth aspect, the communication unit is configured to log information including detected moving objects and their trajectories and adjustments of the path of the transport device, and communicate the information to a control system to establish patterns of movement and activity zones within the healthcare application ecosystem. By recording and analyzing patterns of movement and activity zones within the healthcare application ecosystem, the transport device can gain a deeper understanding of how the healthcare application ecosystem operates. This information can also be used to optimize traffic flow, reduce congestion, and improve the overall efficiency of logistics operations within the healthcare application ecosystem. Moreover, the communication unit's ability to share this information with a control system enables the transport device to integrate seamlessly into existing infrastructure.

[0053] In a further implementation of the device according to the fourth aspect, the interface portion has a form adapted to a form of at least a part of the functional device. By conforming the shape and size of the interface portion to match the dimensions and layout of the functional device, the transport device can engage with the functional device effectively, reducing the risk of damage or misalignment during transport. Moreover, the transport device can accommodate various types and sizes of functional devices, expanding its utility within the healthcare application ecosystem. The interface portion's adaptive form can facilitate easier loading and unloading of the functional device, improving the overall efficiency of the transport process and minimizing downtime.

[0054] In a further implementation of the device according to the fourth aspect, the device further comprises an adaptive speed control system configured to adjust a transport speed of the transport device based on a weight and size of the functional device. By automatically adjusting the transport speed according to the size and weight of the functional device, the transport device can avoid overstraining or damaging the functional device during transport, while also minimizing the time required to move the functional device between locations. The transport device can also optimize its energy consumption and extend its battery life, as it needs only the necessary amount of power to transport the functional device. Moreover, the adaptive speed control system can learn and adapt to different types and sizes of functional devices over time, further refining its performance within the healthcare application ecosystem. The adaptive speed control system may be an algorithm-based system that may dynamically adjust the transport speed of the transport device based on real-time data and parameters, such as the weight and size of the functional device, the distance traveled, and any obstacles or interruptions encountered along the way. The algorithm-based system may use advanced sensors and actuators to monitor the transport device's movements and environment and employ machine learning techniques to refine its performance over time. By continuously adapting to changing conditions and requirements, the adaptive speed control system can ensure that the transport device operates at optimal speeds, minimizes energy consumption, reduces wear and tear on the transport device or on the transported functional device and its components.

[0055] In a further implementation of the device according to the fourth aspect, the communication unit is configured to send a task completion message after depositing the functional device at the target location. By confirming the successful completion of each transport task with a clear and concise message, the transport device can provide reassurance a control system or to healthcare staff and patients alike that the functional device has been delivered safely and efficiently. The transport device can maintain accurate records of its activities and performance, supporting ongoing maintenance and quality assurance efforts within the healthcare application ecosystem.

[0056] According to a fifth aspect, a system for deploying transport devices in one or more healthcare application ecosystems is defined. The system comprises an interface module configured to provide data pertaining to characteristics of one or more healthcare application ecosystems and transport devices deployed in the one or more healthcare application ecosystems; a transportation requirement processor coupled to the interface module, configured to receive current transportation requirements of the one or more healthcare application ecosystems, and to maintain data indicating anticipated transportation requirements across the one or more healthcare application ecosystems; a device deployment optimizer configured to analyze one or more of locations, status, and capabilities of the transport devices across the one or more healthcare application ecosystems, calculate at least one deployment strategy based on the current transportation requirements and the anticipated transportation requirements, and to allocate and route transport devices to the one or more healthcare application ecosystems according to the at least one deployment strategy.

[0057] The transport devices in the system according to the fifth aspects may include transport devices according to the third aspect or implementations of the third aspect, in any combination.

[0058] The system according to the fifth aspect may represent a framework for managing transport devices within multiple healthcare application ecosystems. The system may correspond, at least partially, to a fleet management system. By integrating data from various sources and utilizing advanced algorithms to optimize deployment strategies, the system can ensure that transport devices are allocated and routed efficiently, minimizing costs and maximizing availability. In one or more embodiments, a preferred inclusion of real-time monitoring and tracking features, such as GNSS and sensor data, may add to precision and accountability, allowing for prompt response times and effective management of the transport devices. The system's ability to take into account the unique characteristics of each healthcare application ecosystem and adapt to changing requirements over time, makes it a versatile and reliable solution for managing (or deploying) transport devices within complex and dynamic healthcare environments.

[0059] It is to be understood that embodiments according to the third, fourth, or fifth aspect may include logic, processor(s), or functional device(s), which may be configured according to features of an embodiment of the first aspect of the disclosure or any implementations of the first aspect, in any combination. Preferably, the transport device and the system may be configured according to embodiments of the first aspect, in any combination. Likewise, the method according to embodiments of the first aspect may include processing steps reflecting a function of the structural features of the transport device or the system, in any combination.

[0060] According to further aspects and embodiments, a system and a software architectural setup for transporting functional devices in healthcare application ecosystems and / or for deploying transport devices in one or more healthcare application ecosystems are defined. The system and the software architectural setup can be configured to perform a method or provide a device according to aspects, implementations, and embodiments according to aspects of the present disclosure, in any combination.

[0061] It is to be understood that a healthcare application ecosystem may include (or correspond) to a healthcare facility, and / or that a healthcare application ecosystem may include (or correspond) to an area. Embodiments addressing multiple healthcare application ecosystems may also include a combination of both, such as a hospital and a rescue area, which may be associated with the hospital. BRIEF DESCRIPTION OF THE DRAWINGS

[0062] To illustrate the technical features of embodiments of the present invention more clearly, the accompanying drawings provided for describing the embodiments are introduced briefly in the following. The accompanying drawings in the following description are merely some embodiments of the present invention, modifications on these embodiments are possible without departing from the scope of the present invention as defined in the claims.

[0063] Fig. 1 is a flow chart illustrating a method in accordance with an embodiment of the present disclosure;

[0064] Fig. 2 is a schematic diagram of a transport device in accordance with an embodiment of the present disclosure; and

[0065] Fig. 3 is a diagram of a system in accordance with an embodiment of the present disclosure.

[0066] DETAILED DESCRIPTION OF EMBODIMENTS

[0067] In the following description, reference is made to drawings which show by way of illustration various embodiments. Also, various embodiments will be described below by referring to several examples. It is to be understood that the embodiments may include changes in design and structure without departing from the scope of the claimed subject matter.

[0068] The techniques described herein may be implemented in various computing systems, examples of which are described in greater detail below. Such systems generally involve the use of suitably-configured computing devices implementing a number of modules, each providing one or more operations needed to complete execution of such techniques. Each module may be implemented in its own way; all need not be implemented the same way. As used herein, a module may be a structural component of a system which performs an operational role, which may be a portion of or an entire software element (e.g., a function of a process, a discrete process, or any other suitable embodiment). A module may comprise computer-executable instructions and may be encoded on a computer storage medium. Modules may be executed in parallel or serially, as appropriate, and may pass information between one another using a shared memory on the computer on which they are executing, using a message passing protocol or in any other suitable way. Exemplary modules are described below carrying out one or more tasks, though it should be appreciated that the modules and division of tasks described may be merely illustrative of the type of modules that may implement the exemplary techniques described herein, and that the invention is not limited to being implemented in any specific number, division, or type of modules. In some implementations, all functionalities may be implemented in a single module. Further, the modules may be discussed below as all executing on a single computing device for clarity, though it should be appreciated that, in some implementations, the modules may be implemented on separate computing devices adapted to communicate with one another.

[0069] The present disclosure may use various abbreviations. For example, Al may be used to abbreviate the term Artificial Intelligence. Al refers to the simulation of intelligence processes by computer systems. Al may be used as a synonym for machine learning. Al systems according to the present disclosure are designed to perform tasks that typically require (human) intelligence, such as reasoning, problem-solving, learning, perception, and language understanding. AGV may be used to abbreviate Automated Guided Vehicles. An AGV is a robotic vehicle that is designed to transport devices or goods without the need for human intervention. ARM may abbreviate the term Autonomous Mobile Robot. AMRs are robotic systems equipped with onboard intelligence that enable them to move and navigate autonomously in dynamic environments. GNSS stands for Global Navigation Satellite System. It is a general term for a satellite system that is used to determine a geographic location or geo-location of a GNSS receiver, module, or sensor anywhere in the world. GNSS systems include GPS (Global Positioning System), GLONASS (Global Navigation Satellite System), Galileo, or BeiDou, to name a few.

[0070] Fig. 1 is a flow chart illustrating a method in accordance with an embodiment of the present disclosure.

[0071] The method 100 may be a computer-implemented method, which may be executed on one or more computing devices. The method 100 may interact with the environment by providing interfaces, such as programming interface or API to interact with a network, other devices, hardware, or software, such as sending and / or receiving data. The method 100 may further provide user interfaces, such as graphical user interfaces (GUIs), which may be displayed or rendered, for example, on a display or another output unit of a computing device or a display or output unit of other modalities (such as loudspeakers) of portable computing devices, to enable interaction with user(s), including rendering of information and receiving user input.

[0072] The method 100 may be configured for transporting functional devices in healthcare application ecosystems and may start in item 102.

[0073] In item 104, one or more transport devices may be provided in a healthcare application ecosystem. The method 100 may maintain a list of transport devices in the healthcare application ecosystem. The method 100 may maintain a list of functional devices in the healthcare application ecosystem. Each transport device may be configured to engage with at least one functional device deployed in the healthcare application ecosystem.

[0074] The method 100 may proceed with item 106 by accessing a task list. The task list may include one or more tasks, each specifying a target location for a functional device in the healthcare application ecosystem. The task list can be obtained from or generated based on input received via any interface, such as commands from a cloud or user input via a user interface, or using data that may be automatically generated, such as tasks related to automated maintenance or cleaning of functional devices.

[0075] Based on tasks in the task list, the method 100 may control the one or more transport devices according to the task list in item 108. Item 108 may include an identification or selection of a (current) task 110. The identification or selection of the task 100 may be based on a task allocation table for the one or more transport devices. The task allocation table may be the result of an analysis of the task list and may specify the tasks for the one or more transport devices, including respective functional devices and target locations specified in the task list.

[0076] For each task and a functional device specified in the task, a transport device may be selected in item 112. If the functional device is (permanently) connected with a transport device, item 112 may select the connected transport device to perform the task 110. If the functional device is not connected with a transport device, the method 100 may select a transport device of the one or more transport devices in item 112 and may optionally navigate the transport device to a current location of the functional device in item 114. The selection in item 112 may be based on one or more of the following factors, such as, distance to the functional device, capacity of the transport device, maneuverability of the transport device and of the functional device, speed of the transport device, safety factors, and the like, in any combination. For example, a distance to the functional device may be calculated. The capacity factor can be used to ensure that the transport device has sufficient space and capacity to accommodate the functional device, taking into account its size, weight, and any special handling requirements. The maneuverability factor can be used to consider the ease with which the transport device can navigate through tight spaces and around corners on a planned path to the functional device or to the target location, particularly if the functional device requires frequent movement or repositioning. The speed factor may assess the transport device's speed and acceleration capabilities to determine whether it can meet the needs of the healthcare application ecosystem, particularly in emergency situations. Various safety features may be used to assess whether the transport device is equipped for the task, such as whether the transport device has an automatic braking systems, collision avoidance sensors, and ergonomic designs to reduce the risk of accidents and injuries.

[0077] In item 116, the transport device may engage with the functional device. For example, if the transport device is (permanently) connected to the functional device, said engaging could include securing the functional device for transport. If the selected transport device is not connected with the functional device yet, after arrival at the current location of the functional device, the transport device can engage with the functional device to transport it. For example, the transport device can be equipped with a docking part that securely attaches to the functional device, ensuring stable connection and preventing accidental detachment during transport. Additionally or as an alternative, the transport device can feature magnetic attachment points that securely hold the functional device in place during transport, or further physical connectors or docking parts. Additionally or as an alternative, the transport device can be fitted with adjustable clamps or cradles that hold the functional device during transport, which may protect the functional device from damage and ensure smooth mobility. Other engagement mechanisms are envisaged by the present disclosure.

[0078] The method 100 may continue with transporting of the functional device to the target location specified in the task using the transport device in item 117. In optional item 114 and in item 117 the transport device may calculate a safe and efficient path from its current location to the target destination. Path planning algorithms may consider one or more of, in any combination, a map of at least a local part of the healthcare application ecosystem, obstacles, and any dynamic changes in the environment, and further information, which may be available locally or received from a remote control unit or server. Optimization criteria for the calculation may include minimizing travel time, avoiding collisions, and adhering to safety constraints.

[0079] At the target location, the transport device can optionally disengage the functional unit in optional item 118 and send a task completion message to indicate availability for a next task. The method 100 may proceed with item 120 to determine whether other tasks are in the task list.

[0080] Additionally or as an alternative, after sending a task completion message or indicating task completion in any other suitable way, the method 100 may take into consideration the transport device for assignment of further tasks from the task list or may update the task allocation table in item 106 to further control the transport devices in item 108. In particular, the transport device may be assigned with a next task and the method 100 may iterate with items 112 to 118 for the next task.

[0081] If all tasks are completed, the method 100 may end in item 122. This may include returning the transport devices to a parking position, including charging of the transport devices, maintenance of the transport devices, and the like.

[0082] Fig. 2 is a schematic diagram of a transport device in accordance with an embodiment of the present disclosure.

[0083] The transport device 200 may be deployed in a healthcare application ecosystem to transport functional devices 202 in the healthcare application ecosystem. Particularly, the transport device 200 may be configured to engage with functional devices deployed in the healthcare application ecosystem. The transport device 200 may have technical components that enable the transport device 200 to navigate, transport the functional devices 202, and perform specific tasks, such as maintenance, charging, and the like, autonomously. The transport device 200 may include one or more processing components. The processing components may be computing devices or computing modules having one or more processors, memory, and interfaces. The processing components and respective interfaces may be interconnected by a network or bus to exchange data with each other and / or with a remote control unit or server. The transport device 200 may be configured to perform one or more steps of the method 100 as described with respect to Fig. 1. The transport device 200 may include one or more user interfaces, such as interfaces for configuration, monitoring, and controlling of the transport device 200, such touchscreen displays, web-based dashboards, or mobile apps, and the like, in any combination. An interaction with the transport device 200 is not limited to voice or touch or control panel or mobile phones / tablets / computers or any other connection. Rather, any suitable user interfaces may be used to enable input related to processing and configuration of the transport device and / or an associated functional devices 202.

[0084] The processing components may implement, for example, diagnostics and maintenance units, which may include built-in diagnostics for identifying issues and performing routine maintenance; security features, such as authentication and authorization mechanisms to prevent unauthorized access or operation; data logging and reporting to log data, such as sensor readings and operational statistics, for analysis and reporting; and / or autonomous behavior control units, which may allow the transport device 200 to operate autonomously, make decisions, and adapt to changing conditions.

[0085] The transport device 200 may have a mechanical design with a robust construction suitable for the healthcare application ecosystem and the payload capacity of the functional devices.

[0086] The transport device 200 may include a communication unit 204 that can be configured to receive a task from a task list specifying a target location for the functional device 202 in the healthcare application ecosystem. The communication unit 204 can employ any wired or wireless communication connection or link to receive data from an entity, computing device, or data base, which can be remote, such as in a cloud or on a server, or local to the healthcare application ecosystem. The network can be a local network, such as a WiFi or LAN, or a network covering a larger area, such as a MAN (Metropolitan Area Network) or WAN (Wide Area Network). The communication unit 204 may further ensure an integration into a centralized system implementing a transport management system, which may be local to the healthcare application ecosystem or remote. This may be used to receive tasks and send status updates.

[0087] Preferably, the transport device 200 may directly communicate with any of the functional devices 202 using the communication unit 204. Direct communication may omit any intermediate communication entity, such as an access point or router of a communication environment. This may enable the transport device 200 to maintain a communication link with the functional device 202 even if the communication environment cannot be accessed, such as in case of (power) failure or breakdown.

[0088] Embodiments of the present disclosure may also employ LoRaWAN (Long Range Wide Area Network) as network and communication technology. The technology may be particularly suited for the efficient and cost-effective creation of smart cities, buildings, and factories. Embodiments may provide LoRaWAN starter packages that enable users to use the Internet of Things (loT). Advantages of using LoRaWAN may include cost-effectiveness, excellent coverage, energy efficiency, ease of implementation, end-to-end encryption, and expandability for additional use cases, to name a few.

[0089] The transport device 200 may further include a navigation unit 206 configured to transport the functional device 202 to the target location specified in the task. The navigation unit 206 may employ a path planning approach to calculate an optimal path from the current location to a target destination, considering obstacles, safety constraints, and efficiency, to name a few factors, in any combination. The navigation unit 206 may interact with a control system that may be responsible for managing the transport device's motion, speed, and direction based on the calculated path and real-time sensor feedback.

[0090] The processing components of the transport device 200 may further include collision avoidance systems to prevent accidents, emergency stop buttons or mechanisms, and modules that may be configured to ensure compliance with safety standards and regulations.

[0091] The transport device 200 may further include an interface portion 208 configured to engage with the functional device. Even though Fig. 2 depicts an interface portion with two elements, it is to be understood that this is an example only and the present disclosure is not limited by a particular size and form of the interface portion 208. The interface portion 208 may use any kind of mechanical, electrical or magnetic means to engage with (or disengage) the functional device 202 to secure the functional device 202 for transport or deliver the functional device 202 at the target location. Depending on the application, the interface portion 208 of the transport device 200 may have custom attachments, such as lifting arms, conveyor belts, or specialized tooling for specific tasks.

[0092] The transport device 200 is depicted, as an example, with wheels or rolls. However, it is to be understood that this is an example only and the transport device 200 can use any other mode of transport, such as magnetic or hovering means similar to magnetic levitation devices or hovercraft devices. Transportation means may further include tracks or other means of locomotion designed for specific surfaces.

[0093] The transport device 200 may further include one or more sensors 210a, 210b. The sensors may include position sensors; accelerometers; laser-based sensors (lidars) that may provide 2D or 3D mapping of the environment, allowing the transport device 200 to detect obstacles and navigate the environment; optical sensors or vision systems, such as cameras, used for object recognition, navigation, and obstacle avoidance; ultrasonic sensors that may emit ultrasonic waves to measure distances to nearby objects and avoid collisions; infrared sensors; wheel sensors that may monitor wheel rotations for accurate distance measurement and odometry, and the like, in any combination. It is to be understood that the transport device 200 may include less or more that the two depicted sensors 210a, 201b, which may also be located at different locations, outside and inside of a body of the transport device 200.

[0094] The transport device 200 may be configured to perform mapping and localization tasks. This may include SLAM (Simultaneous Localization and Mapping) techniques, which enable the transport device 200 to create and update maps of its environment while simultaneously determining its own position within the environment. If the transport device 200 is configured to travel outside areas of the healthcare application ecosystem, GNSS could be used for outdoor navigation and localization.

[0095] The transport device 200 may further include various components and units, such as a power source (not shown), including batteries or other power sources that provide the energy needed for the transport device's operation, localization and positioning markers (not shown), such as beacons, QR codes, or other markers in the environment that help the transport device 200 navigate and determine its position, and the like, in any combination. The transport device 200 may further include a charging unit configured to charge the batteries or other power sources.

[0096] It is to be understood that Fig. 2 shows a schematic illustration of a transport device only and the present disclosure is not limited by the illustrated device, its form or arrangement of components. Embodiments may include variations, such as interface portions 208 that may be adapted to engage with the functional device 202, or further elements to enable the transport device 200 to perform the task of transporting functional devices in a healthcare application ecosystem.

[0097] Fig. 3 is a diagram of a system in accordance with an embodiment of the present disclosure.

[0098] The illustrated system 300 may be for deploying transport devices in one or more healthcare application ecosystems. The system 300 may include an interface module for providing data pertaining to characteristics of one or more healthcare application ecosystems and transport devices deployed in the one or more healthcare application ecosystems, including the transport devices in the healthcare application ecosystem.

[0099] The system 300 may maintain data indicating transportation requirements across the one or more healthcare application ecosystems and a device deployment optimizer may analyze several factors, such as location, status, and capabilities of the transport devices across the one or more healthcare application ecosystems, calculate at least one deployment strategy based on the current transportation requirements and the anticipated transportation requirements, and to allocate and route transport devices to the one or more healthcare application ecosystems according to the at least one deployment strategy.

[0100] Fig. 3 illustrates a healthcare facility 302 of the one or more healthcare application ecosystems and deployed transport devices 304a, 304b, 304c, . . ., 304n in the healthcare facility 302. Even though four transport devices are depicted, it is to be understood that the present disclosure is not limited by a number of transport devices and that more or less transport devices may be dispatched in the healthcare facility 302 depending on transportation requirements. One or more of the transport devices 304a, 304n may correspond to the transport device

[0101] 200 as depicted in Fig. 2.

[0102] The transport requirements and a task list may be stored in a data base 306 or any other data source, which may be located on-site in the healthcare facility 302 or in a remote location, such as in a cloud. The system 300 may retrieve the transport requirements and process the transport requirements to compile a task list. This can be performed by any suitable processing component, such as an optional on-site control component 308 or in a cloud-based processing component, or by a plurality of distributed processing components that may be interconnected and located at several locations, which may include processing components located in the individual transport devices 304a, . . ., 304n.

[0103] The transport devices 304a, ..., 304n may be configured to engage with functional devices 310a, 310b, ..., 310m deployed in the healthcare facility 302. Even though three functional devices are depicted in Fig. 3, it is to be understood that the present disclosure is not limited by a number of functional devices and that more or less transport devices may be present in the healthcare facility 302.

[0104] The processing component(s) 308 may access the compiled task list, which may include one or more tasks, each specifying a target location for a functional device in the healthcare facility 302. For example, a (first) task in the task list may include a target location 312a for the functional device 310a. Another (second) task in the task list may specify a target location 312m for the functional device 310m.

[0105] The processing component(s) 308 may associate a transport device with a functional unit to perform a task in the task list. For example, to complete the first task, transport device 304a may be associated with functional device 310a, and to complete the second task, transport device 304b may be associated with functional device 310m. If the current location of the transport device deviates from the current location of the associated functional device, the processing component(s) 308 may navigate the transport device to the current location of the functional device and engage the transport device with the functional device. Subsequently, the associated transport device may be used to transport the functional device to the target location specified in the task. For example, the transport device 304a may engage with functional device 310a and may transport the functional device 310a to the target location 312a. Similarly, the transport device 304b may engage with functional device 310m and may transport the functional device 310m to the target location 312m. Subsequently, the transport devices 304a, 304b may be assigned with another task of the task list.

[0106] As shown in Fig. 3, even though transport devices 304a, 304b may be assigned to individual functional units 310a, 310m, the ecosystem may include other functional devices, such as 310b, that may not have an assigned transport device. If the task list indicates a further task related to functional unit 310b, the system may associate a transport device with the functional unit 310b to perform the further task in the task list.

[0107] According to one or more preferred use cases, the functional device may be a self-automated (patient) bed, such as the functional device 310a. The self-automated bed may be designed to move on command without the need for human interaction, providing significant time and cost savings as well as convenient extended patient services. The self-automated bed can be used for daily operations, emergencies, or other special operations, and can be applied to all types of beds.

[0108] The technology used in the self-automated bed is not limited to remote or non-remote controlled, tracked or monitored beds, and can be communicated with in various ways. The term “self-automated” can be used throughout this disclosure as referring to autonomous, automat- ed-guided, self-driving, or driverless, or similar terms referring to processing without full human interaction.

[0109] It is to be understood that the functional devices, such as the self-automated bed, are independent of technical standards, norms or designs. Embodiments may include any kind of functional device, including existing functional devices.

[0110] The system 300 may be designed for hardware, software, mobility, central command operation center and communication to provide safe and secure operations using state-of-the-art standards and sustainable and efficient technology. The system 300 may include one or more of features for protecting an environment of transport devices, supporting modular concepts, allowing for easy adoption to future Smart Hospitals or Smart City applications. Embodiments of the present disclosure can be integrated into existing environments without interrupting current operations, processes or other intelligent projects. In a preferred embodiment, a central command operation center may be used for daily operations. The assignments of transport devices 304a, ..., 304n to functional devices 310a, 310b, ..., 310m and / or deployment of the transport devices to individual healthcare application ecosystems can be done with the highest safety options. The tasks can be run, for example, outside of speaking and visiting hours of patients / visitors in the healthcare facility. In every part of the healthcare facility 302, such as a wing, there can be a maximum number of transport devices in operation to ensure the availability of facility instalments, such as elevators. Every floor can carry a maximum of one transport device in operation, for example.

[0111] Patients and staff of the healthcare facility 302 can recognize visually and audible signals to understand when there is a transport device 304a, ..., 304n in action. Patients and staff of the healthcare facility 302 may have the opportunity to immediately stop a transport device in action via emergency buttons or remote controls. In case of doubts, all actions may stop according to the principle “humans first”. The central command operations center may guide the control of the transport device 304a, ..., 304n, and staff may have the authority via remote control to start / stop actions. The movement patterns within a healthcare application ecosystem may be standardized and simple to understand for humans to ensure the highest safety. The central command operation center can be integrated into existing logistic systems within a healthcare application ecosystem.

[0112] In a preferred use case, the system 300 may enhance safety standards for AGVs or AMRs used in intra-logistics. This can be achieved by safety functions, such as, safe stop and emergency stop, safe brake, safe parking and charging, safe speed supervision, and safe load handling. Requirements can be derived from IEC 61508 as the primary safety standard and ISO 13849 as the sector standard. The system 300 may employ a method for determining a required performance level (PLa-PLe) and SIL level (SIL1 - SIL4) based on a risk graph of the standards' required failure probabilities, required diagnostic coverage DC, and minimum level of performance needed. Further requirements can be derived from ISO 26262. ISO 26262 is an international standard for functional safety of electrical and / or electronic systems in production road vehicles, derived from the broader IEC 61508 standard but specifically tailored for automotive industry requirements. Furthermore, use cases of the present disclosure can apply Standard ISO 19649:2017, which provides definitions for terms associated with mobile robots that operate on solid surfaces, including both industrial and service robot applications. It clarifies the terms used to describe robot mobility, locomotion, and navigation.

[0113] In one or more use cases, applications within buildings may use AMRs as transport devices. The transport devices may be equipped with advanced sensors, artificial intelligence, machine learning, and a path-planning calculator. They may sense their surroundings and move independently through the environment without needing any changes for the infrastructure, such as fixed rails or tracks like QR codes, markings, magnetic strips, etc. and do not require operator monitoring. AMRs may differ from AGVs as they typically run on rails or fixed tracks and often require operator supervision.

[0114] In case of encountering obstacles, the transport devices 304a, ..., 304n can use navigation techniques to avoid them and continue the assigned task. Cameras and / or sensors (such as lidar) enable the transport devices to reduce their speed and choose an alternative path to navigate around objects or people on the route. Remote access can also be used to guide the navigation of the transport device.

[0115] For applications outside of buildings, the cameras and / or sensors (such as lidar) may be additionally triangulated by geo-specific data, which can be obtained via GNSS systems, such as GPS, GLONASS, Galileo, or BeiDou, to name a few, and fixed tracks (e.g. markings) may be designed, especially when people are to be transported, analogous to AGV technology. Additionally, cameras may observe movements from a camera close to the application setup, which may not be part of the respective transport device. The central control command center may control actions performed by the one or more transport devices.

[0116] In another embodiment, the system 300 may include a charging system in the healthcare facility 302, which can include a contactless charging systems. The transport devices 304a, ..., 304n may automatically receive energy they need for their transport tasks. Preferably, the transport devices 304a, ..., 304n do not have to interrupt their workflow for longer charging breaks. This can be achieved, for example, by using inductive charging. This can be a key to maximum productive automation and 24 / 7 operation of the systems 300. According to another embodiment, transport devices 304a, ..., 304n powered by Al may be equipped with advanced deep-learning algorithms that enhance their versatility, productivity, reliability, efficiency, and safety in collaborative environments. Al can be used to make one or more of safe routing, navigation, and maintenance decisions, predicting, optimizing, and ensuring efficient and safe operation, in any combination. Additionally, the transport devices 304a, ..., 304n can be trained on the job to accommodate new tasks as they arise. Dedicated operating area profiles may be created to ensure the highest level of safety. Detection technologies, such as lidar, cameras or sensors, enable mobile robots to collect real-time data from their environment, which Al algorithms process and analyze.

[0117] Embodiments may relate to transport devices 304a, ..., 304n fixed to a functional device, such as autonomous robot beds, equipped with real-time mapping capability for navigating complex and ever-changing infrastructures such as healthcare application ecosystems. The transport device can preferably autonomously adapt to environmental changes, avoid obstacles, optimize routes efficiently, and operate in dynamic and unpredictable environments. The transport devices 304a, ..., 304n may be equipped with advanced Al algorithms that allow them to calculate the most efficient routes in real-time for transporting from point A to point B in the healthcare facility 302, reducing waiting times and operational costs and increasing productivity. The transport devices 304a, ..., 304n may be designed to enhance operational efficiency and safety in healthcare application ecosystems inside and outside premises and can operate in areas with large crowds of people.

[0118] In one or more embodiments, the transport devices 304a, ..., 304n can detect early signs of failure by implementing Al predictive maintenance and plan maintenance stops to minimize unexpected downtime.

[0119] Preferably, the transport devices 304a, . . ., 304n may be set up to take on a range of tasks related to the functional devices 310a, 310b, ..., 310m, such as cleaning beds, assisting visitors, and escorting patients to appointments within the healthcare facility 302. The operating environment may be thoroughly assessed and secured in profiles. The profiles may be downloaded to the transport device once a task is assigned to ensure the utmost safety and efficiency.

[0120] In a preferred embodiment, the disclosure may encompass a processing device with a plurality of means that may be configured to perform functionality of embodiments of the present in- vention. In particular, the device may be configured for transporting functional devices in healthcare application ecosystems and may comprise means for providing one or more transport devices in a healthcare application ecosystem, the one or more transport devices configured to engage with functional devices deployed in the healthcare application ecosystem; means for accessing a task list, the task list including one or more tasks, each specifying a target location for a functional device in the healthcare application ecosystem; and means for controlling the one or more transport devices according to the task list, including, for a task of the one or more tasks, selecting a transport device of the one or more transport devices for a functional device specified in the task, engaging the transport device with the functional device, and transporting the functional device to the target location specified in the task using the transport device. Preferred embodiments of the device may include further means for implementing details of the first aspect and implementations thereof, and further embodiments as disclosed with regard to Fig. 1 to 3 and corresponding description, in any combination.

[0121] It is to be understood that the implementational details as provided in Fig. 1 to 3 represent preferred examples. Other implementations using different components, modules, blocks, units, circuitry, connections, and links can be used, and the present disclosure is not restricted by a particular implementation in silicon.

[0122] While some embodiments have been described in detail, it is to be understood that aspects of the disclosure can take many forms. In particular, the claimed subject matter may be practiced or implemented differently from the examples described, and the described features and characteristics may be practiced or implemented in any combination. The embodiments shown herein are intended to illustrate rather than to limit the invention as defined by the claims.

[0123] Embodiments of the present disclosure may be defined according to one or more of the following examples:

[0124] Example 1. A computer-implemented method for transporting functional devices in healthcare application ecosystems, comprising: providing one or more transport devices in a healthcare application ecosystem, the one or more transport devices configured to engage with functional devices deployed in the healthcare application ecosystem; accessing a task list, the task list including one or more tasks, each specifying a target location for a functional device in the healthcare application ecosystem; and controlling the one or more transport devices according to the task list, including, for a task of the one or more tasks, selecting a transport device of the one or more transport devices for a functional device specified in the task, engaging the transport device with the functional device, and transporting the functional device to the target location specified in the task using the transport device.

[0125] Example 2. The method of example 1, further comprising analyzing the task list to generate a task allocation table for the one or more transport devices, the task allocation table specifying tasks for the one or more transport devices, including respective functional devices and target locations specified in the task list.

[0126] Example 3. The method of example 1 or 2, further comprising identifying dependencies in the task list and defining an order of the one or more tasks according to the dependencies.

[0127] Example 4. The method according to any one of the preceding examples, further comprising determining an optimized route for the one or more transport devices based on current locations of the functional devices in the healthcare application ecosystem and target locations of the functional devices specified in the task list.

[0128] Example 5. The method according to any one of the preceding examples, wherein the transport unit and the functional device are connected with each other.

[0129] Example 6. The method according to any one of the preceding examples, further comprising navigating the transport device to a current location of the functional device.

[0130] Example 7. The method according to any one of the preceding examples, wherein said navigating includes using one or more sensors of the transport device to determine a current location of the transport device, and continuously adjusting a path of the transport device during navigation based on real-time feedback from the one or more sensors.

[0131] Example 8. The method according to any one of the preceding examples, wherein said navigating includes detecting moving objects using proximity sensors of the transport device in real-time, dynamically estimating trajectories of the moving objects, and adjusting a path of the transport device in real-time based on the estimated trajectories to avoid collisions. Example 9. The method according to any one of the preceding examples, further comprising logging information including detected moving objects and their trajectories and adjustments of the path of the transport device, and communicating the information to a control system to establish patterns of movement and activity zones within the healthcare application ecosystem.

[0132] Example 10. The method according to any one of the preceding examples, wherein said engaging includes detecting an identification of the functional device using one or more sensors of the transport device and determining a type of the functional device using the identification.

[0133] Example 11. The method according to any one of the preceding examples, wherein said engaging includes aligning the transport device with the functional device and engaging an interface portion of the transport device with the functional device.

[0134] Example 12. The method according to any one of the preceding examples, wherein the interface portion has a form adapted to the form of at least a part of the functional device.

[0135] Example 13. The method according to any one of the preceding examples, wherein said transporting includes adjusting, by an adaptive speed control system, a transport speed of the transport device based on a weight and size of the functional device.

[0136] Example 14. The method according to any one of the preceding examples, further comprising providing real-time feedback to the control system, including status and progress of transportation, and using the real-time feedback to dynamically adjust control of other transport devices.

[0137] Example 15. The method according to any one of the preceding examples, further comprising after reaching the target location, sending a task completion message to the control system.

[0138] Example 16. The method according to any one of the preceding examples, further comprising controlling the transport device to complete another task in the task list. Example 17. The method according to any one of the preceding examples, wherein the functional device provides a function in the healthcare application ecosystem.

[0139] Example 18. The method according to any one of the preceding examples, wherein the functional device is a bed.

[0140] Example 19. The method according to any one of the preceding examples, wherein the healthcare application ecosystem is a healthcare facility.

[0141] Example 20. One or more computer-readable media storing instructions thereon that, when executed by one or more computing devices, configure the one or more computing devices to perform a method according to any one of the preceding examples.

[0142] Example 21. A computing device, configured to perform a method according to any one of the examples 1 to 19.

[0143] Example 22. A transport device, configured to engage with functional devices deployed in a healthcare application ecosystem, the transport device comprising: a communication unit configured to receive a task from a task list specifying a target location for a functional device in the healthcare application ecosystem; a navigation unit configured to transport the functional device specified in the task to the target location specified in the task; and an interface portion configured to engage with the functional device.

[0144] Example 23. The transport device according to example 22, wherein the transport unit and the functional device are connected with each other.

[0145] Example 24. The transport device according to example 22 or 23, wherein the navigation unit is configured to navigate the transport device to a current location of the functional device.

[0146] Example 25. The transport device according to any one of the examples 22 to 24, wherein said navigation unit is configured to use one or more sensors of the transport device to determine a current location of the transport device and continuously adjust a path of the transport device during navigation based on real-time feedback from the one or more sensors. Example 26. The transport device according to any one of the examples 22 to 25, further comprising proximity sensors, wherein the navigation unit is configured to detect moving objects using the proximity sensors in real-time, dynamically estimate trajectories of the moving objects, and adjust a path of the transport device in real-time based on the estimated trajectories to avoid collisions.

[0147] Example 27. The transport device according to any one of the examples 22 to 26, wherein the communication unit is configured to log information including detected moving objects and their trajectories and adjustments of the path of the transport device, and communicate the information to a control system to establish patterns of movement and activity zones within the healthcare application ecosystem.

[0148] Example 28. The transport device according to any one of examples 22 to 27, wherein the interface portion has a form adapted to a form of at least a part of the functional device.

[0149] Example 29. The transport device according to any one of the examples 22 to 28, further comprising an adaptive speed control system configured to adjust a transport speed of the transport device based on a weight and size of the functional device.

[0150] Example 30. The transport device according to any one of the examples 22 to 29, wherein the communication unit is configured to send a task completion message after depositing the functional device at the target location.

[0151] Example 31. A system for deploying transport devices in a healthcare application ecosystem, the system comprising: an interface module configured to provide data pertaining to characteristics of one or more locations of a healthcare application ecosystem and transport devices deployed in the one or more locations; a transportation requirement processor coupled to the interface module, configured to receive current transportation requirements of the one or more locations of the healthcare application ecosystem, and to maintain data indicating anticipated transportation requirements across the one or more locations of the healthcare application ecosystem; a device deployment optimizer configured to analyze one or more of locations, status, and capabilities of the transport devices across the one or more locations of the healthcare application ecosystem, calculate at least one deployment strategy based on the current transportation requirements and the anticipated transportation requirements, and to allo- cate and route transport devices to the one or more locations according to the at least one deployment strategy.

Claims

CLAIMS1. A computer-implemented method for transporting functional devices in healthcare application ecosystems, comprising: providing one or more transport devices in a healthcare application ecosystem, the one or more transport devices configured to engage with functional devices deployed in the healthcare application ecosystem; accessing a task list, the task list including one or more tasks, each specifying a target location for a functional device in the healthcare application ecosystem; and controlling the one or more transport devices according to the task list, including, for a task of the one or more tasks, selecting a transport device of the one or more transport devices for a functional device specified in the task, engaging the transport device with the functional device, and transporting the functional device to the target location specified in the task using the transport device.

2. The method of claim 1, further comprising analyzing the task list to generate a task allocation table for the one or more transport devices, the task allocation table specifying tasks for the one or more transport devices, including respective functional devices and target locations specified in the task list.

3. The method of claim 1 or 2, further comprising identifying dependencies in the task list and defining an order of the one or more tasks according to the dependencies.

4. The method according to any one of the preceding claims, further comprising determining an optimized route for the one or more transport devices based on current locations of the functional devices in the healthcare application ecosystem and target locations of the functional devices specified in the task list.

5. The method according to any one of the preceding claims, wherein the transport unit and the functional device are connected with each other.

6. The method according to any one of the preceding claims, further comprising navigating the transport device to a current location of the functional device.

7. The method according to any one of the preceding claims, wherein said navigating includes using one or more sensors of the transport device to determine a current location of the transport device, and continuously adjusting a path of the transport device during navigation based on real-time feedback from the one or more sensors.

8. The method according to any one of the preceding claims, wherein said navigating includes detecting moving objects using proximity sensors of the transport device in real-time, dynamically estimating trajectories of the moving objects, and adjusting a path of the transport device in real-time based on the estimated trajectories to avoid collisions.

9. The method according to any one of the preceding claims, further comprising logging information including detected moving objects and their trajectories and adjustments of the path of the transport device, and communicating the information to a control system to establish patterns of movement and activity zones within the healthcare application ecosystem.

10. The method according to any one of the preceding claims, wherein said engaging includes detecting an identification of the functional device using one or more sensors of the transport device and determining a type of the functional device using the identification.

11. The method according to any one of the preceding claims, wherein said engaging includes aligning the transport device with the functional device and engaging an interface portion of the transport device with the functional device.

12. The method according to any one of the preceding claims, wherein the interface portion has a form adapted to the form of at least a part of the functional device.

13. The method according to any one of the preceding claims, wherein said transporting includes adjusting, by an adaptive speed control system, a transport speed of the transport device based on a weight and size of the functional device.

14. The method according to any one of the preceding claims, further comprising providing real-time feedback to the control system, including status and progress of transportation, and using the real-time feedback to dynamically adjust control of other transport devices.

15. The method according to any one of the preceding claims, further comprising after reaching the target location, sending a task completion message to the control system.

16. The method according to any one of the preceding claims, further comprising controlling the transport device to complete another task in the task list.

17. The method according to any one of the preceding claims, wherein the functional device provides a function in the healthcare application ecosystem.

18. The method according to any one of the preceding claims, wherein the functional device is a bed.

19. The method according to any one of the preceding claims, wherein the healthcare application ecosystem is a healthcare facility.

20. One or more computer-readable media storing instructions thereon that, when executed by one or more computing devices, configure the one or more computing devices to perform a method according to any one of the preceding claims.

21. A computing device, configured to perform a method according to any one of the claims 1 to 19.

22. A transport device, configured to engage with functional devices deployed in a healthcare application ecosystem, the transport device comprising: a communication unit configured to receive a task from a task list specifying a target location for a functional device in the healthcare application ecosystem; a navigation unit configured to transport the functional device specified in the task to the target location specified in the task; and an interface portion configured to engage with the functional device.

23. The transport device according to claim 22, wherein the transport unit and the functional device are connected with each other.

24. The transport device according to claim 22 or 23, wherein the navigation unit is configured to navigate the transport device to a current location of the functional device.

25. The transport device according to any one of the claims 22 to 24, wherein said navigation unit is configured to use one or more sensors of the transport device to determine a current location of the transport device and continuously adjust a path of the transport device during navigation based on real-time feedback from the one or more sensors.

26. The transport device according to any one of the claims 22 to 25, further comprising proximity sensors, wherein the navigation unit is configured to detect moving objects using the proximity sensors in real-time, dynamically estimate trajectories of the moving objects, and adjust a path of the transport device in real-time based on the estimated trajectories to avoid collisions.

27. The transport device according to any one of the claims 22 to 26, wherein the communication unit is configured to log information including detected moving objects and their trajectories and adjustments of the path of the transport device, and communicate the information to a control system to establish patterns of movement and activity zones within the healthcare application ecosystem.

28. The transport device according to any one of claims 22 to 27, wherein the interface portion has a form adapted to a form of at least a part of the functional device.

29. The transport device according to any one of the claims 22 to 28, further comprising an adaptive speed control system configured to adjust a transport speed of the transport device based on a weight and size of the functional device.

30. The transport device according to any one of the claims 22 to 29, wherein the communication unit is configured to send a task completion message after depositing the functional device at the target location.

31. A system for deploying transport devices in a healthcare application ecosystem, the system comprising: an interface module configured to provide data pertaining to characteristics of one or more locations of a healthcare application ecosystem and transport devices deployed in the one or more locations; a transportation requirement processor coupled to the interface module, configured to receive current transportation requirements of the one or more locations of the healthcare application ecosystem, and to maintain data indicating anticipated transportation requirements across the one or more locations of the healthcare application ecosystem; a device deployment optimizer configured to analyze one or more of locations, status, and capabilities of the transport devices across the one or more locations of the healthcare application ecosystem, calculate at least one deployment strategy based on the current transportation requirements and the anticipated transportation requirements, and to allocate and route transport devices to the one or more locations according to the at least one deployment strategy.

Citation Information

Patent Citations

  • Robotic transportation devices and systems

    US20120029697A1

  • Transport system, transport method, and program

    US20220208328A1

  • Transportation device, coupling assembly for affixing onto a movable device, and method of driving a movable device

    WO2023208621A1

Cited By

  • Stacker multi-roadway orbital transfer scheduling method and system

    CN121504326A