Medical information registration management method, device, medium, and apparatus

Abstract

The present application provides a medical information registration management method, device, medium and equipment, which is applied to a medical information processing platform, a management background end with modification authority is used to add or modify a disease data registration template, and is synchronized to a doctor user end, specifically, a data synchronization request is received, the data synchronization request includes a data association request for requesting to synchronize the same kind of disease item data to multiple doctor user ends; a disease data registration template is created in response to the data synchronization request; and the disease data registration template is sent to the doctor user end, so that the doctor user end of the corresponding pathological item can use a more suitable disease data registration template to register information. In addition, the detection results returned by the laboratory end are stored in the inspection registration template sent by the doctor user end, and the data of the doctor user end and the laboratory end are integrated.

Description

Technical Field

[0001] This invention relates to the field of medical information digitization technology, and in particular to methods, devices, media and equipment for medical information registration and management. Background Technology

[0002] Real case data for various diseases are of great value for applications in many fields such as disease research, clinical trials, and efficacy tracking.

[0003] Previously, case data was primarily recorded and managed using paper forms or Excel spreadsheets. This data included clinical information, imaging examination information, medical testing information, and medication and treatment information, resulting in a wide variety of data from diverse sources, making management time-consuming and labor-intensive. Furthermore, third-party medical testing institutions also faced the problem of time-consuming and labor-intensive data management when entering information from externally sent specimens. Based on the aforementioned scenarios involving hospitals and third-party medical testing institutions, the separation of information between the two entities caused significant inconvenience for integrated data management.

[0004] In addition, some current case registration systems are customized for specific diseases based on customer needs, and their adaptability is not wide.

[0005] Therefore, finding a suitable method for managing case data is a technical problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0006] In view of the shortcomings of the prior art, the purpose of this invention is to at least solve one of the technical problems existing in the prior art, and to provide a medical information registration and management method, device, medium and equipment that can synchronize disease data registration templates to the doctor user terminal, thereby solving the problem of low adaptability of disease data registration templates.

[0007] In a first aspect, to achieve the above objectives, the present invention provides a medical information registration and management method, applied to a medical information processing platform, the medical information processing platform including a management backend and doctor user terminals; the method includes: receiving a data synchronization request, the data synchronization request including a data association request to synchronize data of the same disease items with multiple doctor user terminals; responding to the data synchronization request and creating a disease data registration template; and sending the disease data registration template to the doctor user terminals.

[0008] Furthermore, the receipt of the data synchronization request, which includes a data association request to synchronize data of similar disease items with multiple doctor user terminals, includes: receiving a request to create a pathology item sent through the management backend, responding to the request to create a pathology item, establishing a pathology item, which includes a digestive tract pathology item, a respiratory tract pathology item, and a thyroid pathology item, and the similar disease item is one of the pathology items; and granting corresponding permissions to the doctor user terminals associated with the pathology item.

[0009] Furthermore, the step of responding to the data synchronization request and creating a disease data registration template includes: the disease data registration template includes a case registration template, a follow-up registration template, and a sample submission registration template.

[0010] Furthermore, it also includes: configuring a registration module in the disease data registration template, and configuring several fields to be registered in the registration module; receiving a request from the management backend to modify the target disease data registration template, wherein the request to modify the target disease data registration template includes a request to modify fields to be registered in the target disease data registration template, a request to add fields to be registered in the target disease data registration template, and a request to delete fields to be registered in the target disease data registration template; publishing the modified target disease data registration template as a target disease data registration correction template; and when a first instruction associated with the target disease data registration template is received from the doctor user terminal, the first instruction... The system stores target disease data registration information for which fields to be registered are to be filled in. If it is detected that the fields to be registered in the first instruction are inconsistent with the fields to be registered in the target disease data registration correction template, then the fields to be registered in the first instruction that are consistent with the fields to be registered in the target disease data registration correction template are selected, and the target disease data registration information for which fields to be registered are stored in the first instruction is imported into the corresponding fields to be registered in the target disease data registration correction template. Fields to be registered in the first instruction that do not exist in the target disease data registration correction template are deleted, and newly added fields to be registered in the target disease data registration correction template are added. Target disease data registration correction information is generated.

