Triage method and system, image cloud server, front-end machine and image device

Abstract

The application discloses a triage method and system, an image cloud server, a front-end machine and an image device, and relates to the technical field of medical treatment. After the image cloud server receives registration information of an object, the image cloud server can generate triage information based on the registration information. The triage information comprises a target image device for imaging the object and the registration information of the object. The registration information comprises basic information and an imaging mode. The front-end machine can issue the basic information of the object to the target image device based on the triage information, so that the target image device can image the object based on the basic information and obtain medical images. The target image device can send the medical images to the front-end machine, so that the front-end machine can upload the medical images to the image cloud server. In this way, on the one hand, the triage efficiency and accuracy are improved, and the efficiency of image examination is improved, without manual triage. On the other hand, the whole image examination process from information registration to imaging is automated, and the efficiency of image examination is improved.

Description

Technical Field

[0001] This application relates to the field of medical technology, and in particular to a triage method and system, an image cloud server, a front-end processor, and an imaging device. Background Technology

[0002] In a medical setting, patients may need to undergo imaging examinations. When an imaging examination is required, the patient can register their information in the hospital's hospital information system (HIS) based on the examination order issued by the doctor. The patient can then proceed to the imaging examination area. Staff in the imaging examination area will verify the patient's registration information and actual condition, and then manually assign available imaging equipment to the patient based on the availability of various imaging devices.

[0003] This shows that the current triage process for allocating imaging equipment to patients relies too heavily on manual operation, resulting in relatively low efficiency. Summary of the Invention

[0004] This application provides a triage method and system, an image cloud server, a front-end processing unit, and imaging equipment, which can solve the problem of low triage efficiency. The technical solution is as follows: On the one hand, a triage method is provided for use on an image cloud server; the method includes: If registration information of an object to be imaged is received, triage information of the object is generated based on the registration information. The triage information includes: a target imaging device for imaging the object, and the registration information. The registration information includes basic information and imaging mode. The imaging mode of the target imaging device is the same as the imaging mode in the registration information. The triage information of the object is sent to the front-end unit associated with the target imaging device. The triage information is used by the front-end unit to send the basic information of the object to the target imaging device, so that the target imaging device can image the object based on the basic information and send the imaged medical image to the front-end unit. Receive the medical images of the object uploaded by the front-end machine.

[0005] Optionally, triage information for the object is generated based on the registration information, including: From multiple imaging devices, at least two alternative imaging devices with the same imaging method as the imaging method in the registration information are selected; The target imaging device is acquired from the at least two alternative imaging devices; Based on the identifier of the target imaging device and the registration information, triage information for the object is generated.

[0006] Optionally, obtaining the target imaging device from the at least two candidate imaging devices includes: The system receives the status of each of the imaging devices sent by the front-end unit, and the completion time of imaging by the imaging device in the idle state, wherein the status is either the idle state or the busy state. Based on the status of each of the candidate imaging devices, a candidate imaging device whose status is idle is obtained from the at least two candidate imaging devices; Based on the completion time of each candidate imaging device, a target imaging device is obtained from the candidate imaging devices, wherein the target imaging device has the longest idle time.

[0007] Optionally, the triage information of the object is sent to the front-end unit associated with the target imaging device, including: Receive a data retrieval request sent by the front-end unit associated with the target imaging device; In response to the data retrieval request, the triage information of the object is sent to the front-end machine.

[0008] Optionally, the data retrieval request carries a signature; in response to the data retrieval request, the triage information of the object is sent to the front-end machine, including: Verify the signature carried in the data retrieval request; After the signature is verified, the encrypted triage information is sent to the front-end machine.

[0009] On the other hand, a triage method is provided for use in a pre-treatment unit, the method comprising: The system receives triage information of an object to be imaged from an image cloud server. The triage information is generated based on the registration information of the object and includes: a target imaging device for imaging the object, and the registration information, which includes basic information and imaging mode. The imaging mode of the target imaging device is the same as the imaging mode in the registration information, and the target imaging device is associated with the front-end unit. The basic information of the object is sent to the target imaging device so that the target imaging device can image the object based on the basic information to obtain a medical image; The system receives the medical images sent by the target imaging device and uploads the medical images to the image cloud server.

[0010] Optionally, basic information about the object is sent to the target imaging device, including: Receive the data query request sent by the target imaging device; In response to the query request, the first data in the basic information is sent back to the target imaging device, and the first data is used for display by the target imaging device; Receive a data transfer request sent by the target imaging device, the data transfer request being sent by the target imaging device after determining that the object has completed check-in; In response to the data transfer request, the second data in the registration information is sent to the target imaging device.

[0011] Optionally, there are multiple objects, and the imaging priority of the first object among the multiple objects is higher than that of the second object; the basic information of the object is sent to the target imaging device, including: The basic information of the first object is sent to the target imaging device first.

[0012] Optionally, the method further includes: The system receives the status of each of the imaging devices sent by the front-end unit, and the completion time of imaging by the imaging device in the idle state, wherein the status is either the idle state or the busy state. Based on the status of each of the candidate imaging devices, a candidate imaging device whose status is idle is obtained from the at least two candidate imaging devices; Based on the completion time of each candidate imaging device, a target imaging device is obtained from the candidate imaging devices, wherein the target imaging device has the longest idle time.

[0013] On another front, a triage method is provided, applied to imaging equipment; the method includes: The system receives basic information about an object sent by a front-end server associated with the imaging device. The triage information to which the basic information belongs is generated by the imaging cloud server based on the registration information of the object and sent to the front-end server. The triage information includes the imaging device and the registration information. The registration information includes the basic information and the imaging method. The imaging method of the imaging device is the same as the imaging method in the registration information. Based on the basic information, the object is imaged to obtain a medical image of the object; The medical image is sent to the front-end processor so that the front-end processor can upload the medical image to the image cloud server.

[0014] Optionally, the system receives basic information about the object sent by the front-end unit associated with the imaging device, including: Send a data query request to the front-end device, the data query request being used to request the front-end device to send back the first data in the basic information to the imaging device; Display the first data; After confirming that the object has completed the check-in, a data transfer request is sent to the front-end device. The data transfer request is used to request the front-end device to send back the second data in the basic information to the imaging device.

[0015] Optionally, sending the medical images to the front-end processor includes: A data storage request is sent to the front-end machine, the data storage request carrying the medical image.

[0016] Optionally, the front-end machine is equipped with a DICOM protocol stack; The data query request is a C-FIND request, the data transfer request is a C-MOVE request, and the data storage request is a C-STORE request.

[0017] In another aspect, an image cloud server is provided, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, it implements the triage method applied to the image cloud server as described above.

[0018] In another aspect, a front-end processor is provided, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, it implements the triage method applied to the front-end processor as described above.

[0019] In another aspect, an imaging device is provided, the imaging device comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, it implements the triage method applied to the imaging device as described above.

[0020] In another aspect, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the triage method as described above.

[0021] In another aspect, a computer program product is provided, the computer program product comprising a computer program that, when executed by a processor, implements the triage method as described above.

[0022] Furthermore, a triage system is provided, the system comprising: Image cloud servers as described above; The front-end machine as described above; And the imaging devices described above.

