Medical data processing method and device, storage medium and surgical robot

Abstract

The application relates to a medical data processing method and device, a storage medium and a surgical robot. The method comprises the following steps: acquiring version identification information of analysis planning software; determining member information matched with the version identification information from a planning result update file; the planning result update file is used for storing version identification information of each version member information and processing rules corresponding to the member information; determining target member information needing serialization according to the processing rules corresponding to the member information; and determining planning result data matched with the analysis planning software according to a serialization result of the target member information. The medical data processing method provided in the application can quickly and accurately determine the planning result data matched with the analysis planning software from the planning result update file.

Description

Technical Field

[0001] This application relates to the field of medical technology, and in particular to a medical data processing method, apparatus, storage medium, and surgical robot. Background Technology

[0002] Hip surgery planning software can perform preliminary planning based on user data. During the planning process, users can input information such as hospital number, surgical side, surgical procedure, and surgical approach. It automatically extracts markers such as the anterior superior iliac spine, midpoint of the pubic symphysis, center of the acetabulum, center of the femoral head, lesser trochanter protrusion, and upper and lower endpoints of the medullary canal axis. It also allows selection of prosthesis specifications such as the acetabular cup, femoral stem, ball head, and liner. Algorithms are used to mark and process the reamed areas in the user's imaging data, ultimately exporting the planning result file. This planning result file can be imported into other surgical robot software to guide the operation using those robots.

[0003] Generally, software versions undergo continuous iteration, often adding or removing parameters. This results in the final exported planning result file containing different content than before, leading to compatibility issues. For example, after adding, removing, or modifying member information, deserializing the previously serialized file or data can result in errors or serialization failures. Since surgical robot software typically can only parse planning results matching its version, updates prevent the loading of previously completed planning results, impacting subsequent surgical operations. Existing technologies utilize version control for member serialization and deserialization; however, in this process, the surgical robot software may only obtain partial data, such as partial member information, after deserialization, thus affecting subsequent normal business processing flows.

[0004] Therefore, there is an urgent need for a highly accurate medical data processing method in related technologies. Summary of the Invention

[0005] Therefore, it is necessary to provide a medical data processing method, device, storage medium, and surgical robot to address the aforementioned technical problems and solve the problem of incomplete planning result data obtained in the prior art.

[0006] In a first aspect, embodiments of this application provide a medical data processing method, the method comprising:

[0007] Obtain the version identification information of the analytical planning software;

[0008] The member information that matches the version identification information is determined from the planning result update file; the planning result update file is used to store the version identification information of each version member information and the processing rules corresponding to the member information;

[0009] Based on the processing rules corresponding to the member information, determine the target member information that needs to be serialized;

[0010] Based on the serialization result of the target member information, the planning result data that matches the analytical planning software is determined.

[0011] The medical data processing method provided in this application can utilize a planning result update file to store all information from each version iteration of the planning result data, including changed member information and the corresponding processing rules. Thus, after determining the version of the planning result data required by the parsing planning software, the corresponding target member information can be quickly and accurately determined from the planning result update file. Then, based on the serialization result of the target member, it can be determined that the parsing planning software can successfully parse the planning result data, thereby enabling a normal surgical workflow. Furthermore, since the planning result update file stores all the information, the parsed planning result data is complete and sufficient.

[0012] Optionally, in one embodiment of this application, the planning result update file is configured to be determined in the following manner:

[0013] If the member information changes in the planning result data, the changed member information is stored in the planning result update file;

[0014] Based on the type of change, determine the processing rules corresponding to the member information;

[0015] Update the version identifier information of the changed member information.

[0016] Optionally, in one embodiment of this application, determining the planning result data matching the planning software based on the serialization result of the target member information includes:

[0017] Obtain the planning results data from the previous version and the corresponding reference member information;

[0018] Based on the reference member information and the member information, the target member information is determined;

[0019] The previous version of the planning result data is updated based on the serialization result of the target member information to determine the planning result data that matches the parsing planning software.

[0020] Optionally, in one embodiment of this application, the serialization result of the target member information is determined in the following manner:

[0021] Receive parameter values ​​set by the user for the target member information;

[0022] Based on the parameter values, the serialization result of the target member information is determined.

[0023] Optionally, in one embodiment of this application, after determining the target member information based on the reference member information and the member information, the method further includes:

[0024] The target member information is displayed on a visual interface, which provides users with the authority to set the parameter values ​​of the target member information.