[0011] Furthermore, the medical information processing platform also includes a laboratory end and a logistics end; the method further includes: when a request is received from the testing logistics end for an identifier bound to a submitted sample, if disease data registration information associated with the identifier is detected based on the identifier, then a page of the disease data registration information associated with the identifier is automatically popped up on the laboratory end.

[0012] Furthermore, the configuration of the registration module in the disease data registration template, and the configuration of several fields to be registered in the registration module, includes: configuring the registration module in the test submission registration template, the registration module including a hospital information module, a patient information module, and a clinical information module, the fields to be registered in the hospital information module including the submitting hospital, the submitting doctor, and the department, and the fields to be registered in the patient information module including the patient's name, contact information, and the patient's age.

[0013] Furthermore, the method also includes: generating a report based on the target submission registration information recorded in the target submission registration template, and sending the report back; and importing the test results into the registration field in the corresponding target submission registration template.

[0014] Secondly, the present invention provides a medical information registration and management device, applied to a medical information processing platform, the medical information processing platform including a management backend, a doctor user terminal, a laboratory terminal, and a logistics terminal; the device includes: a synchronization module, which receives data synchronization requests, the data synchronization requests including data association requests to synchronize similar disease item data with multiple doctor user terminals; a creation module, which responds to the data synchronization requests and creates a disease data registration template; and a sending module, which sends the disease data registration template to the doctor user terminal.

[0015] Thirdly, the present invention provides a computer-readable storage medium storing a computer program, which, when executed by a processor, causes the processor to perform the steps of the medical information registration and management method described in any of the preceding claims.

[0016] Fourthly, the present invention provides a computer device including a memory and a processor, the memory storing a computer program, which, when executed by the processor, causes the processor to perform the steps of the medical information registration and management method described in any of the preceding claims.

[0017] The medical information registration and management method, apparatus, medium, and equipment provided by this invention are applied to a medical information processing platform. They allow for the addition or modification of disease data registration templates via a management backend with modification permissions, and synchronization with doctor user terminals. Specifically, this involves receiving data synchronization requests, including data association requests to synchronize similar disease item data with multiple doctor user terminals; responding to the data synchronization requests by creating disease data registration templates; and sending the disease data registration templates to doctor user terminals, enabling doctor user terminals for corresponding pathology items to use more suitable disease data registration templates to register information. Additionally, test results returned from the laboratory are stored in the submission registration template sent by the doctor user terminal, integrating data from both the doctor user terminal and the laboratory. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, 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 the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 This is a flowchart illustrating a medical information registration and management method in one embodiment;

[0020] Figure 2 This is a flowchart illustrating a medical information registration and management method in one embodiment;

[0021] Figure 3 This is a schematic diagram of a medical information registration and management device in one embodiment;

[0022] Figure 4 This is a schematic diagram of the structure of a computer device in one embodiment. Detailed Implementation

[0023] It should be understood that the specific embodiments described herein are merely illustrative of this application and are not intended to limit this application.

[0024] The technical solutions in the embodiments of this application will now be explained with reference to the accompanying drawings.

[0025] Clearly and completely described, it is obvious that the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0026] It should be noted that the terms "comprising," "including," and "having," and any variations thereof, in the specification, claims, and accompanying drawings of this application, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses. Terms such as "first" and "second" in the claims, specification, and accompanying drawings of this application, as well as relational terms, are used merely to distinguish one entity / operation / object from another entity / operation / object, and do not necessarily require or imply any such actual relationship or order between these entities / operations / objects.