[0023] The beneficial effects of the technical solution provided in this application can include at least the following: This application provides a triage method and system, an image cloud server, a front-end processor, and an imaging device. After receiving registration information of an object, the image cloud server generates triage information based on this registration information. This triage information includes a target imaging device for imaging the object, and the object's registration information, which includes basic information and imaging method. Subsequently, the front-end processor sends the object's basic information to the target imaging device based on the triage information, enabling the target imaging device to image the object and obtain a medical image. The target imaging device then sends the medical image to the front-end processor for uploading to the image cloud server. In other words, in this method, the image cloud server automatically generates triage information based on registration information to triage the object; the front-end processor sends the object's basic information to the matching target imaging device based on the triage information; and the target imaging device, after imaging the object, uploads the medical image to the image cloud server through the front-end processor. Therefore, on the one hand, the elimination of manual triage improves triage efficiency and accuracy, thereby increasing the efficiency of imaging examinations; on the other hand, it enables data exchange between the imaging cloud server and imaging equipment, solving the problem of data silos in the hospital intranet caused by security factors; and on yet another hand, it automates the entire imaging examination process from information registration to imaging, further improving the efficiency of imaging examinations.

[0024] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0025] Figure 1 This is a schematic diagram of the structure of a triage system provided in an embodiment of this application; Figure 2 This is a flowchart of a triage method provided in an embodiment of this application; Figure 3 This is a flowchart of another triage method provided in the embodiments of this application; Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0026] The embodiments of this application are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application.