[0025] Optionally, in one embodiment of this application, obtaining the version identification information of the analytical planning software includes:

[0026] Load the planning result data using analytical planning software;

[0027] If the analytical planning software fails to load, obtain the version identification information of the analytical planning software.

[0028] Optionally, in one embodiment of this application, determining the target member information to be serialized according to the processing rules corresponding to the member information includes:

[0029] If the processing rule corresponding to the first member information is deletion, the first member information is deleted from the member information to determine the target member information that needs to be serialized.

[0030] Secondly, embodiments of this application also provide a medical data processing device, the device comprising:

[0031] The module for obtaining version identification information is used to obtain the version identification information of the parsing and planning software;

[0032] The member information determination module is used to determine member information that matches the version identification information from the planning result update file; the planning result update file is used to store the version identification information of each version member information and the processing rules corresponding to the member information.

[0033] The target member information determination module is used to determine the target member information that needs to be serialized based on the processing rules corresponding to the member information.

[0034] The planning result data determination module is used to determine the planning result data that matches the analytical planning software based on the serialization result of the target member information.

[0035] Thirdly, embodiments of this application also provide a surgical robot, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of the methods described in the above embodiments.

[0036] Fourthly, embodiments of this application also provide a computer-readable storage medium having computer program instructions stored thereon, which, when executed by a processor, implement the steps of the methods described in the above embodiments. Attached Figure Description

[0037] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0038] Figure 1 This is a schematic diagram of an application scenario provided by an embodiment of this application;

[0039] Figure 2 A flowchart of a medical data processing method provided in one embodiment of this application;

[0040] Figure 3 This is a schematic diagram of a visual interface provided in an embodiment of this application;

[0041] Figure 4 This is a schematic diagram of the module structure of the medical data processing device 105 provided in the embodiments of this application;

[0042] Figure 5 This is a schematic diagram of the module structure of the processing device provided in the embodiments of this application. Detailed Implementation

[0043] To make the objectives, technical solutions, and advantages of this application clearer, the application is described and illustrated below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the application. All other embodiments obtained by those skilled in the art based on the embodiments provided in this application without inventive effort are within the scope of protection of this application. Furthermore, it is understood that although the efforts made in such a development process may be complex and lengthy, for those skilled in the art related to the content disclosed in this application, modifications to design, manufacturing, or production based on the technical content disclosed in this application are merely conventional technical means and should not be construed as insufficient disclosure of the content of this application.

[0044] In this application, the reference to "embodiment" means that a specific feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment that is mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described in this application may be combined with other embodiments without conflict.

[0045] Unless otherwise defined, the technical or scientific terms used in this application shall have the ordinary meaning understood by one of ordinary skill in the art to which this application pertains. The terms "a," "an," "a kind," "the," and similar words used in this application do not indicate quantity limitation and may indicate singular or plural. The terms "comprising," "including," "having," and any variations thereof used in this application are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or device that includes a series of steps or modules (units) is not limited to the listed steps or units, but may also include steps or units not listed, or may include other steps or units inherent to these processes, methods, products, or devices. The terms "connected," "linked," "coupled," and similar words used in this application are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. "A plurality" used in this application means two or more. The terms "first," "second," "third," etc., used in this application are merely to distinguish similar objects and do not represent a specific ordering of objects.

[0046] Furthermore, to better illustrate this application, numerous specific details are provided in the following detailed description. Those skilled in the art should understand that this application can be implemented without certain specific details. In some instances, apparatus, means, elements, and circuits well known to those skilled in the art have not been described in detail in order to highlight the main points of this application.

[0047] To clearly illustrate the technical solutions of the various embodiments of this application, the following describes... Figure 1 One exemplary scenario of an embodiment of this application will be described.