[0027] In this document, the term "embodiment" means that a particular 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 throughout the specification does not necessarily refer to the same embodiment, nor is it a mutually exclusive, independent, or alternative embodiment. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0028] Digitalization of medical information is an important means of managing case data. Real case data for various diseases is of great value for applications in disease research, clinical trials, and efficacy tracking. Therefore, the clinical demand for the collection and management of case data is very strong. In the past, case data was mostly recorded and managed in the form of paper forms or Excel spreadsheets. However, multi-dimensional data, such as clinical information, imaging examination information, medical test information, and medication and treatment information, need to be manually entered from different sources. For example, clinical information is entered by clinicians, and medical test information is entered by laboratories. Integrating this information is a huge workload.

[0029] In addition, while there are existing registration systems on the market that are customized for specific diseases, the development and maintenance costs of such systems are relatively high.

[0030] Therefore, a case registration system that uses information technology to address this pain point has emerged.

[0031] Example 1

[0032] See Figure 1 As shown, this embodiment provides a medical information registration and management method, applied to a medical information processing platform, which includes a management backend and doctor user terminals. The method includes: receiving a data synchronization request, the data synchronization request including a data association request to synchronize data of the same disease items with multiple doctor user terminals; responding to the data synchronization request and creating a disease data registration template; and sending the disease data registration template to the doctor user terminals.

[0033] It should be noted that, for reference Figure 2 As shown, the management backend first creates a pathology project, and then creates multiple disease data registration templates based on the pathology project. Doctors in the pathology project can select the disease data registration template of their project to register information.

[0034] It should be noted that the steps to create a disease data registration template include: embedding an H5 page for managing disease data registration templates in the management backend, customizing the required disease data registration template according to the fields to be registered, publishing the required disease data registration template, and synchronizing it to the doctor's user end.

[0035] The problem this embodiment aims to solve is that recording and managing case data using traditional paper forms or Excel spreadsheets is time-consuming and labor-intensive. Furthermore, existing pathology registration templates require customization for specific diseases, limiting their use to these customized systems. If a different pathology registration template is needed, further customization is required, leading to high development and maintenance costs. Therefore, a medical information registration and management system with customizable configuration templates for different diseases is needed.

[0036] According to the solution provided in this embodiment, disease data registration templates are added or modified through a management backend with modification permissions, and then synchronized to the doctor's user end. Specifically, this involves receiving a data synchronization request, which includes a data association request to synchronize data on similar disease items with multiple doctor user ends; responding to the data synchronization request by creating a disease data registration template; and sending the disease data registration template to the doctor's user end, enabling the doctor's user end for the corresponding pathology item to use a more suitable disease data registration template to register information. Additionally, the test results returned from the laboratory are stored in the submission registration template sent by the doctor's user end, integrating the data from the doctor's user end and the laboratory end.

[0037] Example 2

[0038] This embodiment provides a further solution, wherein receiving the data synchronization request includes a data association request to synchronize data of similar disease items with multiple doctor user terminals. Prior to this, the process includes: receiving a request to create a pathology item sent through the management backend; responding to the request to create a pathology item; establishing a pathology item, which includes digestive tract pathology items, respiratory tract pathology items, and thyroid pathology items, and the similar disease item is one type of the pathology item; and granting corresponding permissions to the doctor user terminals associated with the pathology item.

[0039] It should be noted that the pathology items mentioned are not limited to common disease categories, such as digestive tract and respiratory tract diseases. Pathology items can also be included in health testing.

[0040] It is worth noting that all licensed research centers have a need to collect pathological data. If the pathological data is not organized in a standardized manner, it will require a significant investment of manpower and resources, and will be inconvenient for researchers to use and analyze the data. This is the problem that this embodiment aims to further solve. According to the solution provided in this embodiment, pathological projects are created based on the research center, and disease data registration templates are created within the corresponding pathological projects. One pathological project corresponds to one disease data registration template, or one pathological project corresponds to multiple disease data registration templates. Doctors belonging to the pathological project can select the required disease data registration template to enter, register, save, and submit information. In addition, one doctor's account can join multiple pathological projects, and this solution supports multi-user, multi-center, and multi-template registration.

