Multi-source health service data processing method and device, equipment and medium

Abstract

The invention relates to the field of data processing, and discloses a multi-source health service data processing method and device, equipment and a medium. The method comprises the following steps: acquiring health record data of a full life cycle of target residents in a target community from different medical service systems, and splitting health service items in the health record data according to service item dimensions to obtain standard data items and mapping data items; for each target resident, performing fusion processing on different types of health service items based on the standard data item to generate an individual service management rule; and generating a service task according to the individual service management regulation, and writing back the service data of the service task to the original medical service system according to the mapping data item when the service task is completed. According to the method, health record data of different medical service systems in a target community are integrated, a full-life-cycle health service management regulation is generated for each resident, and unified planning and execution of resident health service tasks are achieved.

Description

Technical Field

[0001] This application relates to the field of data processing, and in particular to a method, apparatus, device, and medium for processing multi-source health service data. Background Technology

[0002] Currently, community doctors provide residents with over ten health services, including basic public health services and supplementary services, each with standardized service procedures. However, with urbanization, residents move more frequently between different areas. When residents have multiple key health issues or move between multiple areas, their health records often rely on multiple, unconnected service systems within each region for processing. Consequently, community doctors often cannot fully grasp residents' health status or provide one-stop health services based on the provided content. Furthermore, because the data from multiple healthcare systems (such as community healthcare, hospitals, and public health institutions) are independent, residents may need to repeatedly perform similar health service items across different systems, lacking a unified task management mechanism. Summary of the Invention

[0003] In view of this, in order to solve the problems existing in the prior art, this application provides a method, apparatus, device and medium for processing multi-source health service data.

[0004] Firstly, this application provides a method for processing multi-source health service data, including: Health record data of the target residents in the target community throughout their entire life cycle is obtained from different medical service systems. The health service items in the health record data are then broken down according to the service item dimension to obtain standard data items and mapping data items. The mapping data items are used to represent the mapping relationship between the standard data items and each of the medical service systems. For each target resident, the different types of health service items are integrated based on the standard data items to generate an individual service management procedure; Service tasks are generated according to the individual service management procedure, and service reminders are pushed to community doctors and residents of the target community through a message queue. When the service task is completed, the service data of the service task is written back to the original medical service system according to the mapped data items.

[0005] In an optional implementation, the step of splitting the health service items in the health record data according to the service item dimension to obtain standard data items and mapped data items includes: Extract project data for different health service items from the health record data of the target residents; The project data is split according to the service project dimension to obtain multiple project data items; Several project data items of the same type are merged to obtain standard data items; the standard data items include disease items and symptom information. The mapping relationship between the standard data items and each of the medical service systems is constructed to obtain the mapped data items.

[0006] In an optional implementation, the step of integrating different types of health service items based on the standard data items to generate individual service management procedures includes: The population type of each target resident is determined. Based on the management procedures corresponding to the population type and the standard data items, the different types of health service items for each target resident are merged and sorted according to the expected execution time to generate individual service management procedures. Each individual service management procedure contains multiple health service items that the target resident needs to perform.

[0007] In an optional implementation, the step of merging and sorting the different types of health service items for each target resident according to their expected execution time includes: If it is determined that the estimated execution time of the target health service item is not a fixed time, and a time adjustment request is received, then the estimated execution time of the target health service item will be adjusted. The different types of health service items for each target resident are merged and sorted according to the adjusted expected execution time.

[0008] In an optional implementation, generating service tasks according to the individual service management procedure includes: For each target resident, the health service items in the individual service management procedure are merged according to the expected execution time to generate task execution queues under different management cycles. Each task execution queue contains multiple service tasks, and a service task includes multiple health service items corresponding to the same expected execution time. After merging the various health service items within the individual service management procedure into multiple service tasks according to their expected execution times, the method further includes: For a single service task, service content text is generated based on the standard data items of each of the health service items; the service content text is used to generate service data for the service task.

