Medical service method and system

Abstract

The invention provides a medical service system and method. The system comprises a hardware device and a processing device. The hardware device is configured to collect data related to physical entities of a physical hospital. The processing equipment is configured to map the data to a virtual hospital corresponding to a physical hospital; and providing user services to related users of the physical hospital through the user space application. The virtual hospital comprises an intelligent agent, and the intelligent agent achieves self-evolution based on the data and the artificial intelligence technology. The user space application is configured to provide a relevant user of the physical hospital with an access portal to interact with the agent, and at least a portion of the user service is provided to the relevant user based on the interaction between the relevant user and the agent.

Description

Case Analysis

[0001] This application is a divisional application of Chinese application filed on September 30, 2024, with application number 202411386522.X, entitled "Medical Service Method and System". The aforementioned Chinese application claims priority to international application filed on July 31, 2024, with application number PCT / CN2024 / 109056, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This specification relates to the field of healthcare services, and in particular to a healthcare service system and method built on XR technology, AI technology and / or other pioneering technologies. Background Technology

[0003] Currently, when patients require multiple medical services in a hospital, they face complex and fragmented service processes. This is both cumbersome and time-consuming for patients, making it more difficult for them to understand the procedures and identify appropriate facilities. Consequently, the overall efficiency of healthcare services is reduced. Furthermore, this complexity presents significant challenges for hospital staff in providing medical services and managing related medical resources.

[0004] The rapid development of cutting-edge technologies, such as extended reality (XR) technologies (e.g., augmented reality (AR), virtual reality (VR), mixed reality (MR), etc.), artificial intelligence (AI), digital twins, the Internet of Things (IoT), blockchain, spatial computing, and image rendering, has already triggered transformative changes and brought substantial benefits to various systems. However, despite these advancements, the full utilization of these innovative technologies in hospital systems has not yet been achieved. Therefore, there is a need to develop healthcare service systems and methods that integrate these advanced technologies to improve service efficiency, accuracy, and patient satisfaction (e.g., patient experience, especially immersive healthcare experiences). Summary of the Invention

[0005] One aspect of this specification provides a medical service system. The medical service system may include hardware devices and processing devices. The hardware devices may be configured to collect data related to a physical hospital. The processing devices are configured to map the data related to the physical hospital to a virtual hospital corresponding to the physical hospital, and to provide user services to relevant users of the physical hospital through a user space application. The user space application is configured to provide relevant users of the physical hospital with an access point for interacting with the virtual hospital, and to provide at least a portion of the user services to relevant users based on the interaction between the relevant users and the virtual hospital.

[0006] One aspect of this specification provides a medical service system. The medical service system may include hardware devices and processing devices. The hardware devices may be configured to collect data related to a physical hospital. The processing devices may be configured to maintain digital intelligent objects and provide user services to relevant users of the physical hospital through user-space applications, enabling the digital intelligent objects to participate in the processing of data related to the physical hospital.

[0007] One aspect of this specification provides a healthcare service system. The system includes hardware and processing devices. The hardware is configured to collect data related to a physical entity of a physical hospital, the physical entity including at least the physical hospital's hardware and healthcare service processes. The processing device is configured to map the data to a virtual hospital corresponding to the physical hospital; and to provide user services to relevant users of the physical hospital via a user-space application. The virtual hospital includes a digital twin corresponding to the physical entity of the physical hospital, at least a portion of which is updated during the data mapping process. The user-space application is configured to provide relevant users of the physical hospital with access to interact with the virtual hospital, at least a portion of the user services being provided to the relevant users based on interactions between the relevant users and at least one digital twin.

[0008] One aspect of this specification provides a healthcare service system. The system includes hardware and processing devices. The hardware is configured to collect data related to the physical entity of a physical hospital. The processing device is configured to map the data to a virtual hospital corresponding to the physical hospital and to provide user services to relevant users of the physical hospital via a user space application. The virtual hospital includes an intelligent agent that self-evolves based on the data and artificial intelligence (AI) technology. The user space application is configured to provide relevant users of the physical hospital with access to interact with the intelligent agent, and at least a portion of the user services are provided to the relevant users based on the interaction between the relevant users and the intelligent agent.

[0009] Additional features will be set forth in the description below, and some of these additional features will be apparent to those skilled in the art from the study of the following description and the accompanying drawings, or from an understanding of the production or operation of the embodiments. The features of this application can be implemented and achieved through the practice or use of various methods, means, and combinations thereof with respect to the specific embodiments described below. Attached Figure Description

[0010] This application is further described with reference to exemplary embodiments. These exemplary embodiments are described in detail with reference to the accompanying drawings. These embodiments are non-limiting exemplary embodiments, wherein the same reference numerals denote similar structures throughout multiple views of the figures, and wherein:

[0011] Figure 1 This is a block diagram of an exemplary medical service system according to some embodiments of this application;

[0012] Figure 2 These are schematic diagrams of exemplary medical service systems according to some embodiments of this application;

[0013] Figure 3 This is a schematic diagram of an exemplary hospital support platform according to some embodiments of this application;

[0014] Figure 4 This is a block diagram of an exemplary processing apparatus according to some embodiments of this application;

[0015] Figure 5 These are schematic diagrams illustrating exemplary processes for providing user services according to some embodiments of this application;

[0016] Figure 6 These are schematic diagrams illustrating exemplary processes for providing user services according to some embodiments of this application;

[0017] Figure 7 This is a flowchart illustrating an exemplary process for providing user services according to some embodiments of this application;

[0018] Figure 8 These are schematic diagrams illustrating exemplary medical treatment processes according to some embodiments of this application;

[0019] Figure 9 This is a schematic diagram illustrating an exemplary process for providing pre-consultation services according to some embodiments of this application;

[0020] Figure 10 This is a flowchart illustrating an exemplary process for making a second inquiry according to some embodiments of this application;

[0021] Figure 11 This is a flowchart illustrating an exemplary process for providing medical outpatient services based on perceived information, according to some embodiments of this application;

[0022] Figure 12 These are schematic diagrams of exemplary medical consultation interfaces shown in some embodiments of this application;

[0023] Figure 13 This is a schematic diagram illustrating an exemplary hospitalization process according to some embodiments of this application;

[0024] Figure 14 This is a flowchart illustrating an exemplary process for providing inpatient services according to some embodiments of this application;

[0025] Figure 15This is a schematic diagram illustrating an exemplary process for providing nursing services according to some embodiments of this application;

[0026] Figure 16 These are exemplary schematic diagrams illustrating a process for surgical planning and execution according to some embodiments of this application;

[0027] Figure 17 This is a schematic diagram illustrating an exemplary process of preoperative education according to some embodiments of this application;

[0028] Figure 18 These are schematic diagrams illustrating exemplary preoperative guidance according to some embodiments of this application;

[0029] Figure 19 This is a schematic diagram illustrating an exemplary surgical procedure according to some embodiments of this application;

[0030] Figure 20 These are schematic diagrams illustrating exemplary medical service processes according to some embodiments of this application;

[0031] Figure 21 This is a schematic diagram illustrating an exemplary process for determining a target step according to some embodiments of this application;

[0032] Figure 22 This is a schematic diagram illustrating an exemplary first preset operation according to some embodiments of this application;

[0033] Figure 23 This is a schematic flowchart illustrating an exemplary process for assisting a doctor's work, as shown in some embodiments of this application;

[0034] Figure 24 These are schematic diagrams of exemplary interactive interfaces shown according to some embodiments of this application; and

[0035] Figure 25 This is a schematic diagram of an exemplary system for hospital management according to some embodiments of this application. Detailed Implementation

[0036] In the following detailed description, numerous specific details are set forth by way of example in order to provide a thorough understanding of the relevant disclosure. However, it will be apparent to those skilled in the art that this specification may be practiced without these details. In other instances, well-known methods, processes, systems, components, and / or circuits have been described at a higher level to avoid unnecessarily obscuring various aspects of this application. Various modifications to the disclosed embodiments will be apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments and applications without departing from the spirit and scope of this specification. Therefore, this specification is not limited to the embodiments shown, but is accorded the widest scope consistent with the claims.

[0037] The terminology used in this specification is for describing particular exemplary embodiments only and is not intended to be limiting. As used herein, the singular forms “a,” “an,” and “the” are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the terms “comprising” and / or “including”, as used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not exclude the possibility of the presence and addition of at least one other feature, integer, step, operation, element, component, and / or combination thereof.

[0038] It should be understood that when a unit, engine, module, or block is referred to as being "in," "connected to," or "coupled to" another unit, engine, module, or block, it may be directly in connection with or coupled to the other unit, engine, module, or block, or communicate with other units, engines, modules, or blocks, or there may be intermediate units, engines, modules, or blocks, unless the context clearly indicates otherwise. As used in this specification, the term "and / or" includes any and all combinations of at least one of the related listed items.

[0039] The features and characteristics of this specification, as well as the operation and function of the related structural elements, and the economic efficiency of the combination and manufacture of the components, will become more apparent upon consideration of the following description. All accompanying drawings form part of this specification. However, it should be clearly understood that the drawings are for illustrative and descriptive purposes only and are not intended to limit the scope of this specification. It should be understood that the drawings are not drawn to scale.

[0040] Figure 1 This is a block diagram of an exemplary medical service system 100 according to some embodiments of this application.

[0041] The Medical Service System 100, also known as the Meta-Hospital System, is built upon a variety of innovative technologies, including metaverse technology, XR technology (e.g., AR, VR, MR), AI technology, digital twin technology, IoT technology, data circulation technology (e.g., blockchain technology, data privacy computing technology), spatial computing technology, and image rendering technology.

[0042] like Figure 1 As shown, the medical service system 100 may include a physical hospital 110, a virtual hospital 130, a user space application 120, and a hospital support platform 140. In some embodiments, the hospital support platform 140 may map data related to the physical hospital 110 to the virtual hospital 130 corresponding to the physical hospital 110, and provide user services to relevant users of the physical hospital 110 through the user space application 120. For example, at least some user services may be provided to relevant users based on the interaction between relevant users and the virtual hospital 130.

[0043] A physical hospital (110) refers to a hospital that exists in the physical world and possesses tangible attributes (e.g., measurable attributes such as mass, volume, and shape, which can be perceived by human senses or instruments). In this article, healthcare institutions that provide medical, surgical, and psychiatric care and treatment are collectively referred to as hospitals.

[0044] like Figure 1 As shown, a physical hospital 110 may include multiple physical entities. For example, multiple physical entities may include departments, users, hardware equipment, user services, public areas, medical service processes, etc., or any combination thereof.

[0045] A department is a specialized unit or department that provides a particular type of medical care, treatment, and services. Each department may focus on a specific medical area and may be staffed with healthcare professionals specializing in that area. For example, depending on the medical service process corresponding to each department, a department may include outpatient departments, inpatient departments, surgical departments, support departments (e.g., registration departments, pharmacy departments), etc., or any combination thereof. As another example, depending on the medical field corresponding to each department, a department may include internal medicine, surgery, specialty medicine, pediatric health care, etc., or any combination thereof.

[0046] Users can include any user associated with Physical Hospital 110 (or referred to as a user related to Physical Hospital 110). For example, users can include patients (or parts of patients, such as organs), companions, visitors to patients, hospital staff of Physical Hospital 110, suppliers of Physical Hospital 110, application developers of Physical Hospital 110, etc., or any combination thereof. Hospital staff of Physical Hospital 110 can include healthcare providers (e.g., doctors, nurses, technicians, etc.), hospital administrators, support staff, or similar personnel, or any combination thereof. Exemplary hospital administrators can include ward nursing administrators, clinical administrators, ward directors, hospital directors, hospital administrators, functional administrators, or similar personnel, or any combination thereof.

[0047] The hardware devices may include hardware devices located in the physical hospital 110 and / or hardware devices communicating with hardware devices in the physical hospital 110. Exemplary hardware devices may include terminal devices, medical service devices, sensing devices, infrastructure devices, etc., or any combination thereof.

[0048] Terminal devices may include terminal devices that interact with users of the healthcare service system 100. For example, terminal devices may include terminal devices that interact with patients (also called patient terminals), terminal devices that interact with doctors (also called doctor terminals), terminal equipment that interacts with nurses (also called nurse terminals), terminal devices that interact with remote visitors (also called remote terminal devices), or public terminals in the hospital (e.g., clinic terminals, bedside terminal devices, terminal devices in waiting areas, smart surgical terminals), etc., or any combination thereof. In this application, unless clearly obtained from the context or otherwise specified, terminal devices owned by the user and terminal devices provided to the user by the physical hospital 110 will be collectively referred to as user terminal devices or user-interacting terminal devices.

[0049] Terminal devices may include mobile terminals, XR devices, smart wearable devices, etc. Mobile terminals may include smartphones, personal digital assistants (PDAs), displays, gaming devices, navigation devices, handheld terminals (POS), tablets, etc., or any combination thereof.

[0050] XR devices can include devices that allow users to participate in extended reality experiences. For example, XR devices can include VR components, AR components, MR components, etc., or any combination thereof. In some embodiments, XR devices can include XR headsets, XR glasses, XR patches, stereo headphones, etc., or any combination thereof. For example, XR devices can include Google Glass. TM Oculus Rift TM GearVR TM AppleVisionproTM Specifically, an XR device may include a display component on which virtual content can be presented and / or displayed. In some embodiments, the XR device may further include an input component. The input component enables user interaction between the user and the virtual content (e.g., a virtual surgical environment) displayed on the display component. For example, the input component may include a touch sensor, microphone, image sensor, etc., configured to receive user input, which can be provided to the XR device and used to control the virtual world by changing the visual content presented on the display component. The input component may include a handle, glove, stylus, console, etc.

[0051] Smart wearable devices may include smart bracelets, smart shoes and socks, smart glasses, smart helmets, smartwatches, smart clothing, smart backpacks, smart accessories, and any combination thereof. In some embodiments, smart wearable devices may acquire a user's physiological data (e.g., heart rate, blood pressure, body temperature, etc.).

[0052] Medical service equipment can be configured to provide medical services to patients. For example, medical service equipment may include examination equipment, nursing equipment, treatment equipment, or any combination thereof.

[0053] The examination equipment can be configured to provide examination services to patients, such as collecting patient examination data. Exemplary examination data may include heart rate, respiratory rate, body temperature, blood pressure, medical imaging data, fluid test reports (e.g., blood test reports), or any combination thereof. Accordingly, the examination equipment may include vital sign monitors (e.g., blood pressure monitors, blood glucose meters, heart rate monitors, thermometers, digital stethoscopes, etc.), medical imaging equipment (e.g., computed tomography (CT) equipment, digital subtraction angiography (DSA) equipment, magnetic resonance (MR) equipment, etc.), laboratory equipment (e.g., routine blood test equipment, etc.) or any combination thereof.

[0054] Nursing devices can be configured to provide nursing services to patients and / or assist healthcare providers in providing nursing services. Exemplary nursing devices may include hospital beds, patient care robots, smart nursing carts, smart medicine boxes, smart wheelchairs, etc.

[0055] Treatment devices can be configured to provide treatment services to patients and / or assist healthcare providers in providing treatment services. Exemplary treatment devices may include surgical equipment, radiation therapy equipment, physical therapy equipment, etc., or any combination thereof.

[0056] Sensing devices can be configured to acquire sensory information related to their environment. For example, sensing devices may include image sensors, sound sensors, etc. Image sensors can be configured to acquire image data in a physical hospital 110, and sound sensors can be configured to acquire voice signals in a physical hospital 110. In some embodiments, sensing devices can be standalone devices or integrated into another device. For example, a sound sensor can be part of a medical service device.

[0057] Basic infrastructure can be configured to support data transmission, storage, and processing. For example, basic infrastructure may include networks, data center facilities, computing devices, computing chips, storage devices, etc.

[0058] In some embodiments, at least a portion of the hardware of the physical hospital 110 is Internet of Things (IoT) devices. IoT devices are devices with sensors, processing capabilities, software, and other technologies that connect and exchange data with other devices and systems via the Internet or other communication networks. For example, one or more medical service devices and / or sensing devices of the physical hospital 110 are IoT devices and are configured to transmit collected data to the hospital support platform 140 for storage and / or processing.

[0059] User services may include any services provided to users by the hospital support platform 140. For example, user services may include medical services provided to patients and / or accompanying persons, support services provided to staff and / or suppliers of the physical hospital 110, etc. In some embodiments, user services may be provided to patients, doctors, and hospital administrators through the user space application 120, which will be described in detail below.

[0060] Public areas refer to shared spaces accessible to users (or some users) within a physical hospital 110, and may also be referred to as the environment of the physical hospital 110. For example, public areas may include reception areas (e.g., front desk), waiting areas, corridors and hallways, or any combination thereof.

[0061] A medical service process refers to the process of providing corresponding medical services to patients. A medical service process typically includes several steps and / or stages through which users must go to obtain the corresponding medical services. Exemplary medical service processes may include outpatient processes, inpatient processes, surgical processes, or similar processes, or any combination thereof. In some embodiments, a medical service process may include medical service processes corresponding to different departments, different diseases, etc. In some embodiments, a preset data collection protocol may be set, and the standard stages involved in the medical service process and how to collect data related to the medical service process may be specified. Further descriptions of medical service processes can be found elsewhere in this application. For example, see [link to relevant documentation]. Figure 5 And its related descriptions.

[0062] User space application 120 provides users with access to user services provided by hospital support platform 140. User space application 120 can be an application, plugin, website, app, or any other suitable form. For example, user space application 120 is an application installed on a user's terminal device, which includes a user interface for users to initiate requests and receive corresponding services.

[0063] In some embodiments, the user space application 120 may include different applications corresponding to different types of users. For example, the user space application 120 may include a patient space application corresponding to a patient, a medical space application corresponding to a doctor, a management space application corresponding to an administrator, or any combination thereof. The user services provided through the patient space application, medical space application, and management space application are also referred to as patient space services, medical space services, and management space services, respectively. Exemplary patient space services include registration services, route guidance services, pre-consultation services, remote consultation services, inpatient services, and discharge services. Exemplary medical space services include scheduling services, surgical planning services, surgical simulation services, patient management services, remote ward rounds services, and remote outpatient services. Exemplary administrator space services include monitoring services, medical service evaluation services, equipment parameter setting services, service parameter setting services, and resource scheduling services.

[0064] In some embodiments, the patient space application, medical space application, and management space application can be integrated into a single user space application 120, and the user space application 120 can be configured to provide access points for each type of user (e.g., patients, healthcare providers, administrators, etc.). As an example only, a specific user can have a corresponding account, which can be used to log in to the user space application, view relevant medical data, and obtain corresponding user services.

[0065] According to some embodiments of this application, by providing user space applications for different types of users, each type of user can easily obtain various user services that he / she may need on their respective user space application. Furthermore, currently users typically need to install various applications to obtain different user services, which leads to poor user experience and high development costs. Therefore, the user space application of this application can improve user experience, enhance service quality and efficiency, strengthen service security, and reduce development or operating costs.

[0066] In some embodiments, the user space application 120 can be configured to provide relevant users of the physical hospital 110 with an access point to interact with the virtual hospital 130. For example, through the user space application 120, users can enter instructions to retrieve digital content of the virtual hospital 130 (e.g., digital twin models of hardware devices, patient organs, and public areas), view digital content, and interact with digital content. As another example, through the user space application 120, users can communicate with virtual characters representing intelligent agents. In some embodiments, the hospital's public terminals can have a management space application installed, and administrator accounts for the corresponding departments of the public terminals can be logged into the management space application. Users can receive user services through the management space application installed on the public terminals.

[0067] Virtual hospital 130 is a digital twin (i.e., a virtual representation or virtual copy) of physical hospital 110, used to simulate, analyze, predict, and optimize the operational status of physical hospital 110. For example, virtual hospital 130 can be a real-time digital copy of physical hospital 110.

[0068] In some embodiments, digital technologies can be used to present the virtual hospital 130 to a user. For example, when a user interacts with the virtual hospital 130, XR technology can be used to present at least a portion of the virtual hospital 130 to the user. By way of example only, MR technology can be used to overlay at least a portion of the virtual hospital 130 onto the user's real-world view.

[0069] In some embodiments, the virtual hospital 130 may include digital twins of physical entities associated with the physical hospital 110. A digital twin is a virtual representation of a physical entity (e.g., a virtual copy, a mapping, a digital simulator). The digital twin can reflect and predict the state, behavior, and performance of the physical entity in real time. For example, the virtual hospital 130 may include digital twins of at least a portion of the physical hospital 110's medical services, departments, users, hardware equipment, user services, public areas, and medical service processes. Digital twins of physical entities can take various forms, including models, images, graphics, text, and numerical values. For example, a digital twin may be a virtual hospital corresponding to a physical hospital, virtual personnel (e.g., virtual doctors, virtual nurses, and virtual patients) corresponding to personnel entities (e.g., doctors, nurses, and patients), and virtual equipment (e.g., virtual imaging equipment and virtual scalpels) corresponding to medical service equipment (e.g., imaging equipment and scalpels).

[0070] In some embodiments, a digital twin may include one or more first digital twins and / or one or more second digital twins. The state of each first digital twin may be updated based on updates to the state of the corresponding physical entity. For example, in the process of mapping data associated with a physical hospital 110 to a virtual hospital 130, one or more first digital twins may be updated. One or more second digital twins may be updated through at least one of user-space applications 120, and an update to each second digital twin may result in an update to the state of the corresponding physical entity. In other words, when the state of the corresponding physical entity changes, the first digital twin may be updated accordingly; when the second digital twin is updated, the state of the corresponding physical entity also changes. For example, one or more first digital twins may include digital twins of public areas, medical services, users, hardware devices, etc., and one or more second digital twins may include digital twins of hardware devices, user services, medical service processes, etc. It should be understood that a digital twin may be either a first digital twin or a second digital twin.

[0071] According to some embodiments of this application, by generating a virtual hospital 130 that includes a digital twin of the physical entity associated with the physical hospital 110, the physical hospital 110 (including hardware equipment, users, user services, medical service processes, etc.) can be simulated and tested in a safe and controlled environment. Through virtual reality linkage (e.g., real-time interaction between the physical hospital 110 and the virtual hospital 130), various medical scenarios can be predicted and responded to more accurately, thereby improving the quality and efficiency of medical services. Furthermore, the application of XR technology and virtual reality integration technology makes the interaction of relevant users more natural and intuitive, providing a more comfortable and efficient medical environment, thereby enhancing the user experience.

[0072] In some embodiments, the virtual hospital 130 may further include an intelligent agent that can self-evolve based on data related to the physical hospital 110 and AI technology.

[0073] An intelligent agent is an agent that acts intelligently. For example, an intelligent agent can include a computing / software entity that can autonomously learn and evolve, and perceive and analyze data to perform specific tasks and / or achieve specific goals (e.g., healthcare service processes). Through AI technologies (e.g., reinforcement learning, deep learning, etc.), intelligent agents can continuously learn and self-optimize through interactions with their environment. Furthermore, intelligent agents can collect and analyze massive amounts of data (e.g., data related to physical hospital emergency services) using big data technologies, and mine patterns and learn rules from the data to optimize decision-making processes, thereby identifying environmental changes in uncertain or dynamic environments, responding quickly, and making reasonable judgments. For example, an intelligent agent can autonomously learn and evolve based on AI technology to adapt to changes in physical hospital emergency services. As an example only, an intelligent agent can be built based on NLP technologies (e.g., large language models, etc.) and can automatically learn and autonomously update through large amounts of linguistic text (e.g., hospital business data and patient feedback information) to improve the quality of user services provided by physical hospital emergency services.