[0027] Figure 1This is a schematic diagram of the structure of a triage system provided in an embodiment of this application. See also... Figure 1 The triage and examination system includes: an image cloud server 100, and at least one front-end processor 200 (e.g., Figure 1 The image server 200 is shown as one or more imaging devices 300. The front-end server 200 has established communication connections with the image cloud server 100 and each imaging device 300.

[0028] The communication protocol between the front-end processor 200 and the image cloud server 100 can be the Hypertext Transfer Protocol (HTTP), such as using a secure HTTP-based protocol (i.e., HTTPS). Furthermore, the front-end processor 200 and the image cloud server 100 can communicate through a firewall, achieving network isolation while ensuring secure data exchange.

[0029] The communication protocol between the front-end processor 200 and each imaging device 300 can be a digital imaging and communications in medicine (DICOM) protocol, such as the DICOM 3.0 protocol. Furthermore, each front-end processor 200 is located within a hospital's intranet (i.e., deployed on a dedicated hospital network), and multiple imaging devices 300 located within the same hospital as the front-end processor 200 are located on the same intranet as that front-end processor 200.

[0030] The plurality of imaging devices 300 may include: X-ray equipment, CT equipment, MRI equipment, DR equipment, and ultrasound equipment. Therefore, at least two of the imaging devices 300 may use different imaging methods. For example, the X-ray equipment may use X-ray imaging.

[0031] In this embodiment, the object to be imaged can register information on the image cloud server 100. After receiving the object's registration information, the image cloud server 100 can automatically allocate an available target imaging device to the object to generate triage information, thereby achieving triage of the object to be imaged. Subsequently, the front-end processor 200 can retrieve the triage information from the image cloud server 100, that is, retrieve the triage information of the already triaged object. Furthermore, after the front-end processor 200 sequentially listens to the data query request and data transfer request sent by the target imaging device 300, it can automatically send the first and second data from the basic information for imaging through the target imaging device 300 to the target imaging device 300. This allows the target imaging device 300 to image the object based on the first and second data and transmit the object's medical image back to the image cloud server 100 via the front-end processor 200.

[0032] Therefore, the image cloud server 100 needs to have functions such as information registration, triage processing, and data storage, and needs to set up a standard interface (also known as a general interface) to allow the front-end server to retrieve the triage information of the triaged individuals and upload the medical images of the individuals to the image cloud server. This standard interface is a widely used interface in the computer and communications industries. Optionally, this standard interface can be a RESTful interface. REST stands for representational state transfer. Furthermore, this RESTful interface also supports HTTPS encrypted transmission.

[0033] The front-end processor 200 needs to have data synchronization and data storage functions to retrieve and store triage information through the standard interface of the image cloud server. Furthermore, the front-end processor 200 also needs to deploy a DICOM protocol stack, which has a built-in or integrated DICOM SCU (service class user) component and SCP (service class provider) component. This enables the front-end processor 200 to establish DICOM communication connections with each imaging device 300.

[0034] Based on this, the deployment of each device in the triage system will be briefly explained below: I. Image Cloud Server 1. Deployment environment: Deployed in a public cloud environment or a private cloud environment, i.e., a public cloud server or a private cloud server.

[0035] 2. Software Architecture: A microservice architecture is adopted, with core modules including object registration service, triage rule engine, standard interface service and DICOM image storage service. 3. Network Configuration: Open an HTTPS port (e.g., port 443) for access from the front-end server, and implement load balancing through an Nginx reverse proxy. Configure a firewall (e.g., WAF) to filter illegal requests and ensure secure data transmission. The HTTPS port supports HTTPS encrypted transmission, meeting the requirements for secure transmission of medical data.

[0036] In addition, the image cloud server supports elastic scaling, which means that computing resources, storage resources and network resources can be flexibly adjusted according to business needs, and can be expanded or reduced without downtime.

[0037] II. Front-end processor 1. Deployment environment: Deployed on the hospital's intranet and communicates with the image cloud server through a firewall.

[0038] 2. Hardware Requirements: A dedicated server or industrial PC with dual network ports. The minimum configuration is an Intel Core i5 processor, 8GB of RAM, and a 256GB solid-state disk (SSD). The dual network ports include an internal network port and an external network port. The internal network port connects to the imaging equipment within the facility, while the external network port connects to the imaging cloud server via a firewall.

[0039] 3. Software environment: Supports Windows Server / Linux Ubuntu systems, pre-installed with Java runtime environment (such as JRE 1.8+), DICOM toolkit (such as DCM4CHEE toolkit) and database (MySQL 5.7+).

[0040] 4. Security Strategy: Communication between the front-end server and the image cloud server uses the TLS 1.3 encryption protocol. During data transmission, registration information can be encrypted using the AES (e.g., AES-256) algorithm, meeting medical data security standards such as the Health Insurance Portability and Accountability Act (HIPAA) and the General Data Protection Regulation (GDPR). AES stands for Advanced Encryption Standard.

[0041] Furthermore, the front-end processor supports automatic transfer syntax negotiation, ensuring compatibility with the DICOM protocol formats of different imaging devices, such as explicit VR littleendian or implicit VR. This ensures that the front-end processor and various imaging devices can correctly interpret and process DICOM data.

[0042] III. Imaging Equipment 1. Equipment Requirements: Supports the DICOM protocol (such as DICOM 3.0) and requires a fixed Internet Protocol (IP) address and a unique identifier. This identifier is used to uniquely identify the imaging device among multiple imaging devices.

[0043] For example, this identifier can be the application entity title (AETitle) used to identify the communication entity between DICOM nodes. The AETitle is different for any two imaging devices. The AETitle is a unique logical identifier in the DICOM protocol used to identify DICOM devices (such as imaging devices) in a network.

[0044] 2. Network Connection: Imaging equipment and front-end processors located within the same hospital are deployed on the same intranet, such as the same intranet segment (e.g., 192.168.1.0 / 24), and local area network communication is achieved through a switch, with unnecessary ports closed. For example, only the DICOM standard port 104 can be opened. In this embodiment, after the deployment of each device in the triage system is completed, during the communication establishment phase, each imaging device can proactively provide a device information object (DIO) to the front-end server. This DIO may include the imaging device's identifier, IP address, and port number. Correspondingly, the front-end server can automatically obtain the device parameters (i.e., identifier, IP address, and port number) of each imaging device without requiring manual configuration of these parameters. After obtaining the device parameters, the front-end server can store them in a local cache and send a request to the imaging cloud server via HTTPS to send the device parameters of each imaging device along with the identification code (ID) of the hospital to the imaging cloud server.

[0045] Optionally, the triage system may further include a terminal for the object to be imaged. This terminal can log into the image cloud server and send the object's registration information to the image cloud server. For example, the terminal may have a triage application installed, and the image cloud server may serve as the backend server for that application. The terminal can then send the object's registration information to the image cloud server through the triage application.

[0046] Optionally, the terminal can be a mobile terminal or a fixed terminal. The mobile terminal can be a mobile phone, tablet computer, laptop computer, or wearable device, etc. The fixed terminal can be a desktop computer.

[0047] This application provides a triage method, applied to a triage system, for example... Figure 1 The triage system shown. See also Figure 2 The triage method includes: Step 101: If the image cloud server receives the registration information of the object to be imaged, it generates the triage information of the object based on the registration information.

[0048] For each individual, if an imaging examination is deemed necessary based on the doctor's diagnostic needs, registration information can be sent to the image cloud server via the terminal. Upon receiving this registration information, the image cloud server can generate triage information for that individual based on the registration information.

[0049] The triage information includes: the target imaging device used to image the subject, and the subject's registration information. The registration information includes: basic information and imaging mode. The imaging mode of the target imaging device is the same as the imaging mode in the registration information.

[0050] This basic information includes: the subject's name, age, gender, imaging site, symptom description, provisional diagnosis, and imaging precautions. The imaging site can be any body part of the subject, such as the head, chest, abdomen, and legs. The imaging method can be one of the following: X-ray imaging, CT imaging, MRI imaging, DR imaging, and ultrasound imaging.

[0051] Step 102: The image cloud server sends triage information for each object to be imaged to the front-end machine.

[0052] The front-end processor can send a data retrieval request to the image cloud server. In response to this request, the image cloud server can send triage information for each object to be imaged to the front-end processor. The imaging devices recorded in the triage information sent to the front-end processor are associated with that front-end processor.

[0053] Step 103: The front-end unit sends basic information about the object to be imaged by the imaging device.

[0054] The imaging device can request basic information about the object to be imaged by the front-end processor, and the front-end processor can then send the basic information about the object to the imaging device.

[0055] Optionally, the front-end processor can directly send complete basic information to the imaging device. Alternatively, the front-end processor can first send the first data from the basic information to the imaging device. This first data is used to confirm the object for subsequent imaging. Subsequently, after the object completes its check-in, the front-end processor sends the second data from the basic information to the imaging device. That is, the front-end processor can send the data from the basic information to the imaging device in batches.

[0056] Step 104: The imaging device performs imaging on the object based on the object's basic information to obtain a medical image of the object.

[0057] The imaging device can first display the first data from the basic information for the subject to check in, in order to proceed with subsequent imaging. After the subject has checked in, the imaging device can then image the subject based on the second data from the basic information, thereby obtaining the subject's medical image.

[0058] Step 105: The imaging equipment sends the medical images of the target to the front-end unit.

[0059] Once the imaging equipment generates a medical image of the object, it can transmit the medical image to the front-end processor.

[0060] Step 106: The front-end processor uploads the object's medical images to the image cloud server.

[0061] After receiving the medical image of the object, the front-end machine can transmit the medical image to the image cloud server for storage and to trigger subsequent diagnostic processes.

[0062] In summary, this application provides a triage method. After receiving registration information of an object, the image cloud server generates triage information based on this registration information. This triage information includes a target imaging device for imaging the object, and the object's registration information, which includes basic information and imaging method. Subsequently, the front-end processor sends the object's basic information to the target imaging device based on the triage information, enabling the target imaging device to image the object and obtain a medical image. Afterward, the target imaging device sends the medical image to the front-end processor for uploading to the image cloud server. In other words, in this method, the image cloud server automatically generates triage information based on registration information to triage the object; the front-end processor sends the object's basic information to the matching target imaging device based on the triage information; and the target imaging device, after imaging the object, uploads the medical image to the image cloud server through the front-end processor. Therefore, on the one hand, the elimination of manual triage improves triage efficiency and accuracy, thereby increasing the efficiency of imaging examinations; on the other hand, it enables data exchange between the imaging cloud server and imaging equipment, thus solving the data silo problem in the hospital intranet caused by security factors; and on yet another hand, it automates the entire imaging examination process from information registration to imaging, further improving the efficiency of imaging examinations.

[0063] Figure 3 This is a flowchart of another triage method provided in an embodiment of this application, which can be applied to a triage system. See also... Figure 3 The method may include: Step 201: The terminal sends the object's registration information to the image cloud server.

[0064] For each individual, if the physician determines that an imaging examination is required based on the individual's diagnostic needs, the control terminal can log in to the image cloud server. Subsequently, the individual can input registration information into the terminal. In response to this input, the terminal can retrieve the registration information and send it to the image cloud server.

[0065] The registration information includes: basic information and imaging method. The basic information includes: the subject's name, age, gender, imaging site, symptom description, provisional diagnosis, and imaging precautions. The provisional diagnosis and imaging precautions can be determined by the physician based on the subject's physical condition.

[0066] The imaging site can be any part of the subject's body, such as the head, chest, abdomen, and legs. The imaging method can be one of the following: X-ray imaging, CT imaging, MRI imaging, DR imaging, and ultrasound imaging.

[0067] It is understood that a triage application can be installed on the terminal, and the terminal can log in to the image cloud server through the triage application. Optionally, the triage application can be a web application.

[0068] Step 202: The image cloud server generates triage information for the object to be imaged based on the registration information of the object.

[0069] After receiving the registration information for each object, the image cloud server can allocate an available target imaging device to the object based on the imaging method specified in the registration information, and generate triage information for the object based on the target imaging device and the registration information. The triage information for each object may include: the target imaging device used to image the object, and the object's registration information.

[0070] The imaging method of the target imaging device is the same as the imaging method in the registration information of the object. Same imaging method means the imaging methods are identical, such as both being CT. It can be understood that triage information including the target imaging device means including the identifier of the target imaging device, which is used to uniquely identify the target imaging device among multiple imaging devices.

[0071] To facilitate the differentiation of triage information for different objects, the triage information may also include: an object ID. This object ID can be an ID automatically generated by the image cloud server in response to an object addition operation to uniquely identify the object.

[0072] In this embodiment of the application, the image cloud server can first obtain at least two candidate image devices from multiple image devices whose imaging methods are the same as those in the registration information of the object, and then obtain the target image device for imaging the object from the at least two candidate image devices.

[0073] The process by which the image cloud server acquires the target image device from at least two candidate image devices can be described as follows: In one alternative implementation, the image cloud server can identify any one of the at least two alternative image devices as the target image device.

[0074] In another optional implementation, the image cloud server can receive the status of each image device uploaded by the front-end server, as well as the completion time of imaging for image devices in an idle state (either idle or busy). Multiple image devices include at least two alternative image devices. The completion time is the time when the image device completes imaging of the last imaged object, which is the last imaged object among all imaged objects assigned to the image device. In other words, the completion time is the time when the image device last generated an image. After completing imaging of the last imaged object, the image device can then enter an idle state.

[0075] Subsequently, the image cloud server can, based on the status of each candidate image device, select candidate image devices with idle states from at least two candidate image devices; then, based on the completion time of each candidate image device, select the target image device from the candidate image devices. The target image device has the longest idle time. For example, for each candidate image device, the image cloud server can determine the idle time of that candidate image device based on the difference between the current time and the completion time of that candidate image device. Then, the image cloud server can compare the idle times of each candidate image device to obtain the target image device with the longest idle time.

[0076] For example, assuming the imaging equipment is a CT scanner, and the completion time of CT scanner A (i.e., the time when the last image was generated) is 2025-12-23 09:00:00, while the completion time of CT scanner B is 2025-12-23 09:05:00, then the image cloud server can determine that CT scanner A is the target imaging equipment. That is, the next automatic triage will prioritize assigning the image to scanner A.

[0077] For example, CT device A was triaged at 09:00:00 on December 23, 2025, and the triage was completed at 09:05:00 on the same day. CT device B was triaged at 09:01:00 on December 23, 2025, and the imaging was completed at 09:03:00 on the same day. CT device B last generated images a longer time ago, therefore the image cloud server can identify CT device B as the target imaging device.

[0078] Optionally, the triage information may also include: examination time, registration time and validity period of the registration information. That is, the triage information includes: subject ID, subject name, age, gender, examination site, imaging method, target imaging device identifier, examination time, symptom description information, and registration time. The examination time refers to the time period during which the target imaging device images the subject. The registration time can refer to the time when the image cloud server receives the registration information. The validity period refers to the remaining validity time of the triage information.

[0079] In this embodiment, after obtaining the triage information of each object, the image cloud server can also store the triage information of the object in a cloud database in JSON format. Therefore, after allocating an available target imaging device to an object, the image cloud server can bind and store the target imaging device with the object's object ID.

[0080] Understandably, for sensitive information about an object, such as the identification number (e.g., ID card number) entered when adding an object, the image cloud server can encrypt and store this sensitive information. For example, the image cloud server can use an asymmetric encryption algorithm (such as the RAS algorithm) to encrypt this sensitive information.

[0081] Optionally, the image cloud server can also record the synchronization status of each triage record and the imaging status of the object. The synchronization status can be "pending synchronization" or "retrieved." "Pending synchronization" means the image has not yet been sent to the front-end server. "Retrieved" means the image has been sent to the front-end server. The imaging status can be "pending imaging" or "images already formed." "Pending imaging" means the medical image for this instance has not yet been received. "Images already formed" means the medical image for this instance has been received.

[0082] Understandably, after generating triage information, the image cloud server can set the status of the triage information to "pending synchronization". And after the image cloud server sends the triage information to the front-end server, it can update the synchronization status of the triage information from "pending synchronization" to "pulled".

[0083] It is also understandable that the image cloud server is equipped with a triage rule engine, which can generate triage information for an object based on the object's registration information.

[0084] In this embodiment, after the image cloud server generates the triage information for an object, it can also feed the triage information back to the object's terminal. The terminal can then display the triage information for the object to view and arrive at the hospital where the target imaging device recorded in the triage information is located before the examination time.

[0085] Step 203: The front-end device sends a data retrieval request to the image cloud server.

[0086] The front-end server can send data retrieval requests to the image cloud server according to a retrieval cycle. These requests can carry a timestamp. For example, the retrieval request can carry both a timestamp and the front-end server's identifier. The retrieval cycle can be pre-stored by the front-end server, for example, it can be 30 seconds (s). The front-end server's identifier can be used to uniquely identify the front-end server among multiple front-end servers. For example, since a hospital typically deploys one front-end server, its identifier could be the hospital's ID.

[0087] Optionally, the data retrieval request may carry a signature. This signature may be obtained by the front-end machine processing key parameters of the data retrieval request using an application programming interface (API) key and a security algorithm.

[0088] This key parameter may include a timestamp. The API key may be pre-stored on the front-end server, or it may be generated by the image cloud server based on the ID of the hospital where the front-end server is located and then distributed to the front-end server.

[0089] Optionally, the security algorithm can be a hash-based message authentication code (HMAC) algorithm, such as HMAC-SHA256.

[0090] In this embodiment of the application, when the front-end machine pulls triage information from the image cloud server for the first time, it can pull the full amount of information, that is, it can obtain all triage information from the image cloud server for the first time.

[0091] When the front-end server subsequently (i.e., not for the first time) retrieves triage information from the image cloud server, it can use an incremental retrieval method, that is, only retrieving triage information added since the last retrieval. In this way, the duplicate transmission of triage information can be avoided, thereby avoiding the performance overhead and resource waste caused by full retrieval.

[0092] For example, the front-end server can use the registration time to identify newly added triage information. Specifically, the front-end server can only retrieve triage information whose registration time is later than the last time it was retrieved, in order to achieve incremental retrieval of triage information.

[0093] Alternatively, the front-end server can use the synchronization status of triage information to identify newly added triage information. Specifically, the front-end server can obtain triage information with a status of "pending synchronization" to achieve incremental retrieval of triage information.

[0094] Step 204: The image cloud server responds to the data retrieval request sent by the front-end machine and sends encrypted triage information to the front-end machine.

[0095] After receiving a data retrieval request from the front-end server, the imaging cloud server responds by obtaining at least one triage record associated with that front-end server. It can then encrypt this triage record and send the encrypted triage records back to the front-end server. The association between the triage record and the front-end server means that the imaging device recorded in the triage record is associated with the front-end server. The imaging device associated with the front-end server is deployed in the same hospital as the front-end server.

[0096] As described in steps 203 and 204 above, the front-end server and the image cloud server can communicate using a "one-way request" - "response" mode. In this mode, the front-end server actively pulls triage information, and the image cloud server does not actively push triage information. This can largely avoid the risk of internal network exposure. Understandably, for each piece of triage information, the image cloud server can use an encryption algorithm to process and encrypt the triage information. This encryption algorithm can be a symmetric encryption algorithm, such as AES.

[0097] In this embodiment, the data retrieval request also includes a signature option. Specifically, for cases requiring authentication of the data retrieval request, the image cloud server, upon receiving the data retrieval request from the front-end server, can verify the signature carried in the request. After successful verification, it can send encrypted triage information to the front-end server. This ensures secure access.

[0098] Understandably, the image cloud server can pre-store the mapping between the IDs and API keys of each hospital. The image cloud server can obtain the corresponding API key based on the identifier of the front-end server, and use the API key to verify the signature in the data retrieval request sent by the front-end server.

[0099] In this embodiment of the application, after the triage information is sent to the front-end machine, the image cloud server can update the synchronization status of the triage information from "pending synchronization" to "retrieved".

[0100] In some embodiments, the image cloud server interface can be configured to support batch JSON responses (maximum 1MB), and the amount of data pulled by the front-end machine at one time can not exceed 100 records. This can improve transmission efficiency. Step 205: The front-end machine decrypts the encrypted triage information to obtain the decrypted triage information.

[0101] After receiving the encrypted triage information, the front-end processor can process the encrypted triage information using a decryption algorithm corresponding to the encryption algorithm to decrypt the triage information and obtain the decrypted triage information. For example, the decryption algorithm can be the AES algorithm.

[0102] Because the front-end processor and the image cloud server can encrypt the transmission of triage information, the secure transmission of triage information is effectively ensured.

[0103] In this embodiment, after obtaining the decrypted triage information, the front-end processor can use a JSON parser to parse the triage information to extract its content, such as the object ID, basic object information, and the identifier of the target imaging device. Subsequently, the front-end processor can store the extracted triage information locally, for example, in a local database. Optionally, this database can be a MySQL database.

[0104] Understandably, the front-end processor can store the retrieved information in a table format. Furthermore, the front-end processor can record the synchronization time and processing status of each triage record in the table. This processing status can be either unassigned or assigned. Synchronization time refers to the time it takes to retrieve the triage information. "Unassigned" means it has not yet been distributed to the corresponding imaging equipment. "Assigned" means it has already been distributed to the corresponding imaging equipment.

[0105] Optionally, the front-end server can use Redis to cache recent triage information to reduce database query pressure. This recent triage information refers to triage information valid for 2 hours.

[0106] In this embodiment, the image cloud server can provide RESTful interfaces of type GET or POST. Hereinafter, the RESTful interface of type GET will be referred to as the GET interface, and the RESTful interface of type POST will be referred to as the POST interface. Correspondingly, the front-end server can call the GET interface of the image cloud server to send a data retrieval request to the image cloud server.

[0107] For example, the front-end processing unit can send a data pull request to the imaging cloud server as follows: GET / api / v1 / patient / pull?hospitalId=HOSP001. HOSP001 is the hospital ID, i.e., the identifier of the front-end processing unit. After verifying the signature, the imaging cloud server can return triage information in the following JSON format: { "data": [ { "visitId": "CL20250428001", "patientName": "Zhang San", "modality": "CT", "aetitle": "CT_01", "registerTime": "2025-04-28 10:00:00" } ], "total": 1 }

[0108] The object's visitId is CL20250428001, patientName is Zhang San, imaging modality is CT, the target imaging device identifier (aetitle) assigned to this object is CT_01, and the object's registration time on the image cloud server is 2025-04-28 10:00:00. The total number of triage information retrieved this time is 1.

[0109] In this embodiment, if the front-end server fails to retrieve triage information, it can record an error log and automatically retry a preset number of times. If it still fails, the front-end server can mark this retrieval as "to be retried" and prioritize it for the next retrieval. Therefore, this front-end server supports resuming interrupted downloads.

[0110] The preset value is pre-stored by the front-end machine, for example, it is 3. Furthermore, during the retry process, the interval between two adjacent fetches can be 10 seconds (s).

[0111] Step 206: The imaging equipment sends a data query request to the front-end unit.

[0112] Each imaging device can send a data query request to the imaging cloud server when it is idle. The data query request carries the identifier of the imaging device.

[0113] Understandably, the front-end processor is equipped with a DICOM protocol stack. When querying data from the front-end processor, the imaging device can act as an SCP (requester) and send a C-FIND request (data retrieval request) to the front-end processor, which acts as an SCU (responder). This C-FIND request can also carry the processing status of the triage information to be queried, which is "unassigned." In other words, each imaging device requests triage information that is unassigned and for which the target imaging device is located. That is, the identification of the imaging device and its processing status constitute the query conditions of the C-FIND request.

[0114] Step 207: In response to the data query request sent by the imaging device, the front-end unit sends back the first data from the basic information of the target object to the imaging device.

[0115] After receiving a data query request from the imaging device, the front-end processor can query its local database based on the parameters carried in the request to obtain triage information for the target object. Subsequently, the front-end processor can send back the first piece of basic information included in the triage information to the imaging device. For example, the front-end processor can send a C-FIND response to the imaging device to send back the first piece of data.

[0116] The first data includes: the name of the target object and the examination site. This parameter includes at least the identifier of the imaging device, and if it does include the identifier of the imaging device and the processing status of the triage information, the processing status is "unassigned". The triage information of the target object is the triage information that meets the query conditions. For example, if the parameter includes the identifier of the imaging device and the processing status of the triage information, then the triage information of the target object is the triage information among multiple triage information where the identifier of the target imaging device is the identifier of that imaging device, and the processing status is "unassigned".

[0117] Furthermore, in response to a data query request sent by the imaging device, the front-end processor can also send back the object ID of the target object to the imaging device. This makes it easier to distinguish between multiple objects.

[0118] In this embodiment of the application, the front-end processor can encapsulate the target object into a DICOM format dataset and send the dataset back to the imaging device.

[0119] Understandably, if the front-end unit determines that the imaging device is offline before sending the first data, it can temporarily store the first data and automatically send a C-FIND response after determining that the imaging device is online, so as to send the first data back to the imaging device.

[0120] In some embodiments, if the front-end sensor detects that the imaging device's heartbeat has timed out (e.g., no response for 5 minutes), it can determine that the imaging device is offline.

[0121] In this embodiment, the front-end processor can also obtain the imaging priority of each object. This imaging priority can be obtained by the image cloud server in response to the object's input operation and sent to the front-end processor along with the triage information.

[0122] Among multiple objects, the imaging priority of the first object is higher than that of the second object. The imaging priority of each object can be represented by "emergency" or "non-emergency," with "emergency" having a higher priority than "non-emergency." In this case, the front-end processor can prioritize sending the basic information of the first object to the target imaging device. That is, the front-end processor can support the priority transmission of triage information with higher imaging priority back to the imaging device.

[0123] This allows for tiered processing of triage information, which can largely meet the treatment needs of those with tighter timeframes and ensure the precise allocation of medical resources.

[0124] Step 208: The imaging device displays the first data in the basic information of the target object.

[0125] Once the imaging device receives the first data from the basic information of the target object sent by the front-end unit, it can display the first data for the target object to view.

[0126] Understandably, if the front-end camera also sends the object ID of the target object back to the imaging device, the imaging device can also display the object ID of the target object.

[0127] Optionally, the imaging device may display the first data and object ID in a list format. For example, the imaging device may display the first data and object ID of the target object in a list of objects to be inspected.

[0128] Step 209: The imaging device sends a data transfer request to the front-end unit.

[0129] After the target object completes its check-in at the imaging device, the imaging device can send a data transfer request to the front-end camera to obtain the target object's second data, thus obtaining more complete data. Optionally, this data transfer request can carry the target object's object ID.

[0130] Optionally, the target can check in at the imaging device by swiping a card or scanning a QR code.

[0131] Understandably, this data transfer request can be a C-MOVE request.

[0132] Step 210: In response to the data transfer request, the front-end device sends the second data from the basic information of the target object to the imaging device.

[0133] After receiving a data transfer request from the imaging device, the front-end processor can obtain second data from the target object's basic information, such as the object ID carried in the data transfer request. Subsequently, the front-end processor can send this second data to the imaging device. This second data may include: imaging location, symptom description information, clinical diagnostic information, examination precautions, and the target object's age and gender.

[0134] It is understandable that the implementation method of the front-end device sending the second data to the imaging device can refer to the relevant implementation process of sending the first data back to the imaging device, and will not be described again in the embodiments of this application.

[0135] Imaging devices can first acquire and display the first data from the basic information of the target object, and then acquire the second data of the target object after determining the target object and performing imaging. This effectively saves the display and storage resources of the imaging device.

[0136] Step 211: The imaging device performs an imaging operation based on the basic information of the target object to obtain a medical image of the target object.

[0137] After acquiring the second data of the target object, the imaging device can load the basic information of the target object into the examination queue. When imaging the target object, the imaging device can perform imaging operations based on this basic information and generate a medical image of the target object after imaging is completed. The medical image is a DICOM image file, which includes metadata and pixel data of the target object. The metadata may include a study instance unique identifier (StudyInstanceUID) and a series instance unique identifier (SeriesInstanceUID).

[0138] Understandably, imaging equipment can load the basic information and object ID of the target object into the inspection queue and perform imaging operations based on this basic information and object ID.

[0139] It is also understandable that after completing imaging of the target object, the imaging device can send a notification message to the front-end camera. This notification message includes the completion time of imaging and the target object's identifier (such as an object ID). Furthermore, if the target object is the last object assigned to the imaging device for imaging, the device can enter an idle state after completing imaging of that object. If the target object is not the last object assigned to the imaging device, the device will need to image the next target object after completing imaging of that object; that is, the imaging device will be in a busy state.

[0140] Step 212: The imaging equipment sends the medical images of the target object to the front-end unit.

[0141] Imaging equipment can send the medical image to the front-end processor via a C-STORE request. For example, it can send it to port 104 of the front-end processor.

[0142] It is understandable that when uploading medical images to the front-end processor, the imaging device can act as the SCU (i.e., the requester), and the front-end processor can act as the SCP (i.e., the responder).

[0143] Step 213: The front-end processor uploads the medical images of the target object to the image cloud server.

[0144] Once the front-end receives the medical image of the target object, it can upload the medical image to the image cloud server.

[0145] In this embodiment, the front-end processor can call the POST interface provided by the image cloud server to upload the medical image. For example, the front-end processor can send POST / api / v1 / image / upload to the image cloud server, along with the medical image and the associated object ID, to upload the medical image of the target object and the object ID to the image cloud server.

[0146] Understandably, after receiving a medical image, the front-end processor can extract the StudyInstanceUID from the image's metadata and associate this StudyInstanceUID with an object ID in the local database. Furthermore, the front-end processor can store the medical image in a temporary storage area.

[0147] For example, the storage path for this temporary storage area could be / dicom_uploads / visitId / series / .

[0148] In this embodiment of the application, after the image cloud server receives the medical image of the target object, it can store the medical image and update the imaging status of the object from "not imaged" to "imaged", and trigger the subsequent remote diagnosis process.

[0149] Optionally, the image cloud server can store the medical image in object storage.

[0150] In this embodiment, the front-end processor can also receive notification messages sent by the imaging device. Based on the notification messages, the front-end processor can detect whether the target imaging device has completed imaging of all imaging objects allocated to it. If the front-end processor determines that the imaging device has completed imaging of all imaging objects allocated to it, it can determine that the imaging device is in an idle state; and if it determines that the imaging device has not completed imaging of all imaging objects allocated to it, it can determine that the imaging device is in a busy state. All imaging objects include the target object. Subsequently, the front-end processor can also send the status of the imaging device to the image cloud server, and if the imaging device is in an idle state, send the completion time of the target imaging device to the image cloud server. This facilitates the image cloud server in allocating allocation information to the imaging device.

[0151] It should be understood that after receiving the notification message, the front-end device can count the objects in all notification messages sent by the imaging device up to the time of the notification message, and determine that the imaging device has completed imaging of all imaging objects assigned to the imaging device when it is determined that the objects in all notification messages include all imaging objects assigned to the imaging device.

[0152] Traditional hospitals rely on locally deployed picture archiving and communication systems (PACS) and hospital information systems (HIS) for triage and image management of patients requiring imaging. Specifically, patients first register their information in the HIS and then proceed to the imaging examination area. Staff in the imaging examination area verify the patient's registration information and actual condition, and then manually assign available imaging equipment to the patient based on the availability of various imaging devices. The imaging device then takes an image of the patient and uploads the resulting medical image to the PACS for storage.

[0153] However, traditional triage methods rely on manual triage, which is inefficient and prone to inaccuracies due to human error. Furthermore, because PACS and HIS are deployed locally—on servers within the hospital—they are completely isolated from external networks (such as image cloud servers), preventing the sharing of medical images with other hospitals or remote consultation platforms. This results in two problems: firstly, a relatively closed system leading to data gaps and data silos; and secondly, high deployment costs.

[0154] With the popularization of cloud computing technology, image cloud servers can be used to realize functions such as information registration, image sharing, and remote diagnosis, thereby solving the problem of data silos to some extent. However, in order to ensure data security, hospitals usually isolate internal equipment from the external network, which means that image cloud servers and hospital equipment cannot directly transmit data. Instead, cross-network interaction must be achieved through manual copying or manual configuration of network gateways, which poses the risk of data leakage and is inefficient.

[0155] Among related technologies, cloud-edge collaboration technology can be used for data transfer to achieve interconnection between the imaging cloud server and in-hospital equipment. This cloud-edge collaboration technology refers to deploying an edge server within the hospital and manually configuring a DICOM gateway to connect the imaging cloud server and imaging equipment.

[0156] However, cloud-edge collaboration technology only processes local data through edge servers and can only achieve one-way data transmission (such as uploading medical images to an imaging cloud server), failing to address the issue of actively pushing data from the imaging cloud server to imaging devices. Consequently, even if the subject to be imaged can register information on the imaging cloud server, the information still needs to be repeatedly entered into the HIS (Hospital Information System), and manual intervention is still required for triage. Furthermore, the computing power of edge servers is limited and cannot support complex triage logic.

[0157] The method provided in this application embodiment allows the image cloud server to generate triage information based on the registration information of an object after receiving that registration information. This triage information includes a target imaging device for imaging the object, and the object's registration information, which includes basic information and imaging method. Subsequently, the front-end processor can send the object's basic information to the target imaging device based on the triage information, enabling the target imaging device to image the object and obtain a medical image. Afterward, the target imaging device can send the medical image to the front-end processor for uploading to the image cloud server. Therefore, through the collaborative work of the image cloud server, the hospital's front-end processor, and the imaging equipment, automatic triage by the image cloud server can be achieved, improving triage efficiency and accuracy. Furthermore, the front-end processor enables automated interconnection between the image cloud server and hospital equipment, thereby achieving secure synchronization of the object's basic information and the image image between the imaging equipment and the image cloud server.

[0158] Specifically, firstly, by configuring a standard interface for the image cloud server and deploying a front-end server within the hospital, a secure and reliable cross-network data exchange channel is established, enabling the registration information on the image cloud server to be automatically synchronized to the imaging equipment within the hospital. This solves the problem of information gaps caused by network isolation between the image cloud server and the imaging equipment within the hospital, and realizes bidirectional flow of registration information between the image cloud server and the imaging equipment.

[0159] Second, the system generates triage information for each patient based on their registration information via an image cloud server, enabling patient triage. A front-end server periodically retrieves triage information from the image cloud server and establishes an SCU-SCP relationship with imaging equipment based on the DICOM protocol, actively listening for data query requests from the imaging equipment. This allows the system to distribute basic patient information to the appropriate imaging equipment for imaging. Thus, the entire process from registration on the image cloud server to in-hospital imaging equipment examination is automated without manual intervention, improving triage and imaging efficiency and avoiding the inefficient operation of repeatedly entering registration information and manually assigning equipment by staff.

[0160] Third, through the DICOM protocol stack and automatic negotiation transmission syntax, the front-end machine can automatically meet the communication requirements of various types of imaging equipment and automatically parse the parameters of the imaging equipment without the need for manual configuration of parameters such as AETitle within the hospital; and all imaging equipment are managed by a unified imaging cloud server, which can directly replace or be compatible with traditional PACS / HIS systems, providing a low-cost and easy-to-deploy information solution for small and medium-sized hospitals.

[0161] Fourth, the front-end server is deployed on the hospital's private network. Encrypted transmission and firewall policies effectively ensure data security, while also supporting seamless access for various types of devices. Therefore, without altering the hospital's existing equipment and network architecture, efficient collaboration between the imaging cloud server and hospital equipment can be achieved, thus meeting medical data security compliance requirements and system compatibility needs in complex scenarios.

[0162] It is understood that the order of steps in the triage method provided in this application embodiment can be appropriately adjusted, and steps can be added or removed as needed. For example, step 203 can be deleted as needed; or step 206 can be deleted as needed; or step 209 can also be deleted as needed. Any variations that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the protection scope of this application, and therefore will not be elaborated further.

[0163] In summary, this application provides a triage method. After receiving registration information of an object, the image cloud server generates triage information based on this registration information. This triage information includes a target imaging device for imaging the object, and the object's registration information, which includes basic information and imaging method. Subsequently, the front-end processor sends the object's basic information to the target imaging device based on the triage information, enabling the target imaging device to image the object and obtain a medical image. Afterward, the target imaging device sends the medical image to the front-end processor for uploading to the image cloud server. In other words, in this method, the image cloud server automatically generates triage information based on registration information to triage the object; the front-end processor sends the object's basic information to the matching target imaging device based on the triage information; and the target imaging device, after imaging the object, uploads the medical image to the image cloud server through the front-end processor. Therefore, on the one hand, the elimination of manual triage improves triage efficiency and accuracy, thereby increasing the efficiency of imaging examinations; on the other hand, it enables data exchange between the imaging cloud server and imaging equipment, solving the problem of data silos in the hospital intranet caused by security factors; and on yet another hand, it automates the entire imaging examination process from information registration to imaging, further improving the efficiency of imaging examinations.

[0164] Figure 4 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application. Figure 4As shown, the electronic device 400 includes a processor 401 and a memory 403. The processor 401 and the memory 403 are connected, for example, via a bus 402. Optionally, the electronic device 400 may also include a transceiver 404. It should be noted that in practical applications, the transceiver 404 is not limited to one type, and the structure of this electronic device 400 does not constitute a limitation on the embodiments of this application.

[0165] Processor 401 may be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. Processor 401 may also be a combination that implements computational functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc.

[0166] Bus 402 may include a pathway for transmitting information between the aforementioned components. Bus 402 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, etc. Bus 402 can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 4 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0167] The memory 403 stores a computer program corresponding to the triage method provided in the above embodiments of this application. This computer program is controlled and executed by the processor 401. The processor 401 executes the computer program stored in the memory 403 to implement the content shown in the aforementioned method embodiments.