[0009] In an optional implementation, the method further includes: For each target resident, obtain the task execution queue for the current management cycle, the task execution queue containing multiple service tasks to be executed; Each service task is processed according to its task type and execution status; wherein, the task type includes cyclical tasks and single-cycle tasks; If it is determined that the service task is a cyclical task and its execution status in the current management cycle is completed, then the service task is removed from the task execution queue and added to the task execution queue of the next management cycle. If it is determined that the service task is a single-cycle task and its execution status within the current management cycle is completed, then the service task is removed from the task execution queue.

[0010] In an optional implementation, writing the service data of the service task back to the original medical service system according to the mapped data items includes: The service data of the service task is split according to the standard data items to obtain multiple service form information; The information in each service form is written back to the original medical service system according to the mapped data items.

[0011] Secondly, this application provides a multi-source health service data processing device, comprising: The standardization module is used to acquire full-life-cycle health record data of target residents in the target community from different medical service systems, and to break down the health service items in the health record data according to the service item dimension to obtain standard data items and mapping data items; the mapping data items are used to represent the mapping relationship between the standard data items and each of the medical service systems. The data fusion module is used to fuse different types of health service items based on the standard data items for each target resident, and generate individual service management procedures. The data processing module is used to generate service tasks according to the individual service management procedure, push service reminders to community doctors and residents of the target community through a message queue, and write back the service data of the service task to the original medical service system according to the mapped data items when the service task is completed.

[0012] Thirdly, this application provides a computer device, the computer device including a processor and a memory, the memory storing a computer program, and the processor executing the computer program to implement the aforementioned multi-source health service data processing method.

[0013] Fourthly, this application provides a computer storage medium storing a computer program, which, when executed on a processor, implements the aforementioned multi-source health service data processing method.

[0014] The embodiments of this application have the following beneficial effects: This application provides a multi-source health service data processing method. By integrating health record data from different medical service systems in a target community, it generates a full-lifecycle health service management procedure for each resident. This enables unified planning and execution of residents' health service tasks, and upon completion of the task, the service data is written back to the original system, ensuring data synchronization and integrity. While solving the data silo problem between multiple medical service systems, it can also generate individual service management procedures, improving personalized service capabilities. Furthermore, the data can be written back to the original system after service completion, ensuring data consistency and real-time performance. This allows community doctors to fully understand the implementation of residents' health services and provide timely reminders and interventions. Attached Figure Description

[0015] To more clearly illustrate the technical solutions of this application, the accompanying drawings used in the embodiments will be briefly described below. It should be understood that the following drawings only show some embodiments of this application and therefore should not be considered as a limitation on the scope of protection of this application. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0016] Figure 1 A flowchart illustrating a multi-source health service data processing method in an embodiment of this application is shown. Figure 2 This paper illustrates another flowchart of the multi-source health service data processing method in an embodiment of this application. Figure 3 A schematic diagram of a multi-source health service data processing device is shown in an embodiment of this application. Detailed Implementation

[0017] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments.

[0018] The components of the embodiments of this application described and illustrated in the accompanying drawings can be arranged and designed in a variety of different configurations. Therefore, the following detailed description of the embodiments of this application provided in the drawings is not intended to limit the scope of the claimed application, but merely to illustrate selected embodiments of the application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.

[0019] In the following, the terms “comprising,” “having,” and their cognates, which may be used in various embodiments of this application, are intended only to indicate a particular feature, number, step, operation, element, component, or combination thereof, and should not be construed as excluding, firstly, the presence of one or more other features, numbers, steps, operations, elements, components, or combinations thereof, or adding the possibility of one or more features, numbers, steps, operations, elements, components, or combinations thereof.

[0020] Furthermore, the terms "first," "second," and "third" are used only to distinguish descriptions and should not be interpreted as indicating or implying relative importance.