[0074] In some embodiments, intelligent agents may include different types of intelligent agents corresponding to different medical service processes, different user services, different departments, different diseases, different hospital positions (e.g., nurses, doctors, technicians, etc.), and different stages of medical service processes. Specific types of intelligent agents are used to handle tasks corresponding to their specific types. In some embodiments, an intelligent agent may correspond to different medical service processes (or different medical services, or different departments, or different diseases, or different hospital locations). In some embodiments, intelligent agents may operate by referring to basic configuration data (e.g., dictionaries, knowledge graphs, templates, etc.) corresponding to the department and / or disease of the intelligent agent. In some embodiments, multiple intelligent agents can collaborate and share information through network communication to jointly complete complex tasks.

[0075] In some embodiments, the configuration of the intelligent agent can be set. For example, basic configuration data used by the intelligent agent in operation can be set. Basic configuration data may include dictionaries, knowledge databases, templates, etc. Furthermore, the usage permissions of the intelligent agent can be set for different users. In some embodiments, the administrator of the physical hospital 110 can set the configuration of the intelligent agent through a management space application.

[0076] In some embodiments, the intelligent agent can be integrated into or deployed on a hardware device. For example, an intelligent agent corresponding to inpatient services can be integrated into a hospital bed or a presentation device for a hospital bed. In some embodiments, the intelligent agent can be integrated into or deployed on an embodied intelligent robot. An embodied intelligent robot is a robotic system that combines physical presence (manifestation) with intelligent behavior (cognition). Embodied intelligent robots can be configured to interact with the real world in a way that mimics or complements human capabilities, utilizing physical form and cognitive functions to perform tasks, make decisions, and adapt to the environment. By utilizing artificial intelligence and sensor technology, embodied intelligent robots can operate autonomously, interact with the environment, and continuously improve their performance. For example, an embodied intelligent robot can be configured with an intelligent agent corresponding to surgical services and assist doctors in performing surgery.

[0077] In some embodiments, at least a portion of user services can be provided based on intelligent agents. For example, at least a portion of user services can be provided to relevant users based on processing results, wherein the processing results are generated by at least one intelligent agent based on data related to the physical hospital 110. As an example only, the data related to the physical hospital 110 may include data related to the medical service processes of the physical hospital 110, the intelligent agents may include intelligent agents corresponding to the medical service processes, and user services can be provided to relevant users of the medical service processes by processing data using the intelligent agents corresponding to the medical service processes.

[0078] The hospital support platform 140 can be configured to provide technical support to the healthcare service system 100. For example, the hospital support platform 140 may include computing hardware and software to support innovative technologies, including XR technology, AI technology, digital twin technology, data flow technology, etc. In some embodiments, the hospital support platform 140 may include at least a storage device for data storage and a processing device for data computation.

[0079] In some embodiments, the hospital support platform 140 can support interaction between a physical hospital 110 and a virtual hospital 130. For example, the processing device of the hospital support platform 140 can acquire data related to the physical hospital 110 from hardware devices and map the data related to the physical hospital 110 into the virtual hospital 130. For example, the processing device of the hospital support platform 140 can update a portion of the digital twin in the virtual hospital 130 (e.g., one or more first digital twins) based on the acquired data, so that each portion of the digital twin in the virtual hospital 130 can reflect the updated status of the corresponding physical entity in the physical hospital 110. Based on this digital twin that is constantly updated with the corresponding physical entity, the user can understand the status of the physical entity related to the physical hospital 110 in real time, thereby enabling the monitoring and evaluation of the physical entity. As another example, the agent corresponding to the data related to the physical hospital 110 can be trained and / or updated based on the data related to the physical hospital 110, thereby self-evolving and self-learning.

[0080] In some embodiments, the hospital support platform 140 can support and / or provide user services to relevant users of the physical hospital 110. For example, in response to receiving a user service request from a user, the processing device of the hospital support platform 140 can provide the user service corresponding to the service request. Alternatively, in response to detecting that a user service needs to be provided to a user, the processing device of the hospital support platform 140 can control a physical or virtual entity corresponding to the user service to provide that service. For example, in response to detecting that a patient has been admitted to a hospital ward, the processing device of the hospital support platform 140 can control a smart nursing cart to guide a nurse to the hospital ward to conduct admission examinations on the patient.

[0081] In some embodiments, at least some user services may be provided to the relevant user based on the interaction between the relevant user and the virtual hospital 130. Interaction refers to the interaction or influence (e.g., dialogue, behavior, etc.) between the relevant user and the virtual hospital 130. For example, the interaction between the relevant user and the virtual hospital 130 may include the interaction between the relevant user and a digital twin in the virtual hospital 130, the interaction between the relevant user and an intelligent agent, the interaction between the relevant user and a virtual character, or any combination thereof.