[0048] Please see Figure 1 , Figure 1This is a schematic diagram of an application scenario provided by an embodiment of this application. This application scenario may include a medical acquisition device 101, a client 103, a medical data processing device 105, and a surgical robot 107. The medical acquisition device 101 and the client 103 can communicate to send acquired medical images to the client 103. The medical acquisition device 101 can be an electronic device with data acquisition and data transmission / reception capabilities. For example, the medical acquisition device 101 can be an electronic device capable of acquiring medical images of a target object, such as, but not limited to, computed tomography (CT) equipment, magnetic resonance imaging (MRI) equipment, positron emission tomography (PET) equipment, etc., or it can be a multimodal imaging device composed of a combination of the above-mentioned electronic devices, such as PET-CT equipment, PET-MRI equipment, etc. Correspondingly, the medical images acquired by the medical acquisition device 101 can be computed tomography images, magnetic resonance images, or positron emission tomography images, etc. The target object can be a human or animal body, or a part of the human or animal body's tissues or organs, such as the lungs or stomach. The client 103 can be equipped with surgical planning software. This software can perform surgical planning based on the acquired medical images and the user's medical experience. For example, it can determine the surgical method, surgical procedure, surgical path, etc., and generate planning result data. This planning result data can include target object information, marker point location information, etc. The surgical planning software can be called a Computer-Assisted Surgery Planning (CASP) system, which refers to obtaining surgical information including surgical method, procedure, surgical approach, path, and instrument selection by acquiring images of the lesion site and other relevant data of the target object before surgery, combined with the use of simulation modules and intelligent hardware. The client 103 can communicate with the medical data processing device 105 to send the generated planning result data to the medical data processing device 105. The surgical robot 107 is equipped with parsing planning software, which can parse the corresponding planning result data to obtain the target object information, marker point location information, instrument information, etc. The surgical robot 107 can then perform surgery based on the parsed information, such as biopsy, hip replacement, etc.Since the parsing and planning software in the surgical robot 107 can only parse the planning result data of the corresponding version, and the planning result data is updated irregularly, the medical data processing device 105 can use the medical data processing method provided in any of the following embodiments of this application to process the planning result data input by the client 103 to determine the planning result data that matches the parsing and planning software. Specifically, the version identification information of the parsing and planning software can be obtained first; member information matching the version identification information can be determined from the planning result update file; the planning result update file is used to store the version identification information of each version member information and the processing rules corresponding to the member information; according to the processing rules corresponding to the member information, the target member information that needs to be serialized can be determined; according to the serialization result of the target member information, the planning result data that matches the parsing and planning software can be determined. Afterwards, the medical data processing device 105 can send the planning result data that matches the parsing and planning software to the surgical robot 107, and the surgical robot 107 can perform surgery according to the parsing result of the planning result data.

[0049] It is understood that the medical data processing device 105 can be an electronic device with data processing and data transmission / reception capabilities. The electronic device can be a physical device or a cluster of physical devices, such as a standalone physical server, a server cluster composed of multiple physical servers, or a distributed system. Of course, the electronic device can also be a virtualized cloud device, such as at least one cloud computing device in a cloud computing cluster, or a cloud server providing basic cloud computing services such as cloud databases, cloud services, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms. This application does not limit the form of the electronic device herein. Besides electronic devices, the medical data processing device 105 can also include various forms such as non-volatile computer-readable storage media, computer program products, and chips. As a non-volatile computer-readable storage medium, computer program product, or chip, the medical data processing device 105 can be coupled internally to the surgical robot 107, enabling the surgical robot 107 to determine and parse matching planning result data. The client 103 can be a smart terminal that can run surgical planning software, such as a smartphone, tablet, laptop, desktop computer, handheld computer, mobile internet device (MID), wearable device (e.g., smartwatch, smart bracelet), smart computer, or smart vehicle device.

[0050] The medical data processing method described in this application will be explained in detail below with reference to the accompanying drawings. Figure 2 This is a flowchart illustrating one embodiment of the medical data processing method provided in this application. While this application provides method operation steps as shown in the following embodiments or figures, the method may include more or fewer operation steps based on conventional or non-inventive effort. For steps where there is no logically necessary causal relationship, the execution order of these steps is not limited to the execution order provided in the embodiments of this application. In actual medical data processing or during method execution, the method may be executed in the order shown in the embodiments or figures, or in parallel (e.g., in a parallel processor or multi-threaded processing environment).

[0051] Specifically, one embodiment of the medical data processing method provided in this application is, for example... Figure 2 As shown, the method may include:

[0052] S201: Obtain the version identification information of the analytical planning software.