[0021] Unless otherwise specified, all terms used herein (including technical and scientific terms) shall have the same meaning as commonly understood by one of ordinary skill in the art to which the various embodiments of this application pertain. Terms (such as those defined in commonly used dictionaries) shall be interpreted as having the same meaning as in their contextual meaning in the relevant technical field and shall not be construed as having an idealized or overly formal meaning, unless clearly defined in the various embodiments of this application.

[0022] The following detailed description of some embodiments of this application is provided in conjunction with the accompanying drawings. Unless otherwise specified, the following embodiments and features can be combined with each other.

[0023] This application provides a multi-source health service data processing method. This application integrates health data from multiple medical service systems to generate a personal health service management procedure, so as to uniformly manage all health service data of a resident. After the corresponding health service is completed, the health service data can be synchronized to multiple medical service systems, thereby effectively monitoring the health data of a resident throughout their entire life cycle and tracking the resident's service execution status in a timely manner.

[0024] This method can be implemented based on a health data management platform with data integration capabilities, a terminal device or a cloud server, or a processor or processing module built into the device. The specific execution device used can be set according to actual needs, and this embodiment does not limit it.

[0025] like Figure 1 As shown, the method includes the following steps: S110: Obtain health record data of the target residents in the target community throughout their entire life cycle from different medical service systems, and break down the health service items in the health record data according to the service item dimension to obtain standard data items and mapped data items.

[0026] This approach integrates massive amounts of multi-source data from multiple healthcare service systems, including health record data covering the entire life cycle of target residents within the target community, to avoid data silos. Optionally, these multiple healthcare service systems include community healthcare service systems, institutional healthcare service systems, and hospital healthcare service systems that provide authorized access to data. The health record data includes health service data from various basic public health services. The target residents include all residents within the community or specific types of residents (such as the elderly, children, etc.). The type and number of target residents can be set according to actual needs, and this embodiment is not limited in this regard.

[0027] Then, the health record data from different medical service systems are standardized to integrate the data from multiple medical service systems. Subsequently, based on the standardized processing, multi-business integrated service tasks can be formed to support community doctors in fully mastering the residents' health service procedures and facilitating the provision of comprehensive health services to residents.

[0028] This process involves extracting project data for different health services from the health records of target residents; splitting each project data according to the service project dimension to obtain multiple project data items; merging several project data items of the same type to obtain standard data items; and constructing a mapping relationship between the standard data items and various medical service systems to obtain mapped data items. The mapped data items represent the mapping relationship between the standard data items and various medical service systems. These standard data items include, but are not limited to, disease items and their symptom information, past medical history, family history, and auxiliary examinations. The disease items include, but are not limited to, hypertension, diabetes, hyperlipidemia, and coronary heart disease. The symptom information refers to the corresponding symptoms of various diseases, such as hypertension symptoms (including but not limited to dizziness, headache, shortness of breath, palpitations, and chest tightness), and diabetes symptoms (including but not limited to polydipsia, polyphagia, polyuria, and significant weight loss).

[0029] It is understandable that, for the health record data of each target resident, it is first broken down into multiple data items of the smallest data unit, and then data items of the same type are integrated to form standard data items. For example, if a disease item is used as the standard data item, then symptom information, medical records, medication records, treatment records, etc., belonging to the same disease can be summarized into data for that disease item from the health record data of each target resident; or, if a single disease symptom is used as the standard data item, then multiple disease items of each target resident with that disease symptom can be summarized into data for that disease symptom; or, if a unique code such as a resident's ID number or medical record number is used as the standard data item, then all disease items and their disease symptom information corresponding to that resident can be summarized into data for that unique code. The standard data items and their splitting rules can be set according to actual needs, and this embodiment does not limit this.

[0030] In one example, when splitting health record data, this embodiment can perform word segmentation processing on the health record data based on a pre-trained natural language model. The natural language model can be trained by selecting the appropriate natural language algorithm or large language model according to actual needs, without limitation, such as using a Transformer-based natural language model.

[0031] For example, Table 1 below shows examples of symptoms of hypertension.

[0032] Table 1