[0168] Specifically, if electronic device 400 serves as an image cloud server, then processor 401 is used for: If the registration information of the object to be imaged is received, the triage information of the object is generated based on the registration information. The triage information includes: the target imaging device for imaging the object, and the registration information, which includes basic information and imaging mode. The imaging mode of the target imaging device is the same as the imaging mode in the registration information. The triage information of the object is sent to the front-end unit associated with the target imaging device. The triage information is used by the front-end unit to send the basic information of the object to the target imaging device, so that the target imaging device can image the object based on the basic information and send the medical image obtained from the image to the front-end unit. Receive medical images of objects uploaded by the front-end processor.

[0169] Optionally, the process by which the processor 401 generates triage information for an object based on registration information may include: From multiple imaging devices, obtain at least two alternative imaging devices whose imaging methods are the same as those in the registration information; Acquire the target imaging device from at least two alternative imaging devices; Based on the identification and registration information of the target imaging equipment, triage information for the subject is generated.

[0170] Optionally, the process by which the processor 401 acquires the target imaging device from at least two alternative imaging devices may include: The system receives the status of each imaging device from the front-end processor, as well as the completion time of imaging for imaging devices in an idle state, which can be either idle or busy. Based on the status of each candidate imaging device, obtain candidate imaging devices that are in an idle state from at least two candidate imaging devices; Based on the completion time of each candidate imaging device, the target imaging device is obtained from the candidate imaging devices, and the target imaging device has the longest idle time.