[0053] In this embodiment, the analysis and planning software can be an application installed in the surgical processing device for analyzing the planning result data, or it can be an application installed in the surgical planning workstation for analyzing the planning result data. The surgical processing device can be the surgical robot 107, or a robotic arm, etc. The surgical robot 107 can include, for example, a laparoscopic surgical robot, an orthopedic surgical robot, a panvascular surgical robot, a natural orifice surgical robot, a percutaneous puncture surgical robot, a neurosurgical robot, etc. The planning result data can be data containing surgical information generated by the surgical planning software. For example, the planning result data can include various types of information, such as target object information, surgical path information, marker point information, process information, etc. The target object information can include relevant information about the target object, such as height, weight, age, and gender. The surgical path information can include the order of organs or tissues traversed during the surgery. For example, in a hysterectomy, different surgical paths can be selected, such as abdominal, laparoscopic, or vaginal. The marker point information varies depending on the type of surgery. For example, in the case of hip joint surgery, the marker point information may include the location information of marker points such as the anterior superior iliac spine, the midpoint of the pubic symphysis, the center of the acetabulum, the center of the femoral head, the lesser trochanter protrusion, and the upper and lower endpoints of the medullary canal axis. Of course, in other embodiments of this application, the analytical planning software can also be integrated into the surgical planning software, for example, as a functional module or a quick application.

[0054] In practical applications, to improve the storage and transmission of planning result data, the planning result data can be serialized. In one embodiment of this application, object serialization methods can be used for data serialization. For example, necessary data in the planning software workflow can be converted into strings and stored in a Digital Imaging and Communications in Medicine (DICOM) file. In one embodiment, the DICOM file can consist of a DICOM file header and a DICOM dataset. The DICOM file header can be used to identify the dataset and may include a 128-byte file preface, a 4-byte DICOM prefix, and file metadata. The dataset may include at least one data element for storing image information. The data element may include a tag, value representation (VR), length, and value field (VF). Based on this, during the serialization process of the planning result data, different data can be stored in different tags so that the corresponding data can be quickly and accurately found in subsequent processing. The deserialization process can involve reading data elements with specified tags from the DICOM file and then converting the string content into numerical values ​​according to the serialization order. It is understood that during the serialization of the planning result data, each type of information is encapsulated using a class. In one embodiment of this application, when the planning result data is in a serialized data format, the parsing planning software can deserialize the received planning result data to determine the various types of information contained within it.

[0055] In this embodiment, the version identification information can be used to uniquely identify the latest version of the planning result data that the parsing and planning software can successfully parse. The version identification information can have various expressions, including at least one of the following: numbers, letters, characters, symbols, etc., typically including, for example, "A", "1.1", "Version 1". In one embodiment of this application, the version identification information of the parsing and planning software can be the total version identification information of the planning result data output by the surgical planning software. For example, the total version identification information can be version 1, version 2, version 3, etc. For example, in one example, when the planning result data output by the surgical planning software is updated, a different total version identification information can be set for each updated planning result data, and the total version identification information can be sent to the parsing and planning software in real time to inform the surgical robot 107 of the version change of the planning result data, thereby enabling the surgical robot 107 to quickly determine the latest version of the planning result data required for the surgery.

[0056] In practical applications, changes in surgical plans or patient information, such as the addition of new information, can cause version updates of the planning result data. If the updated planning result data is not sent to the surgical robot 107, the planning result data parsed by the parsing planning software in the surgical robot 107 may not be the latest planning result data, or the version of the parsed planning result data may differ from the version of the planning result data output by the surgical planning software, resulting in version incompatibility and affecting subsequent surgical operations. Therefore, based on this, in one embodiment of this application, obtaining the version identification information of the parsing planning software includes:

[0057] S301: Load planning result data using analytical planning software;

[0058] S303: In the event that the planning software fails to load, obtain the version identification information of the planning software.

[0059] In this embodiment of the application, in practical applications, the parsing and planning software can generally only parse planning result data that matches the version information it receives. For example, in one example, after parsing the stored planning result data, the parsing and planning software determines that the included member information is member A and member B. However, the latest planning result data output by the surgical planning software adds member C. Thus, the processing device performing the surgery will lack the deserialization result of member C and cannot load the surgical procedure normally. In this case, the processing device can obtain the version identifier information of the parsing and planning software, and then determine the planning result data that matches the version identifier information, so as to carry out the normal processing flow of subsequent business. Of course, it is understood that when the parsing and planning software is loaded normally, the normal surgical procedure can be carried out according to the information contained in the planning result data.

[0060] S203: Determine the member information that matches the version identification information from the planning result update file; the planning result update file is used to store the version identification information of each version member information and the processing rules corresponding to the member information.