[0041] See Figure 2 As shown, the step of responding to the data synchronization request and creating a disease data registration template includes: the disease data registration template includes a case registration template, a follow-up registration template, and a sample submission registration template.

[0042] It should be noted that, taking the kidney pathology project as an example, the doctor's client for the kidney pathology project selects a case registration template to register case information, and then selects a kidney submission registration template based on the case information. The kidney submission registration template includes ultrasound examination and pathological slide examination. Different submission registration templates require different examination items.

[0043] Example 3

[0044] This embodiment provides a medical information registration and management method, further comprising: configuring a registration module in a disease data registration template, configuring several fields to be registered in the registration module; receiving a request from a management backend to modify a target disease data registration template, wherein the request includes a request to modify fields to be registered in the target disease data registration template, a request to add fields to be registered in the target disease data registration template, and a request to delete fields to be registered in the target disease data registration template; publishing the modified target disease data registration template as a target disease data registration correction template; and when a first instruction associated with the target disease data registration template is received from a doctor user terminal... The first instruction stores target disease data registration information for which fields to be registered are to be filled in. If it is detected that the fields to be registered in the first instruction are inconsistent with the fields to be registered in the target disease data registration correction template, then the fields to be registered in the first instruction that are consistent with the fields to be registered in the target disease data registration correction template are selected, and the target disease data registration information for which fields to be registered are stored in the first instruction is imported into the corresponding fields to be registered in the target disease data registration correction template. Fields to be registered in the first instruction that do not exist in the target disease data registration correction template are deleted, and newly added fields to be registered in the target disease data registration correction template are added. Target disease data registration correction information is generated.

[0045] It should be noted that the disease data registration template provided in this application can be modified after publication. However, the publication or modification of the disease data registration template is carried out by a management backend with corresponding permissions. This management backend includes a main management backend and sub-management backends. A management backend with corresponding permissions means that, within a medical information registration management system with multiple pathology projects, the main management backend has the permission to publish or modify the disease data registration template for all pathology projects, while a sub-management backend has the permission to modify the disease data registration template for its respective pathology project. This hierarchical and permission-based system ensures that different pathology projects can operate within the same medical information registration management system without interfering with each other.

[0046] It should be noted that the disease data registration template contains multiple registration modules, and each module contains multiple fields to be registered. The types of these fields include plain text, single-line text input, multi-line text input, number input, date input, single selection, multiple selection, dropdown selection, image upload, and file upload; basically meeting the types of case data. Furthermore, each field type has validation rules. The content entered into these fields is checked against the validation rules corresponding to the field type. For example, the validation rules include: numerical range, decimal places, and phone number length; this ensures the accuracy of the entered pathological data and plays a role in data quality control. Additionally, the fields to be registered can be set to be either required or not.

[0047] It is worth noting that the management backend can modify the published disease data registration templates and adjust them in real time according to specific circumstances in order to adapt to more scenarios that require more suitable disease data registration templates.

[0048] The problem to be solved in this embodiment is the synchronization of disease data registration templates. For example, in a specific scenario, when a doctor's client registers case information using a disease data registration template, the management backend simultaneously modifies the disease data registration template used by the doctor's client. That is, when the doctor's client selects a disease data registration template to register, the management backend modifies the disease data registration template and publishes it, and when the doctor's client saves the information registered using the disease data registration template, the registered information needs to be synchronized to the latest published disease data registration template.

[0049] According to the solution proposed in this embodiment, a suitable disease data registration template can be customized according to the pathology project, and the management backend with the necessary permissions can publish or modify the disease data registration template. The modified target disease data registration correction template is synchronously rendered to the doctor's user end, and the information increment registered by the doctor's user end during the modification of the disease data registration template in the management backend is synchronized to the modified target disease data registration correction template.