[0171] Optionally, the processor 401 can be used for: Receive data retrieval requests sent by the front-end unit associated with the target imaging device; In response to a data retrieval request, triage information for the target object is sent to the front-end server.

[0172] Optionally, the data fetch request carries a signature. Optionally, the processor 401 can be used for: Verify the signature carried in the data retrieval request; After the signature is verified, the encrypted triage information is sent to the front-end machine.

[0173] If electronic device 400 is used as a front-end processor, then processor 401 is used for: The system receives triage information of the object to be imaged from the image cloud server. The triage information is generated based on the object's registration information and includes: the target imaging device used to image the object, and the registration information, which includes basic information and imaging method. The imaging method of the target imaging device is the same as the imaging method in the registration information, and the target imaging device is associated with the front-end unit. Send basic information about the object to the target imaging device so that the target imaging device can image the object based on the basic information to obtain medical images; It receives medical images sent by the target imaging device and uploads them to the imaging cloud server.

[0174] Optionally, the processor 401 can be used for: Receive data query requests sent by the target imaging device; In response to a query request, the first data from the basic information is sent back to the target imaging device. The first data is used for display by the target imaging device. Receive data transfer requests sent by the target imaging device. The data transfer requests are sent by the target imaging device after the target has completed its check-in. In response to a data transfer request, the second data from the registration information is sent to the target imaging device.