[0061] In this embodiment, to record the update results of each planning result data, such as deleting or adding information about a member, a planning result update file can be constructed to store the update information of the planning result data. In this way, the parsing planning software can find the planning result data matching the version identifier information from the planning result update file. The member can be an object contained in various types of information. For example, if the type information is patient information, the member can be gender, height, weight, etc.; and if the type information is marker information, the member can be marker 1, marker 2, marker 3, etc. In one embodiment of this application, the planning result update file can take various forms, such as graphical or tabular formats. In one embodiment of this application, the planning result update file can be used to store member information that has changed in each version compared to the previous version, and update the version identifier information corresponding to the changed members. Specifically, the planning result update file is set to be determined in the following manner:

[0062] S401: If the member information changes in the planning result data, the changed member information is stored in the planning result update file;

[0063] S403: Determine the processing rules corresponding to the member information based on the type of change;

[0064] S405: Update the version identifier information of the changed member information.

[0065] In this embodiment, the change type of member information can include adding members, deleting members, changing member attributes, etc. For example, if the member information changes to adding member A, the information of member A can be stored in the planning result update file. Based on this, since a new member has been added to the planning result data, meaning the version of the planning result data has been updated, the overall version identifier information of the planning result data containing member A can be set to version 2, i.e., member A has been added compared to version 1. In one embodiment of this application, to facilitate subsequent determination of whether the changed member should be serialized, corresponding processing rules can be set for the changed member according to the change type. These processing rules can include adding, changing, deleting, etc. The following is a specific example illustrating the construction of the planning result update file. For example, as shown in Table 1 below, the planning result update file stores three versions of planning result data, such as version 1, version 2, and version 3. As can be seen, version 1 of the planning results data added members A and B; version 2 of the planning results data added members C and D compared to version 1, so the version identifier information of members C and D can be updated, for example, set to version 2; version 3 of the planning results data deleted member D compared to version 2, so the version identifier information of member D can be set to version 3.

[0066] Table 1. Planning Results Update Document Table

[0067]

[0068] In this embodiment, after determining the planning result update file, member information matching the version identifier information can be determined from the planning result update file based on the version identifier information. The matching can include the member information having a version identifier information that is less than or equal to the version identifier information of the parsing planning software. For example, in one example, if the version identifier information is version 3, the matching members can be determined to be member A, member B, member C, and member D. Through the above embodiments, the planning result update file can be used to record comprehensive and accurate changes in planning result data, facilitating the parsing planning software to find all the required member information from the planning result update file.

[0069] S205: Determine the target member information that needs to be serialized according to the processing rules corresponding to the member information.

[0070] In this embodiment, the planning result update file stores not only the member information contained in each version of the planning result data, but also the processing rules corresponding to each member. Therefore, based on this, member information that meets the serialization conditions can be further determined. Specifically, when the processing rule is for addition or modification, the corresponding member can be determined to be a member that needs to be serialized; while when the processing rule is for deletion, no further processing is needed for that member, i.e., that member is not a member that needs to be serialized. Specifically, determining the target member information that needs to be serialized based on the processing rules corresponding to the member information can include:

[0071] S401: If the processing rule corresponding to the first member information is deletion, delete the first member information from the member information to determine the target member information that needs to be serialized.

[0072] In this embodiment, after determining the member information matching the version identifier information using the above embodiments, the processing rules corresponding to each member information can be determined based on the updated file according to the planning results. If the processing rule is determined to be deletion, the member can be deleted from multiple member information sets to determine the target member information. For example, in one example, when the matching member information is determined to be member A, member B, member C, and member D, since the processing rule corresponding to member D is deletion, the corresponding target member information should be member A, member B, and member C. Through the above embodiments, more accurate target member information can be determined through two screenings. Specifically, the first screening is based on the version identifier information of each member, and the second screening is based on the processing rules of each member. This can prevent abnormal errors from occurring, thus avoiding disruption to the normal operation of the surgery.

[0073] S207: Based on the serialization result of the target member information, determine the planning result data that matches the analytical planning software.

[0074] In this embodiment, after determining the target member information using the above embodiments, the target member information can be serialized and stored sequentially in the various tags of the DICOM file to determine the planning result data that matches the parsing planning software, i.e., the planning result data that can be successfully parsed. In one embodiment of this application, all target member information can be serialized to determine the planning result data. Of course, to improve processing efficiency and save computational costs, the planning result data can also be determined based on the planning result data of the previous version received by the processing device and the serialization results of some target member information. Specifically, in one embodiment of this application, determining the planning result data that matches the parsing planning software based on the serialization results of the target member information includes:

[0075] S501: Obtain the planning result data from the previous version and the corresponding reference member information;

[0076] S503: Determine the target member information based on the reference member information and the member information;

[0077] S505: Update the previous version of the planning result data based on the serialization result of the target member information to determine the planning result data that matches the parsing planning software.

[0078] In this embodiment, reference member information contained in the previous version of the planning result data is obtained from the planning result update file. For example, if the version identifier information is version 2, the previous version of the planning result data can be determined to be the planning result data of version 1. Then, the reference member information contained in the previous version of the planning result data can be determined to be member A and member B. In one embodiment of this application, since the previous version of the planning result data already contains member A and member B, member C and member D, which were added in version 2, can be added to version 1 to obtain the target member information as member A, member B, member C, and member D. Then, based on the serialization results of the four members, the planning result data matching the parsing planning software can be determined, thereby improving processing efficiency while parsing the planning result data normally.

[0079] In this embodiment, a planning result update file can be used to store all information about each version iteration of the planning result data, including changed member information and the corresponding processing rules. Thus, after determining the version of the planning result data required by the parsing planning software, the corresponding target member information can be quickly and accurately determined from the planning result update file. Then, based on the serialization result of the target member, it can be determined that the parsing planning software can successfully parse the planning result data, thereby enabling the normal surgical workflow. Furthermore, since the planning result update file stores all the information, the parsed planning result data is complete and sufficient.

[0080] In practical applications, users can assign values ​​to different target member information based on their medical experience and actual surgical needs. Then, the serialization result of the target member information can be determined based on the assigned values. Specifically, the serialization result of the target member information is determined in the following manner:

[0081] S601: Receive the parameter value set by the user for the target member information;

[0082] S603: Based on the parameter values, determine the serialization result of the target member information.

[0083] In this embodiment, the user can set corresponding parameter values ​​for the target member information through button input, voice input, control panel input, etc. on the processing device. For example, the parameter value for the gender member in the patient information can be set to male, and the height member can be set to 170cm, etc. The processing device can then serialize the parameter values ​​of each target member information to obtain the serialized result of the target member information. The user can be a doctor, nurse, or other relevant personnel with medical experience. For example, in one example, user A can set the parameter values ​​of the target member through voice input. The surgical robot can then obtain the serialized result of the target member information, parse the serialized result, and perform the corresponding surgery according to the surgical procedure.

[0084] It is understood that, in one embodiment of this application, parameter values ​​can be set for target member information that is deficient compared to the previous version of the planning result data, or corresponding parameter values ​​can be set for all target member information. This application does not impose any restrictions on this.

[0085] In practical applications, to facilitate users' understanding of the target member's situation and to allow them to set parameter values ​​for the target member's information, a visual interface can be provided. Specifically, in one embodiment of this application, after determining the target member information based on the reference member information and the member information, the process further includes:

[0086] S701: Display the target member information on a visualization interface, which provides the user with the authority to set the parameter values ​​of the target member information.

[0087] In this embodiment, the visual interface may include multiple data input boxes, each labeled with its corresponding function. Users can then fill in the corresponding parameter values ​​into the data input boxes as needed. The visual interface may also include controls to enable interaction between the user and the interface, such as a "OK" button. Specifically, in one example, such as... Figure 3 As shown, the visualization interface 300 can be used to provide users with the permission to input parameter values ​​such as gender and age of target members.

[0088] Finally, it should be noted that any variations or substitutions 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. Furthermore, without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, product, or apparatus that includes said element, nor does it affect the combination of multiple said elements.

[0089] The above text describes in detail the medical data processing method provided in this application. The following section will refer to the appendix... Figure 4 The medical data processing apparatus 105 provided according to this application may include:

[0090] The version identification information acquisition module 1051 is used to acquire the version identification information of the parsing planning software;

[0091] The member information determination module 1053 is used to determine member information that matches the version identification information from the planning result update file; the planning result update file is used to store the version identification information of each version member information and the processing rules corresponding to the member information.

[0092] The target member information determination module 1055 is used to determine the target member information that needs to be serialized according to the processing rules corresponding to the member information;

[0093] The planning result data determination module 1057 is used to determine the planning result data that matches the analytical planning software based on the serialization result of the target member information.

[0094] Optionally, in one embodiment of this application, the planning result update file is configured to be determined in the following manner:

[0095] If the member information changes in the planning result data, the changed member information is stored in the planning result update file;

[0096] Based on the type of change, determine the processing rules corresponding to the member information;

[0097] Update the version identifier information of the changed member information.

[0098] Optionally, in one embodiment of this application, determining the planning result data matching the planning software based on the serialization result of the target member information includes:

[0099] Obtain the planning results data from the previous version and the corresponding reference member information;

[0100] Based on the reference member information and the member information, the target member information is determined;

[0101] The previous version of the planning result data is updated based on the serialization result of the target member information to determine the planning result data that matches the parsing planning software.

[0102] Optionally, in one embodiment of this application, the serialization result of the target member information is determined in the following manner:

[0103] Receive parameter values ​​set by the user for the target member information;

[0104] Based on the parameter values, the serialization result of the target member information is determined.

[0105] Optionally, in one embodiment of this application, after determining the target member information based on the reference member information and the member information, the method further includes:

[0106] The target member information is displayed on a visual interface, which provides users with the authority to set the parameter values ​​of the target member information.

[0107] Optionally, in one embodiment of this application, obtaining the version identification information of the analytical planning software includes:

[0108] Load the planning result data using analytical planning software;

[0109] If the analytical planning software fails to load, obtain the version identification information of the analytical planning software.

[0110] Optionally, in one embodiment of this application, determining the target member information to be serialized according to the processing rules corresponding to the member information includes:

[0111] If the processing rule corresponding to the first member information is deletion, the first member information is deleted from the member information to determine the target member information that needs to be serialized.

[0112] The medical data processing apparatus 105 according to the embodiments of this application can be used to execute the methods described in the embodiments of this application. The above and other operations and / or functions of each module in the medical data processing apparatus 105 are respectively for implementing the corresponding processes of the methods provided in the above embodiments. For the sake of brevity, they will not be described again here.

[0113] It should also be noted that the embodiments described above are merely illustrative. The modules described as separate components may or may not be physically separate, and the components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. In addition, in the accompanying drawings of the device embodiments provided in this application, the connection relationship between modules indicates that they have a communication connection, which can be implemented as one or more communication buses or signal lines.

[0114] This application also provides a surgical robot, including a memory and a processor, wherein the memory stores computer program instructions, and the processor is configured to run the computer program instructions to perform the methods described in the various embodiments above.

[0115] This application also provides a computer-readable storage medium storing computer program instructions thereon, which, when executed by a processor, implement the steps of the methods described in the above embodiments.

[0116] A computer-readable storage medium can be a tangible device capable of holding and storing instructions for use by an instruction execution device. A computer-readable storage medium can be, for example, but not limited to, an electrical storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination thereof. More specific examples (a non-exhaustive list) of computer-readable storage media include: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), electrically programmable read-only memory (EPROM or flash memory), static random-access memory (SRAM), compact disc read-only memory (CD-ROM), digital video disc (DVD), memory sticks, floppy disks, mechanical encoding devices, such as punch cards or recessed protrusions storing instructions thereon, and any suitable combination thereof.

[0117] The computer program instructions described herein can be downloaded from a computer-readable storage medium to various computing / processing devices, or downloaded via a network, such as the Internet, local area network, wide area network, and / or wireless network, to an external computer or external storage device. The network may include copper cables, fiber optic cables, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives the computer program instructions from the network and forwards them to a computer-readable storage medium within the respective computing / processing device.

[0118] The computer program instructions used to perform the operations of this application may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Smalltalk, C++, etc., and conventional procedural programming languages ​​such as "C" or similar languages. The computer program instructions may be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer may be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or may be connected to an external computer (e.g., via the Internet using an Internet service provider). In some embodiments, electronic circuits, such as programmable logic circuits, field-programmable gate arrays (FPGAs), or programmable logic arrays (PLAs), are personalized by utilizing state information from computer program instructions. These electronic circuits can execute computer program instructions to implement various aspects of this application.

[0119] Various aspects of this application are described herein with reference to flowchart illustrations and / or block diagrams of methods and apparatus according to embodiments of this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, as well as combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions.

[0120] These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed by the processor of the computer or other programmable data processing apparatus, they create means for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram. These computer program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner; thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

[0121] Computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other equipment to cause a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other equipment to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other equipment to perform the functions / actions specified in one or more blocks of a flowchart and / or block diagram.