[0033] Table 2 below shows examples of symptoms of diabetes.

[0034] Table 2

[0035] Based on the steps in S110 above, using a single disease symptom as the standard data item, the disease symptom information of each target resident regarding the above two diseases (hypertension and diabetes) is summarized, resulting in Table 3 below.

[0036] Table 3

[0037] S120, for each target resident, integrates different types of health service items based on standard data items to generate individual service management procedures.

[0038] Based on the standard data items, the population type of each target resident is first determined. According to the management procedures and standard data items corresponding to the population type, the different types of health service items for each target resident are merged and sorted according to the expected execution time to generate individual service management procedures. Each individual service management procedure includes multiple health service items that the target resident needs to perform and the expected execution time.

[0039] It is understandable that, for each target resident, the different types of health services required by that resident are integrated according to their expected execution time to form an individual service management procedure. Each health service item in this individual service management procedure is sorted according to its corresponding expected execution time, which makes it easier for residents and community doctors to query and promptly execute the health services required at each time point. Furthermore, this individual service management procedure summarizes all the health services required by the target resident, avoiding omissions or confusion, and facilitating the unified management of the target resident's health service data.

[0040] For example, for the children population, services such as children's health care and immunization will be integrated according to the expected execution time; for the elderly population, services such as hypertension monitoring and diabetes monitoring will be integrated according to the expected execution time.

[0041] As a further example, Table 4 below shows the service management procedures for child health care services and immunization services, sorted by their expected execution time.

[0042] Table 4

[0043] Table 5 below shows the individual service management procedures obtained by integrating child health care services and immunization services according to the expected execution time.

[0044] Table 5

[0045] As an optional implementation method, if the execution time of some health service items is not fixed (i.e., the execution time is not limited), the estimated execution time of the health service items can be flexibly adjusted accordingly before generating the personal service management procedure.

[0046] Furthermore, if it is determined that the estimated execution time of the target health service item is not a fixed time, and a time adjustment request is received, the estimated execution time of the target health service item is adjusted; the different types of health service items for each target resident are then merged and sorted according to the adjusted estimated execution time. This time adjustment request can be triggered by the target resident or by the processor or corresponding processing module when generating the personal service management procedure. If triggered by the target resident, the estimated execution time of the health service item is changed to the time point indicated by the target resident; if triggered by the processor or processing module, adjustments are made based on a preset time adjustment strategy and the estimated execution times of each health service item. This time adjustment strategy is set according to actual needs; for example, the strategy could be to evenly distribute the estimated execution time of each health service item to different time points.

[0047] S130 generates service tasks according to the individual service management procedure, pushes service reminders to community doctors and residents in the target community through a message queue, and writes the service data of the service task back to the original medical service system according to the mapped data items when the service task is completed.

[0048] For each target resident, the various health service items within the individual service management procedure are integrated according to the expected execution time to generate task execution queues under different management cycles; each task execution queue contains multiple service tasks, and a service task includes multiple health service items corresponding to the same expected execution time.

[0049] It is understandable that different service tasks are generated for each health service item within the individual service management procedure, and the estimated execution time of the health service item is the execution time of the service task. Specifically, for the same target resident, multiple service tasks can be added to the task execution queue in order of execution time, and then the service tasks in the queue are executed sequentially according to the task execution queue.

[0050] For example, a health service project for hypertension monitoring can be generated into a service task for hypertension monitoring (i.e., a blood pressure measurement task). Subsequently, based on the execution time of this service task, a reminder message can be sent to community doctors and target residents to indicate that the hypertension monitoring task (i.e., blood pressure measurement) needs to be performed when the execution time arrives.

[0051] Furthermore, each service task can include multiple health service items, that is, multiple health service items that need to be executed at the same execution time, thereby realizing real-time monitoring and management of multiple health service items, which makes it easier for community doctors and residents to execute multiple health service items in a timely manner and avoid omissions.