[0175] Optionally, there can be multiple objects, with the imaging priority of the first object being higher than that of the second object. The processor 401 can be used for: Prioritize sending basic information about the first object to the target imaging device.

[0176] Optionally, the processor 401 can also be used for: Receive a notification message sent by the target imaging device. The notification message is sent by the target imaging device after it has completed imaging of the object. The notification message includes the completion time of the imaging by the target imaging device and the object. Based on the notification message, if it is determined that the target imaging device has completed imaging of all imaging objects assigned to the target imaging device, then the state of the target imaging device is determined to be idle; and if it is determined that the target imaging device has not completed imaging of all imaging objects assigned to the target imaging device, then the state of the target imaging device is determined to be busy, wherein all imaging objects include objects. Send the status of the target imaging device to the image cloud server, and if the target imaging device is in an idle state, send the completion time of the target imaging device to the image cloud server.

[0177] If the electronic device 400 is used as an imaging device, then the processor 401 is used for: The system receives basic information about the object sent by the front-end machine associated with the imaging device. The triage information to which the basic information belongs is generated by the imaging cloud server based on the object's registration information and sent to the front-end machine. The triage information includes: the imaging device and the registration information. The registration information includes basic information and imaging mode. The imaging mode of the imaging device is the same as the imaging mode in the registration information. Based on basic information, images are formed of the object to obtain its medical images; Send medical images to the front-end processor so that the front-end processor can upload the medical images to the image cloud server.