[0050] Example 4

[0051] This embodiment provides a further solution.

[0052] See Figure 2 As shown, the medical information processing platform also includes a laboratory end and a logistics end; the method further includes: when a request is received from the testing logistics end for an identifier bound to a submitted sample, if disease data registration information associated with the identifier is detected based on the identifier, then a page of the disease data registration information associated with the identifier is automatically popped up on the laboratory end.

[0053] It should be noted that the disease data registration template includes a case registration template, a follow-up registration template, and a sample submission registration template. This embodiment uses the sample submission registration template as an example. The doctor fills out the sample submission registration template based on the case details and completes the sample submission request form within the template. The request form records the required laboratory tests. The doctor collects the case sample according to the request form, and each sample is assigned an identifier. When the laboratory receives a sample, it checks if the corresponding request form exists in the testing system. If it does, the request form automatically pops up on the laboratory's front-end page for easy viewing and testing.

[0054] The process of configuring a registration module in the disease data registration template, and configuring several fields to be registered in the registration module, includes: configuring a registration module in the test submission registration template, the registration module including a hospital information module, a patient information module, and a clinical information module, the fields to be registered in the hospital information module including the submitting hospital, the submitting doctor, and the department, and the fields to be registered in the patient information module including the patient's name, contact information, and the patient's age.

[0055] The medical information registration and management method also includes: generating a report based on the target submission registration information recorded in the target submission registration template after the laboratory test results are completed, and sending the report back; and importing the test results into the fields to be registered in the corresponding target submission registration template.

[0056] It should be noted that the laboratory completes the testing based on the submitted samples, sends back the report, and imports the test results into the pending registration field of the corresponding submission registration template, so that doctors can easily view the test results of the cases in the submission registration template; in addition, the generated report facilitates the subsequent receipt of the cases.

[0057] It should be noted that the test results returned by the laboratory include positive / negative results and digital pathology slides. Doctors can view a global view of the digital pathology slides through a specific editor on their mobile devices. Additionally, pathology users can view the report via a WeChat official account, significantly reducing the waiting time for receiving the report.

[0058] According to the solution provided in this embodiment, disease data registration templates for multiple pathology projects can be managed through a single system. Simultaneously, it integrates information exchange between the management backend, doctor user interface, logistics system, and laboratory system. This not only solves the problem of inconvenient information integration when using traditional registration methods but also significantly improves report generation time, bringing great convenience to users. Furthermore, the system collects case data in a unified format, and the exported data is standardized and compliant. The original case data can be directly used for various downstream statistical analyses, eliminating the need for classification, organization, and extraction of pathology data, thus facilitating pathology management.

[0059] Example 5

[0060] See Figure 3 As shown, this embodiment provides a medical information registration and management device applied to a medical information processing platform, which includes a management backend, doctor user terminals, laboratory terminals, and a logistics terminal. The device includes: a synchronization module for receiving data synchronization requests, which include data association requests to synchronize similar disease data with multiple doctor user terminals; a creation module for responding to the data synchronization requests and creating a disease data registration template; and a sending module for sending the disease data registration template to the doctor user terminals.

[0061] Example 6

[0062] This embodiment provides a computer-readable storage medium storing a computer program, which, when executed by a processor, causes the processor to perform the steps of the medical information registration and management method described in any of the above embodiments.

[0063] Example 7

[0064] See Figure 4 As shown, this embodiment provides a computer device, including a memory and a processor. The memory stores a computer program, and when the computer program is executed by the processor, the processor performs the steps of the medical information registration and management method described in any of the above embodiments.

[0065] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments described above. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and RAMbus dynamic RAM (RDRAM), etc.