[0052] Furthermore, based on this task queue and the established message reminder mechanism, reminder information can be generated for each service task in the task queue according to its execution time, and the reminder information can be pushed to the target residents and community doctors, so that community doctors and target residents can perform each service task in a timely manner.

[0053] As an optional implementation, after merging the various health service items within the individual service management procedure into multiple service tasks according to the expected execution time, this embodiment can generate service content text for a single service task based on the standard data items of each health service item; wherein, the service content text is used to generate service data for the service task.

[0054] This embodiment can generate service content text based on standard data items and pre-set templates. This service content text includes, but is not limited to, follow-up log forms for community doctors' home visits and forms for residents' visits to community hospitals, which are used to record the real-time implementation of health service projects. The format or style of this service content text, template content, etc., can be specifically set according to actual needs.

[0055] For example, Table 6 below is a follow-up log form for residents with hypertension in a typical scenario.

[0056] Table 6

[0057] Table 7 below shows the follow-up log form for residents with diabetes in a typical scenario.

[0058] Table 7

[0059] Obviously, if a resident suffers from both hypertension and diabetes, two different follow-up log forms need to be issued and recorded to meet the follow-up needs of multiple diseases.

[0060] Furthermore, Table 8 below illustrates the follow-up log form generated based on standard data items and a pre-set template using the multi-source health service data processing method of this application (only the follow-up log form integrating hypertension and diabetes is used as an example for explanation). It is evident that this embodiment simplifies the process of generating the follow-up log form and can comprehensively generate a follow-up log form based on the specific health status of each resident, thereby facilitating the recording and management of each resident's follow-up data.

[0061] Table 8

[0062] In one embodiment, after each service task is completed, the service data of the service task is written back to the corresponding original medical service system according to the mapped data items.

[0063] In other words, this embodiment can write the service data back to the original medical service system after the service task is completed, so that each service system can synchronize the service data, avoid duplicate services, and improve residents' service satisfaction.

[0064] The service data for the service tasks is split into multiple service form information items according to standard data items; each service form information is then written back to the original medical service system according to the mapped data items.

[0065] In other words, based on the mapping relationship between each standard data item and the original medical service system, the service data corresponding to the standard data item is written back to the original medical service system to ensure the synchronization of service data in each medical service system.

[0066] As an optional implementation, in the process of sequentially processing service tasks, the embodiments of this application, such as Figure 2 As shown, the process includes the following steps: S210: For each target resident, obtain the task execution queue within the current management cycle, and process each service task according to its task type and execution status.

[0067] The task execution queue contains multiple service tasks that need to be executed; the task types include cyclical tasks and single-cycle tasks.

[0068] S220, if it is determined that the execution status of any service task in the current management cycle is incomplete, then continue to monitor the execution status of the service task, and issue corresponding reminder information when the service task is about to arrive or when the estimated execution time of the service task arrives, according to the preset reminder strategy.

[0069] The reminder strategy includes reminder methods corresponding to different reminder time periods. The specific reminder strategy can be set according to actual needs, and this embodiment does not limit it.

[0070] S230, if it is determined that the execution status of any service task in the current management cycle is completed, then the service task is removed from the task queue corresponding to the current management cycle, and the task type of the service task is further determined.

[0071] If the service task is a cyclical task, it will be removed from the current task queue and added to the task execution queue of the next management cycle, so as to perform execution monitoring of the service task in the next management cycle.

[0072] Conversely, if the service task is determined to be a single-cycle task, it is removed directly from the current task execution queue.

[0073] In this embodiment, the service data of each service task is saved in a timely manner after each service task is completed, so as to trace the service process later.

[0074] In one embodiment, this embodiment also includes an exception handling mechanism to trigger in case of abnormal situations during the execution of a service task. Under the management of this exception handling mechanism, the service task is regenerated. That is, if an abnormal situation such as missing service data occurs during the execution of a service task, the service task can be regenerated based on this exception handling mechanism. The exception handling mechanism or exception handling strategy can be set according to actual needs, and this embodiment is not limited to it.