[0178] Optionally, the processor 401 can be used for: Send a data query request to the front-end camera. The data query request is used to request the front-end camera to send the first data in the basic information back to the imaging device. Display the first data; After the confirmed object has completed the check-in, a data transfer request is sent to the front-end camera. The data transfer request is used to request the front-end camera to send the second data from the basic information back to the imaging equipment.

[0179] Optionally, the processor 401 can be used for: A data storage request is sent to the front-end processor, and the data storage request carries medical images.

[0180] Optionally, the front-end machine is equipped with a DICOM protocol stack; Data query requests are C-FIND requests, data transfer requests are C-MOVE requests, and data storage requests are C-STORE requests.

[0181] In summary, this application provides an image cloud server, a front-end processor, and an imaging device. After receiving registration information of an object, the image cloud server can generate triage information based on this registration information. This triage information includes a target imaging device for imaging the object, and the object's registration information, which includes basic information and imaging method. Subsequently, the front-end processor can send the object's basic information to the target imaging device based on the triage information, enabling the target imaging device to image the object based on this basic information and obtain a medical image. Afterward, the target imaging device can send the medical image to the front-end processor for uploading to the image cloud server. In other words, the image cloud server can automatically generate triage information based on the registration information to achieve object triage; the front-end processor can send the object's basic information to the matching target imaging device based on the triage information; and the target imaging device, after imaging the object, can upload the medical image to the image cloud server through the front-end processor. Therefore, on the one hand, the elimination of manual triage improves triage efficiency and accuracy, thereby increasing the efficiency of imaging examinations; on the other hand, it enables data exchange between the imaging cloud server and imaging equipment, solving the problem of data silos in the hospital intranet caused by security factors; and on yet another hand, it automates the entire imaging examination process from information registration to imaging, further improving the efficiency of imaging examinations.