[0066] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. 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 method for medical information registration and management, characterized in that, It is applied to a medical information processing platform, which includes a management backend and a doctor user interface; The method includes: Receive a data synchronization request, which includes a data association request to synchronize data on similar disease items with multiple doctor user terminals; In response to the data synchronization request, a disease data registration template is created; Send the disease data registration template to the doctor's user terminal; Also includes: Configure the registration module in the disease data registration template, and configure several fields to be registered in the registration module; Receive a request from the management backend to modify the target disease data registration template. The request to modify the target disease data registration template includes a request to modify a field to be registered in the target disease data registration template, a request to add a field to be registered in the target disease data registration template, and a request to delete a field to be registered in the target disease data registration template. The revised target disease data registration template will be published as the target disease data registration correction template. When a first instruction is received from the doctor's user terminal to save the data registration template associated with the target disease, the first instruction stores the target disease registration information to be filled in the fields to be registered. If it is detected that the field to be registered in the first instruction is inconsistent with the field to be registered in the target disease data registration correction template; Then, the fields to be registered that are consistent with the target disease data registration correction template in the first instruction are selected, and the target disease registration information stored in the first instruction and filled into the fields to be registered is imported into the corresponding fields to be registered in the target disease data registration correction template. Delete the fields to be registered that do not exist in the target disease data registration correction template in the first instruction, and add the newly added fields to be registered in the target disease data registration correction template; Generate corrected information for the target disease registry.

2. The medical information registration and management method according to claim 1, characterized in that, The receiving of the data synchronization request includes a data association request to synchronize data on similar disease items with multiple doctor user terminals, which previously included: Receive a request to create a pathology project sent through the management backend, respond to the request to create a pathology project, and create a pathology project. The pathology project includes a digestive tract pathology project, a respiratory tract pathology project, and a thyroid pathology project. The same type of disease project is one of the pathology projects. Grant appropriate permissions to physician users associated with pathology projects.

3. The medical information registration and management method according to claim 2, characterized in that, The response to the data synchronization request, creating a disease data registration template, includes: The disease data registration templates include case registration templates, follow-up registration templates, and sample submission registration templates.

4. The medical information registration and management method according to claim 3, characterized in that, The medical information processing platform also includes a laboratory end and a logistics end; The method further includes: When a request is received from the testing logistics end regarding the identifier bound to the submitted sample, if disease data registration information associated with the identifier is detected based on the identifier, a page of disease data registration information associated with the identifier will automatically pop up on the laboratory end.

5. The medical information registration and management method according to claim 4, characterized in that, The process involves configuring a registration module within the disease data registration template, and configuring several fields to be registered within the registration module, including: The registration module is configured in the sample submission registration template. The registration module includes a hospital information module, a patient information module, and a clinical information module. The fields to be registered in the hospital information module include the submitting hospital, the submitting doctor, and the department. The fields to be registered in the patient information module include the patient's name, contact information, and the patient's age.

6. The medical information registration and management method according to claim 5, characterized in that, The method further includes: The laboratory test results are used to generate a report based on the target test registration information recorded in the target test registration template, and the report is then sent back. Import the test results into the fields to be registered in the corresponding target submission registration template.

7. A medical information registration and management device, applied to a medical information processing platform, characterized in that: The medical information processing platform for use in applying any one of claims 1 to 6 includes a management backend, a doctor user end, a laboratory end, and a logistics end; The device includes: The synchronization module receives data synchronization requests, which include data association requests to synchronize similar disease data with multiple doctor user terminals. Create a module that responds to the data synchronization request and creates a disease data registration template; The sending module sends the disease data registration template to the doctor's user terminal.

8. A computer-readable storage medium, characterized in that, The system contains a computer program that, when executed by a processor, causes the processor to perform the steps of the medical information registration and management method as described in any one of claims 1 to 6.

9. A computer device, characterized in that, It includes a memory and a processor, the memory storing a computer program that, when executed by the processor, causes the processor to perform the steps of the medical information registration and management method as described in any one of claims 1 to 6.

Images