[0082] In some embodiments, at least a portion of user services can be provided to a relevant user based on the interaction between the relevant user and at least one of the digital twins. For example, an update instruction for a second digital twin input by a relevant user can be received through the user space application 120, and the corresponding physical entity of the second digital twin can be updated according to the update instruction. As another example, a user can view a first digital twin of a physical entity (e.g., a 3D digital twin model of a patient's organ or hardware device) through the user space application 120 to understand the state of the physical entity. Optionally, the user can change the display angle, display size, etc. of the digital twin. Further descriptions of digital twins of physical entities can be found elsewhere in this application (e.g., Figure 25 (and related descriptions).

[0083] In some embodiments, the processing device of the hospital support platform 140 can present a virtual character corresponding to the intelligent agent through a user space application, interact with relevant users, and provide at least a portion of user services to relevant users based on the interaction between relevant users and the virtual character.

[0084] In some embodiments, the hospital support platform 140 may have a five-layer structure, including a hardware device layer, an interface layer, a data processing layer, an application development layer, and a service layer. In some embodiments, the hardware devices of the physical hospital 110 may be part of the hospital support platform 140. Further description of the hospital support platform can be found elsewhere in this application (e.g., Figure 3 (and related descriptions).

[0085] According to some embodiments of this application, a virtual hospital corresponding to the physical hospital can be established by comprehensively integrating various internal and external resources of the physical hospital (e.g., medical service equipment, hospital personnel, medicines, and consumables). This virtual hospital can reflect the real-time status (e.g., changes, updates, etc.) of the physical entities related to the physical hospital, thereby enabling the monitoring and evaluation of these physical entities. This integration can provide accurate data support for the operation and intelligent decision-making of healthcare services. Furthermore, through the virtual hospital, users related to healthcare services can jointly establish an open and shared ecosystem, thereby promoting innovation and improvement in healthcare services.

[0086] Furthermore, it can provide comprehensive patient healthcare services throughout the entire life cycle, linking both in-hospital and out-of-hospital care. The perspective of medical services expands from simple disease treatment to encompass the entire patient lifecycle, including prevention, diagnosis, treatment, rehabilitation, and health management. By establishing in-hospital and out-of-hospital collaboration, physical hospitals can better integrate online and offline resources to provide patients with comprehensive and continuous healthcare services. For example, through remote monitoring and online consultations, patients' health status can be followed up in real time, treatment plans can be adjusted promptly, and treatment outcomes improved.

[0087] Figure 2 This is a schematic diagram of an exemplary medical service system 200 according to some embodiments of this application.

[0088] like Figure 2 As shown, the healthcare service system 200 may include a processing device 210, a network 220, a storage device 230, one or more healthcare service devices 240, one or more sensing devices 250, one or more patient terminals 260 for a patient 261, and one or more doctor terminals 270 for a doctor 271 associated with the patient 261. In some embodiments, the components in the healthcare service system 200 may be interconnected and / or communicate with each other via wireless connections, wired connections, or a combination thereof. The connections between the components of the healthcare service system 200 may be variable. By way of example only, the healthcare service device 240 may be connected to the processing device 210 via the network 220 or directly. Similarly, the storage device 230 may be connected to the processing device 210 via the network 220 or directly.

[0089] Processing device 210 can process data and / or information obtained from storage device 230, medical service device 240, sensing device 250, patient terminal 260, and / or doctor terminal 270. For example, processing device 210 can map data related to a physical hospital to a virtual hospital corresponding to the physical hospital, and provide user services to patient 261 and doctor 271 respectively through patient terminal 260 and / or doctor terminal 270 by processing data related to the physical hospital. As another example, processing device 210 can maintain digital intelligent objects and provide user services to patient 261 and doctor 271 respectively through patient terminal 260 and / or doctor terminal 270 by involving digital intelligent objects in processing data related to the physical hospital.

[0090] In some embodiments, the processing device 210 may be a single server or a group of servers. The server group may be centralized or distributed. In some embodiments, the processing device 210 may be located locally or remotely within the healthcare service system 200. In some embodiments, the processing device 210 may be implemented on a cloud platform. For example, the cloud platform may include private cloud, public cloud, hybrid cloud, community cloud, distributed cloud, inter-cloud cloud, multi-cloud, etc., or combinations thereof. In some embodiments, the processing device 210 may be implemented using a computing device.

[0091] In some embodiments, processing device 210 may include one or more processors (e.g., a single-core processor or a multi-core processor). For illustrative purposes only, only one processing device 210 is described in the medical service system 200. However, it should be noted that the medical service system 200 of this application may also include multiple processing devices. Therefore, as in this application, the operations and / or method steps performed by one processing device 210 may also be performed jointly or individually by multiple processing devices. For example, if in this application, processing device 210 of medical service system 200 simultaneously executes process A and process B, it should be understood that process A and process B may also be performed jointly or individually by two or more different processing devices in medical service system 200 (e.g., a first processing device executes process A, a second processing device executes process B; or the first and second processing devices jointly execute processes A and B).

[0092] Network 220 may include any suitable network capable of facilitating information and / or data exchange between the healthcare service system 200. Network 220 may be or include wired networks, wireless networks (e.g., 802.11 networks, Wi-Fi networks), Bluetooth, etc. TM Networks, near field communication (NFC) networks, or any combination thereof.

[0093] Storage device 230 may store data, instructions, and / or any other information. In some embodiments, storage device 230 may store data obtained from other components of the healthcare system 200. In some embodiments, storage device 230 may store data and / or instructions that processing device 210 may perform or be used to perform the exemplary methods described in this application.

[0094] In some embodiments, the data stored in storage device 230 may include multimodal data. Multimodal data may include data in various forms (e.g., images, graphics, videos, text, etc.), various types of data, data obtained from different sources, data related to different medical procedures (e.g., diagnosis, surgery, rehabilitation, etc.), and data related to different users (e.g., patients, medical staff, administrators, etc.). For example, the data stored in storage device 230 may include medical data of patient 261 reflecting the health status of patient 261. For example, medical data may include patient 261's electronic medical record. An electronic medical record is an electronic file that records various types of patient data (e.g., basic information, examination data, imaging data). For example, an electronic medical record may include three-dimensional models of multiple organs and / or tissues of patient 261.

[0095] In some embodiments, storage device 230 may include mass storage devices, removable storage devices, volatile read-write memory, read-only memory (ROM), etc., or any combination thereof. In some embodiments, storage device 230 may include data lakes and data warehouses, combining... Figure 3 Provide a detailed description.

[0096] Medical service equipment 240 can be used to provide or assist with medical services. For example... Figure 2 As shown, the medical service equipment 240 includes a consultation room terminal 240-1, a hospital bed 240-2, an intelligent surgical terminal 240-3, an intelligent nursing cart 240-4, an intelligent wheelchair 240-5, or any combination thereof.

[0097] Clinic terminal 240-1 refers to a terminal device configured in a clinic for use by doctors and patients during outpatient medical procedures. For example, clinic terminal 240-1 may include one or more of a screen, a sound output component, an image sensor, or a sound sensor. The screen of clinic terminal 240-1 may display a consultation interface, on which data may be displayed to facilitate communication between doctor and patient. Exemplary data may include electronic medical records (or portions thereof), pre-consultation records, medical images, 3D organ models, examination results, consultation suggestions, etc.

[0098] Hospital bed 240-2 refers to a hospital bed within a ward that supports inpatients and provides user services to them. Hospital bed 240-2 may include a bed, bedside terminal equipment, bedside examination equipment, sensors, etc., or any combination thereof. Bedside terminal equipment may include XR equipment, display equipment, mobile devices, etc., or any combination thereof. In some embodiments, hospital bed 240-2 may be configured with an intelligent agent corresponding to inpatient services, wherein the hospital bed may also be referred to as a smart hospital bed or a meta-hospital bed.

[0099] The intelligent surgical terminal 240-3 refers to a device configured with an intelligent agent for assisting surgery. The intelligent surgical terminal 240-3 can sense interactions (e.g., dialogues, behaviors, etc.) between the healthcare provider, the patient, and the intelligent agent, and acquire data captured by the sensing device 250, thereby providing surgical assistance. In some embodiments, the intelligent surgical terminal 240-3 can be configured to perform risk warnings for surgical procedures, generate surgical records of the surgical process, etc., based on the intelligent agent configured therein.

[0100] The intelligent nursing cart 240-4 refers to a nursing cart with automatic driving capabilities that can assist in patient treatment and care. For example, the intelligent nursing cart 240-4 can be configured to guide nurses to hospital wards to conduct admission examinations for patients. In some embodiments, the intelligent nursing cart can be controlled by an intelligent agent (e.g., an intelligent agent corresponding to inpatient services, a nursing intelligent agent). In some embodiments, the intelligent nursing cart 240-4 may include a trolley, a presentation device, one or more examination devices and / or nursing tools, sensing devices (such as image sensors, GPS sensors, sound sensors, etc.), etc. In some embodiments, the intelligent nursing cart 240-4 can be configured to acquire relevant treatment and care information of patients and generate physical examination data, nursing data, etc. Physical examination data may include the patient's vital signs data. Nursing data may include detailed records of nursing operations, such as nursing time, nursing operator, nursing measures, patient responses, etc.

[0101] The intelligent wheelchair 240-5 refers to a transportation device for intelligent patient transport. In some embodiments, the intelligent wheelchair 240-5 can be configured to perform autonomous navigation by integrating sensors and maps (e.g., using simultaneous localization and mapping (SLAM) technology or a pre-built environmental model), locate the patient's position using radio frequency identification (RFID), Bluetooth, or Wi-Fi signals, and identify the patient using biometric technology. In some embodiments, the intelligent wheelchair 240-5 can be controlled by an intelligent agent (e.g., an intelligent agent corresponding to inpatient services, an intelligent agent corresponding to surgical services). In some embodiments, the intelligent wheelchair 240-5 can be configured to generate data (e.g., a record of interactions between the intelligent agent and the patient) by sensing interaction data through a built-in camera / sensor.

[0102] The sensing device 250 can be configured to collect sensing information related to its environment. In some embodiments, the sensing device 250 may include sensing devices in the physical hospital 110. For example, the sensing device 250 may include an image sensor 250-1, a sound sensor 250-2, a temperature sensor, a humidity sensor, etc.

[0103] Patient terminal 260 can be a terminal device that interacts with patient 261. In some embodiments, patient terminal 260 may include mobile terminal 260-1, XR device 260-2, smart wearable device 260-3, etc. Doctor terminal 270 can be a terminal device that interacts with doctor 271. In some embodiments, doctor terminal 270 may include mobile terminal 270-1, XR device 270-2, etc. In some embodiments, patient 261 can access user space applications (e.g., patient space applications) through patient terminal 260, and doctor 271 can access user space applications (e.g., medical space applications) through doctor terminal 270. In some embodiments, patient 261 and doctor 271 can communicate remotely with each other through patient terminal 260 and doctor terminal 270 to provide telemedicine services, such as remote outpatient services, remote ward rounds, remote follow-up services, etc.

[0104] Sensing device 250, patient terminal 260, and doctor terminal 270 can be configured as data sources to provide information to healthcare service system 200. For example, these devices can transmit the collected data to processing device 210, and processing device 210 can provide user services based on the received data.

[0105] It should be noted that the descriptions of the healthcare service systems 100 and 200 above are illustrative and not intended to limit the scope of this application. Many alternatives, modifications, and variations will be apparent to those skilled in the art. The features, structures, methods, and other features of the exemplary embodiments herein can be combined in various ways to obtain additional and / or optional exemplary embodiments. For example, healthcare service system 200 may include one or more additional components, such as terminal devices for other users, public terminal devices in the hospital, etc. As another example, two or more components of healthcare service system 200 may be integrated into a single component.

[0106] Figure 3 This is a schematic diagram of an exemplary hospital support platform 300 according to some embodiments of this application.

[0107] like Figure 3 As shown, the hospital support platform 300 may include a hardware layer 310 (also called a hardware module), an interface layer 320 (also called an interface module), a data processing layer 330 (also called a data processing module), an application development layer 340 (also called an application development module), and a service layer 350 (also called a service module). It should be understood that the terms "layer" and "module" in this application are only used for logically dividing the components of the hospital support platform and are not intended to be limiting.

[0108] Hardware layer 310 can be configured to provide a hardware foundation for interaction between the real world and the digital world, and may include one or more hardware devices related to hospital operations. Exemplary hardware devices may include medical service devices, sensing devices, terminal devices, and infrastructure devices. Further description of the hardware devices can be found elsewhere in this application. For example, see... Figure 1 And its related descriptions.

[0109] Interface layer 320 can be connected to hardware layer 310 and data processing layer 330. Interface layer 320 can be configured to acquire data collected by hardware devices of hardware layer 310 and send the data to data processing layer 330 for storage and / or processing. Interface layer 320 can also be configured to control at least a portion of hardware devices of hardware layer 310. In some embodiments, interface layer 320 may include hardware interfaces and software interfaces (e.g., data interfaces, control interfaces).

[0110] The data processing layer 330 can be configured to store and / or process data. The data processing layer 330 may include a processing device on which multiple data processing units can be configured. The data processing layer 330 can be configured to acquire data from the interface layer 320 and process the data through at least one data processing unit to provide user services related to hospital operations.

[0111] The data processing unit may include various preset algorithms for implementing data processing, which may take the form of software, programs, computer code, and / or instructions implemented in various computer programming languages ​​(e.g., Java, C / C++). In some embodiments, the data processing layer 330 may include a processing device (e.g., Figure 2 The data processing unit can be configured on the processing device (processing device 210). In some embodiments, the data processing unit may include an XR unit configured to process data using XR technology to implement XR services, an AI unit (e.g., an intelligent agent unit) configured to process data using AI technology to implement AI services, a digital twin unit configured to process data using digital twin technology to implement digital twin services, and a data circulation unit configured to process data using data circulation technologies (e.g., blockchain technology, data privacy computing technology) to implement data circulation services, etc.

[0112] In some embodiments, the data processing layer 330 may further include a data center configured to store data. In some embodiments, the data center may employ a lake warehouse integrated architecture, which may include a data lake and a data warehouse. The data lake may be used to persistently store large amounts of data in a tamper-proof manner. The data warehouse may be used to store index data corresponding to the data in the data lake. The data stored in the data lake may include native (or raw) data collected by hardware devices, derived data generated based on native data, etc. In some embodiments, the data in the data lake may be processed by a processing device (e.g., processing device 210).

[0113] The application development layer 340 can be configured to support application development, publishing, and subscription. The application development layer 340 is also referred to as the ecosystem suite layer. In some embodiments, the application development layer 340 can be configured to provide application developers with open interfaces to access or invoke at least a portion of the data processing units and utilize at least a portion of the data processing units to develop applications. In some embodiments, such as... Figure 3 As shown, the application development layer 340 can provide development toolkits, application marketplaces, multi-tenant operation platforms, cloud official websites, workspaces, and other support toolkits to assist developers in their work.

[0114] Service layer 350 can be configured so that users related to hospital operations can access user services related to hospital operations through a user space application. Further descriptions of user services and user space applications can be found elsewhere in this application. For example, see [link to relevant documentation]. Figure 1 And its related descriptions.

[0115] This application provides a hospital support platform designed for the comprehensive management of various resources within a hospital, including hardware, software, and data resources. In some embodiments, the platform further integrates data processing units capable of supporting advanced technologies such as artificial intelligence, XR, digital twins, and blockchain. These advanced technologies are used to improve the efficiency and quality of services in the healthcare industry. For example, artificial intelligence technology enables the autonomous evolution and continuous optimization of hospital operations, while XR and digital twin technologies facilitate the creation and maintenance of virtual hospitals. These virtual hospitals can interact with users, providing immersive and novel service experiences. Furthermore, the platform includes an application development layer that grants access to these advanced technologies to third-party developers in the healthcare industry. This access fosters an open ecosystem, promoting application development and innovation, thereby driving advancements in healthcare services.

[0116] Figure 4 This is a block diagram of an exemplary processing device 210 according to some embodiments of this application. In some embodiments, the processing device 210 may be coupled to a computer-readable storage medium (e.g., Figure 2 The processing device 210 communicates with the storage device 230 shown and executes instructions stored in a computer-readable storage medium. The processing device 210 may include an acquisition module 410, a mapping module 420, and a service module 430.

[0117] The acquisition module 410 can be configured to acquire data related to the physical hospital. Further description of acquiring data related to the physical hospital can be found elsewhere in this application. For example, see... Figure 1 , 5 And its related descriptions.

[0118] Mapping module 420 can be configured to map data related to a physical hospital to a virtual hospital corresponding to that physical hospital. Further description of mapping data related to physical hospitals can be found elsewhere in this application. For example, see... Figure 1 , 2 And its related descriptions.

[0119] Service module 430 can be configured to provide user services to relevant users of the physical hospital via a user-space application. Further description of user services can be found elsewhere in this application. For example, see [link to relevant documentation]. Figure 1 and 5 -7 and its related descriptions.

[0120] In some embodiments, the processing device 210 may include one or more other modules. For example, the processing device 210 may include a storage module for storing data generated by the modules in the processing device 210. In some embodiments, any two modules may be combined into a single module, and any module may be divided into two or more units. For example, the service module 430 may include multiple units configured to support and / or implement different user services.

[0121] Figure 5 This is a schematic diagram of an exemplary process 500 for providing user services according to some embodiments of this application.

[0122] like Figure 5 As shown, data 530 related to the medical service process can be collected according to a preset data collection protocol 520 corresponding to the medical service process, and user services 540 can be provided to relevant users of the medical service process through data processing 530.

[0123] A medical service process refers to the process of providing corresponding medical services to a patient. Exemplary medical service processes may include outpatient processes, inpatient processes, surgical processes, or similar processes, or any combination thereof. In some embodiments, a medical service process may include several standard steps that a user needs to go through to obtain the corresponding medical service. For example, an outpatient process may include the following standard steps: registration, waiting, consultation, and post-consultation.

[0124] In some embodiments, the medical service procedures corresponding to different hospital departments within a hospital (e.g., physical hospital 110) may differ. For example, the outpatient procedure corresponding to internal medicine may differ from the outpatient procedure corresponding to surgery. In some embodiments, the medical service procedures corresponding to different diseases may differ. For example, the medical service procedure corresponding to the common cold may differ from the medical service procedure corresponding to cancer.

[0125] A preset data collection protocol 520 is used to guide how to collect data 530 related to the medical service process. In some embodiments, the preset data collection protocol 520 may include data collection protocols corresponding to standard steps in the medical service process. For example, a preset data collection protocol corresponding to an outpatient process may include data collection protocols corresponding to the registration, waiting, consultation, and post-consultation steps in the outpatient process.

[0126] In some embodiments, the data acquisition protocol corresponding to a standard step in the healthcare service process may specify at least one or more hardware devices for collecting data related to that standard step. These one or more hardware devices may include IoT devices, sensing devices, user terminals, hospital public terminals, healthcare service equipment, or any combination thereof.

[0127] In some embodiments, the data acquisition protocol corresponding to the standard step may further specify data interface standards and / or data quality standards for one or more hardware devices. A data interface standard refers to a set of guidelines and specifications that define how data is exchanged between different systems, devices, or software applications. Data interface standards may include protocols, data formats, communication methods, encoding and decoding rules, security standards, etc., or any combination thereof. As an example only, data interface standards may include Health Level 7 (HL7), Digital Imaging and Communication in Medicine (DICOM), etc., or any combination thereof. A data quality standard refers to a set of standards and guidelines designed to ensure that data is accurate, consistent, reliable, and usable for its intended purpose. Exemplary data quality standards may include data quality model ISO / IEC 25012, data quality model ISO 8000, data standard HL7, Basel Committee on Banking Supervision (BCBS 239), etc., or any combination thereof.

[0128] For example only, such as Figure 5 As shown, the processing device 210 can determine a preset data acquisition protocol 520 corresponding to the medical service process based on at least one of the following: hospital department 502, disease 504, standard procedure 506, hardware device 508, data interface standard 510, or data quality standard 512. In some embodiments, the preset data acquisition protocol 520 can be manually set by the user. In some embodiments, the agent can learn the preset data acquisition protocol 520 from historical data and a knowledge database.

[0129] In some embodiments, the processing device 210 may update the preset data collection protocol 520 corresponding to the medical service process based on a healthcare policy 514 related to the medical service process. For example, if the healthcare policy 514 is updated to include new standard steps or remove some standard steps, the processing device 210 may update the standard steps in the preset data collection protocol 520 corresponding to the medical service process.

[0130] Data related to the healthcare service process 530 may include various types of data related to the healthcare service process. For example, data related to the healthcare service process 530 may include patient location information, patient interaction information related to interactions between the patient and patient terminals, patient examination data (e.g., examination reports, medical images, vital signs), physician orders, perceived information related to the patient's environment, patient clinical pathways, and patient data entered by healthcare providers (e.g., physicians, nurses) or similar personnel or any combination thereof.

[0131] In some embodiments, the processing device 210 may obtain data 530 from a hardware device. For example, the hardware device may collect data 530 according to a preset data acquisition protocol 520, and the processing device 210 may obtain data 530 from the hardware device. In some embodiments, the processing device 210 may obtain data 530 from a storage device (e.g., storage device 230) that stores the data 530. For example, the data 530 collected by the hardware device may be stored in the storage device, and the processing device 210 may obtain data 530 from the storage device.

[0132] Furthermore, the processing device 210 can provide user services 540 to relevant users of the medical service process by processing data 530. For example, at least a portion of the data 530 can be processed by an agent corresponding to the medical service process. Further description of agents can be found elsewhere in this application. For example, see... Figure 1 And related descriptions. Further descriptions of using intelligent agents to process data can be found elsewhere in this application. For example, see... Figure 6 And its related descriptions.

[0133] In some embodiments, the relevant users can include a first type of user and a second type of user, and the user space application can include a first user space application corresponding to the first type of user and a second user space application corresponding to the second type of user. For example, the first type of user can be a patient, and the second type of user can be a doctor or administrator. Accordingly, the first user space application can be a patient space application, and the second user space application can be a doctor space application or an administrator space application.

[0134] In some embodiments, after obtaining the interaction information between a first type of user and a first user space application, the processing device 210 can provide first user services to the first user through the first user space application based on the interaction information, and provide second user services to the second user through a second user space application based on the interaction information. For example, when a patient is admitted to a hospital ward, the processing device 210 can provide the patient with hospital admission services through the patient space application, and remind the nurses in the hospital ward to pay attention to the patient through the patient space application.

[0135] According to some embodiments of this application, data from different patients participating in the same type of medical service process is collected using the same pre-defined data acquisition protocol corresponding to the medical service process. The pre-defined data acquisition protocol specifies the hardware devices for collecting data related to each standard step, data interface standard, data quality standard, etc. Compared to traditional hospital systems that only collect data from specific scenarios without considering the entire medical service process, the method disclosed herein can collect more comprehensive, granular, and real-time medical service process data. The collected data can then be used to evaluate various aspects of the medical service process, thereby promoting performance optimization and improving the overall efficiency of the medical service system.

[0136] Figure 6 This is a schematic diagram of an exemplary process 600 for providing user services according to some embodiments of this application.

[0137] like Figure 6 As shown, after collecting data 610 related to the physical hospital, the intelligent agent 620 can process the data 610 to provide user services 640. As mentioned above, the intelligent agent 620 includes different types. Depending on the type and content of the data 610, a target type of intelligent agent 620 can be used to process the data 610. For example, if the data 610 is related to a step in the patient's medical service process, then the data 610 is processed by the intelligent agent corresponding to that medical service process or a step in that process. As another example, if the data 610 involves specific user services, the data 610 is processed by the intelligent agent corresponding to the user service.

[0138] In some embodiments, the processing device 210 can present a virtual character 634 corresponding to the intelligent agent 620 through a user space application 630 (e.g., a patient space application), and can provide user services 640 based on the interaction between relevant users (e.g., patients, hospital staff (e.g., doctors, nurses, hospital administrators)) and the virtual character 634 in the medical service process. In some embodiments, relevant users can access the virtual character 634 through a user terminal (e.g., ...). Figure 6 The XR device 632 shown interacts with the virtual character 634. For example, a user space application on a user terminal can use XR technology to present the virtual character to the relevant user, and the relevant user can interact with the virtual character through XR technology.

[0139] A virtual persona refers to a computer-generated person or entity designed to interact with relevant users in a digital environment. Virtual persona 634 can be configured to interact with relevant users to provide user services 640. For example, virtual persona 634 can communicate with users by simulating human speech, gestures, etc., providing a realistic communication experience. During communication, users can express their needs or requests using natural language through voice, text, gestures, etc. Intelligent agent 620 can be constructed based on natural language processing algorithms to understand and analyze user input, determine feedback information, and convey the feedback information to the user through virtual persona 422.

[0140] In some embodiments, the virtual character 634 may be a digital person with certain physical features, voice features, etc. For example, the processing device 210 may determine the physical features and / or voice features of the virtual character 634 based on the patient's patient data. As another example, the processing device 210 may determine the physical features and / or voice features of the virtual character 634 based on the patient's doctor or nurse data, so that the virtual character 634 can simulate a doctor or nurse.

[0141] Exemplary user services 640 provided to patients based on interactions with virtual character 634 include registration services, pre-consultation services, admission inquiry services, route guidance services, discharge services, follow-up services, and any combination thereof. Some of these services may be provided by different agents. For example, the registration service may be provided by a registration agent based on interactions between the patient and a first virtual character (such as a nurse virtual character) representing that registration agent. As another example, the pre-consultation service may be provided by a pre-consultation agent based on interactions between the patient and a second virtual character (such as a nurse virtual character) representing that pre-consultation agent. As yet another example, the admission inquiry service may be provided by an admission agent based on interactions between the patient and a third virtual character (such as a doctor virtual character) representing that admission agent.

[0142] In some embodiments, the intelligent agent 620 can generate a processing result 650 based on the data 610, and can provide user services 640 to relevant users based on the processing result 650. For example, the processing result 650 may include speech recognition results, image recognition results, anomaly detection results, etc. The intelligent agent 620 can utilize various AI technologies (e.g., machine learning models) to generate the processing result 650. For example, relevant users may include hospital staff (e.g., doctors, nurses, hospital administrators), and the user services 640 provided to hospital staff may include providing records, notifications, suggestions, etc., based on the processing result 650.

[0143] According to some embodiments of this application, by integrating intelligent agents, user services can be provided automatically, thereby reducing the need for a large amount of human labor, lowering operating costs, and improving the efficiency of providing user services. Furthermore, the intelligent agents can continuously optimize the rules and mechanisms they have learned, improving the accuracy, efficiency, and quality of user services. In addition, this application provides different types of intelligent agents that can handle tasks from different healthcare providers, departments, and hospital positions. Each intelligent agent can self-optimize and evolve from specific data to better handle the corresponding tasks.

[0144] Figure 7 This is a flowchart of an exemplary process 700 for providing user services according to some embodiments of this application.

[0145] Step 702, the processing device 210 can monitor updates to patient data.

[0146] Patient data may include data relating to patients involved in a healthcare service process. A healthcare service process refers to the procedure by which appropriate healthcare services are provided to a patient. Further descriptions of healthcare service processes can be found elsewhere in this application. For example, Figure 1 , 5 And related descriptions. In some embodiments, patient data can be considered as multimodal data, which includes multiple types of data, multidimensional data, etc.

[0147] In some embodiments, patient-related data may be collected according to a preset data collection protocol corresponding to a medical service process. For example, at least one hardware device may collect patient-related data according to a preset data collection protocol, and processing device 210 may acquire data from at least one hardware device. Further description of data collection can be found elsewhere in this application. For example, see... Figure 5 And its related descriptions.

[0148] In some embodiments, the processing device 210 can monitor updates to patient-related data by monitoring at least one hardware device. An update can be detected when the hardware device acquires updated data 704 that has not yet been processed by the processing device 210. For example, assuming a vital signs monitor acquires the patient's heart rate hourly, the processing device 210 can detect an update when the vital signs monitor acquires a new heart rate (i.e., updated data).

[0149] In some embodiments, the processing device 210 may have a direct communication connection with at least one hardware device and directly monitor at least one hardware device. Alternatively, the processing device 210 may have a communication connection with a storage device (e.g., storage device 230) that stores patient-related data collected by at least one hardware device and monitors at least one hardware device by monitoring the storage device.

[0150] Update data 704 refers to data collected by at least one hardware device that has not yet been processed by processing device 210. For example, if the at least one hardware device includes an IoT device, then update data 704 may include IoT data. Update data 704 may be obtained directly from the at least one hardware device or from a storage device.

[0151] If the patient-related data includes updated data 704 obtained from at least one hardware device, the processing device 210 can perform an event of interest (EOI) detection 706 on the updated data. Simultaneously, the processing device 210 can continue with step 702 to continuously monitor updates in the patient data.

[0152] In some embodiments, the processing device 210 may perform an EOI detection 706 on the updated data 704.

[0153] An Expression of Interest (EOI) refers to a specific event or behavior that requires attention. EOI detection 706 refers to processing updated data 704 collected by at least one hardware device to detect whether one or more EOIs have occurred. For example, for a hospitalization process, exemplary EOIs may include a patient being admitted to a hospital ward, a patient undergoing admission examinations, at least one physician making rounds in a hospital ward, a patient undergoing a nursing procedure or medical examination, a patient initiating a service request, receiving or updating a physician's orders for a patient, an abnormal physiological state in a patient, or a physician issuing instructions to a patient. As another example, for a surgical process, exemplary EOIs may include instructions issued by a surgical participant (e.g., a chief surgeon issuing an order for a blood transfusion), detection of a surgical risk (e.g., cardiac arrest or severe bleeding in a patient), an abnormal physiological state in a patient (e.g., low blood pressure in a patient), a count of surgical instruments falling below a threshold (e.g., a scalpel count falling below a scalpel quantity threshold), completion of the surgery (i.e., the end of the surgical procedure), or any combination thereof.

[0154] In some embodiments, the processing device 210 may perform EOI detection 706 based on EOI detection rule 712. EOI detection rule 712 refers to the rules that must be followed when performing EOI detection 706. For example, EOI detection rule 712 may specify the EOIs to be detected, the algorithm or technology used to detect specific EOIs, the algorithm or technology used to analyze data collected from specific data sources, EOIs corresponding to different stages of the hospitalization process, EOIs corresponding to different types of patients, etc., or any combination thereof.

[0155] In some embodiments, the EOI detection rule 712 may be determined based on the history of EOI detection, or it may be manually set by a user (e.g., a doctor, nurse, technician, etc.). For example, the processing device 210 may perform EOI detection 706 on the updated data 704 based on the type of the updated data 704.

[0156] In some embodiments, each stage of the medical service process may correspond to one or more Expressions of Interest (EOIs), and different stages of the medical service process may correspond to different types of EOIs. Therefore, the processing device 210 can perform EOI detection 706 on the updated data 704 based on the patient's current stage in the medical service process. For example, the processing device 210 can determine the patient's current stage in the medical service process and determine the type of EOI data to be detected based on the patient's current stage. Furthermore, the processing device 210 can perform EOI detection 706 on the updated data 704 based on the type data.

[0157] By performing EOI detection based on the patient's current stage in the healthcare process, only specific types of EOI need to be detected or tracked, which reduces the amount of data to be processed, thereby reducing the processing requirements of the processing equipment 210 and improving the efficiency of EOI detection.

[0158] If an Expression of Interest (EOI) occurs (708), the processing device 210 may execute one or more preset operations (710) corresponding to the EOI to provide user services to the relevant user. Simultaneously, the processing device 210 may continue to execute steps 702 and EOI detection (706) to continuously monitor data updates and detect EOIs.

[0159] In some embodiments, the processing device 210 may perform one or more preset operations 710 corresponding to the EOI to provide user services to the relevant user.

[0160] Relevant users can include any user associated with the healthcare process. For example, users can include patients (or parts of patients, such as organs), companions, visitors to patients, hospital staff involved in the healthcare process (e.g., healthcare providers (e.g., doctors, nurses, technicians, etc.), hospital administrators, support staff, etc.), healthcare process suppliers, healthcare process application developers, etc., or any combination thereof.

[0161] User services may include any services provided within the healthcare service process. For example, user services include medical services corresponding to the healthcare service process provided to patients and / or accompanying persons, support services corresponding to the healthcare service process provided to hospital staff and / or suppliers, etc.

[0162] Preset actions corresponding to an Expression of Interest (EOI) refer to the actions that need to be performed when an EOI occurs. In some embodiments, preset actions may include general actions and / or specific actions. General actions are those that need to be performed whenever an EOI occurs, regardless of the type of EOI. For example, general actions may include generating a record associated with the EOI. Specific actions are those that are performed when a specific type of EOI occurs. For example, updating a patient's daily schedule based on updated data can be identified as a specific action corresponding to an EOI that updates a physician's orders for a patient.

[0163] In some embodiments, the processing device 210 may determine a correspondence 714 between an EOI and a preset operation, and determine one or more preset operations 710 corresponding to the detected EOI based on the correspondence 714. The correspondence 714 may indicate that one or more preset operations 710 need to be performed when a specific type of EOI occurs. For example, the correspondence 714 may be in the form of a lookup table.

[0164] In some embodiments, the correspondence 714 may be predetermined and stored in a storage device, and the processing device 210 may obtain the correspondence 714 from the storage device. In some embodiments, the processing device 210 may determine the correspondence 714 between EOI and preset operation based on historical records.

[0165] In some embodiments, one or more preset operations 710 corresponding to the EOI may be further determined based on the patient's profile data. The patient's profile data may include basic data, health data, historical data, registration data, etc., or any combination thereof. For example, different types of patients (e.g., those with different diseases or of different ages) may correspond to different scheduled surgeries.

[0166] In some embodiments, a preset operation corresponding to the EOI can be performed immediately after the EOI is detected. For example, the processing device 210 can enable the nurse terminal to provide an alarm when the patient's physiological state is abnormal. In some embodiments, a preset operation corresponding to the EOI can be performed after the EOI is completed. For example, a record associated with the EOI can be generated in response to the completion of the EOI detection.

[0167] According to some embodiments of this application, at least one hardware device that captures information about the healthcare service process is monitored. This monitoring helps to promptly detect data updates and the occurrence of Expressions of Interest (EOIs), triggering corresponding preset operations in a timely manner. Therefore, user services can be provided to relevant users automatically and efficiently, thereby improving service efficiency and quality. Furthermore, the monitored hardware device collects multi-modal data at different stages of the entire healthcare service process, thereby enabling patient-centered healthcare and comprehensive hospital services.

[0168] In some embodiments, the processing device 210 may be configured with an agent corresponding to a medical service process, the agent being capable of executing at least a portion of process 700. An agent is an agent that acts intelligently. For example, the agent can learn an EOI detection rule 712 from historical records and perform EOI detection according to that rule. An EOI detection rule is a rule for detecting EOIs on updated data. For example, the agent can learn from historical records which types of EOIs need to be monitored, how to effectively detect EOIs, and what data needs to be analyzed to detect EOIs. Furthermore, the agent can learn from historical records the correspondence between EOIs and preset operations, and determine one or more preset operations corresponding to an EOI based on the correspondence. For example, the agent can learn from historical records which operations need to be performed when an EOI occurs.

[0169] In some embodiments, the agent can further learn EOI detection rules and / or the correspondence between EOIs and preset operations based on the profile data of different patients. For example, the agent can determine different EOI detection rules and different preset operations for different types of patients (e.g., different diseases, different ages).

[0170] By integrating intelligent agents, the system can continuously learn EOI detection rules and / or corresponding relationships using big data technology, machine learning technology, and other advanced methods. This continuous optimization of EOI detection rules and / or corresponding relationships improves the accuracy, efficiency, and quality of inpatient services.

[0171] Figure 8 This is a schematic diagram of an exemplary medical outpatient process 800 according to some embodiments of this application. Figure 8As shown, the medical outpatient process 800 may include multiple stages such as registration 810, waiting 820, consultation 830, and post-consultation 840. In some embodiments, the processing device 210 (e.g., service module 430, an intelligent agent corresponding to the outpatient service / process configured on the processing device 210) can perform the operations involved in the multiple stages of the medical outpatient process 800.

[0172] Patients can schedule an appointment during the registration process (810). Figure 8 As shown, operations related to the registration process 810 may include obtaining / creating electronic medical records, providing intelligent registration services, providing route planning services, and providing route guidance services. In some embodiments, patients can initiate registration requests through a patient terminal or a registration terminal at the hospital, or initiate remote registration requests through a patient terminal at other locations outside the hospital.

[0173] In some embodiments, upon receiving a registration request from a patient, the processing device 210 may acquire or create the patient's electronic medical record.

[0174] An electronic medical record (EMR) is an electronic file that records various types of patient data. In some embodiments, the EMR can be updated as the patient's outpatient process progresses. For example, when a patient registers, the EMR may include the patient's basic information; after the patient completes registration, the EMR can be updated to further include the patient's chief complaint and registration details.

[0175] In some embodiments, when receiving a registration request from a patient, the processing device 210 can provide the patient with an intelligent registration service. The intelligent registration service can be used to match the patient with the appropriate department, doctor, and appointment time. In some embodiments, the processing device 210 can provide services related to the registration process through a hospital's registration terminal or the patient's personal terminal.

[0176] If a patient does not have a specific department to register with, the processing device 210 can provide intelligent registration services based on the patient's chief complaint, uploaded examination reports, and / or historical patient information stored in the storage device, to determine a recommended department that matches the patient's medical needs. If the patient does not have a specific doctor to register with, the processing device 210 can recommend a doctor to the patient based on the patient's chief complaint, and / or display the doctor in the department to be registered with. The registration module 410 of the processing device 210 can recommend a less busy registration time slot to the patient based on the doctor's appointment information.

[0177] In some embodiments, the processing device 210 can determine the patient's attending physician by conducting a first inquiry with the patient using a patient terminal or registration terminal. For example, the processing device 210 can obtain the patient's chief complaint through the patient terminal or registration terminal and determine at least one candidate department based on the patient's chief complaint. Then, the processing device 210 can cause the patient terminal or registration terminal to conduct a first inquiry with the patient based on at least one candidate department. For example, the processing device 210 can determine the first inquiry content of the first inquiry based on the patient's chief complaint and at least one candidate department, and cause the patient terminal or registration terminal (e.g., an XR device) to display a first virtual character, which conducts the first inquiry with the patient based on the first inquiry content. Finally, the processing device 210 can determine the doctor based on the first data collected in the first inquiry by the patient terminal or registration terminal.

[0178] Route planning services can be used to provide patients with a planned route to the doctor's office. Specifically, processing device 210 can generate a planned route to the doctor's office based on the patient's current location and the location information of the doctor's office. In some embodiments, processing device 210 can generate a planned route after the patient registers at the hospital in person. In some embodiments, processing device 210 can generate a planned route when the patient registers remotely and arrives at the hospital.

[0179] The route guidance service can be used to guide patients to the doctor's office based on a planned route. In some embodiments, the processing device 210 can display guidance information to the patient via their patient terminal (e.g., an XR device). For example, using AR technology, the XR device can overlay guidance information related to the planned route onto the patient's actual view.

[0180] Patients can wait and prepare for their appointment in the waiting area. During this waiting area 820, patients can be at the hospital (e.g., in the waiting area in front of the doctor's office) or at another location outside the hospital (e.g., at their home). Figure 8 As shown, operations related to the waiting area 820 may include providing pre-consultation services, providing force feedback / temperature feedback, etc.

[0181] Pre-consultation services can be used to collect information about patients by conducting preliminary inquiries before they enter the consultation room for a formal consultation. Specifically, while patients are waiting for their consultation, the processing device 210 can conduct a pre-consultation through the patient's terminal or a waiting terminal located in the waiting area to alleviate the patient's anxiety while waiting, generate a pre-consultation record, and provide the pre-consultation record to the doctor for reference, thereby improving the doctor's consultation efficiency.

[0182] Force feedback / temperature feedback can be used to provide soothing feedback to patients. Specifically, while a patient is waiting, the processing device 210, after detecting the patient's emotions (e.g., tension, fear, anxiety, etc.), can apply force feedback and / or temperature feedback to the patient through the patient's wearable device, allowing the patient to feel actions such as handshakes or hugs, thereby soothing the patient's negative emotions.

[0183] Patients can communicate with their registered doctor during the consultation process (8:30) to receive medical outpatient services (e.g., in-person consultation in the clinic, or remote consultation). Figure 8 As shown, operations related to the consultation process 830 may include previewing the outpatient clinic for the day, displaying medical data, providing consultation suggestions, generating diagnostic records, and providing remote escort services.

[0184] During the consultation phase 830, the same-day outpatient preview is used to display relevant information about patients scheduled for appointments that day to the doctor. For example, the processing device 210 can display the categories of patients who have registered or are waiting for appointments that day to the doctor before the doctor begins the consultation. These patient categories may include first-time patients, returning patients, etc. In some embodiments, the doctor can browse the same-day outpatient preview through a shared terminal device in the consultation room or the doctor's personal terminal (e.g., an XR device).

[0185] During the consultation phase 830, medical data display is used to present the patient's medical data, such as electronic medical records, to the doctor, patient, and / or remote companion. Specifically, processing device 210 can synchronously display the patient's medical data to the doctor, patient, and / or remote companion via at least one terminal device. Furthermore, the display method and / or content of the electronic medical record are updated based on the interactive operations of the doctor, patient, and / or remote companion on the medical data to facilitate communication between the doctor, patient, and / or remote companion.

[0186] In the consultation phase 830, providing consultation suggestions refers to offering doctors suggestions for reference during the consultation process. Specifically, the processing device 210 can generate consultation suggestions for the doctor based on the sensory information collected by the sensing device during the consultation process, so that the doctor can adjust the diagnostic methods, diagnostic results, and prescriptions, thereby improving the efficiency and accuracy of the consultation.

[0187] Diagnostic record generation assists doctors in generating diagnostic records for patients. Specifically, processing device 210 can generate diagnostic records to record information about the patient's medical condition diagnosed by the doctor, the doctor's medical orders, etc.

[0188] Remote companionship services can be used to provide immersive companionship experiences for patients and remote companions. For example, processing device 210 can display a virtual examination room simulating a real examination room, a real-time view of the doctor inside the examination room, and a real-time view of the patient to the remote companion. As another example, processing device 210 can display the real-time image of the remote companion through a public terminal device inside the examination room. As yet another example, processing device 210 can display the real-time image of the remote companion to the doctor and the patient, respectively, through the doctor's terminal and the patient's terminal.

[0189] More details about medical data display, providing consultation suggestions, generating diagnostic records, and remote medical companionship services can be found on [website / platform name]. Figure 11 The relevant description can be found here, so it will not be repeated here.

[0190] In some embodiments, the processing device 210 can provide services related to the consultation process to relevant users (e.g., doctors, patients, remote companions) through at least one terminal device. The at least one terminal device includes a public terminal device in the consultation room, a patient terminal, a doctor terminal, a remote companion terminal device, etc.

[0191] The public terminal equipment in the consultation room refers to the terminal equipment installed on-site in the consultation room, which may include a display screen, a sound output device, a sound sensor, an XR device, a wearable device, or any combination thereof. For example, after a patient enters the consultation room, the processing device 210 can present electronic medical records, decision suggestions, pre-consultation records, diagnostic records, real-time images of remote companions, etc., to the doctor and / or patient through the display screen of the public terminal equipment. Alternatively, the patient can wear the wearable device of the public terminal equipment to receive force feedback from the remote companion. Furthermore, the doctor and patient can wear the XR device of the public terminal equipment, and the processing device 210 can present various types of information to the doctor and / or patient through the XR device of the public terminal equipment. In some embodiments, the XR device worn by the patient can also be the XR device of the registration terminal.

[0192] refer to Figure 12 , Figure 12 This is a schematic diagram of an exemplary medical consultation interface 1200 according to some embodiments of this application. For example... Figure 12 As shown, the consultation interface 1200 may include a first interface element 1210 related to the patient's electronic medical record, a second interface element 1220 related to the remote escort service, a third interface element 1230 related to medical documents, and a fourth interface element 1240 related to consultation suggestions.

[0193] The content and / or format of the patient interface 1200 can change as the patient visit progresses. For example, doctors and / or patients can issue control commands to adjust the content displayed on the patient interface 1200. Control commands can include various forms of commands, such as voice control commands, gesture control commands, touch control commands, and control commands input via input devices (e.g., mouse, keyboard, etc.).

[0194] The first interface element 1210 may be an icon corresponding to the electronic medical record, or it may be used to display the content of the electronic medical record. During the consultation, the doctor and / or patient may issue control commands to retrieve at least a portion of the electronic medical record, which will then be presented through the first interface element 1210.

[0195] The second interface element 1220 can be an icon corresponding to the remote accompaniment service, or it can be used to display the remote accompaniment screen. When a patient's remote accompaniment request is approved by the doctor, the patient can communicate with the remote accompaniment person during the consultation and view the remote accompaniment person's screen through the second interface element 1220.

[0196] The third interface element 1230 can be an icon corresponding to medical documents, or it can be used to display medical documents, such as pre-consultation records, diagnostic records (preliminary diagnostic records or target diagnostic records), etc. When a patient's consultation is detected, the pre-consultation record can be presented through the third interface element 1230; after the doctor and patient have completed their communication, the third interface element 1230 can be updated to present the initial diagnostic record; after the doctor confirms the modification of the initial diagnostic record, the third interface element 1230 can be updated to present the target diagnostic record.

[0197] In some embodiments, the processing device 210 can determine the start of a patient's consultation based on a call number instruction. A call number instruction is a doctor's command to begin the next patient's consultation. The doctor can initiate a call number instruction proactively through a public terminal or a doctor's terminal. Alternatively, the processing device 210 can automatically generate a call number instruction after the doctor submits the target diagnostic record for the previous patient. In some embodiments, when a patient receives on-site medical outpatient services, the processing device 210 can determine the start of the patient's consultation based on the patient's terminal's location information. Alternatively, the processing device 210 can determine the start of the patient's consultation based on an image of the patient entering the examination room acquired by a sensing device (e.g., an image sensor). When a patient receives remote medical outpatient services, the processing device 210 can determine the start of the patient's consultation by acquiring remote consultation confirmation messages sent by the doctor and patient respectively through the doctor's terminal and the patient's terminal.

[0198] The fourth interface element 1240 can be an icon corresponding to the consultation suggestion, or it can be used to present the content of the consultation suggestion. During the consultation process, after a consultation suggestion is generated based on the perceived information, the consultation suggestion can be presented through the fourth interface element 1240.

[0199] In some embodiments, the processing device 210 can provide services related to the consultation process to doctors and patients through doctors' doctor terminals and patients' patient terminals. At least a portion of the content presented on the doctor terminals and patient terminals can be synchronized.

[0200] In some embodiments, the processing device 210 can further provide services related to the consultation process to the remote patient via the remote terminal device (e.g., an XR terminal device). When the remote patient participates in the consultation process, the remote terminal device of the remote patient can simultaneously display a virtual consultation room.

[0201] In some embodiments, the processing device 210 can provide telemedicine outpatient services. For example, the processing device 210 can acquire or generate a 3D patient model. The 3D patient model may correspond to a patient or a part of a patient (e.g., the upper body). As an example only, the processing device 210 can acquire an initial 3D patient model from the patient's electronic medical record and update the initial 3D patient model based on the patient's real-time dynamic data and physiological data to obtain a 3D patient model. Furthermore, the processing device 210 can present the 3D patient model to a doctor and receive examination instructions input by the doctor through a doctor's terminal. Specifically, the processing device 210 can present the 3D patient model in the doctor's field of vision through the doctor's terminal. The examination instructions input by the doctor may include examination parts, examination equipment, and examination operations. The doctor can input examination instructions in various ways, such as voice, gestures, and operating input devices (e.g., smart gloves, smart grips, etc.). For example, the doctor's terminal can present virtual examination equipment corresponding to multiple examination devices. The doctor can select a virtual examination device through an input device and use the virtual examination device to perform virtual examination operations on the 3D patient model. The processing device 210 can determine the examination site, examination equipment, and examination operation based on the virtual examination operation performed by the doctor, and generate examination instructions. In addition to examination instructions, the doctor can also input other instructions to instruct the doctor's terminal to rotate, zoom in, zoom out, etc., of the 3D patient model.

[0202] In some embodiments of this application, doctors and patients can communicate remotely in a virtual examination room space via doctor terminals and patient terminals, providing a barrier-free and immersive medical experience. Furthermore, a three-dimensional patient model can be presented to the doctor, enabling more accurate and convenient remote examinations and improving diagnostic accuracy.

[0203] After completing their consultation, patients can proceed to the post-consultation phase. For example... Figure 8 As shown, operations related to the post-diagnosis process 840 may include providing medication dispensing services, providing examination services, and providing health monitoring services.

[0204] Medication pickup service assists patients in obtaining medications prescribed by their doctors. For example, it helps patients pay for medications, schedule pharmacy pickups, and guide them to the pharmacy. Examination service assists patients in undergoing examinations requested by their doctors. For example, it helps patients pay for examinations, schedule examinations with the relevant department, and guide them to the appropriate department.

[0205] In some embodiments, in response to detecting the end of the consultation process, the processing device 210 can determine the target service to be provided to the patient after the consultation process and make an appointment for the patient with the target business unit providing the target service. The processing device 210 can detect whether the consultation process has ended in a variety of ways. For example, the processing device 210 can determine that the patient's consultation process has ended when it detects that the doctor has submitted the patient's target diagnostic record or the doctor calls the next patient's number.

[0206] In some embodiments, the processing device 210 can determine the target service needed by the patient based on the target treatment prescription in the target diagnostic record. For example, the target service may be a medication pickup service, and the target business unit may be a pharmacy. When the patient needs a medication pickup service, the processing device 210 can send the patient's medication prescription information to the pharmacy and schedule a pickup. As another example, the target service may be an examination service, and the target business unit may be an examination department. When the patient needs an examination service, the processing device 210 can send the patient's examination prescription information to the examination department and schedule an examination. Optionally, after scheduling with the target business unit, the processing device 210 can send the scheduling information to the patient's terminal. Health monitoring services can be used to continuously monitor the patient's health status after the consultation process. For example, the processing device 210 can generate a health monitoring plan based on the target diagnostic record and enable one or more monitoring devices to obtain the patient's health monitoring information based on the health monitoring plan. Optionally, the processing device 210 can further update the health monitoring plan based on the health monitoring information.

[0207] In some embodiments, one or more operations in the medical outpatient process 800 may be performed by an intelligent agent corresponding to the medical outpatient service / process. In some embodiments, different stages of the medical outpatient process 800 may share a single intelligent agent, or different stages may correspond to different intelligent agents.

[0208] Figure 9 This is a schematic diagram of an exemplary process 900 for providing pre-consultation services according to some embodiments of this application. Figure 9 The process 900 shown can be executed in the waiting area 820.

[0209] Step 910: Determine the content of the second inquiry based on the doctor's department.

[0210] The second question, also known as the pre-consultation question, is used to conduct an initial inquiry with the patient before the formal consultation. The second question may involve multiple rounds of questioning. The content of the second question may include the questions asked in each round of questioning. Alternatively, the content of the second question may only include the questions asked in the first round of questioning.

[0211] In some embodiments, the processing device 210 can acquire a pre-consultation record template corresponding to the doctor's department and determine the second inquiry content based on the pre-consultation record template.

[0212] In some embodiments, the processing device 210 can obtain known information about the patient (e.g., electronic medical records, chief complaints, etc.) and determine any missing information not yet collected in the pre-consultation record template by comparing it with the known information. For example, if the known information includes the patient's family medical history, then the missing information does not need to include the family medical history. Similarly, if the patient's chief complaint includes the patient's medical history, then the missing information does not need to include the medical history. In some embodiments, the missing information can be determined based on the patient's basic information. For example, for male patients, the missing information does not need to include menstrual history or reproductive history. Furthermore, the processing device 210 can determine the content of a second inquiry based on the missing information.

[0213] In some embodiments, the processing device 210 may use a first query model to determine the content of a second query based on the doctor's department and known information about the patient. The first query model may include a CNN model, an RNN model, an LSTM model, a BERT model, a ChatGPT model, etc. In some embodiments, the first query model may include a missing information determination model and a first query content determination model. The missing information determination model may be configured to output missing information by processing the doctor's department and known information about the patient. The first query content determination model may be configured to output the second query content based on the patient's missing information.

[0214] Step 920: Based on the content of the second inquiry, control the patient terminal to conduct a second inquiry on the patient.

[0215] In some embodiments, after a patient registers with a doctor, the processing device 210 can determine the estimated waiting time for the patient to receive medical services. For example, the estimated waiting time could be the time difference between the current moment and the patient's registered appointment time slot. Alternatively, the estimated waiting time could be determined based on the doctor's daily outpatient record and the patient's registration record. The patient's registration record can include the patient's scheduled appointment time slot. The doctor's daily outpatient record reflects the doctor's outpatient activities for that day.

[0216] In some embodiments, in response to determining that the estimated waiting time is greater than a first preset time threshold, the processing device 210 may cause the patient's patient terminal to initiate a second inquiry to the patient or display a suggestion to conduct a second inquiry. This approach ensures sufficient time for pre-consultation and prevents doctors from calling patients during the pre-consultation process.

[0217] In some embodiments, in response to determining that the estimated waiting time is less than a second preset time threshold, the processing device 210 can enable the patient's terminal to initiate a second inquiry to the patient or display a suggestion to conduct a second inquiry. The second preset time threshold may be greater than a first preset time threshold. For example, when it is detected that the time remaining from the current time to the registration period is less than 24 hours (i.e., the estimated waiting time is less than 24 hours), the patient terminal can display a suggestion to conduct a second inquiry to the patient (e.g., by using a virtual avatar to make the suggestion), thereby promptly reminding the patient to conduct a pre-consultation.

[0218] In some embodiments, the processing device 210 may detect that a patient has initiated a pre-consultation request through a patient terminal, and then enable the patient's patient terminal to conduct a second inquiry with the patient.

[0219] In some embodiments, the patient terminal may present a second virtual avatar to conduct a second inquiry based on the second inquiry content. The second virtual avatar refers to a digitally created human figure with specific characteristics (e.g., specific physical features, voice characteristics, etc.) that can communicate with the patient for pre-diagnosis. Specifically, the processing device 210 can display the second virtual avatar on the screen of the patient terminal (e.g., an XR device) and play the second inquiry content through the patient terminal's audio output device. Simultaneously, the second virtual avatar can simulate human speech, gestures, etc., providing the patient with a realistic communication experience.

[0220] In some embodiments, the second virtual character may have preset physical characteristics. In some embodiments, the physical characteristics of the second virtual character may be determined based on optical image data of the doctor who registered the patient. In some embodiments, the physical characteristics of the second virtual character may be determined based on the patient's basic information. In some embodiments, the processing device 210 may select a suitable virtual character as the second virtual character from a virtual character library based on the doctor's physical characteristics and / or the patient's basic information.

[0221] In some embodiments, the second question includes multiple rounds of questioning, and the content of the second question may include the content of each round of questioning in the second question. The second question can be conducted through... Figure 10 The process shown is performed in step 1000.

[0222] like Figure 10As shown, for the first round of questioning, the processing device 210 can enable the patient terminal to conduct the first round of questioning based on the corresponding question content.

[0223] For each current round of questioning (excluding the first round of questioning), the processing device 210 can adjust the content of the current question (hereinafter referred to as the current question content) based on the second data collected before the current questioning, so that the question content is more in line with the patient's condition. Specifically, the processing device 210 can determine the semantic and emotional information of the patient's historical answers based on the second data collected before the current questioning. The second data can be collected by the sound sensor of the third terminal device after sound detection. Historical answers are the patient's answers to questions in previous rounds. The semantic information of historical answers represents the content of historical answers. The emotional information of historical answers can indicate the patient's emotions when providing historical answers (e.g., calm, tense, anxious, fearful, suspicious, irritable, etc.). The processing device 210 can determine the semantic information by performing text transcription, speech content recognition, etc. on the second data. The processing device 210 can determine the emotional information by analyzing the content, tone, intonation, speech rate, and other features of the second data.

[0224] Continue to refer to Figure 10 The processing device 210 can adjust the current inquiry content based on semantic and emotional information. For example, when the patient's emotional information is "nervous" or "fearful," the processing device 210 can add reassuring words to the current inquiry content. Similarly, when semantic information indicates that the patient has not clearly answered previous inquiries, the processing device 210 can adjust the current inquiry content to repeat the previous inquiries, thereby guiding the patient to provide clear answers. The originally determined current inquiry content can be used as the content for the next round of inquiries. This allows for timely adjustment of the current consultation content based on the patient's condition, thereby improving the quality of pre-consultation services.

[0225] In some embodiments, in addition to adjusting the current question content, the voice features used for the questioning can be adjusted in real time based on the patient's condition. Voice features include speech rate features, tone features, intonation features, volume features, etc. Figure 10 As shown, the processing device 210 can determine the voice characteristics of the current inquiry based on the semantic and emotional information of the patient's historical responses, and enable the patient's terminal to conduct the current inquiry based on the adjusted inquiry content and the voice characteristics of the current inquiry. This method can better cater to the patient's emotional changes, thereby enhancing the anthropomorphic effect of the second virtual character and improving the quality of pre-diagnosis services.

[0226] In some embodiments, such as Figure 10As shown, the processing device 210 can further obtain the patient's physiological state information. The patient's physiological state information can reflect the patient's real-time physiological state. The physiological state information may include the patient's physiological parameter values ​​(e.g., heart rate, pulse rate, respiratory rate, etc.). The physiological state information may also include information related to the patient's posture, limb behavior, facial expressions, muscle state, etc. In some embodiments, the patient's physiological state information can be obtained using a wearable device worn by the patient.

[0227] Furthermore, the processing device 210 can adjust the current inquiry content based on semantic information, emotional information, and physiological state information. Specifically, the processing device 210 can update the patient's emotional information based on the patient's physiological state information. It is understood that a patient's inner emotions are not always fully expressed through their answers; therefore, the patient's emotional information may be updated or modified based on the patient's physiological state information. In addition, the processing device 210 can adjust the current inquiry content based on semantic information and updated emotional information.

[0228] According to some embodiments of this application, by further considering the patient's physiological state data, the accuracy of the patient's emotional information can be improved, thereby improving the accuracy of adjusting the current inquiry content and thus improving the service quality of the pre-diagnosis service.

[0229] like Figure 10 As shown, in some embodiments, the processing device 210 can determine feedback parameters based on at least a portion of semantic information, emotional information, and physiological state information, and control the wearable device to apply feedback to the patient according to the feedback parameters. Feedback may include at least one of force feedback or temperature feedback. Feedback parameters can be used to control the manner in which feedback is applied, such as the type of feedback, the body part to which feedback is applied, and the intensity of feedback. In some embodiments, the processing device 210 can determine the patient's mood and mood level based on at least a portion of semantic information, emotional information, and physiological state information, and determine feedback parameters based on the mood and mood level. This method can promptly soothe the patient's negative emotions, thereby improving the quality of pre-consultation services.

[0230] In some embodiments, the processing device 210 may terminate the second query based on a second preset condition. The second preset condition may be that the number of remaining missing information is 0. The second preset condition may be that the time difference between the patient's current time and the estimated waiting time is less than a threshold. The second preset condition may also be similar to the first preset condition.

[0231] In some embodiments, the second inquiry content determined in step 910 may only include the inquiry content of the first round of inquiries. The current inquiry content of each current inquiry in the first round of inquiries may be determined during the second inquiry process. For example, in the current inquiry, the processing device 210 may input the inquiry content of historical inquiries, the patient's historical answers, the patient's known information, etc., into the second inquiry content determination model, and the second inquiry content determination model will output the current inquiry content.

[0232] Step 930: Generate a pre-consultation record based on the second data collected during the second inquiry on the patient's terminal.

[0233] The second data may include voice data, text data, and image data input by the patient through their terminal during the second consultation. The pre-consultation record can be used to record patient information collected during the second consultation (i.e., the pre-consultation). Optionally, some known information about the patient may also be recorded in the pre-consultation record. In some embodiments, the pre-consultation record is generated according to a preset template. The preset template may be a template corresponding to the doctor's department or a template set by the doctor.

[0234] For example, when the second data includes a speech signal, the processing device 210 can first transcribe the speech signal into text and extract the second keyword from the text using a keyword extraction algorithm. Furthermore, the processing device 210 can convert the second keyword into medical terminology. Additionally, the processing device 210 can obtain multiple template fields from the pre-consultation record template, retrieve the corresponding content for each template field from hospital terminology, and fill it into the appropriate position in the pre-consultation record template. The conversion of the second keyword can be based on a terminology conversion model or on a knowledge dictionary.

[0235] In some embodiments, the second inquiry can be performed via a terminal device other than the patient's terminal (e.g., a waiting terminal). In some embodiments, process 900 can be performed by an agent corresponding to a medical outpatient service or medical outpatient process. For example, a pre-consultation service can be provided by a pre-consultation agent.

[0236] Figure 11 This is a flowchart of an exemplary process 1100 for providing medical outpatient services based on perceived information, according to some embodiments of this application. In some embodiments, process 1100 may include one or more of sub-processes 1110, 1120, 1130, and 1140.

[0237] Sub-process 1110 can be used to provide consultation suggestions based on perceived information. Sub-process 1110 can be executed during the consultation phase 830. For example... Figure 11 As shown, subprocess 1110 may include steps 1112 and 1114.

[0238] Step 1112 involves generating consultation suggestions based on perceived information and the patient's patient data. Consultation suggestions refer to recommendations that assist doctors in providing outpatient medical services. Exemplary consultation suggestions may include suggestions for supplementary inquiries, physical examinations, prescriptions, and treatment plans.

[0239] In some embodiments, consultation recommendations can be determined based on a knowledge database corresponding to the registered department, consultation guidelines, etc. For example, processing device 210 can determine the content of the conversation between the doctor and the patient based on the voice signal collected by the sound sensor, and search the knowledge database, consultation guidelines, etc., based on the conversation content and / or patient data to determine consultation recommendations. As an example only, a search can be performed based on the conversation content and / or patient data in the consultation guidelines to determine which information in the consultation guidelines has not yet been collected, and supplementary inquiry suggestions can be provided based on this information.

[0240] In some embodiments, consultation suggestions can be generated based on a diagnostic model. Specifically, the consultation module 430 can determine the model input based on sensory information and patient data, and input the model input into the diagnostic model, which can then output corresponding consultation suggestions. For example, the model input may include patient data, communication content determined based on voice signals, patient status information determined based on image data, or any combination thereof.

[0241] In some embodiments, consultation recommendations may be generated by an agent corresponding to a medical outpatient service. The agent can learn a mechanism for generating consultation recommendations from various data (e.g., historical diagnostic records, knowledge databases, and consultation guidelines), and process perceived information and patient data according to this mechanism to provide consultation recommendations.

[0242] Step 1114: At least a portion of at least one terminal device can be controlled to present consultation suggestions.

[0243] For example, when a patient receives in-person medical consultation services in a clinic, the processing device 210 can control a public terminal device or a doctor's terminal to present consultation suggestions. Similarly, when a patient receives telemedicine consultation services, the processing device 210 can control both the doctor's terminal and the patient's terminal to present consultation suggestions. Consultation suggestions can improve the accuracy of diagnoses and prescriptions, and increase the efficiency of medical services.

[0244] Sub-process 1120 can be used to generate a target diagnostic record based on perceived information. Sub-process 1120 can be executed at the end of the consultation phase 830. Figure 11 As shown, subprocess 1120 may include steps 1122, 1124 and 1126.

[0245] Step 1122: An initial diagnostic record can be generated based on the perceived information.

[0246] The initial diagnostic record can be an automatically generated diagnostic record. In some embodiments, the initial diagnostic record may include the initial patient medical record, initial diagnostic opinion, initial diagnostic prescription (e.g., initial treatment prescription and initial examination prescription), initial medical orders, etc. In some embodiments, key content can be extracted from perceived information based on a diagnostic record template. Key content refers to content related to template fields in the diagnostic record template. Key content can be converted into professional content based on a knowledge dictionary or terminology conversion model. Further, the initial diagnostic record is generated by updating the diagnostic record template based on professional content and a knowledge database. The knowledge database refers to the knowledge database of the registered department, for example, including the department's consultation guidelines (e.g., disease description guidelines, diagnostic guidelines, prescription guidelines, medical order guidelines, etc.).

[0247] In some embodiments, physical examination data of patients collected by one or more examination devices during an outpatient process can be obtained, and an initial diagnostic record can be further generated based on the physical examination data. In some embodiments, the initial diagnostic record can be generated by an agent corresponding to the medical outpatient service. The agent can learn the mechanism for generating diagnostic records from various data (e.g., diagnostic record templates, knowledge dictionaries, knowledge databases, etc.), and process perceived information and patient data according to the learned mechanism to generate diagnostic records.

[0248] Step 1124: Present the initial diagnostic record to the doctor.

[0249] For example, processing device 210 can control a public terminal to present an initial diagnostic record, such as when a patient has started an outpatient visit. As another example, processing device 210 can control a doctor's terminal to present an initial diagnostic record to a doctor. In some embodiments, the doctor's terminal may present the initial diagnostic record to the doctor at a preset time (e.g., after the doctor has finished their day's consultations).

[0250] Step 1126: Generate the target diagnostic record based on the initial diagnostic record and the feedback information entered by the doctor on the initial diagnostic record.

[0251] The feedback information entered by the doctor may include modifications and / or confirmations of the initial diagnostic record. The target diagnostic record is the diagnostic record after the doctor's modifications and / or confirmation. In some embodiments, the target diagnostic record may include the target patient's medical record, the target diagnostic opinion, the target diagnostic prescription (e.g., the target treatment prescription and the target examination prescription), the target medical orders, etc.

[0252] By generating targeted diagnostic records, errors in manual writing of these records can be reduced, improving their generation efficiency. On the other hand, it reduces doctors' paperwork, allowing them to focus more on patient care and improving the quality of outpatient services.

[0253] Sub-process 1130 can be used to provide remote escort services based on perceived information. Patients can request remote escort services during the pre-consultation. Sub-process 1130 can be executed during the consultation phase 830. Figure 11 As shown, subprocess 1130 may include steps 1132 and 1134.

[0254] Step 1132: Based on the perceived information, determine whether the patient needs to communicate with the remote companion.

[0255] In some embodiments, the processing device 210 can detect whether a patient has requested to communicate with a remote companion based on perceived information (e.g., voice data and / or image data). In some embodiments, the processing device 210 can determine the patient's state information based on the perceived information and determine whether the patient needs to communicate with a remote companion based on the patient's state information. For example, when the state information indicates that the patient is in a state of high tension, fear, etc., the processing device 210 can determine that the patient needs to communicate with a remote companion.

[0256] When it is determined that the patient needs to communicate with a remote companion, the processing device 210 may execute step 1134.

[0257] Step 1134 allows control of at least a portion of at least one terminal device to magnify the second interface elements.

[0258] When a patient receives in-person medical consultation services in the clinic, the processing device 210 can control the public terminal device to zoom in on the second interface elements. When a patient receives telemedicine consultation services, the processing device 210 can control the patient's terminal to zoom in on the second interface elements. Through the zoomed-in second interface elements, the patient can view the real-time image of the remote companion and better communicate with them.

[0259] In some embodiments, when a patient is receiving on-site medical outpatient services in a clinic, and when it is detected that the patient needs to communicate with a remote companion, the processing device 210 can remind the patient to wear an XR device and control the XR device to display the image data of the remote companion.

[0260] In some embodiments of this application, the patient's communication needs can be detected based on sensory information, and these needs can be met in a timely manner, thereby providing the patient with more humane care and a more realistic and immersive accompanying experience.

[0261] Subprocess 1140 can be used to present medical data to target users based on perceived information. For example... Figure 11 As shown, subprocess 1140 may include steps 1142 and 1144.

[0262] Step 1142 may involve obtaining control commands issued by at least one target user based on perceived information, for retrieving at least a portion of medical data.

[0263] Target users may include at least patients and doctors. In some embodiments, target users may further include remote companions to the patient. Patient medical data may include various data reflecting the patient's health status (e.g., electronic medical records, medical images, medical examination results, etc.).

[0264] Control instructions are instructions used to retrieve and display at least a portion of medical data (such as electronic medical records). For example, control instructions may be used to retrieve and display a 3D model of a patient's organ of interest from an electronic medical record. In some embodiments, control instructions may also be used to set display parameters (such as display angle, display size, and display position). In some embodiments, control instructions may also be used to annotate key data on the medical data (such as the 3D model of the organ of interest).

[0265] In some embodiments, the perceptual information may include speech signals acquired by a sound sensor, and control commands may be obtained by performing semantic analysis on the speech signals. In some embodiments, the target user may issue control commands by uttering a preset wake word. In some embodiments, the perceptual information may include optical image data of the target user (e.g., a patient and / or doctor) acquired by an image sensor, and control commands may be obtained by performing gesture recognition on the target user in the optical image data. In some embodiments, the target user may issue control commands using a control device (e.g., a remote control, smart control gloves, etc.).

[0266] In some embodiments of this application, the target user can flexibly adjust the displayed content and / or display parameters, for example, through voice, gestures, etc., thereby optimizing the user experience and improving the efficiency of medical services.

[0267] In step 1144, in response to the control command, at least a portion of the medical data is retrieved and presented through the at least one terminal device.

[0268] For example, processing device 210 can retrieve at least a portion of the medical data from a storage device and control the at least one terminal device to display at least a portion of the medical data. When the control instruction includes a display parameter, processing device 210 can control the at least one terminal device to display at least a portion of the medical data based on the display parameter.

[0269] In some embodiments of this application, multiple target users can browse medical data together through at least one terminal device, and can synchronously change the presentation content and presentation method of medical data on different terminal devices. This helps to improve the communication efficiency between target users and enhance the interactivity of the medical treatment process.

[0270] Figure 13 This is a schematic diagram of an exemplary hospitalization process 1300 according to some embodiments of this application. Figure 13 As shown, the inpatient process 1300 includes inpatient admission 1310, admission inquiry 1320, inpatient procedure 1330, discharge 1340, follow-up 1350, etc., or any combination thereof. Different user services can be provided to relevant users of the inpatient process 1300 as the patient is at different stages of the inpatient process 1300. Relevant users of the inpatient process can include the patient, healthcare providers (e.g., doctors, nurses, etc.) providing medical services to the patient during the inpatient process, and the patient's visitors. In some embodiments, the processing device 210 (e.g., service module 430, an agent corresponding to the inpatient service / process configured on the processing device 210) can execute the steps involved in multiple stages of the inpatient process 1300.

[0271] At the hospital admission stage 1310, the patient can complete the relevant admission procedures. In some embodiments, hospitalization services related to the hospital admission stage 1310 can be provided to the relevant user. For example, hospitalization services may include guiding the patient to the patient's corresponding hospital ward, explaining the hospitalization rules to the patient, conducting admission examinations for the patient, generating the patient's registration record, etc., or any combination thereof. Further descriptions of hospitalization services can be found elsewhere in this application. For example, see... Figure 14 And its related descriptions.

[0272] In the admission inquiry stage 1320, the patient may receive an admission inquiry, which is used to collect basic information about the patient. In some embodiments, admission inquiry services related to the admission inquiry stage 1320 may be provided to relevant users. For example, admission inquiry services may include performing one or more inquiries on the patient, generating an admission record for the patient, or any combination thereof. The admission inquiry of the patient may be conducted in accordance with... Figure 9 and Figure 10The second inquiry described herein is conducted in a similar manner and will not be repeated here. In some embodiments, the processing device 210 may obtain feedback information regarding the admission record entered by the doctor through a doctor's terminal. The feedback information may include information that is not present in the admission record but is considered essential by the doctor. Further, the processing device 210 may determine the content of supplementary inquiries based on the feedback information and cause a public terminal device in the hospital ward to conduct supplementary inquiries based on the supplementary inquiries. The supplementary inquiries may be conducted in a manner similar to the admission inquiry. Then, the processing device 210 may obtain supplementary sensing information collected by one or more sensing devices during the supplementary inquiry and update the admission record based on the supplementary sensing information. Alternatively, the doctor may also conduct supplementary inquiries for the patient directly in the hospital ward. The processing device 210 may obtain supplementary sensing information collected by one or more sensing devices during the supplementary inquiry. The processing device 210 may further update the admission record based on the supplementary sensing information.

[0273] In the hospitalization phase 1330, a patient may stay in a hospital (e.g., a hospital ward) for a period of time to receive 24 / 7 medical care. In some embodiments, hospital ward services related to the hospitalization phase 1330 may be provided to the relevant user. For example, hospital ward services may include nursing services 1332, ward rounds services 1334, visitation services 1336, etc., or any combination thereof.

[0274] Nursing services 1332 refer to the provision of direct care to patients, including administering medication, conducting physical examinations, monitoring vital signs, and assisting with activities of daily living. Further descriptions of nursing services can be found elsewhere in this application. For example, see [link to relevant documentation]. Figure 15 And its related descriptions.

[0275] Ward rounds service 1334 involves ward rounds conducted by a medical team (e.g., at least one physician) of a patient in a hospital ward, where the medical team can review and discuss the patient's condition and care plan during the ward round. For example, ward rounds service 1334 may include presenting data to facilitate communication between physicians and patients, generating ward round records, presenting a virtual ward space to one or more telephysicians, or any combination thereof.

[0276] As an example only, processing device 210 can acquire sensory information collected by at least one physician during ward rounds in a hospital ward and / or physical examination data of patients collected by one or more examination devices during ward rounds, and generate ward round records based on the sensory information and / or the patients' physical examination data. The ward round records are used to record relevant data from the ward rounds, including the ward round time, participants, patient data, communication content between the patient and at least one physician, and medical orders during the ward rounds. As another example, processing device 210 can generate a virtual ward space based on sensory information and present the virtual ward space to one or more remote physicians via one or more XR devices. The virtual ward space refers to the digital environment of a ward round. Optionally, remote physicians can communicate with at least one physician and patient in the hospital ward via XR devices.

[0277] Visitation service 1336 allows remote visitors to communicate remotely with patients. For example, visitation service 1336 may include generating a virtual visitation space for patients and remote visitors, presenting a virtual visitation space to patients and remote visitors, or any combination thereof.

[0278] As an example only, upon responding to an access request, processing device 210 can acquire the patient's first current information and the remote visitor's second current information, and generate a virtual access space for the patient and the remote visitor based on the first and second current information. The first current information may indicate the patient's current state and / or current environment. The second current information may indicate the remote visitor's current state and / or current environment. The virtual access space refers to the digital environment presented to the patient and the remote visitor during the visit. Furthermore, processing device 210 can present the virtual access space to the patient and the remote visitor respectively through public terminal devices in the hospital ward and remote terminal devices of the remote visitor.

[0279] During the discharge process, patients can complete discharge procedures. In some embodiments, discharge services related to discharge procedure 1340 can be provided to relevant users to guide patients out of the hospital. As an example only, in response to a discharge instruction received from the patient's doctor's terminal, processing device 210 can obtain the patient's target hospitalization record. The target hospitalization record may record information about the patient's hospitalization process, such as medical history, treatments received, prescribed medications, examination results, and discharge summary. Furthermore, processing device 210 can generate discharge data based on the target hospitalization record and present the discharge data to the patient through a public terminal device in the hospital ward. Discharge data may include a discharge summary, doctor's discharge orders, guidance information on discharge procedures, guidance information on the discharge process, discharge fees, payment methods, etc., or any combination thereof. Accordingly, upon determining that the patient is performing a discharge procedure, processing device 210 can generate a discharge record corresponding to that patient. Discharge records are used to record relevant data upon discharge, including discharge time, discharge summary, doctor's discharge instructions, discharge fees, payment method, and the patient's condition at discharge.

[0280] In follow-up phase 1350, continuous care can be provided to the patient after discharge to ensure continued recovery, address any lingering health issues, and prevent readmission. In some embodiments, follow-up services related to follow-up phase 1350 can be provided to relevant users. As an example only, processing device 210 can determine a patient's follow-up plan based on the patient's target hospitalization record. The follow-up plan guides how follow-up services are provided to the patient. In some embodiments, the follow-up plan may include one or more follow-ups performed at one or more scheduled times. Furthermore, processing device 210 can prompt the doctor's physician terminal and the patient's patient terminal, respectively, according to the follow-up plan. Follow-ups can be conducted offline or remotely in a virtual follow-up space.

[0281] In some embodiments, after a follow-up visit, the processing device 210 can generate a follow-up record corresponding to the patient. The follow-up record records data related to the follow-up visit, including the time of the follow-up, updated medical orders, and health monitoring information. In some embodiments, the processing device 210 can update the follow-up plan. For example, the processing device 210 can acquire the patient's health monitoring information and update the follow-up plan based on this information. The health monitoring information can be collected by one or more home monitoring devices in the patient's home.

[0282] In some embodiments, the processing device 210 can monitor data sources that collect data related to the patient's hospitalization process. In response to detecting a data update in at least one data source, the processing device 210 can perform an Expression of Interest (EOI) detection based on the updated data collected from the at least one data source. If an EOI occurs, the processing device 210 can perform one or more preset operations corresponding to the EOI to provide at least a portion of the hospitalization services.

[0283] Updated data refers to data collected from at least one data source that has not yet been processed by processing device 210. For example, if at least one data source includes a sensing device, the updated data may include sensory information collected by the sensing device, such as image data collected by an image sensor, sound data collected by a sound sensor, etc. As another example, if at least one data source includes a terminal device of a doctor associated with the patient, the updated data may include patient input data entered by the doctor through that terminal device. As another example, if at least one data source includes a vital signs monitor, the updated data may include the patient's vital signs. As yet another example, if at least one data source includes a medical examination department, the updated data may include the patient's examination results.

[0284] An Expression of Interest (EOI) is a specific event or behavior that requires attention. EOI detection involves processing updated data collected from at least one data source to detect whether one or more EOIs have occurred. For example, exemplary EOIs may include: a patient being admitted to a hospital ward, a patient undergoing admission examination, at least one physician making rounds in a hospital ward, a patient undergoing a nursing procedure or medical examination, a patient initiating a service request, receiving or updating a physician's orders for a patient, an abnormal physiological state of a patient, a physician issuing instructions to a patient, or similar events, or any combination thereof.

[0285] In some embodiments, at least one data source may include multiple data sources that collect data related to the same EOI. In some embodiments, at least one data source may include data sources that collect data related to multiple EOIs.

[0286] In some embodiments, the processing device 210 may perform EOI detection based on EOI detection rules. EOI detection rules refer to the rules that need to be followed when performing EOI detection. In some embodiments, EOI detection rules may be determined based on the historical record of EOI detection, or manually set by a user (e.g., a doctor, nurse, technician, etc.).

[0287] In some embodiments, each stage of the hospitalization process may correspond to one or more Expressions of Interest (EOIs), and different stages of the hospitalization process may correspond to different types of EOIs. Therefore, the processing device 210 can perform EOI detection on updated data based on the patient's current stage in the hospitalization process.

[0288] Preset operations can include general operations and / or specific operations. General operations are those that need to be performed whenever an EOI occurs, regardless of the type of EOI. For example, general operations may include generating records associated with the EOI, sending the records associated with the EOI to the relevant users for confirmation, or sending them to storage devices for storage.

[0289] A specific action refers to the action performed when a specific type of Expression of Interest (EOI) occurs. For example, updating a patient's daily schedule based on updated data can be identified as a specific action corresponding to an EOI that updates a doctor's prescription for a patient. As another example, providing a notification related to an EOI to a healthcare provider can be identified as a specific action corresponding to an EOI that indicates an abnormality in a patient's physical condition.

[0290] For example, when the EOI includes a patient being admitted to a hospital ward, one or more preset operations may include: determining the content of the questions to be asked to the patient after the patient is admitted to the hospital ward based on the patient's patient data, enabling the terminal device in the hospital ward to conduct the questions based on the questions; acquiring the sensing information collected by one or more sensing devices in the hospital ward during the questioning period, and generating a hospitalization record for the patient based on the sensing information.

[0291] As another example, when the EOI includes a request for hospitalization guidance, one or more preset operations may include obtaining a first location of the patient's terminal and a second location of the patient's hospital ward, determining a planned path from the first location to the second location based on a real-time map of the hospital, and instructing the patient's terminal device to present the patient with guidance information related to the planned path.

[0292] As another example, when the EOI includes conditions for conducting admission examinations, one or more preset actions may include controlling a smart nursing vehicle to guide a nurse to a hospital ward to conduct admission examinations on the patient.

[0293] As another example, when the Expression of Interest (EOI) includes obtaining or updating a patient's medical orders, one or more pre-defined actions may include determining the patient's daily schedule based on the patient's patient data and medical orders or updated medical orders, presenting the daily schedule to the patient via a terminal device in the patient's ward, and presenting the daily schedule to the patient's corresponding nurse via a nurse's terminal device. The daily schedule may include requiring at least one medical procedure to be performed on the patient each day.

[0294] As another example, when the EOI includes at least one doctor making rounds in a patient's hospital ward, one or more preset operations may include acquiring sensing information collected by one or more sensing devices in the hospital ward when at least one doctor is making rounds in the hospital ward, and generating a ward round record based on the sensing information.

[0295] As another example, when the EOI includes obtaining a visitation request, one or more preset operations may include obtaining the patient's first current information and the remote visitor's second current information, generating a virtual visitation space for the patient and the remote visitor based on the first current information and the second current information, and presenting the virtual visitation space to the patient and the remote visitor respectively.

[0296] As another example, when the EOI includes a received discharge instruction, one or more preset operations may include obtaining the patient's target hospital record, generating discharge data based on the target hospital record, and presenting the discharge data to the patient through a terminal device in the patient's ward.

[0297] As another example, when the EOI includes a patient who has been discharged, one or more pre-defined actions may include determining a follow-up plan for the patient based on the patient's target hospital record. The follow-up plan may include one or more follow-ups performed at one or more scheduled times. For each of one or more follow-ups, the pre-defined actions may also include alerting the attending physician's terminal and the patient's terminal, respectively, according to the scheduled follow-up time.

[0298] In some embodiments, one or more preset operations can be performed based on the data source corresponding to the EOI. For example, when at least one data source includes multiple data sources that collect data related to the same EOI, one or more preset operations can be performed based on a combination of data related to the same EOI collected by the multiple data sources. As another example, at least one data source includes data sources that collect data related to multiple EOIs, and the one or more preset operations corresponding to at least two of the multiple EOIs can be different.

[0299] In some embodiments, the processing device 210 may be configured with an agent capable of executing at least a portion of the process 1300. For example, the agent may learn EOI detection rules from historical records and perform EOI detection according to the EOI detection rules. Alternatively, the agent may learn the correspondence between EOIs and preset operations from historical records and determine one or more preset operations corresponding to the EOI based on the correspondence.

[0300] In some embodiments, the agent can further learn EOI detection rules and / or the correspondence between EOI and preset operations based on patient data from different patients.

[0301] Figure 14This is a flowchart of an exemplary process 1400 for providing inpatient services, as shown in some embodiments of this application. Process 1400 can be executed when the processing device 210 detects that a patient has been admitted (e.g., the patient has completed the relevant admission procedures).

[0302] In step 1410, the processing device 210 can guide the patient to a hospital ward.

[0303] For example, processing device 210 can instruct the patient's patient terminal to guide the patient to a hospital ward. As an example only, in response to a hospitalization guidance request, processing device 210 can obtain a first location of the patient's patient terminal and a second location of the hospital ward, and determine a planned path from the first location to the second location based on a real-time map of the hospital. Processing device 210 can then instruct the patient terminal to present guidance information related to the planned path to the patient.

[0304] Step 1420: Processing device 210 can provide admission education to the patient.

[0305] Hospital admission education can be used to introduce patients to admission information (e.g., admission procedures, admission processes, pre-admission fees, payment methods, etc.), admission and hospitalization rules, the hospital environment, and the patient's doctor and / or nurse. In some embodiments, the processing device 210 can display a third virtual avatar providing admission education on the patient terminal.

[0306] Step 1430, the processing device 210 can assist the nurse in preparing for admission.

[0307] Hospitalization preparation can be performed by nurses, who prepare hospital supplies for the patient. In some embodiments, the processing device 210 can present the patient admission notification via the nurse terminal 1405 in the nurse workstation or the intelligent nursing cart 240-4 to assist nurses in admission preparation. The admission notification may include the patient's patient data, the patient's list of hospital supplies, the patient's ward information, information on the patient's admission examinations, etc.

[0308] Admission examinations, also known as inpatient examinations, are performed after a patient is admitted to a hospital ward. Admission examinations are used to gather information about the patient's current medical condition (e.g., vital signs, basic health data). Admission examinations may include checking blood pressure, blood sugar, heart rate, body temperature, or any combination thereof.

[0309] In step 1440, the processing device 210 may issue a reminder to perform admission examinations. The reminder may include a message reminder, an audio reminder, a pop-up reminder, etc. For example, the processing device 210 may instruct the nursing terminal device 1405 or the intelligent nursing cart 240-4 to display the reminder.

[0310] In some embodiments, the processing device 210 can determine whether a patient meets the criteria for admission examination in a hospital ward. The criteria for admission examination in a hospital ward may include that the patient has been in the hospital ward for a period of time. If the patient meets the criteria, the processing device 210 can issue a reminder to proceed with the admission examination.

[0311] In step 1450, the processing device 210 can guide the nurse to a hospital ward. In some embodiments, the processing device 210 can control the movement of the intelligent nursing cart 240-4 to guide the nurse into the hospital ward.

[0312] Step 1460 allows for admission examinations of the patient.

[0313] For example, after a nurse arrives at a hospital ward, one or more examination devices can be used to conduct an admission examination on the patient to collect the patient's physical examination data. In some embodiments, the processing device 210 can instruct the intelligent nursing vehicle to present information related to the admission examination to the nurse during the admission examination. For example, the intelligent nursing vehicle can display admission examination diagrams, the patient's electronic medical records, etc.

[0314] In step 1470, the processing device 210 can generate an admission record.

[0315] An admission record is a record that indicates a patient's admission to a hospital ward and / or the patient's status at the time of admission. Admission records may include admission information (e.g., admission number, clinical information, admission time, prepaid hospital fees, payment method, etc.) and physical examination data collected during the initial consultation.

[0316] In some embodiments, the processing device 210 can generate an admission record based on an admission record template and physical examination data. In some embodiments, the processing device 210 can further generate an admission record based on the patient's electronic medical record. In some embodiments, the processing device 210 can present the admission record to the nurse via the intelligent nursing cart 240-4 or the nurse terminal 1405, and generate a target admission record based on the admission record and feedback information entered by the nurse through the intelligent nursing cart 240-4 or the nurse terminal 1405. The feedback information may include confirmation instructions, modification instructions, etc., entered by the nurse.

[0317] In some embodiments, the processing device 210 may be configured with an agent (e.g., an admission agent) that may participate in one or more steps of the process 1400. For example, the agent may guide a patient into a hospital ward, provide admission education to the patient, assist nurses with admission examinations, generate admission records, etc.

[0318] According to some embodiments of this application, inpatient services can be provided to patients in a semi-automatic manner with the help of a medical service system (e.g., intelligent nursing vehicle 240-4) and / or intelligent agents, thereby reducing labor costs and improving the efficiency of inpatient services.

[0319] Figure 15 This is a schematic diagram of an exemplary process 1500 for providing care services, according to some embodiments of the present disclosure. In some embodiments, this process 1500 may be performed daily during a patient's hospitalization to provide care services to the patient.

[0320] Step 1502: The processing device 210 can determine the patient's daily schedule based on the patient's data and the doctor's instructions to the patient.

[0321] A doctor's orders to a patient refer to instructions or directives given by a doctor to a patient. In some embodiments, a patient's orders may be stored in a storage device and updated whenever a doctor issues a new order to the patient. Processing device 210 can retrieve the latest version of the orders from the storage device. In some embodiments, processing device 210 can monitor various hardware devices to detect whether a doctor's orders to a patient have been updated. For example, when providing admission inquiry services and / or ward rounds to a patient, the patient's doctor may issue a new order. Processing device 210 can detect the new order based on sensing information collected by sensing devices during admission inquiry services and / or ward rounds. Once a new order is detected, it can be stored in the storage device. As another example, a doctor can update patient orders stored in the storage device via a doctor's terminal. In some embodiments, processing device 210 can determine a doctor's orders based on the patient's electronic medical record.

[0322] In some embodiments, the processing device 210 can determine a patient's daily schedule based on the patient's patient data and the doctor's orders. The daily schedule may include requiring at least one medical procedure for the patient that day. Exemplary medical procedures may include nursing procedures, examinations, etc.

[0323] In step 1504, the processing device 210 can present the daily schedule to the patient via a public terminal device (e.g., a bedside terminal) in the hospital ward.

[0324] In step 1506, the processing device 210 can present the daily plan to the nurse corresponding to the patient through a nurse terminal (e.g., a terminal device in a nurse workstation).

[0325] Step 1508: When the daily plan includes at least one nursing procedure, the nurse may perform at least one nursing procedure on the patient, and the processing device 210 may assist the nurse in performing at least one nursing procedure according to the daily plan.

[0326] like Figure 15 As shown, for each of at least one nursing procedure, processing device 210 can control the intelligent nursing cart to guide the nurse to the hospital ward to perform the procedure according to the scheduled time of the nursing procedure. For example, before the scheduled time of the nursing procedure, the intelligent nursing cart can be controlled to move to the nurse's workstation, notifying the nurse that a nursing procedure needs to be performed on the patient. Then, the intelligent nursing cart can be controlled to move and guide the nurse to the patient's hospital ward. Processing device 210 can further control the intelligent nursing cart to display nursing instructions related to the nursing procedure after the nurse arrives at the hospital ward.

[0327] In step 1510, the processing device 210 can generate a nursing record.

[0328] A nursing record refers to a record of nursing procedures applied to a patient and / or their condition (e.g., vital signs and other physiological measurements) before, after, or during a nursing procedure. In some embodiments, the processing device 210 may acquire fifth sensing information collected by one or more sensing devices within a hospital ward while performing at least one nursing procedure, and generate a nursing record based on this fifth sensing information. In some embodiments, the nursing record may be displayed to a nurse for confirmation via a smart nursing cart or a nurse terminal.

[0329] In some embodiments, the processing device 210 may be configured with an intelligent agent (e.g., a nursing agent) that can participate in the execution of process 1500. For example, the intelligent agent may determine the patient's daily schedule, present the daily schedule to the patient and / or nurse, assist the nurse in performing at least one nursing procedure, and generate a nursing record. In some embodiments, the processing device 210 configured with the nursing agent may be integrated into a hospital bed, into a public terminal device in a hospital ward, or into a smart nursing vehicle.

[0330] According to some embodiments of this application, the automated generation of daily plans and nursing records can significantly reduce the workload of nurses. This automation allows nurses to focus more on direct patient care rather than administrative tasks. Furthermore, monitoring of updated medical orders ensures timely updates to daily plans. This proactive approach improves nursing efficiency and quality by ensuring that interventions and care plans are adjusted promptly based on the latest medical instructions.

[0331] Figure 16 This is an exemplary schematic diagram of a process 1600 for surgical planning and execution according to some embodiments of this application. Process 1600 may be executed by a processing device 210 (e.g., service module 430, an agent corresponding to a surgical service / process configured on the processing device 210).

[0332] Step 1610: Plan the surgery.

[0333] Surgical planning refers to the process of developing a surgical plan (e.g., an optimal surgical plan or multiple feasible surgical plans) for a patient. In some embodiments, processing device 210 can generate a surgical plan based on patient data (e.g., patient personal data, historical diagnostic and treatment data, medical examination data, etc.), physician feedback information (e.g., second feedback information), and / or sensory information (e.g., fourth sensory information). In some embodiments, processing device 210 can generate an initial surgical plan based on patient data, present the patient data to the physician through a physician terminal, and generate a surgical plan based on the initial surgical plan and second feedback information about the initial surgical plan input by the physician through the physician terminal.

[0334] In some embodiments, the processing device 210 can determine the surgical difficulty coefficient based on patient data, and further determine whether to convene an expert meeting based on the surgical difficulty coefficient. In response to determining that an expert meeting is needed, the processing device 210 presents virtual meeting spaces via the doctor's terminal and the remote expert's remote terminal device (e.g., an XR device). During the expert meeting, the processing device 210 obtains fourth-sensory information collected by the doctor's terminal and the remote terminal device. The processing device 210 generates a surgical plan based on the patient data and the fourth-sensory information.

[0335] In some embodiments, the processing device 210 can generate a risk assessment result for the surgical plan by processing the surgical plan and at least a portion of patient data using a risk assessment model. The processing device 210 determines risk prevention measures based on the risk assessment result and presents the risk assessment result and risk prevention measures of the surgical plan to the physician. In some embodiments, the processing device 210 can perform... Figure 17 Steps 1710-1740 are used to generate a surgical plan.

[0336] Step 1620: Perform a surgical simulation.

[0337] Surgical simulation refers to the process by which doctors practice surgery in a safe and controlled environment to improve surgical planning and / or enhance their surgical skills. For example, for complex or rare surgeries, doctors can use XR equipment to simulate surgery on a virtual patient in a virtual surgical scenario (e.g., an extended reality surgical scenario) based on the surgical plan. This allows them to identify potential risks during the surgery and develop corresponding risk prevention measures. Furthermore, for multiple surgical plans, doctors can simulate each plan in a virtual surgical scenario using extended reality equipment to compare the advantages and disadvantages of different plans and determine the optimal surgical plan.

[0338] In some embodiments, the processing device 210 can generate a virtual surgical scene for surgical simulation based on the surgical plan, and present the virtual surgical scene to the doctor through the doctor's terminal. The processing device 210 can obtain interactive instructions related to the virtual surgical device input by the doctor through the doctor's terminal or an interactive device corresponding to the virtual surgical device. The processing device 210 can update the virtual surgical site and virtual surgical device in the virtual surgical scene according to the interactive instructions.

[0339] In some embodiments, the processing device 210 can determine potential emergency situations in the virtual surgical scenario based on interactive instructions. Based on the potential emergency situation, the processing device 210 can update the virtual surgical site and virtual surgical equipment in the virtual surgical scenario. As an example only, the processing device 210 can obtain simulation data of the virtual surgical site and virtual surgical equipment during the surgical simulation process. The processing device 210 can determine whether the surgical plan needs optimization based on the simulation data. In response to determining that the surgical plan needs optimization, the processing device 210 can update the surgical plan based on the simulation data. In some embodiments, step 1620 can be omitted.

[0340] Step 1630: Prepare the patient for surgery.

[0341] Preoperative patient preparation refers to the preparations made by the patient before the surgical procedure or before entering the operating room for the surgical procedure. For example... Figure 16 As shown, preoperative patient preparation may include preoperative education (or preoperative care) 1632 and preoperative instruction 1634.

[0342] Preoperative education refers to the process of explaining the patient's condition and surgical plan to the patient and / or their family, and predicting the patient's postoperative recovery. Preoperative education can be achieved through... Figure 17 The process is as follows: 1700. Preoperative guidance refers to the process by which patients complete preoperative preparations before surgery. Preoperative education can be conducted according to... Figure 18 The process is carried out at 1800.

[0343] Step 1640, surgery performed.

[0344] Surgical execution refers to the procedures performed on a patient after entering the operating room. In some embodiments, the processing device 210 may acquire first sensing information collected by one or more first sensing devices in the operating room during the patient's surgery and perform an Expression of Interest (EOI) detection on the first sensing information. In response to determining that an EOI has occurred, the processing device 210 may execute one or more preset operations corresponding to the EOI. For example, the EOI may include a target surgical tool instruction issued by the surgical participant, and one or more preset operations corresponding to the EOI may include instructing an intelligent robotic nurse to pass the target surgical tool to the surgical participant. As another example, the first sensing information may include an image of the surgical tool captured by an image sensor, the EOI may include a count of surgical tools being less than a preset value, and one or more preset operations corresponding to the EOI may include controlling the intelligent robotic nurse to replenish the surgical tool. As another example, the EOI may include detecting surgical risks, and one or more preset operations corresponding to the EOI may include providing notification about the surgical risks. As another example, the EOI may include the surgery being completed, and one or more preset operations corresponding to the EOI may include generating a surgical record based on the first sensing information.

[0345] Step 1650: Postoperative review.

[0346] Postoperative review may include at least one of the following: updating medical advice reports, generating surgical results and physician operation records (to facilitate review of the surgical procedure), and developing a postoperative care plan.

[0347] Figure 17 This is a schematic diagram of an exemplary preoperative education process 1700 according to some embodiments of this application.

[0348] Step 1710: Generate explanatory materials for explaining the surgical plan.

[0349] The explanatory materials are configured to explain information related to the surgical plan, such as explanatory notes on the surgical plan, the execution process of the surgical plan at the patient's surgical site, and the postoperative recovery process after the patient uses the surgical plan. In some embodiments, the explanatory materials may include text, images, audio, or video. In some embodiments, multiple surgical plans may exist. The processing device 210 can generate explanatory materials corresponding to each surgical plan.

[0350] In some embodiments, the explanatory material is generated based on a digital twin model (e.g., a three-dimensional anatomical model) of the patient's surgical site. For example, processing device 210 can simulate the surgical procedure and outcome (e.g., postoperative incision size) based on a surgical plan on a three-dimensional anatomical model of the patient's surgical site.

[0351] In some embodiments, the explanatory materials include surgical videos. The surgical videos demonstrate the surgical procedure at the patient's surgical site. For example, in a surgical plan where invasive surgery is the type of procedure, the surgical video shows the appearance of the patient's surgical site before the incision, the incision process with a scalpel, the removal of the lesion, the suturing process, and the appearance after the suturing process.

[0352] In some embodiments, explanatory materials may include a patient's postoperative recovery process. For example, surgical videos may further demonstrate the patient's postoperative recovery process. Processing device 210 may predict the patient's postoperative recovery process based on patient data. The recovery process reflects the healing of the patient's vital signs and surgical wound. In some embodiments, surgical videos may further demonstrate the risks the patient faces during or after surgery (e.g., intraoperative and postoperative risks). Postoperative risks refer to adverse conditions the patient may face after surgery.

[0353] Step 1720: The explanatory materials can be presented to both the patient and the doctor simultaneously via at least one terminal device.

[0354] In some embodiments, at least one terminal device includes a patient's patient terminal, a doctor's doctor terminal, and a home terminal device. For example... Figure 17 As shown, the processing device 210 can simultaneously present explanatory materials to the patient, doctor, and family members via the XR device 260-2 worn by the patient, the XR device 270-2 worn by the doctor, and the XR device 1722 worn by the family member. In some embodiments, the processing device 210 can simultaneously present explanatory materials via at least one terminal device, with the doctor providing explanations. Users can choose to update the displayed content and display method of the explanatory materials by inputting commands through their own terminal devices.

[0355] Step 1730: Based on the second sensing information collected by one or more second sensing devices during the explanation of the surgical plan, determine the first feedback information about the surgical plan.

[0356] A second sensing device refers to a sensing device configured to receive input information (e.g., text information, voice information, etc.) from a user (e.g., a doctor or patient). For example, a second sensing device may be a sound sensor (e.g., a microphone), an image sensor, etc., integrated into a user terminal device.

[0357] The first feedback information includes feedback from preoperative education participants (e.g., doctors, patients, and patients' families) regarding the surgical plan. For example, the first feedback information may include at least selection information for the surgical plan. Selection information refers to the result of selecting a surgical plan. In some embodiments, the first feedback information may also include modification information for the selected surgical plan. The processing device 210 may analyze and process the second perceptual information using speech recognition, image recognition, or the like to determine the first feedback information.

[0358] Step 1740: Confirm or update the surgical plan based on the first feedback information.

[0359] In some embodiments, the processing device 210 can determine a target surgical plan from multiple surgical plans based on first feedback information. In some embodiments, the processing device 210 can update the patient's surgical plan based on the first feedback information. In some embodiments, after determining the target surgical plan from multiple surgical plans, the processing device 210 can further obtain a first confirmation instruction and a second confirmation instruction. The first confirmation instruction is an instruction regarding the surgical plan entered by the patient through a patient terminal. The second confirmation instruction is an instruction regarding the surgical plan entered by the patient's family member through a home terminal device. In response to receiving the first and second confirmation instructions, the processing device 210 can cause the patient terminal, doctor terminal, and home terminal device to respectively present operating protocols. The processing device 210 can obtain signature information of the surgical protocol from the patient terminal, doctor terminal, and home terminal device respectively.

[0360] The input method for confirmation instructions or signature information may include button input, gesture input, voice input, etc. In some embodiments, the input method for confirmation instructions or signature information may be fingerprint input. The processing device 210 may verify the user's identity based on the fingerprint input by the user, for example, using blockchain verification technology.

[0361] Step 1750: Generate a video explaining the surgical plan.

[0362] In some embodiments, such as Figure 17 As shown, processing device 210 can generate explanatory annotations for the surgical plan based on the second sensory information. Processing device 210 can create an explanatory video of the surgical plan based on the surgical video and the explanatory notes. The explanatory notes may include the surgeon's explanations of one or more frames in the surgical video and the corresponding operations. For example, the explanatory notes may include explanations of incision site selection, incision path, incision length, etc. The explanatory notes can be incorporated into the surgical video in text or audio form to obtain the explanatory video.

[0363] In some embodiments, the processing device 210 may acquire interactive instructions related to the explanatory materials from at least one terminal device, and update the explanatory materials displayed through the at least one terminal device based on the interactive instructions. Interactive instructions refer to control or modification instructions for the explanatory materials input by a patient through a patient terminal or by a doctor through a doctor terminal. For example, if the explanatory material is a surgical video, the interactive instruction might be "rewind the video 15 seconds."

[0364] According to some embodiments of this application, in a virtual patient education space, the patient's condition progression and surgical plan can be explained to the patient and their family via video, enabling remote doctor-patient communication. This helps the patient and their family to quickly understand the situation, improves the efficiency of doctor-patient communication, helps the patient and their family to fully understand the patient's current condition and postoperative risks, reduces the patient's fear and anxiety, and increases the success rate of the surgical procedure.

[0365] Figure 18 This is a schematic diagram of an exemplary preoperative guidance process according to some embodiments of this application.

[0366] Preoperative guidance may include patient transport, patient verification, preoperative education, preoperative cleaning, and establishment of intravenous access. Patient transport refers to moving the patient from his / her current location to the waiting area of ​​the operating room.

[0367] Patient verification refers to verifying whether a patient meets the surgical criteria. For example, patient verification may include: verifying whether the verification subject's identity information matches the target patient for the current surgical procedure; verifying whether the verification subject's surgical schedule is currently available; and verifying whether the verification subject's current physical condition meets the requirements of the surgical procedure. It is understandable that if the verification subject does not meet any of the surgical criteria, the patient's surgical schedule may be postponed or delayed.

[0368] In some embodiments, the processing device 210 may collect the patient's biometric information through one or more third sensing devices in the waiting area and verify the patient's identity based on the biometric information. For example, such as Figure 18 As shown, after transporting the patient to waiting area 1810, processing device 210 can collect the patient's biometric information through one or more third sensing devices 1811 (e.g., image capture device, microphone, fingerprint sensor, etc.) in waiting area 1810, and verify the patient's identity based on the biometric information (e.g., perform patient authentication). In some embodiments, processing device 210 can utilize a nurse agent to verify the patient's identity. For example, the nurse agent can verify the collected biometric information or verify the patient's identity through voice interaction with the patient (e.g., asking the patient's age, name, gender, etc.).

[0369] Preoperative care includes preoperative reassurance and preoperative education. Preoperative reassurance refers to preoperative preparation, using methods such as verbal communication, videos, and music to help reduce negative emotions in patients (e.g., anxiety, tension, fear). Preoperative education refers to preoperative preparation, helping patients understand the surgical procedure. Preoperative cleaning refers to preoperative preparation, such as body cleaning, hair removal (e.g., hair removal), and dressing the patient in surgical gowns. Establishing intravenous access refers to establishing a pathway for intravenous drug administration to ensure that medications are effectively delivered to the patient during surgery.

[0370] In some embodiments, the processing device 210 can determine a planned path from the patient's current location to the waiting area and control the smart wheelchair to transport the patient to the waiting area along the planned path. For example, as Figure 18 As shown, before performing preoperative procedures on the patient according to the surgical plan, the processing device 210 can determine a planned path from the patient 261's current location 1803 (e.g., a hospital ward) to the waiting area 1810. The processing device 210 can control the intelligent wheelchair 240-5 to transport the patient 261 from the hospital ward 1803 to the waiting area 1810 along the planned path.

[0371] In some embodiments, the processing device 210 may determine a planned route from the current location to the waiting area based on a hospital map. In some embodiments, the processing device 210 may configure a nurse agent that performs certain tasks on behalf of a nurse and may present a virtual nurse avatar. The processing device 210 may use the nurse agent to control a smart wheelchair to transport the patient from the current location to the waiting area. In some embodiments, after transporting the patient to the waiting area, the processing device 210 may perform patient verification.

[0372] In some embodiments, the processing device 210 can determine preoperative care materials for a patient based on patient data and surgical plans. During patient transport to the waiting area, the processing device 210 can use a patient terminal to provide preoperative education based on the preoperative care materials. Preoperative care materials may include videos, music, images, text, and other materials related to surgical explanation and / or emotional relaxation.

[0373] In some embodiments, the processing device 210 may use a nurse agent to provide preoperative education to patients. For example, such as Figure 18As shown, the processing device 210 can display a virtual nurse avatar 1823 on the XR device 260-2 worn by the patient 261. The virtual nurse avatar 1823 explains preoperative nursing materials to the patient 261. In some embodiments, the virtual nurse avatar 1823 can interact with the patient 261 via voice to alleviate the patient's negative emotions or answer the patient's questions through communication. In some embodiments, the processing device 210 can determine whether it is necessary to alleviate the patient's emotions by collecting the patient's facial expressions, physiological characteristics, tone of voice, etc.

[0374] In some embodiments, the processing device 210 may use a nurse agent to guide nurses in performing preoperative cleaning and / or establishing intravenous access.

[0375] In some embodiments, during the transport of a patient to a waiting area, the processing device 210 may obtain third-sensing information related to a portion of the planned path from the current location of the smart wheelchair to the waiting area (e.g., a portion of the planned path that the smart wheelchair has not yet traveled) via one or more fourth-sensing devices in the hospital. Based on the third-sensing information, the processing device 210 may determine the potential risks of the untraveled portion of the planned path and update the untraveled portion based on the potential risks.

[0376] One or more fourth-sensing devices may include image capture devices (e.g., infrared surveillance camera 1813), lidar, etc. These devices may be installed in locations such as smart wheelchairs, hospital ceilings, or hospital walls.

[0377] In some embodiments of this application, the aforementioned preoperative guidance process provides a humanized, transparent, and efficient preoperative preparation process. Furthermore, preoperative preparation items can be dynamically adjusted based on patient feedback, improving efficiency. The aforementioned patient transport and identity verification processes avoid human error and enhance the safety of the entire surgical procedure. Utilizing virtual nurse images to assist in completing many preoperative preparation tasks can save labor costs.

[0378] Figure 19 This is a schematic diagram of an exemplary surgical procedure 1900 according to some embodiments of this application. The surgical procedure may include preoperative preparation, intraoperative matters, and postoperative matters. Figure 19 As shown, preoperative preparation (i.e., the steps before the surgery) may include steps 1911, 1913, and 1915.

[0379] Step 1911: Activate the operating room.

[0380] Activating the operating room may include opening the operating room door, activating surgical equipment and monitoring equipment within the operating room, adjusting parameters within the operating room, and verifying the status of the surgical equipment. In some embodiments, the processing device 210 may control the intelligent robot nurse to activate the operating room or guide the nurse to activate the operating room. For example, the processing device 210 may control the intelligent robot nurse to automatically activate the operating room equipment at a predetermined surgical time and adjust the indoor temperature, humidity, and air quality.

[0381] Step 1913: Prepare surgical instruments.

[0382] Surgical tools may include surgical instruments and surgical consumables. In some embodiments, the processing device 210 may control the intelligent robotic nurse to prepare surgical tools in the operating room before surgery, according to the surgical plan. In some embodiments, the processing device 210 may further control the intelligent robotic nurse to disinfect and arrange the operating table (e.g., to position various surgical tools on the operating table).

[0383] Step 1915, Identify and / or anesthetize the patient. Patient identification means confirming the patient's identity. Patient anesthesia means administering anesthesia to the patient.

[0384] Step 1920: Perform the surgical procedure. In some embodiments, such as... Figure 19 As shown, matters during the surgical procedure (e.g., intraoperative matters) may include remote collaboration, tool transfer, image interaction, intraoperative planning and navigation, and real-time alerts.

[0385] Remote collaboration refers to remote participation in and / or guidance of the surgical procedure.

[0386] Tool delivery refers to the handing over of surgical tools to the surgical practitioner during surgery. In some embodiments, processing device 210 can identify instructions issued by the surgical participant for a target surgical tool based on first sensing information collected by one or more first sensing devices in the operating room during surgery. Based on these instructions, processing device 210 can control an intelligent robotic nurse to deliver the target surgical tool to the surgical participant.

[0387] Image interaction refers to displaying a digital body model of the patient (e.g., a three-dimensional anatomical model of the surgical site), the patient's electronic medical record, the surgical plan for the current operation, real-time images of the patient's surgical site, etc., to surgical participants (e.g., local surgical participants, remote surgical participants) and / or the patient through interactive devices (e.g., displays in the operating room, doctor's terminal 270).

[0388] Intraoperative planning and navigation refers to the process of fusing images of the patient's lesion (e.g., CT scan images of the lesion) with the patient's digital body model during surgery, projecting the lesion image onto the patient's body, or overlaying the positioning and tracking of surgical tools to guide surgical participants in the operation.

[0389] Real-time alarms can include behavioral alarms for surgical participants, patient vital sign alarms, and equipment status alarms. Behavioral alarms refer to the monitoring and alerting of surgical participants' intraoperative actions. Patient vital sign alarms can be activated when abnormalities occur in patient vital signs (e.g., electrocardiogram, blood pressure, etc.). Equipment status alarms are alerts issued when surgical equipment malfunctions.

[0390] like Figure 19 As shown, the post-operative process (e.g., post-operative matters) may include steps 1931, 1933, and 1935.

[0391] Step 1931, Patient Transfer. Patient transfer refers to the process of moving the patient from the operating room to the recovery area after the surgical procedure is completed. In some embodiments, the patient transfer may be performed by a healthcare professional assisted by an intelligent robotic nurse.

[0392] Step 1933: Perform operating room cleaning. Operating room cleaning refers to the process of cleaning or disinfecting surgical equipment and instruments. In some embodiments, the processing device 210 can control an intelligent robotic nurse to perform the room cleaning operation.

[0393] Step 1935: Generate the surgical report.

[0394] The surgical report may include surgical-related information, patient-related records, participant-related records, etc. In some embodiments, the processing device 210 may generate an initial surgical report based on data collected during the surgical procedure (e.g., first sensing information collected by one or more first sensing devices in the operating room). The processing device 210 may generate a surgical report based on the initial surgical report and feedback information entered by the physician regarding the initial surgical report.

[0395] In some embodiments, the processing device 210 can also monitor the patient's postoperative vital signs using vital sign monitoring equipment (e.g., electrocardiogram monitor, blood pressure monitor, etc.) in the hospital ward to determine whether the patient's postoperative vital signs are within the normal range, whether there are any abnormalities, or whether the recovery process is normal. Furthermore, the processing device 210 can update the medical recommendation report based on the patient's postoperative vital signs. In some embodiments, the processing device 210 can update the medical recommendation report according to the doctor's instructions. In some embodiments, the processing device 210 can send the updated medical recommendation report to the display device of the nurse's workstation and / or the display device of the doctor's workstation.

[0396] In some embodiments, the processing device 210 can determine a postoperative care plan based on an updated medical advice report. A postoperative care plan refers to the nursing tasks that need to be performed by caregivers (e.g., nurses, caregivers, etc.) during the patient's postoperative hospitalization. In some embodiments, the processing device 210 can control intelligent surgical equipment (e.g., intelligent nursing cart 240-4) to provide care to the patient according to the postoperative care plan. In some embodiments, the processing device 210 can send the postoperative care plan to a nurse so that the nurse can provide postoperative care to the patient. In some embodiments, the processing device 210 can update the postoperative care plan in real time based on the patient's condition during the care process. The execution of the postoperative care plan is similar to... Figure 15 The daily schedule described in the document.

[0397] In some embodiments, the processing device 210 can generate surgical results and surgical records for doctors based on surgical reports and medical advice reports, so that doctors can review the surgical procedure. Surgical results refer to data reflecting the outcome of the surgical process. In some embodiments, surgical results also include summary data of surgical results over a predetermined time period (e.g., one month). Surgical records refer to the doctor's operational records during the surgical procedure. Operational records may include motion records, force records, positioning records, etc. In some embodiments, the processing device 210 can generate surgical results and surgical records based on surgical reports and medical advice reports.

[0398] In some embodiments, the surgical procedure can be reviewed. For example, processing device 210 can present the surgeon's surgical results and surgical records to the surgeon, thereby allowing the surgeon to review the surgical procedure.

[0399] Figure 20 This is a schematic diagram of an exemplary medical service process 2000 according to some embodiments of this application. In some embodiments, a processing device 210 (e.g., a service module 430 or an agent corresponding to a patient service configured on the processing device 210) may perform the steps involved in the medical service process 2000.

[0400] Step 2010: Obtain patient data.

[0401] Patient data may be information related to patients receiving medical services. In some embodiments, patient-related data may include, but is not limited to, patient location information 2011, patient interaction information 2012, patient examination data 2013, sensory data 2014, clinical pathways 2015, and / or data entered by the healthcare provider 2016.

[0402] Patient location information 2011 is information used to determine the patient's location at the current moment.

[0403] Patient interaction information 2012 can be information generated through interactions between patients and terminal devices. Examples include personal information, health status, medical history, symptom descriptions, and lifestyle habits entered by patients through patient terminals and / or hospital terminals. Other examples include patient responses, remote companionship requests, and selected target stages entered by patients through patient terminals.

[0404] The examination data 2013 refers to the results of examinations related to the patient's health status. Examples include the patient's examination reports, medical images, and vital signs.

[0405] Sensing data 2014 refers to information collected by sensing devices. For example, when a patient is in a hospital, patient data may include patient-related sensing information collected by one or more sensing devices in the hospital.

[0406] Clinical pathways 2015 refer to standardized models and methods for providing healthcare services, which can be tailored to specific diseases or conditions by developing detailed treatment steps and management plans. For example, a clinical pathway can be a time-series table that details standardized, evidence-based diagnostic and treatment steps for a specific patient group within a specific time period. These steps can include specific operations and goals at each point in time corresponding to the processes of diagnosis, treatment, nursing care, and rehabilitation.

[0407] Data input by healthcare providers in 2016 refers to patient-related data input by healthcare providers (e.g., doctors, nurses, caregivers, etc.) through doctor terminals or hospital terminal equipment, such as disease diagnoses, treatment plans, medical orders, and document modifications.

[0408] In some embodiments, the acquisition module 410 may acquire patient-related data through one or more hardware devices, including a patient terminal 2010-a, a doctor terminal 2010-b, a hospital terminal device 2010-c, an examination device 2010-d, and / or a sensing device 2010-e of the patient's environment.

[0409] Step 2020: Based on patient data, the system detects that the patient has entered the target stage of the medical service process.

[0410] The medical service process is a series of standardized operations and service steps that a patient experiences from their first contact with medical services to the completion of treatment and their departure. For example... Figure 20 As shown, the medical service process can include multiple stages such as registration, waiting, consultation, hospitalization, and follow-up. The target stage refers to the medical service stage the patient is about to enter. A detailed description of how to detect when a patient enters the target stage can be found... Figure 21 Found it.

[0411] Step 2030: In response to detecting that a patient has entered the target stage, control the patient terminal to perform at least one first preset operation corresponding to the target stage.

[0412] The first preset operation refers to the dynamic operation performed through the interactive interface of the patient terminal. Figure 22 This is a schematic diagram illustrating an exemplary first preset operation according to some embodiments of this application. For example... Figure 22 As shown, the first preset operation may include one or more of the following: presenting guidance information 2210, presenting introductory information for the target stage 2220, and / or presenting a service entry point 2230. The guidance information is navigation information for a planned path from the patient's current location to the target location corresponding to the target stage. The planned path can be determined by acquiring an initial 3D map of the hospital and real-time information related to the hospital, generating a real-time 3D map of the hospital based on the initial 3D map and the real-time information, and determining the planned path based on the real-time 3D map of the hospital.

[0413] The introductory information for the target procedure describes the medical services and processes involved. In some embodiments, the processing device 210 may present a virtual avatar explaining the introductory information. Alternatively, after providing the introductory information, the processing device 210 may receive a question about the target procedure from the patient's terminal and determine the answer to that question. The processing device 210 may then present the answer to the question to the patient via the patient's terminal.

[0414] A service entry point is the point through which a user obtains medical services at a target stage and / or at a stage following the target stage. In some embodiments, the processing device 210 may display guidance information related to the planned path from the patient's current location to the target location corresponding to the target stage on the patient's terminal, and determine whether the patient has reached the target location based on relevant patient data. To determine that the patient has reached the target location, the processing device 210 may display a service entry point on the patient terminal for accessing user services related to the target stage.

[0415] In some embodiments, the patient terminal includes an XR device, and the processing device 210 enables the XR device to overlay information related to a first preset operation onto the patient's real-world view using AR or MR technology. In some embodiments, the patient terminal has a patient space application. The patient space application can be used to obtain patient interaction information 2012 between the patient and the patient terminal. The first preset operation can be performed using the patient space application.

[0416] In some embodiments of this application, when a patient is detected to have entered a target stage, the patient terminal is controlled to perform a first preset operation according to the target stage, providing the patient with medical services corresponding to the target stage and helping the patient participate in the required medical service process, thereby improving the efficiency and quality of medical services.

[0417] In some embodiments, in response to detecting that a patient has switched from the current medical service stage to the target stage, the doctor's terminal is controlled to perform at least one second preset operation.

[0418] The second preset operation is an operation performed by the doctor's terminal's interactive interface. In some embodiments, a Medical Space application is installed on the doctor's terminal. The second preset operation can be performed using the Medical Space application.

[0419] In some embodiments, the second preset operation may include presenting a prompt indicating that the patient has completed the current step, presenting patient records related to the patient's current step, and / or presenting patient schedules or patient requests related to the services the patient requested at the target step.

[0420] In some embodiments, in response to the detection that a patient's process has switched from the current medical service process to the target process, the hospital terminal device is controlled to perform at least one third preset operation.

[0421] The third preset operation is an operation performed by the interactive interface of the hospital terminal device. In some embodiments, a management space application is installed on the hospital terminal device. The management space application can be used to perform the third preset operation. In some embodiments, the processing device 210 can cause public terminal devices in the hospital to perform at least one third preset operation.

[0422] In some embodiments, the third preset operation may include presenting patient records related to the patient's current stage, presenting a prompt indicating that the patient has completed the current stage, presenting the patient's schedule or patient request related to the service at the target stage, and / or presenting the service appointment information for the patient's target stage.

[0423] In some embodiments, in response to detecting that a patient's stage has switched from the current medical service stage to the target stage, the processing device 210 can schedule service resources for the medical services of the patient's target stage. For example, when a patient is detected entering an examination stage, the processing device 210 can assign an examination room and examination technician to the patient.

[0424] In some embodiments, if the target stage is the outpatient registration stage, at least one preset operation may include conducting a first inquiry with the patient to determine the doctor the patient will register with.

[0425] In some embodiments, if the target stage is the waiting stage of an outpatient clinic, at least one preset operation may include conducting a second inquiry with the patient for a pre-consultation.

[0426] In some embodiments, if the target step is a follow-up step, at least one preset action may include reminding the patient to attend the follow-up at the scheduled time.

[0427] Figure 21This is a schematic diagram of an exemplary process 2100 for determining a target step according to some embodiments of this application.

[0428] Step 2110: Based on the patient data, it was detected that the current stage of the medical service process has been completed.

[0429] The current stage refers to the medical service stage the patient is currently participating in. For example, processing device 210 can detect that the current stage has been completed based on the patient's location information 2011. For instance, when the medical service system 200 provides on-site medical services, processing device 210 determines the completion of the current stage by determining the location where the patient leaves the current stage based on the patient's location information 2011.

[0430] As another example, processing device 210 can detect that the current step has been completed based on patient interaction information 2012. As another example, processing device 210 can detect that the current step has been completed based on data input by the healthcare provider 2016. As another example, processing device 210 can detect that the current step has been completed based on examination data 2013. As another example, processing device 210 can detect that the current step has been completed based on a clinical pathway 2015. As another example, processing device 210 can detect that the current step has been completed based on sensory data 2014.

[0431] Step 2020: Predict the next steps that one or more patients may take.

[0432] In some embodiments, the processing device 210 may determine one or more next steps a patient might take based on standardized operating procedures of a healthcare service process. These standardized operating procedures are healthcare service processes applicable to most patients. For example, after detecting that a patient has completed the registration process, the processing device 210 may determine that the patient's next step is the waiting period, based on the standardized operating procedures for outpatient services.

[0433] In some embodiments, the processing device 210 can determine one or more next steps a patient may take based on a patient-personalized process within a healthcare service workflow. A patient-personalized process refers to a healthcare service workflow tailored to specific patients (e.g., VIPs, critically ill patients). In some embodiments, the processing device 210 can determine one or more next steps a patient may take based on the patient's outpatient health information.

[0434] In some embodiments, when there are multiple possible next steps for patients, the processing device 210 can recommend a next step based on the time it takes for the patient to travel to the location corresponding to the next step and the patient's estimated waiting time. For example, for each of the multiple next steps, the processing device 210 can determine a first estimated time from the current location to the target location of the corresponding next step and a second estimated time of waiting at the target location based on a real-time 3D map of the hospital. Furthermore, the processing device 210 can determine at least a portion of the multiple next steps based on the first and second estimated times for each next step.

[0435] Step 2130: Control the patient terminal to present at least a portion of one or more next steps that the patient may perform.

[0436] The patient terminal 2010-a can present one or more possible next steps that the patient may perform, or the next steps that the processing device 210 recommends the patient to enter first. For example, after completing the registration process, the patient terminal 2010-a can present multiple possible next steps, such as the waiting process, the consultation process, and the hospitalization process.

[0437] Step 2140: Obtain the target stage selected by the patient from the patient terminal.

[0438] Patients can select target steps using a patient terminal via text input, voice input, screen clicks, gesture input, etc. In some embodiments of this application, after detecting the completion of the current step, the system can automatically present the next possible step to the patient, based on the different medical procedures corresponding to different patients, helping them understand the medical process and giving them the freedom of choice. Furthermore, personalized services are provided to patients.

[0439] Figure 23 This is a schematic flowchart illustrating an exemplary process 2300 for assisting a doctor's work, according to some embodiments of this application. In some embodiments, process 2300 may be implemented by processing device 210 (e.g., service module 430 or an agent corresponding to a doctor service configured on processing device 210).

[0440] Step 2310: You can obtain an access request for the medical space application from the doctor's terminal.

[0441] An access request refers to a doctor initiating a request to access the Medical Space application. Doctors can generate access requests in various ways. For example, the Medical Space application can be displayed on the screen of mobile terminal device 270-1, and doctor 271 can generate an access request by tapping the Medical Space application icon on the screen or by issuing a voice command (e.g., “Launch Medical Space application”). As another example, XR device 270-2 can generate a virtual reality version of the Medical Space application, and doctor 271 can generate an access request by interacting with the virtual reality Medical Space application or using voice commands.

[0442] Step 2320: In response to the access request, one or more pending tasks for the doctor can be determined based on the time the access request was received and the doctor's schedule information.

[0443] The time of receiving the access request refers to the point in time when the processing device 210 receives the access request sent from the doctor terminal 270.

[0444] A doctor's schedule information refers to the details of a doctor's work arrangements for the day. A doctor's schedule information can include various tasks that the doctor needs to complete that day, as well as the corresponding time for each task (e.g., the planned start and end times for each task). For example, a doctor's schedule information could be "Ward round preparation (7:45-8:00), Ward rounds (8:00-9:00), Pre-consultation preview (9:00-9:10), Consultation (9:10-11:30), Preoperative preparation (13:30-14:00), Surgery (14:00-17:00)".

[0445] Pending tasks refer to tasks that a doctor has not yet completed that day, which may include tasks that the doctor is currently working on but have not yet started, or a combination thereof. For example, taking the doctor's schedule information in the example above as an example, if the doctor is currently seeing patients, one or more pending tasks may include seeing patients, preoperative preparation, and surgery. In some embodiments, processing device 210 may identify one or more tasks whose scheduled end time is later than the time the access request is received as pending tasks.

[0446] In some embodiments, one or more pending tasks may include conducting ward rounds in a hospital ward. In some embodiments, doctors may conduct ward rounds remotely. For example, processing device 210 may receive a request to participate in a ward round remotely input by the doctor from a doctor's terminal. In response to detecting that a ward round is being conducted in a hospital ward, processing device 210 may obtain sensory information collected by one or more sensing devices in the hospital ward during the ward round, generate a virtual ward space based on the sensory information and patient data, and display the virtual ward space on the doctor's terminal.

[0447] In some embodiments, one or more pending tasks may include providing medical services in an examination room. In some embodiments, one or more pending tasks may include providing remote medical services. Remote medical services refer to doctors providing medical diagnosis and treatment services through an online platform (e.g., MedSpace application). In some embodiments, one or more pending tasks may include performing surgery on a target patient.

[0448] In some embodiments, one or more pending tasks may include writing work logs. Work logs may record details of a doctor's daily activities, such as the work completed that day, working hours, emergencies during the task, and task summaries. In some embodiments, work logs may include daily work logs, work logs for each task, or work logs for preset time periods (e.g., 3 hours, 5 hours, 24 hours, etc.). In some embodiments, one or more pending tasks for writing work logs may be continuously displayed.

[0449] In some embodiments, one or more pending tasks may include reviewing records of one or more completed tasks. For example, physician 271 may access and view records related to ward rounds, consultations, surgeries, etc., through physician terminal 270. When viewing records of one or more completed tasks, the physician may add, modify, and / or delete content in the records.

[0450] In some embodiments, the processing device 210 can determine one or more completed tasks for the doctor based on the doctor's reception time and schedule information. In some embodiments, the processing device 210 can determine tasks whose scheduled end time is earlier than the reception time of the access request as completed tasks. In some embodiments, since some tasks can be completed ahead of schedule, the doctor can input a task completion instruction (e.g., a voice command "consultation task completed") through the doctor's terminal 270 based on the actual completion status of the task. The doctor's terminal 270 can send a task completion instruction to the processing device 210, and the processing device 210 can determine the corresponding task as a completed task based on the task completion instruction.

[0451] In some embodiments, in response to an access request, the processing device 210 may cause the doctor's terminal 270 to present an initial interactive interface, which includes an eighth interface element for reminding the doctor to check the work schedule (i.e., the doctor's schedule information) via a medical space application. In some embodiments, in response to a doctor's request to access the work schedule entered through the doctor's terminal, the processing device 210 may identify one or more tasks to be processed.

[0452] Step 2330 allows the doctor's terminal to display an interactive interface through the Medical Space application. For example, as... Figure 23As shown, the processing device 210 can enable the doctor's terminal 270 to display an interactive interface 2331. The interactive interface 2331 can be displayed in the following ways: if the doctor's terminal 270 is a terminal device with a display screen (e.g., a mobile terminal device 270-1 or a desktop terminal device), the interactive interface 2331 can be directly displayed on the screen; if the doctor's terminal 270 is an XR device 270-2, the XR device 270-2 can display the interactive interface 2331 within the virtual reality space generated by the XR device 270-2. Further description of the interactive interface can be found in... Figure 24 It was found in its related description.

[0453] The user interface may include at least one interface element. Doctors can access one or more auxiliary services corresponding to at least one interface element by accessing it. Doctors can access at least one interface element by clicking, long-pressing, voice selection, etc.

[0454] Ancillary services refer to the functions provided by medical space applications to assist doctors in completing their work tasks. For example, ancillary services may include displaying patient data, displaying 3D maps of target locations within the hospital, and providing doctors with services for remotely participating in consultations or ward rounds.

[0455] In some embodiments, the interactive interface may include a first interface element for accessing an assistive service associated with at least one of one or more pending tasks. A physician can access the assistive service corresponding to the first interface element by clicking or selecting it via voice. Further description of the interactive interface is available in [link to relevant documentation]. Figure 24 It was found in its related description.

[0456] Figure 24 This is a schematic diagram of an exemplary interactive interface 2331 according to some embodiments of this application.

[0457] In some embodiments, such as Figure 24 As shown, the interactive interface 2331 may include a first interface element 2410 (hereinafter referred to as a plurality of first interface elements 2410) for accessing an auxiliary service associated with at least one of one or more pending tasks.

[0458] In some embodiments, when one or more pending tasks involve ward rounds in a hospital ward, the first interface element may include a first interface element for requesting remote participation in the ward round (hereinafter referred to as the ward round interface element). For example, such as Figure 24 As shown, the multiple first interface elements 2410 may include ward interface elements 2411.

[0459] In some embodiments, when one or more pending tasks involve providing outpatient services in an examination room, the first interface element may include a first interface element (hereinafter referred to as the consultation interface element) for accessing patient data of patients who have booked consultation services. For example, such as Figure 24 As shown, the plurality of first interface elements 2410 may include a consultation interface element 2412. In some embodiments, the first interface elements further include a first interface element for accessing an initial diagnostic record related to outpatient services, which is generated based on sensing information collected by one or more sensing devices in the consultation room during the outpatient service. For example, the processing device 210 may receive a request from a doctor's terminal to access patient data of a target patient, generate a virtual persona representing the target patient based on the target patient's patient data, and cause the doctor's terminal to present the virtual persona to explain the target patient's patient data to the doctor.

[0460] In some embodiments, when one or more pending tasks include providing remote outpatient services, the first interface element may include a first interface element for accessing a virtual consultation room (hereinafter referred to as the consultation room interface element). For example, such as Figure 24 As shown, the plurality of first interface elements 2410 may include a consultation room interface element 2413. In response to the interaction between a doctor (e.g., doctor 271) and the consultation room interface element 2413, the processing device 210 may cause the doctor's terminal 270 (e.g., XR device 270-2) to present a virtual consultation room. For example, the processing device 210 may receive a request from the doctor's terminal to enter the virtual consultation room to provide remote outpatient services to a target patient, and cause the doctor's terminal to present a 3D patient model of the target patient. The processing device 210 may also receive examination instructions input by the doctor through interaction with the 3D patient model from the doctor's terminal, and cause the wearable device worn by the target patient to collect the target patient's physical examination data according to the examination instructions.

[0461] In some embodiments, when one or more tasks to be processed include performing surgery on a target patient, the first interface element may include a first interface element (hereinafter referred to as the surgical interface element) for accessing patient data related to the target patient. For example, such as Figure 24 As shown, the plurality of first interface elements 2410 may include surgical interface elements 2414 for accessing patient data related to the target patient. The patient data may include data related to the target surgical plan corresponding to the target patient.

[0462] In some embodiments, the first interface element may further include a first interface element for updating medical orders for the target patient. In some embodiments, the first interface element may further include a first interface element for accessing an initial surgical record of the procedure. The initial surgical record may be generated based on sensing information collected by one or more sensing devices in the operating room during the procedure.

[0463] In some embodiments, such as Figure 24 As shown, the interactive interface 2431 may further include a second interface element 2420 for accessing a real-time 3D map related to the target location corresponding to at least one task to be processed (i.e., browsing the target location corresponding to at least one task to be processed). A real-time 3D map refers to a virtual reality (VR) model of the space corresponding to the target location. In some embodiments, a real-time 3D map of the target location can be generated based on an initial 3D map of the hospital and real-time information about the target location.

[0464] In some embodiments, such as Figure 24 As shown, the interactive interface 2331 may further include a third interface element 2430 for preoperative education. In response to the interaction between the physician and the third interface element 2430, the physician terminal 270 may generate a request for preoperative education of the target patient and send the request to the processing device 210. For example, the processing device 210 may receive the request for preoperative education of the target patient. The request may be obtained from the physician's XR device and input by the physician through interaction with the third interface element. In response to the request, the processing device 210 may generate explanatory materials for explaining the candidate surgical plan for the target patient and simultaneously present the explanatory materials to the target patient and physician using both the patient's XR device and the physician's XR device.

[0465] In some embodiments, such as Figure 24 As shown, the interactive interface 2331 may further include a fourth interface element 2440 for performing surgical simulation. In response to the interaction between the doctor and the fourth interface element 2440, the doctor's terminal 270 may generate a request to simulate a target surgery and send the request to the processing device 210. The target surgery refers to the surgery corresponding to a target surgical plan. For example, the processing device 210 may receive a request to simulate a target surgery. This request may be obtained from the doctor's XR device and input by the doctor through interaction with the fourth interface element. In response to the request, the processing device 210 may generate a virtual surgical scene corresponding to the target surgery. The virtual surgical scene may include a virtual surgical site and virtual surgical equipment. The processing device 210 may cause the doctor's XR device to present the virtual surgical scene to the doctor. In some embodiments, the processing device 210 may obtain interactive instructions input by the doctor regarding the virtual surgical equipment through the doctor's XR device or an interactive device corresponding to the virtual surgical equipment, and update the virtual surgical site and virtual surgical equipment in the virtual surgical scene based on the interactive instructions.

[0466] In some embodiments, such as Figure 24As shown, the interactive interface 2331 may include a fifth interface element 2450 for executing a surgical plan. In response to the interaction between the physician and the fifth interface element 2450, the physician terminal 270 may generate a request to perform a surgical plan for the target patient and send the request to the processing device 210. For example, the processing device 210 may receive a request to perform a surgical plan for the target patient. This request may be obtained from the physician terminal and entered by the physician through interaction with the fifth interface element. The processing device 210 may determine the surgical difficulty coefficient based on the target patient's patient data and determine whether an expert meeting is required based on the surgical difficulty coefficient. In response to determining that an expert meeting is required, the processing device 210 may cause the physician terminal to display a sixth interface element 2460 for initiating an expert meeting.

[0467] In some embodiments, such as Figure 24 As shown, the interactive interface 2331 may further include a seventh interface element 2470 for patient management. Patient management refers to the management of patient-related data (e.g., patient data, surgical records, hospitalization records, nursing records, postoperative recovery records, etc.). In some embodiments, in response to an interaction between a doctor and the seventh interface element 2470, the doctor's terminal 270 may generate a request to access the initial hospitalization record of a target patient and send the request to the processing device 210. For example, the processing device 210 may receive a request to access the initial hospitalization record of a target patient. The request can be obtained from the doctor's terminal and entered by the doctor through interaction with the seventh interface element. In response to the request, the processing device 210 may cause the doctor's terminal to present the initial admission record and update the initial admission record based on feedback information about the initial admission record entered by the doctor through the doctor's terminal.

[0468] In some embodiments, in response to an access request, processing device 210 may cause a doctor's terminal to present an initial interactive interface via a medical space application, which includes an eighth interface element for reminding the doctor to check their work schedule. In response to a doctor's request to access their work schedule via their terminal, processing device 210 may identify one or more pending tasks. In some embodiments, the initial interactive interface may further present a virtual avatar configured to communicate with the doctor.

[0469] In some embodiments, the interface 2331 may further include schedule information related to at least one task to be processed. For example, such as Figure 24 As shown, the interactive interface 2431 may include schedule information 2480 such as ward rounds (scheduled start time can be 8:00), pre-consultation / pre-consultation (scheduled start time can be 9:00), and consultation (scheduled start time can be 9:10).

[0470] In some embodiments, the interactive interface 2331 may further include one or more collapsible elements associated with one or more completed tasks. One or more collapsible elements in the interactive interface can be accessed through human-computer interaction (e.g., clicking or selecting via voice), shrinking (e.g., shrinking to 1 / 4 of their original size), or expanding. Therefore, the collapsible element can include a folded state (the state when shrunk) and an expanded state (the state when expanded). In the expanded state, the collapsible element can display completed tasks and time information (e.g., the start time of one or more completed tasks). For example, as... Figure 24 As shown, the interactive interface 2331 may include a collapsible element 2490 (in an expanded state). The collapsible element 2490 can display ward round preparation tasks, and the start time of the ward round preparation tasks can be 7:45. Doctors can click on the collapsible element 2490 on the interactive interface 2331, and the processing device 210 can cause the collapsible element 2490 to enter a collapsed state according to the click operation (the area of ​​the collapsible element 2490 can be reduced, and the completed tasks will no longer be displayed).

[0471] In some embodiments, the configuration of the interactive interface 2331 can be determined based on the doctor's preference information. The preference information reflects the doctor's preferences for the content, specifications (including shape, color, font, etc.), and / or position of elements on the interface (e.g., first interface elements, second interface elements, etc.). In some embodiments, the preference information may also reflect the doctor's preference for the interface style. The interface style may include a simple style and a detailed style. A simple style may contain fewer interface elements than a detailed style. In some embodiments, the preference information may include whether to display a virtual character.

[0472] Figure 25 This is a schematic diagram of an exemplary system 2500 (also referred to as a hospital management system 2500) for hospital management, shown according to some embodiments of this application. Figure 25 As shown, the hospital management system 2500 may include hospital administrators 2510, management space applications 2520, and resources 2530.

[0473] Administrator 2510 can manage hospital resources 2530 through management space application 2520. Administrator 2510 may include hospital administrators, such as the hospital director, heads of hospital departments (e.g., dentistry, internal medicine, etc.). Hospital resources 2530 may include equipment, personnel, digital twins, digital intelligent resources (e.g., intelligent agents), or any combination thereof. In some embodiments, different administrators 2510 may have different management permissions for different resources 2530. In some embodiments, a specific administrator 2510 manages only specific resources 2530. Management space application 2520 can be displayed through the terminal device of administrator 2510.

[0474] In some embodiments, the management space application 2520 may present an interface. The interface can be presented via a display of the administrator terminal device of the administrator 2510. The display may include a light-emitting diode (LED) display, a liquid crystal display, an electronic ink display, a touch LCD, an organic LED touch, or any combination thereof. The terminal device may include a mobile device, an XR device, a smart wearable device, etc.

[0475] In some embodiments, the management space application 2520 (or its interface) can be configured to present a virtual avatar to assist the administrator 2510 in managing resources. The virtual avatar can be configured to communicate with the administrator 2510. The management space application 2520 can also be configured to provide interface elements to the administrator 2510 to initiate a communication session with the virtual avatar. In some embodiments, the administrator 2510 can initiate a communication session with the virtual avatar through interface elements to express their resource management needs (e.g., viewing information related to a specific type of resource, scheduling a specific type of resource, updating relevant parameters of a specific type of resource) via voice, text, gestures, etc. A processing device (e.g., processing device 210) can analyze user input (e.g., using AI technology, using an intelligent agent), determine feedback information, and convey the feedback information to the administrator 2510 through the virtual avatar during the communication session. In some embodiments, the content displayed by the management space application 2520 can be updated based on the communication content of the communication session.

[0476] Traditional hospital management systems typically have interfaces limited to providing users with pre-defined analytical results. The hospital management system described in this application, however, allows users to retrieve data across different dimensions. Furthermore, virtual avatars allow users to express their needs in natural language, thereby enhancing the user experience and improving the quality and efficiency of resource management services.

[0477] In some embodiments, such as Figure 25 As shown, hospital resource 2530 includes a digital twin 2531. A digital twin can map the state of a corresponding physical entity and is generated according to a predefined data structure. For example, as used herein, a digital twin refers to a virtual representation (or digital copy) of a physical entity. A physical entity refers to any object or phenomenon existing in the physical world that can be directly or indirectly observed, measured, or interacted with.

[0478] In some embodiments, the preset data structure of a digital twin can specify the format of the digital twin, the type of information reflected by the digital twin, the storage address of the digital twin, the access point of the digital twin, the update mode of the digital twin, the modification permissions of the digital twin, the modification permissions of the preset data structure, etc., or any combination thereof. In some embodiments, the preset data structure can be a default data structure provided by the hospital, or a custom data structure set by the administrator 2510 through the management space application 2520.

[0479] In some embodiments, digital twin 2531 may include one or more first digital twins 25311. For each first digital twin, the state mapped to the corresponding physical entity may include updating the first digital twin based on updates to the state of the corresponding physical entity. Exemplary first digital twins may include digital twins corresponding to public areas of a hospital, digital twins corresponding to medical services, digital twins corresponding to users (e.g., patients, patients' organs, doctors), digital twins corresponding to hospital hardware equipment, etc. In some embodiments, state updates of the corresponding physical entity are detected based on real-time information of the corresponding physical entity. For example, the real-time information of the corresponding physical entity includes at least one of information collected by sensing devices within the hospital or information collected by user terminals associated with the hospital.

[0480] In some embodiments, digital twin 2531 may include one or more second digital twins 25312. For each second digital twin, the state mapping of the corresponding physical entity may include updating the corresponding physical entity based on the update of the second digital twin. Exemplary second digital twins may include digital twins of corresponding hardware devices, digital twins of corresponding user services, digital twins of corresponding medical service processes, etc. It should be understood that a digital twin may be a first digital twin or a second digital twin.

[0481] In some embodiments, the administrator 2510 can manage the digital twin 2531 through a management space application 2520. Since the digital twin maps the state of the corresponding physical entity, the physical entities of the hospital can be managed by managing the digital twin 2531. For example, the administrator 2510 can view a first digital twin 25311 of a physical entity (e.g., a 3D digital twin model of a patient's organ or hardware device, a digital twin view of a public area) through the management space application 2520 to understand and assess the state of the physical entity. Optionally, the user can change the display angle, display size, etc., of the displayed first digital twin 25311.

[0482] In some embodiments, one or more first digital twins 25311 may include digital twins corresponding to public areas in a hospital. Based on the digital twins corresponding to the hospital's public areas, monitoring of the public areas can be achieved. In some embodiments, the digital twin corresponding to the public area may reflect a digital twin view of the public area generated based on real-time information about the public area. The digital twin view can be used to monitor, analyze, and predict the performance and operation of the public area in real time, thereby providing insights into the current state of the public area. In some embodiments, the digital twin view of the public area may present a real-time 3D map of the public area and monitoring metrics for the public area. Monitoring metrics may include monitoring metrics related to users within the public area, monitoring metrics related to events within the public area, monitoring metrics related to devices within the public area, and any combination thereof.

[0483] In some embodiments, one or more first digital twins 25311 may include a digital twin corresponding to a medical service. The digital twin corresponding to the medical service can be used to evaluate the medical service. For example, the digital twin corresponding to the medical service may reflect operational metrics of the medical service, which are used to evaluate the quality, efficiency, and profitability of the medical service.

[0484] In some embodiments, one or more first digital twins 25311 may include other digital twins that are updated based on the state updates of the corresponding physical entities. As an example only, a first digital twin may include a digital twin of a patient or a patient's organ, which can be updated once new medical data about the patient is acquired (e.g., new medical images, new examination data). As another example, a first digital twin may include a digital twin of a hardware device, which can be updated once the usage status, operating parameters, etc., of the hardware device are updated.

[0485] In some embodiments, for each of at least a portion of one or more first digital twins 25311, the first digital twin can be updated in a first manner in response to detecting a normal state update of the corresponding physical entity, and the first digital twin can be updated in a second manner in response to detecting an abnormal state update of the corresponding physical entity. The first manner may differ from the second manner. In other words, the first digital twin can be updated in different ways when the corresponding physical entity undergoes abnormal or normal state changes. For example, in response to detecting a normal state update of the corresponding physical entity, the first digital twin can display a first marker symbol (or a first color). In this way, the first digital twin can be used to monitor physical entities for anomalies, facilitating timely adjustments to the physical entities.

[0486] In some embodiments, one or more second digital twins 25312 may include a digital twin corresponding to a hardware device, and the digital twin corresponding to the hardware device reflects the parameters of the hardware device. The second digital twin corresponding to the hardware device can be used to update / set the parameters of the hardware device.

[0487] In some embodiments, the hardware device may include a display device for displaying information related to medical services. A digital twin corresponding to the hardware device may reflect the display parameters of the display device, which can be set or updated by the administrator 2510 through the management space application 2520. For example, by updating the digital twin corresponding to the hardware device, the administrator 2510 can adjust the display content of the display device.

[0488] In some embodiments, one or more second digital twins 25312 may include a digital twin corresponding to a user service, and the digital twin corresponding to the user service may reflect the parameters of the user service. In some embodiments, the parameters of the user service may be updated / set using the digital twin corresponding to the user service. Exemplary parameters of the user service may include the method of providing the user service, the requirements of the user using the user service, the content of the user service, or any combination thereof. In some embodiments, the user service may be accessed from a patient space application installed on a patient terminal or a medical space application installed on a doctor terminal.

[0489] In some embodiments, one or more second digital twins 25312 may include a digital twin corresponding to a medical service process, and the digital twin corresponding to the medical service process reflects the parameters of the medical service process. In some embodiments, the parameters of the medical service process may include a standard operating procedure (SOP) specifying a standard step in the medical service process. In some embodiments, the SOP may further specify a preset data acquisition protocol. In some embodiments, the second digital twin corresponding to the medical service process may be configured to update / set the parameters of the medical service process.

[0490] Digital twins can be instantiated using data from sensors and other sources to dynamically model corresponding real-world entities in real time. Based on the hospital management system disclosed in this paper, digital twins can be deployed for monitoring, analysis, simulation, and control, providing valuable insights to optimize the performance of the hospital management system and improve overall efficiency.

[0491] In some embodiments, hospital resources 2530 include the hospital's digital intelligence resources. Digital intelligence resources may include various types of digital assets and tools enhanced by artificial intelligence to support and improve different aspects of digital operations, learning, and management. In some embodiments, such as Figure 25As shown, digital intelligent resources may include intelligent agents 2532. In some embodiments, a manager 2510 can manage intelligent agents 2532 through a management space application 2520. For example, the manager 2510 can view and modify information related to the intelligent agents through the management space application 2520. Since intelligent agents 2532 participate in processing data to provide user services, user services can be managed by managing intelligent agents 2532.

[0492] In some embodiments, the management space application 2520 may present at least a portion of the basic configuration data used by the agent 2532. The basic configuration data may be updated by the administrator 2510 through the management space application 2520. The basic configuration data includes key information relied upon by the agent when providing specific services. Exemplary basic configuration data may include at least one of a dictionary (e.g., a list of words, a directory of people), a knowledge database, or a template.

[0493] In some embodiments, the pipe space application 2520 may present at least a portion of the operational metrics of the agent 2532. Operational metrics may reflect information related to the quantity and quality of services provided by the agent. The agent's operational metrics may include the number of users served by the agent, the quantity of services provided by the agent, the amount of data processed by the agent, the quality of the agent's services, or any combination thereof.

[0494] In some embodiments, the intelligent agent 2532 includes intelligent agents corresponding to different types of medical service providers, different hospital departments, different medical service processes, and different user services. According to some embodiments of this application, the configuration of various intelligent agents in a hospital can be customized, enhancing the adaptability and application scope of the intelligent agents, thereby significantly improving the accuracy and efficiency of the user services supported by the intelligent agents, while also enhancing the patient's treatment experience.

[0495] In some embodiments, the hospital management system 2500 may further include a processing device. The processing device can process data and / or information obtained from the hospital management system 2500. In some embodiments, the processing device can receive information and / or instructions input by the administrator 2510 through the management space application 2520, and provide corresponding feedback after processing the information and instructions. For example, the processing device 210 can receive update information related to a digital twin corresponding to a hardware device from the administrator terminal presenting the management space application 2520, and control the hardware device to update its configuration based on the update information. For example, the processing device 210 can store the update information in a storage device and send an update notification to the hardware device so that the hardware device can retrieve the update information from the storage device to update its configuration. As another example, the processing device 210 can receive update information related to an intelligent agent from the management space application 2520 and control the intelligent agent to perform specific operations.

[0496] The basic concepts have been described above. It is clear that the detailed disclosure above is merely illustrative and does not constitute a limitation of this specification. Although not explicitly stated herein, various modifications, improvements, and corrections may be made to this specification by those skilled in the art. Such modifications, improvements, and corrections are suggested in this specification and therefore remain within the spirit and scope of the exemplary embodiments described herein.

[0497] Furthermore, this specification uses specific terms to describe embodiments thereof. For example, "an embodiment," "one embodiment," and / or "some embodiments" refer to a particular feature, structure, or characteristic associated with at least one embodiment of this specification. Therefore, it should be emphasized and noted that references to "an embodiment," "one embodiment," or "an alternative embodiment" in different locations throughout this specification do not necessarily refer to the same embodiment. Moreover, certain features, structures, or characteristics in one or more embodiments of this specification can be appropriately combined.

[0498] Furthermore, unless expressly stated in the claims, the order of elements and sequences, the use of numbers and letters, or other names in this specification are not intended to limit the order of the processes and methods described herein. Although various examples have been discussed in the foregoing disclosure of some embodiments that are currently considered useful, it should be understood that such details are for illustrative purposes only, and the appended claims are not limited to the disclosed embodiments; rather, they are intended to cover all modifications and equivalent combinations that conform to the spirit and scope of the embodiments described herein. For example, while the system components described above can be implemented using hardware devices, they can also be implemented solely using software solutions, such as installing the described system on an existing server or mobile device.

[0499] Similarly, it should be noted that, in order to simplify the description disclosed herein and thus aid in the understanding of one or more embodiments of the invention, the foregoing description of embodiments in this specification may sometimes combine multiple features into a single embodiment, drawing, or description thereof. However, this method of disclosure does not imply that the subject matter of this specification requires more features than those mentioned in the claims. In fact, the embodiments contain fewer features than all the features of a single embodiment disclosed above.

[0500] In some embodiments, numbers describing the quantity of components and attributes are used. It should be understood that such numbers used in the description of embodiments are modified in some examples with the terms "approximately," "approximately," or "generally." Unless otherwise stated, "approximately," "approximately," or "generally" indicates that the numbers are allowed to vary by ±20%. Accordingly, in some embodiments, the numerical parameters used in the specification and claims are approximate values, which may be changed depending on the characteristics required by individual embodiments. In some embodiments, numerical parameters should take into account specified significant digits and employ general methods of digit reservation. Although the numerical ranges and parameters used to confirm their breadth of range in some embodiments of this specification are approximate values, in specific embodiments, such numerical values ​​are set as precisely as feasible.

[0501] For each patent, patent application, patent application publication, and other material, such as articles, books, specifications, publications, and documents, referenced in this specification, the entire contents of which are incorporated herein by reference. This excludes historical application documents that are inconsistent with or conflict with the content of this specification, as well as documents that limit the broadest scope of the claims in this specification (currently or subsequently appended to this specification). It should be noted that in the event of any inconsistency or conflict between the descriptions, definitions, and / or terminology used in the supplementary materials and the content of this specification, the descriptions, definitions, and / or terminology used in this specification shall prevail.

[0502] Finally, it should be understood that the embodiments in this specification are merely illustrative of the principles of the embodiments described herein. Other variations may also fall within the scope of this specification. Therefore, alternative configurations of the embodiments in this specification are intended to be illustrative rather than limiting, and should be considered consistent with the teachings of this specification. Accordingly, the embodiments in this specification are not limited to those explicitly described and illustrated herein.

Claims

1. A medical service system, comprising: The hardware devices are configured to collect data related to the physical hospital. The processing equipment is configured as follows: The data is mapped to a virtual hospital corresponding to the physical hospital. The virtual hospital includes an intelligent agent that evolves itself based on the data and artificial intelligence (AI) technology. User services are provided to relevant users of the physical hospital through user space applications, wherein... The user space application is configured to provide the relevant users of the physical hospital with an access point to interact with the intelligent agent. At least a portion of the user services are provided to the relevant user based on the interaction between the relevant user and the agent.

2. The medical service system according to claim 1, wherein, The user space application is configured to present a virtual character corresponding to the agent through extended reality technology, and at least a portion of the user services are provided to the relevant user based on the interaction between the relevant user and the virtual character.

3. The medical service system as described in claim 2, wherein, The virtual character includes a first virtual character corresponding to the registration agent, and the at least part of the user services being provided to the relevant user based on the interaction between the relevant user and the virtual character includes: Obtain the patient's chief complaint through the patient terminal or registration terminal; Based on the patient's chief complaint, at least one candidate department was identified; The content of the first inquiry is determined based on the patient's chief complaint and the at least one candidate department; Control the patient terminal or the registration terminal to display the first virtual avatar, so as to conduct the first inquiry on the patient based on the first inquiry content; and The doctor to whom the patient is registered is determined based on the first data collected by the patient terminal or the registration terminal in the first inquiry.

4. The method as described in claim 3, characterized in that, The virtual character includes a second virtual character corresponding to the pre-diagnosis intelligent agent, and the at least part of the user services provided to the relevant user based on the interaction between the relevant user and the virtual character includes: Based on the doctor's department, determine the content of the second question in the second inquiry; Based on the content of the second inquiry, the patient terminal is controlled to display the second virtual avatar, so as to conduct the second inquiry on the patient based on the content of the second inquiry; and A pre-consultation record is generated based on the second data collected by the patient terminal during the second inquiry.

5. The medical service system according to claim 1, wherein, At least a portion of the user services are provided to the relevant user based on the processing results, which are generated by the agent based on the data.

6. The medical service system according to claim 1, wherein, The data related to the physical hospital includes data related to the medical service process of the physical hospital, and the intelligent agent includes an intelligent agent corresponding to the medical service process. By using the intelligent agent corresponding to the medical service process to process the data related to the medical service process, the user service is provided to the relevant users of the medical service process.

7. The medical service system according to claim 6, wherein, The data related to the medical service process is collected according to a preset data collection protocol corresponding to the medical service process. The preset data collection protocol includes a data collection protocol corresponding to the standard steps of the medical service process.

8. The medical service system according to claim 7, wherein, The processing device is further configured to: In response to the detection of an update to healthcare policies related to the healthcare service process, the preset data collection protocol corresponding to the healthcare service process is updated.

9. The medical service system according to claim 1, wherein, The data related to the medical service process includes data related to patients participating in the medical service process, and the agent corresponding to the medical service process is configured to process the patient-related data by performing the following operations: Monitor updates to the patient-related data; In response to the detection that the patient-related data includes updated data obtained from at least one hardware device, Perform Event of Interest (EOI) detection based on the updated data; as well as In response to the detection of an EOI, one or more preset operations corresponding to the EOI are executed to provide the user service to the relevant user.

10. The medical service system according to claim 9, wherein, The step of performing EOI detection based on the updated data includes: Determine the current stage of the patient's medical service process; Based on the patient's current condition, determine the type of EOI that needs to be detected; and The EOI detection is performed on the updated data based on the type information.

11. The medical service system according to claim 9, wherein, The step of performing EOI detection based on the updated data includes: Based on one or more hardware devices corresponding to the updated data, determine the type information of the EOI to be detected; and The EOI detection is performed on the updated data based on the type information.

12. The medical service system according to claim 9, wherein, The EOI detection is based on EOI detection rules, which are learned by the agent from historical records.

13. The medical service system according to claim 12, wherein, The EOI detection is further performed based on the patient's record data.

14. The medical service system according to claim 9, wherein, One or more preset operations corresponding to the EOI are determined based on the correspondence between the EOI and the preset operations, and the correspondence is learned by the agent from historical records.

15. The medical service system according to claim 14, wherein, One or more preset operations corresponding to the EOI are further determined based on the patient's record data.

16. The medical service system according to claim 1, wherein, At least a portion of the user services are provided to hospital administrators through an interface provided by the management space application, so that the hospital administrators can manage at least a portion of the intelligent agents.

17. The medical service system according to claim 16, wherein, The hospital administrator manages at least a portion of the intelligent agents, including: The basic configuration data of at least a portion of the intelligent agents are presented to the hospital administrators through the aforementioned management space application. Obtain the update information of the basic configuration data input by the hospital administrator through the management space application.

Images