[0182] This application provides a computer-readable storage medium storing a computer program thereon. When the computer program is executed by a processor, it implements the triage method provided in the above-described method embodiments. For example, Figure 1 or Figure 2 The method performed by any of the following devices: the image cloud server, the front-end processor, and the image equipment shown.

[0183] This application provides a computer program product, which includes a computer program that, when executed by a processor, implements the triage method provided in the above-described method embodiments. For example, Figure 1 or Figure 2 The method performed by any of the following devices: the image cloud server, the front-end processor, and the image equipment shown.

[0184] It should be noted that the logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be specifically implemented in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable media include: an electrical connection having one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Alternatively, the computer-readable medium may be paper or other suitable media on which the program can be printed, since the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in a computer memory.

[0185] It should be understood that various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0186] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0187] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "multiple" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0188] In this application, unless otherwise expressly specified and limited, the terms "installation," "connection," "joining," and "fixing," etc., should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral part; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; they can refer to the internal communication of two components or the interaction between two components, unless otherwise expressly limited. Those skilled in the art can understand the specific meaning of the above terms in this application according to the specific circumstances.

[0189] Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of this application.

Claims

1. A triage method, characterized in that, Applied to an image cloud server; the method includes: If registration information of an object to be imaged is received, triage information of the object is generated based on the registration information. The triage information includes: a target imaging device for imaging the object, and the registration information. The registration information includes basic information and imaging mode. The imaging mode of the target imaging device is the same as the imaging mode in the registration information. The triage information of the object is sent to the front-end unit associated with the target imaging device. The triage information is used by the front-end unit to send the basic information of the object to the target imaging device, so that the target imaging device can image the object based on the basic information and send the imaged medical image to the front-end unit. Receive the medical images of the object uploaded by the front-end machine.

2. The method according to claim 1, characterized in that, Based on the registration information, triage information for the object is generated, including: From multiple imaging devices, at least two alternative imaging devices with the same imaging method as the imaging method in the registration information are selected; The target imaging device is acquired from the at least two alternative imaging devices; Based on the identifier of the target imaging device and the registration information, triage information for the object is generated.

3. The method according to claim 2, characterized in that, Obtaining the target imaging device from the at least two candidate imaging devices includes: The system receives the status of each of the imaging devices sent by the front-end unit, and the completion time of imaging by the imaging device in the idle state, wherein the status is either the idle state or the busy state. Based on the status of each of the candidate imaging devices, a candidate imaging device whose status is idle is obtained from the at least two candidate imaging devices; Based on the completion time of each candidate imaging device, a target imaging device is obtained from the candidate imaging devices, wherein the target imaging device has the longest idle time.

4. The method according to any one of claims 1 to 3, characterized in that, Sending triage information of the object to the front-end unit associated with the target imaging device, including: Receive a data retrieval request sent by the front-end unit associated with the target imaging device; In response to the data retrieval request, the triage information of the object is sent to the front-end machine.

5. The method according to claim 4, characterized in that, The data retrieval request carries a signature; in response to the data retrieval request, the triage information of the object is sent to the front-end machine, including: Verify the signature carried in the data retrieval request; After the signature is verified, the encrypted triage information is sent to the front-end machine.

6. A triage method, characterized in that, Applied to a front-end processor, the method includes: The system receives triage information of an object to be imaged from an image cloud server. The triage information is generated based on the registration information of the object and includes: a target imaging device for imaging the object, and the registration information, which includes basic information and imaging mode. The imaging mode of the target imaging device is the same as the imaging mode in the registration information, and the target imaging device is associated with the front-end unit. The basic information of the object is sent to the target imaging device so that the target imaging device can image the object based on the basic information to obtain a medical image; The system receives the medical images sent by the target imaging device and uploads the medical images to the image cloud server.

7. The method according to claim 6, characterized in that, Sending basic information about the object to the target imaging device, including: Receive the data query request sent by the target imaging device; In response to the query request, the first data in the basic information is sent back to the target imaging device, and the first data is used for display by the target imaging device; Receive a data transfer request sent by the target imaging device, the data transfer request being sent by the target imaging device after determining that the object has completed check-in; In response to the data transfer request, the second data in the registration information is sent to the target imaging device.

8. The method according to claim 6, characterized in that, There are multiple objects, and the imaging priority of the first object is higher than that of the second object among the multiple objects; Sending basic information about the object to the target imaging device, including: The basic information of the first object is sent to the target imaging device first.

9. The method according to any one of claims 6 to 8, characterized in that, The method further includes: Receive a notification message sent by the target imaging device, the notification message being sent by the target imaging device after completing the imaging of the object, and the notification message including the completion time of the imaging by the target imaging device, and the object; Based on the notification message, if it is determined that the target imaging device has completed imaging of all imaging objects allocated to the target imaging device, then the state of the target imaging device is determined to be idle; and if it is determined that the target imaging device has not completed imaging of all imaging objects allocated to the target imaging device, then the state of the target imaging device is determined to be busy, wherein all imaging objects include the object. The status of the target imaging device is sent to the image cloud server, and if the status of the target imaging device is idle, the completion time of the target imaging device is sent to the image cloud server.

10. A triage method, characterized in that, Applied to imaging equipment; the method includes: The system receives basic information about an object sent by a front-end server associated with the imaging device. The triage information to which the basic information belongs is generated by the imaging cloud server based on the registration information of the object and sent to the front-end server. The triage information includes the imaging device and the registration information. The registration information includes the basic information and the imaging method. The imaging method of the imaging device is the same as the imaging method in the registration information. Based on the basic information, the object is imaged to obtain a medical image of the object; The medical image is sent to the front-end processor so that the front-end processor can upload the medical image to the image cloud server.

11. The method according to claim 10, characterized in that, Receive basic information about the object sent by the front-end unit associated with the imaging device, including: Send a data query request to the front-end processor, the data query request being used to request the front-end processor to send back the first data in the basic information to the imaging device; Display the first data; After confirming that the object has completed the check-in, a data transfer request is sent to the front-end device. The data transfer request is used to request the front-end device to send back the second data in the basic information to the imaging device.

12. The method according to claim 11, characterized in that, Sending the medical images to the front-end processor includes: A data storage request is sent to the front-end machine, the data storage request carrying the medical image.

13. The method according to claim 11 or 12, characterized in that, The front-end machine is equipped with a DICOM protocol stack; The data query request is a C-FIND request, the data transfer request is a C-MOVE request, and the data storage request is a C-STORE request.

14. An image cloud server, characterized in that, The image cloud server includes: a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the method as described in any one of claims 1-5.

15. A pre-processor, characterized in that, The front-end machine includes: a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the method as described in any one of claims 6-9.

16. An imaging device, characterized in that, The imaging device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, it implements the method as described in any one of claims 10-13.

17. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-13.

18. A triage system, characterized in that, The system includes: The image cloud server as described in claim 14; The front-end processor as described in claim 15; And the imaging device as described in claim 16.

Images