[0075] In one embodiment, this embodiment can also analyze the health fluctuations of target residents based on the execution status and service data of each service task, so as to output health monitoring results and health management suggestions, thereby realizing health management of residents.

[0076] In addition, the health service management decisions or strategies of the target community can be adjusted by combining the performance of service tasks and service data of multiple target residents, so as to improve the reliability of health service management in the target community and enhance residents' satisfaction.

[0077] This embodiment integrates health record data from different medical service systems in the target community to generate a full life-cycle health service management procedure for each resident, thereby achieving unified planning and execution of residents' health service tasks. After the task is completed, the service data is written back to the original system to ensure data synchronization and integrity.

[0078] like Figure 3 As shown in the illustration, this application also provides a multi-source health service data processing device, which includes: The standardization module 310 is used to acquire the full life cycle health record data of the target residents in the target community from different medical service systems, and to split the health service items in the health record data according to the service item dimension to obtain standard data items and mapping data items; the mapping data items are used to represent the mapping relationship between the standard data items and each of the medical service systems. Data fusion module 320 is used to fuse different types of health service items based on the standard data items for each target resident and generate individual service management procedures. The data processing module 330 is used to generate service tasks according to the individual service management procedure, push service reminders to community doctors and residents of the target community through a message queue, and write back the service data of the service task to the original medical service system according to the mapped data items when the service task is completed.

[0079] It is understood that the multi-source health service data processing device in this embodiment corresponds to the multi-source health service data processing method in the above embodiments. The options in the above embodiments are also applicable to this embodiment, so they will not be described again here.

[0080] This application also provides a computer device, exemplary of which includes a processor and a memory, wherein the memory stores a computer program, and the processor executes the computer program to enable the computer device to perform the functions of the various modules in the above-described multi-source health service data processing method or the above-described multi-source health service data processing apparatus.

[0081] The processor can be an integrated circuit chip with signal processing capabilities. The processor can be a general-purpose processor, including at least one of a Central Processing Unit (CPU), Graphics Processing Unit (GPU), Network Processor (NP), Digital Signal Processor (DSP), Application-Specific Integrated Circuit (ASIC), Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The general-purpose processor can be a microprocessor or any conventional processor, capable of implementing or executing the methods, steps, and logic block diagrams disclosed in the embodiments of this application.

[0082] The memory can be, but is not limited to, Random Access Memory (RAM), Read Only Memory (ROM), Programmable Read-Only Memory (PROM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), etc. The memory is used to store computer programs, and the processor can execute the computer programs accordingly after receiving execution instructions.

[0083] This application also provides a computer storage medium for storing the computer program used in the aforementioned computer device. The computer storage medium can be a readable storage medium, a non-volatile storage medium, or a volatile storage medium. For example, the computer storage medium may include, but is not limited to, various media capable of storing program code, such as a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0084] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can also be implemented in other ways. The apparatus embodiments described above are merely illustrative. For example, the flowcharts and block diagrams in the accompanying drawings show the architecture, functionality, and operation of possible implementations of apparatus, methods, and computer program products 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 code containing one or more executable instructions for implementing a specified logical function. It should also be noted that, in alternative implementations, the functions marked in the blocks may occur in a different order than those marked 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. It should also be noted that each block in the block diagram and / or flowchart, and combinations of blocks in the block diagram and / or flowchart, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0085] In addition, the functional modules or units in the various embodiments of this application can be integrated together to form an independent part, or each module can exist independently, or two or more modules can be integrated to form an independent part.

[0086] If the aforementioned functions are implemented as software functional modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a smartphone, personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application.

[0087] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes 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 scope of protection of this application.

Claims