[0122] This application also provides a processing device, including a memory and a processor, wherein the memory stores computer program instructions, and the processor is configured to execute the computer program instructions to perform the methods described in the above embodiments.

[0123] The processing device can be a physical device or a cluster of physical devices, or it can be a virtualized cloud device, such as at least one cloud computing device in a cloud computing cluster. For ease of understanding, this application illustrates the structure of the processing device as an independent physical device.

[0124] like Figure 5 As shown, the processing device 500 includes a processor and a memory for storing computer program instructions for the processor; wherein the processor is configured to implement the above-described means when executing the computer program instructions. The processing device 500 includes a memory 501, a processor 503, a bus 505, and a communication interface 507. The memory 501, processor 503, and communication interface 507 communicate via the bus 505. The bus 505 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, Figure 5 The symbol is represented by only one thick line, but this does not indicate that there is only one bus or one type of bus. Communication interface 507 is used for communication with external devices.

[0125] The processor 503 can be a central processing unit (CPU). The memory 501 can include volatile memory, such as random access memory (RAM). The memory 501 can also include non-volatile memory, such as read-only memory (ROM), flash memory, HDD or SSD, etc.

[0126] Those skilled in the art will understand that Figure 5 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0127] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, and methods according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of an instruction containing one or more executable instructions for implementing a specified logical function. In some alternative implementations, the functions marked in the blocks may occur in a different order than those shown in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved.

[0128] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the invention patent. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.

Claims

1. A medical data processing method, characterized in that, The method includes: Obtain the version identification information of the analytical planning software; The member information that matches the version identification information is determined from the planning result update file; the planning result update file is used to store the version identification information of each version member information and the processing rules corresponding to the member information; Based on the processing rules corresponding to the member information, determine the target member information that needs to be serialized; Based on the serialization result of the target member information, determine the planning result data that matches the analytical planning software; The planning result update file is configured to be determined in the following manner: If the member information changes in the planning result data, the changed member information is stored in the planning result update file; Based on the type of change, determine the processing rules corresponding to the member information; Update the version identifier information of the changed member information; The step of determining the planning result data that matches the analytical planning software based on the serialization result of the target member information includes: Obtain the planning results data from the previous version and the corresponding reference member information; Based on the reference member information and the member information, the target member information is determined; The previous version of the planning result data is updated based on the serialization result of the target member information to determine the planning result data that matches the parsing planning software.

2. The method according to claim 1, characterized in that, The serialization result of the target member information is determined in the following manner: Receive parameter values ​​set by the user for the target member information; Based on the parameter values, the serialization result of the target member information is determined.

3. The method according to claim 1, characterized in that, After determining the target member information based on the reference member information and the member information, the method further includes: The target member information is displayed on a visual interface, which provides users with the authority to set the parameter values ​​of the target member information.

4. The method according to claim 1, characterized in that, The version identification information of the analytical planning software includes: Load the planning result data using analytical planning software; If the analytical planning software fails to load, obtain the version identification information of the analytical planning software.

5. The method according to claim 1, characterized in that, The step of determining the target member information to be serialized according to the processing rules corresponding to the member information includes: If the processing rule corresponding to the first member information is deletion, the first member information is deleted from the member information to determine the target member information that needs to be serialized.

6. A medical data processing device, characterized in that, The device includes: The module for obtaining version identification information is used to obtain the version identification information of the parsing and planning software; A member information determination module is used to determine member information that matches the version identifier information from the planning result update file. The planning result update file is used to store the version identifier information of each version member information and the processing rules corresponding to the member information. The planning result update file is configured to be determined in the following manner: when member information changes in the planning result data, the changed member information is stored in the planning result update file; the processing rules corresponding to the member information are determined according to the type of change; and the version identifier information of the changed member information is updated. The target member information determination module is used to determine the target member information that needs to be serialized based on the processing rules corresponding to the member information. The planning result data determination module is used to determine planning result data that matches the parsing planning software based on the serialization result of the target member information. The determination of planning result data that matches the parsing planning software based on the serialization result of the target member information includes: acquiring the planning result data of the previous version and the corresponding reference member information; determining target member information based on the reference member information and the member information; and updating the planning result data of the previous version based on the serialization result of the target member information to determine the planning result data that matches the parsing planning software.

7. A surgical robot, comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 5.

8. A computer-readable storage medium having computer program instructions stored thereon, characterized in that, When the computer program instructions are executed by the processor, they implement the steps of the method according to any one of claims 1 to 5.

Images