1. A method for processing multi-source health service data, characterized in that, include: Health record data of the target residents in the target community throughout their entire life cycle is obtained from different medical service systems. The health service items in the health record data are then broken down according to the service item dimension to obtain standard data items and mapping data items. The mapping data items are used to represent the mapping relationship between the standard data items and each of the medical service systems. For each target resident, the different types of health service items are integrated based on the standard data items to generate an individual service management procedure; Service tasks are generated according to the individual service management procedure, and service reminders are pushed to community doctors and residents of the target community through a message queue. When the service task is completed, the service data of the service task is written back to the original medical service system according to the mapped data items.

2. The multi-source health service data processing method according to claim 1, characterized in that, The health service items in the health record data are split according to the service item dimension to obtain standard data items and mapped data items, including: Extract project data for different health service items from the health record data of the target residents; The project data is split according to the service project dimension to obtain multiple project data items; Several project data items of the same type are merged to obtain standard data items; the standard data items include disease items and symptom information. The mapping relationship between the standard data items and each of the medical service systems is constructed to obtain the mapped data items.

3. The multi-source health service data processing method according to claim 1, characterized in that, The process of integrating different types of health service items based on the standard data items to generate individual service management procedures includes: The population type of each target resident is determined. Based on the management procedures corresponding to the population type and the standard data items, the different types of health service items for each target resident are merged and sorted according to the expected execution time to generate individual service management procedures. Each individual service management procedure contains multiple health service items that each target resident needs to perform.

4. The multi-source health service data processing method according to claim 3, characterized in that, The process of integrating and sorting the different types of health service items for each target resident according to their expected execution time includes: If it is determined that the estimated execution time of the target health service item is not a fixed time, and a time adjustment request is received, then the estimated execution time of the target health service item will be adjusted. The different types of health service items for each target resident are merged and sorted according to the adjusted expected execution time.

5. The multi-source health service data processing method according to claim 1, characterized in that, The process of generating service tasks according to the individual service management procedure includes: For each target resident, the health service items in the individual service management procedure are merged according to the expected execution time to generate task execution queues under different management cycles. Each task execution queue contains multiple service tasks, and a service task includes multiple health service items corresponding to the same expected execution time. After merging the various health service items within the individual service management procedure into multiple service tasks according to their expected execution times, the method further includes: For a single service task, service content text is generated based on the standard data items of each of the health service items; the service content text is used to generate service data for the service task.

6. The multi-source health service data processing method according to claim 1 or 5, characterized in that, The method further includes: For each target resident, obtain the task execution queue for the current management cycle, the task execution queue containing multiple service tasks to be executed; Each service task is processed according to its task type and execution status; wherein, the task type includes cyclical tasks and single-cycle tasks; If it is determined that the service task is a cyclical task and its execution status in the current management cycle is completed, then the service task is removed from the task execution queue and added to the task execution queue of the next management cycle. If it is determined that the service task is a single-cycle task and its execution status within the current management cycle is completed, then the service task is removed from the task execution queue.

7. The multi-source health service data processing method according to claim 1, characterized in that, The step of writing back the service data of the service task to the original medical service system according to the mapped data items includes: The service data of the service task is split according to the standard data items to obtain multiple service form information; The information in each service form is written back to the original medical service system according to the mapped data items.

8. A multi-source health service data processing device, characterized in that, include: The standardization module is used to acquire full-life-cycle health record data of target residents in the target community from different medical service systems, and to break down the health service items in the health record data according to the service item dimension to obtain standard data items and mapping data items; the mapping data items are used to represent the mapping relationship between the standard data items and each of the medical service systems. The data fusion module is used to fuse different types of health service items based on the standard data items for each target resident, and generate individual service management procedures. The data processing module is used to generate service tasks according to the individual service management procedure, push service reminders to community doctors and residents of the target community through a message queue, and write back the service data of the service task to the original medical service system according to the mapped data items when the service task is completed.

9. A computer device, characterized in that, The computer device includes a processor and a memory, the memory storing a computer program, and the processor executing the computer program to implement the multi-source health service data processing method according to any one of claims 1-7.

10. A computer storage medium, characterized in that, It stores a computer program that, when executed on a processor, implements the multi-source health service data processing method according to any one of claims 1-7.

Images