Memory-based patient master index fast matching method, device and equipment

Abstract

The application relates to the field of medical information technology and provides a patient master index fast matching method, device and equipment based on memory, which comprises the following steps: creating a list container for storing patient master index data in the memory, storing historical patient master index data into the list container; traversing the list container to store the historical patient master index data in the list container into a preset nested Map container in the memory; obtaining a target field in patient medical record data to be matched, which is the same as a matching rule field name; performing matching and searching for a target key with a value of the target field in a target inner container corresponding to the target field according to the value of the target field, and extracting a target value corresponding to the target key; calculating the intersection of the target values, and taking target historical patient master index data with coordinates in the list container as patient master index data of the patient medical record data to be matched. The application can effectively improve the master index matching and query efficiency.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of medical information technology, and in particular to a memory-based patient master index fast matching method, device and equipment. BACKGROUND

[0002] With the continuous advancement of regional medical center construction, the construction of regional medical information platform, the establishment of national health records, and the realization of resident health record sharing and medical information resource sharing have become an important development direction of medical informatization. To achieve this goal, it is necessary to integrate and summarize all patient medical record data in the region. Since the algorithms and formats of patient indexes in various medical institutions are not consistent, when summarizing patient medical record data, it is necessary to recalculate and match the medical record data of the same patient in different medical institutions, so as to ensure the effectiveness and integrity of patient medical record data.

[0003] The patient master index system on the market is usually applied in daily business of medical institutions. The patient master index matching in daily business has the characteristics of discrete matching time and small matching data volume, so the matching efficiency is rarely considered at the beginning of system design.

[0004] However, the patient master index matching in the data integration and summarization process has the characteristics of centralized matching and large data volume, so how to improve the matching efficiency in the data integration and summarization process has become a technical problem to be solved. SUMMARY

[0005] In view of the above problems, the present application is proposed to provide a memory-based patient master index fast matching method, device and equipment to overcome the above problems.

[0006] In one aspect of the present application, a memory-based patient master index fast matching method is provided, which comprises:

[0007] creating a first list container for storing patient master index data in memory, storing historical patient master index data into the first list container, each historical patient master index data comprising a patient master index serial number and a plurality of patient identity information fields;

[0008] traversing the first list container to store the historical patient main index data in the first list container to a preset nested Map container in the memory, the nested Map container comprising an outer container and an inner container, the key of the outer container being a preset matching rule field name of the main index matching model, the matching rule field being a field used to identify patient identity information, the value corresponding to each key of the outer container being an inner container, the key of the inner container being a field value of the matching rule field corresponding to the key of the outer container in the historical patient main index data, and the value corresponding to each key of the inner container being a coordinate set recorded in the container list with the same value as the key of the inner container in the historical patient main index data;

[0009] obtaining target fields in the patient medical record data to be matched, the target fields being the same as the matching rule field names of the main index matching model;

[0010] determining target inner containers corresponding to each target field, and performing matching in the respective target inner containers according to the values of the target fields to find target keys with the value of the current target field, and extracting target values corresponding to each target key;

[0011] pointing to the target historical patient main index data in the first list container in the intersection of the coordinates of each target value as the patient main index data of the patient medical record data to be matched.

[0012] Further, the method further comprises:

[0013] previously constructing the main index matching model, the main index matching model comprising matching rule fields used for patient matching, setting a matching threshold for the main index matching model and setting a weight for each matching rule field, and adding the weights of the fields in the patient medical record data that are the same as the matching rule field names when matching the patients, and determining patient matching if the weight sum is greater than the matching threshold, and determining no matching if the weight sum is less than the matching threshold.

[0014] Further, the obtaining of the target fields in the patient medical record data to be matched, the target fields being the same as the matching rule field names of the main index matching model, comprises:

[0015] obtaining target fields in the patient medical record data to be matched, the target fields being the same as the matching rule field names of the main index matching model;

[0016] arranging and combining each target field to obtain a combination mode with a field weight sum greater than the matching threshold.

[0017] Further, the determining of the target inner containers corresponding to each target field comprises:

[0018] According to the target field contained in each combination mode, the target inner container corresponding to each target field under the current combination mode is taken out in the nested Map container;

[0019] The target historical patient master index data pointed to by the coordinates in the intersection of each target value in the first list container is taken as the patient master index data of the patient medical record data to be matched.

[0020] The coordinate set of each target value extracted under all combination modes is taken intersection, and the target historical patient master index data pointed to by the coordinates in the intersection in the first list container is taken as the patient master index data of the patient medical record data to be matched.

[0021] Further, the method further comprises:

[0022] If the intersection of each target value is empty, it is determined that there is no patient master index data matched with the patient medical record data to be matched, and a new patient master index serial number is generated for the patient medical record data to be matched;

[0023] The obtained new patient master index serial number is combined with the patient basic information field in the patient medical record data to be matched to serve as the patient master index data of the patient medical record data to be matched, and the patient master index data is added to the first list container.

[0024] Further, after taking the target historical patient master index data pointed to by the coordinates in the intersection in the first list container as the patient master index data of the patient medical record data to be matched, the method further comprises:

[0025] The patient basic information non-empty field value in the patient medical record data to be matched is overwritten on the corresponding field of the target historical patient master index data in the first list container.

[0026] Further, the method further comprises:

[0027] According to the patient master index data of the patient medical record data to be matched in the first list container, the storage record of the nested Map container is updated.

[0028] Further, the method further comprises:

[0029] The patient master index data of the patient medical record data to be matched is stored in a preset second list container, and the second list container is used to store the newly matched patient master index data;

[0030] When the second list container reaches a preset data length, all the patient master index data stored in the second list container is batch saved into a preset database.

[0031] Another aspect of the present application provides a memory-based patient master index fast matching device, which comprises functional modules for implementing the memory-based patient master index fast matching method according to any one of the above, in particular, the device comprises:

[0032] a first storage module for creating a first list container for storing patient master index data in memory, storing historical patient master index data into the first list container, each historical patient master index data comprising a patient master index serial number and a plurality of patient identity information fields;

[0033] a second storage module for traversing the first list container to store the historical patient master index data in the first list container into a preset nested Map container in memory, the nested Map container comprising an outer container and an inner container, the key of the outer container being a preset matching rule field name of the master index matching model, the matching rule field being a field for identifying patient identity information, the value corresponding to each key of the outer container being an inner container, the key of the inner container being a field value of the matching rule field in the historical patient master index data corresponding to the key of the outer container, and the value corresponding to each key of the inner container being a coordinate set recorded in the container list with the same value as the key of the inner container in the historical patient master index data;

[0034] a first matching module for obtaining target fields in the patient medical record data to be matched, which are the same as the matching rule field names of the master index matching model;

[0035] a second matching module for determining target inner containers corresponding to each target field, matching in the respective target inner containers according to the values of each target field to find a target key with a value being the value of the current target field, and extracting a target value corresponding to each target key;

[0036] a calculation module for taking target historical patient master index data pointed to by the coordinates in the intersection of each target value in the first list container as the patient master index data of the patient medical record data to be matched.

[0037] Another aspect of the present application provides a computer device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor; when the computer program is executed by the processor, the steps of the memory-based patient master index fast matching method according to any one of the above are implemented.

[0038] The memory-based patient main index fast matching method, device and equipment provided by the embodiment of the application load patient main index data into memory in advance to process into a specific structure, and complete the whole main index matching process in memory, which can greatly improve the main index matching efficiency, and the key-value pair storage data mode based on the Map container can directly locate the value according to the key, avoid traversing data in the search process, and further improve the main index matching efficiency, so as to adapt to the requirement of matching a large number of main indexes in the data integration process and improve the patient medical record data integration efficiency.

[0039] The above description is only a summary of the technical scheme of the application, in order to more clearly understand the technical means of the application, and can be implemented according to the content of the specification, and in order to make the above and other purposes, characteristics and advantages of the application more obvious and easy to understand, the following specific embodiments of the application are described. BRIEF DESCRIPTION OF DRAWINGS

[0040] Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The accompanying drawings are intended to depict only preferred embodiments of the application, and therefore should not be considered to narrow the scope of the present application in any way. In the drawings:

[0041] Figure 1 A flow chart of a memory-based patient main index fast matching method according to an embodiment of the application;

[0042] Figure 2 A patient main index data storage schematic diagram of a list container according to an embodiment of the application;

[0043] Figure 3 A storage structure schematic diagram of a nested Map container according to an embodiment of the application;

[0044] Figure 4 A structure schematic diagram of a memory-based patient main index fast matching device according to an embodiment of the application. DETAILED DESCRIPTION

[0045] Exemplary embodiments of the present disclosure will be described more fully hereinafter with reference to the accompanying drawings. While example embodiments of the present disclosure are shown in the drawings, it is understood that the present disclosure can be embodied in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the present disclosure to those skilled in the art.

[0046] Those skilled in the art can understand that, unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. It should also be understood that terms such as those defined in a general dictionary should be understood to have meanings consistent with meanings in the context of the prior art, and should not be interpreted in an idealized or overly formal sense unless specifically defined.

[0047] Embodiment one

[0048] The embodiment of the application provides a memory-based patient master index fast matching method, as shown in the accompanying drawings. Figure 1 The memory-based patient master index fast matching method provided by the application comprises the following steps:

[0049] S1, a first list container for storing patient master index data is created in the memory, historical patient master index data is stored into the first list container, and each historical patient master index data comprises a patient master index serial number and a plurality of patient identity information fields.

[0050] The application pre-creates a list container for storing historical patient master index data generated after matching calculation in a historical data processing process, and reads the historical patient master index data that has completed matching from a database into the memory and stores the historical patient master index data into the list container, as shown in the accompanying drawings. Figure 2 The master index data at any coordinate position can be directly read through the coordinates of the patient master index in the list container. When executed for the first time, there is no historical patient master index data, and the list container is empty. Each patient master index data contains a unique patient master index serial number generated by the system and a plurality of patient identity information fields, such as name, gender, age, date of birth, telephone, etc. The patient identity information fields contained in the patient master index cover all matching rule fields in the preset master index matching model.

[0051] The master index matching model needs to be pre-constructed, and includes matching rule fields for patient matching. The master index matching model is used for field matching of to-be-matched patient medical record data according to the matching rule fields.

[0052] S2, traversing the first list container to store the historical patient main index data in the first list container to a preset nested Map container in the memory, the nested Map container comprising an outer container and an inner container, the key of the outer container being a preset matching rule field name of the main index matching model, the matching rule field being a field used to identify patient identity information, the value corresponding to each key of the outer container being an inner container, the key of the inner container being a field value of the matching rule field corresponding to the key of the outer container in the historical patient main index data, and the value corresponding to each key of the inner container being a coordinate set of a record in the list container with the same value as the key of the inner container in the historical patient main index data. The matching rule field is specifically a part of a specified field in patient medical record data that can be used to identify patient identity information.

[0053] The application stores patient main index information in a nested Map container by traversing a first list container storing historical patient main indexes, according to a matching rule field name of a main index matching model, a patient main index data field value, and a coordinate of the patient main index data in the list container.

[0054] Specifically, the application pre-constructs a nested Map container. The nested Map container comprises an outer container and an inner container, and the Map container stores data using key-value pairs, can directly locate the value according to the key, and has a very fast access speed. The key of the outer Map container is a matching rule field name of a matching model, for example, name, and the value is also a Map container, i.e., an inner container. The key of the inner container is a value of a field corresponding to the key of the outer Map container in the patient main index data, for example, the key of the outer Map container is "name", and the key of the inner Map container is the patient name "Zhang XX". The value of the inner Map container is a coordinate set of a record in the list container with the same value as the key of the inner container in the patient main index data, for example, the key of the inner container is "Zhang XX", and the value is a coordinate set of all main index data with the name "Zhang XX" in the list in the patient main index list container. The storage structure of the nested Map container is as follows: Figure 3 .

[0055] S3, obtaining a target field in the patient medical record data to be matched, which is the same as the matching rule field name of the main index matching model.

[0056] Specifically, the application matches the field of the patient medical record data to be matched according to the matching rule field of the main index matching model to obtain a field in the patient medical record data to be matched which is the same as the matching rule field name, and obtains a target field. Specifically, the main index matching model is read from the database in advance, the matching rule field is obtained, and is stored in the memory to avoid reading from the database every time.

[0057] S4, determining a target inner container corresponding to each target field, matching in the respective target inner container according to the value of each target field to find a target key whose value is the value of the current target field, and extracting a target value corresponding to each target key.

[0058] Specifically, the application first determines a target inner container corresponding to each target field, matches in the respective target inner container according to the value of each target field to find a target key whose value is the value of the current target field, and extracts a target value corresponding to each target key.

[0059] S5, taking the target historical patient main index data pointed to by the coordinates in the intersection of each target value in the first list container as the patient main index data of the patient medical record data to be matched.

[0060] Specifically, the application calculates the intersection of each target value, and confirms the historical patient main index data pointed to by the coordinates in the intersection in the first list container as the target historical patient main index data, and takes the target historical patient main index data as the patient main index data of the patient medical record data to be matched.

[0061] In this embodiment, when matching the patient main index data, the matching rule field name contained in the set matching model is used to locate the inner Map container in the nested container. The value of the field of the patient medical record data to be matched which is consistent with the matching rule field name of the matching model can be used to locate the coordinate set of the patient main index data in the list container which matches the patient medical record data to be matched. According to the matching rule field name contained in the matching model and the value of the field in the patient medical record data to be matched which is the same as the matching rule field name, the coordinate set of the patient main index data in the list container which matches is obtained. The result of taking the intersection of the sets is obtained, that is, the patient main index record which matches the patient medical record data to be matched.

[0062] The memory-based patient main index fast matching method provided by the embodiment of the application creates a list container for storing patient main index data in the memory, stores historical patient main index data into the list container, and then traverses the list container to store the historical patient main index data in the list container into a preset nested Map container in the memory; obtains target fields in the patient medical record data to be matched which are the same as the matching rule field names, matches in the target inner container corresponding to each target field according to the values of the target fields to find a target key with a value being the value of the current target field, and extracts a target value corresponding to each target key; and takes target historical patient main index data in the intersection of the target values and the coordinates in the first list container as the patient main index data of the patient medical record data to be matched. By preloading the patient main index data into the memory to process into a specific structure and completing the whole main index matching process in the memory, the matching method based on pure memory can reduce I / O processing and greatly improve the query efficiency, and the key-value pair storage data mode based on the Map container can directly locate the value according to the key value, avoid traversing data in the searching process, and further improve the main index matching efficiency to adapt to the requirement of matching a large number of main indexes in the data integration process and improve the patient medical record data integration efficiency.

[0063] The memory-based patient main index fast matching method provided by the embodiment of the application further includes the step of preconstructing the main index matching model. Specifically, a main index matching model is preconstructed, the main index matching model includes matching rule fields for patient matching, a matching threshold is set for the main index matching model, and a weight is set for each matching rule field, so that when a patient is matched, the fields in the patient medical record data which are the same as the matching rule field names are added in the field weight, and if the weight sum is greater than the matching threshold, the patient is determined to be matched, and if the weight sum is less than the matching threshold, the patient is determined not to be matched.

[0064] Specifically, the main index matching model is preinitialized, the fields in the patient medical record data which can identify the patient identity are selected as the matching rule fields of the matching model, for example, the name, mobile phone number, ID number, etc., a weight is set for each matching rule field, and the weight sum of all the matching rule fields is 100. Meanwhile, a matching threshold is set for the main index matching model, the field weights of the matched fields are added when a patient is matched, and if the result is greater than the matching threshold, the patient is determined to be matched, and if the result is less than the matching threshold, the patient is determined not to be matched. When the patient main index fast matching is performed, the main index matching model is pre-read from the database, the matching rule fields, the field weights and the model matching threshold are obtained, and are stored in the memory to avoid reading from the database every time.

[0065] Further, the step S3 includes: acquiring target fields in the patient medical record data to be matched, which are the same as the matching rule field names of the main index matching model; and arranging and combining the target fields to obtain a combination mode in which the field weight sum is greater than the matching threshold.

[0066] Correspondingly, the step S4 includes: extracting a target inner container corresponding to each target field in the current combination mode according to the target fields included in each combination mode.

[0067] Correspondingly, the step S5 includes: taking the target historical patient main index data pointed to by the coordinates in the intersection of each target value in the first list container as the patient main index data of the patient medical record data to be matched.

[0068] In the embodiment of the application, the fields in the patient medical record data to be matched, which are the same as the matching rule field names of the matching model and have values, are arranged and combined to obtain a combination mode in which the field matching weight sum is greater than the matching threshold of the matching model. An inner Map is extracted from the Map container according to the fields included in the combination mode, a patient main index data coordinate set matching the fields of the patient medical record data to be matched is extracted, and the intersection of all the sets extracted by the combination mode is taken as the patient main index data matching the patient medical record data to be matched.

[0069] In the embodiment, when the patient main index is matched, as long as the matching field weight sum is greater than the matching threshold, the same patient can be determined. However, it is not known which fields are matched, so all possible combination modes need to be arranged and combined, and then the intersection is taken according to each combination mode to determine whether there is a matching patient main index.

[0070] The memory-based patient main index fast matching method provided in the embodiment of the application further includes: if the intersection of each target value is empty, it is determined that there is no patient main index data matching the patient medical record data to be matched, and a new patient main index serial number is generated for the patient medical record data to be matched; when the main index data in the main index list container is updated, the new patient main index serial number obtained is combined with the patient basic information field in the patient medical record data to be matched to serve as the patient main index data of the patient medical record data to be matched, and the patient main index data is added to the first list container.

[0071] In the embodiment, if the intersection result of all combination manners is empty, it indicates that there is no patient master index data matched with the patient medical record data to be matched, and a new master index serial number needs to be generated for the patient medical record to be matched. If no existing master index record is matched, the patient basic information in the patient medical record data bound with the new master index serial number is appended to the tail of the patient master index list container. Since the list container records the coordinate position of each data, the application can directly add the patient basic information in the patient medical record data bound with the new master index serial number to the tail of the patient master index list container, that is, a coordinate position is added at the tail of the list container, thereby avoiding the problem of adding to other positions and causing the need to modify the original data and the coordinate position of the original data. Further, after the coordinate in the intersection points to the target historical patient master index data in the first list container as the patient master index data of the patient medical record data to be matched, the method further comprises: covering the non-empty field values of the patient basic information in the patient medical record data to be matched with the corresponding fields of the target historical patient master index data in the first list container. That is, if an existing master index record is matched, the non-empty field values of the patient basic information in the patient medical record data are covered with the corresponding fields of the original patient master index record to update the original patient master index record.

[0072] Further, the memory-based patient master index fast matching method provided by the embodiment of the application further comprises: updating the storage record of the nested Map container according to the patient master index data of the patient medical record data to be matched in the first list container.

[0073] Specifically, for a newly generated master index record, the inner Map container is located according to the matching model rule field name, and the master index coordinate set stored in the inner Map container is located according to the value of the field of the new master index record consistent with the rule field name of the master index matching model, and the coordinate of the new master index record in the list container is added to the coordinate set. For an updated master index record, the field in the master index record whose value is updated and which is consistent with the matching model matching rule field name is added to the Map container according to the coordinate of the master index in the list container in the manner of newly generated master index, and the record of the original value of the field in the coordinate set in the Map container is deleted.

[0074] Further, the memory-based patient master index fast matching method provided by the embodiment of the application further comprises: storing the patient master index data of the patient medical record data to be matched into a preset second list container, and the second list container is used to store the newly matched patient master index data; and when the second list container reaches a preset data length, all the patient master index data stored in the second list container is batch saved into a preset database.

[0075] Specifically, when the matched primary index data is saved to the database, to avoid frequent I / O caused by saving one by one and affecting the matching efficiency, a list container, i.e., a second list container, is first created to store the matched primary index data, and when the container reaches a certain length, the primary index data is saved to the database in batches.

[0076] In addition, if an exception occurs in the matching process and the matching fails, the memory primary index data is reset, and step S2 is re-executed, so as to avoid inconsistency between the memory primary index data and the database record, and ensure data consistency.

[0077] In addition, if it is necessary to modify the primary index matching model and the matching rule field, the primary index matching model construction step and the nested Map container construction step are re-executed in sequence, so as to update the primary index matching model in the memory and re-construct the container.

[0078] The memory-based patient primary index fast matching method provided by the application improves the primary index matching efficiency by preloading the patient primary index data into the memory and processing the data into a specific structure, and completing the entire primary index matching process in the memory, so as to adapt to the requirement of matching a large number of primary indexes in the data integration process, and improve the patient medical record data integration efficiency. When the matching is wrong or the service is down, the memory is reloaded to ensure the consistency between the memory data and the database data, so as to ensure the efficiency and the reliability of the data.

[0079] For the method embodiments, in order to simply describe, they are all described as a series of action combinations, but those skilled in the art should know that the embodiments of the application are not limited by the action sequence described, because according to the embodiments of the application, certain steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should know that the embodiments described in the specification all belong to preferred embodiments, and the actions involved are not necessarily necessary for the embodiments of the application.

[0080] Embodiment two

[0081] Another embodiment of the application further provides a memory-based patient primary index fast matching device, which comprises function modules for realizing the memory-based patient primary index fast matching method according to any one of the above. Figure 4 The structure of the memory-based patient primary index fast matching device provided by the embodiments of the application is schematically shown, and the device comprises a first storage module 201, a second storage module 202, a first matching module 203, a second matching module 204 and a calculation module 205. Figure 4 The memory-based patient primary index fast matching device provided by the embodiments of the application specifically comprises a first storage module 201, a second storage module 202, a first matching module 203, a second matching module 204 and a calculation module 205.

[0082] The first storage module 201 is configured to create a first list container for storing patient master index data in the memory, and store historical patient master index data into the first list container, each of the historical patient master index data including a patient master index serial number and a plurality of patient identity information fields.

[0083] The second storage module 202 is configured to store the historical patient master index data in the first list container into a preset nested Map container in the memory by traversing the first list container, the nested Map container including an outer container and an inner container, a key of the outer container being a matching rule field name of a preset master index matching model, the matching rule field being a field for identifying patient identity information, a value corresponding to each key of the outer container being an inner container, a key of the inner container being a field value of the matching rule field in the historical patient master index data corresponding to the key of the outer container, and a value corresponding to each key of the inner container being a coordinate set of records in the container list with the same value as the key of the inner container in the historical patient master index data.

[0084] The first matching module 203 is configured to obtain a target field in the patient medical record data to be matched, the target field being the same as the matching rule field name of the master index matching model.

[0085] The second matching module 204 is configured to determine a target inner container corresponding to each target field, and perform matching in the respective target inner container according to the value of each target field to find a target key with the value of the current target field, and extract a target value corresponding to each target key.

[0086] The calculation module 205 is configured to take a target historical patient master index data in the intersection of the target values and pointed to by the coordinates in the first list container as the patient master index data of the patient medical record data to be matched.

[0087] In the implementation process, the embodiment two can refer to the embodiment one, and has corresponding technical effects.

[0088] Embodiment three

[0089] The embodiment of the present application provides a computer device, which includes a memory, a processor and a computer program stored in the memory and executable on the processor, and the processor implements the steps in each of the above patient master index fast matching methods based on memory, such as steps S1-S5 shown in the figure. Figure 1 Alternatively, the processor implements the functions of each module in each of the above patient master index fast matching devices based on memory when executing the computer program, such as the functions of the modules in the device shown in the figure. Figure 4The first storage module 201, the second storage module 202, the first matching module 203, the second matching module 204 and the calculation module 205 are shown.

[0090] In the implementation process, the embodiment three can refer to the embodiment one, and has corresponding technical effects.

[0091] In addition, those skilled in the art can understand that although some embodiments herein include certain features included in other embodiments rather than other features, the combination of features of different embodiments means to be within the scope of the present application and forms different embodiments. For example, any one of the claimed embodiments can be used in any combination.

[0092] Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, but not to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: it can still modify the technical solutions recorded in the foregoing embodiments, or make equivalent replacement for part of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A memory-based patient master index fast matching method, characterized in that, The method comprises: creating a first list container in memory for storing patient master index data, storing historical patient master index data into the first list container, each historical patient master index data comprising a patient master index serial number and a plurality of patient identity information fields; traversing the first list container to store the historical patient master index data in the first list container into a preset nested Map container in memory, the nested Map container comprising an outer container and an inner container, the key of the outer container being a preset matching rule field name of the master index matching model, the matching rule field being a field for identifying patient identity information, the value corresponding to each key of the outer container being an inner container, the key of the inner container being the field value of the matching rule field in the historical patient master index data corresponding to the key of the outer container, and the value corresponding to each key of the inner container being a coordinate set recorded in the container list with the same value as the key of the inner container in the historical patient master index data; obtaining target fields in the patient medical record data to be matched which are the same as the matching rule field names of the master index matching model; determining target inner containers corresponding to each target field, matching in the respective corresponding target inner containers according to the values of each target field to find target keys with the value of the current target field, and extracting target values corresponding to each target key; coordinates in the intersection of each target value pointing to target historical patient master index data in the first list container as patient master index data of the patient medical record data to be matched.

2. The method of claim 1, wherein, The method further comprises: previously constructing the master index matching model, the master index matching model comprising matching rule fields for patient matching, setting a matching threshold for the master index matching model and setting a weight for each matching rule field, so that when matching patients, the fields in the patient medical record data which are the same as the matching rule field names are added up by field weight, and if the weight sum is greater than the matching threshold, the patients are determined to be matched, and if the weight sum is less than the matching threshold, the patients are determined not to be matched.

3. The method of claim 2, wherein, The method further comprises: obtaining target fields in the patient medical record data to be matched which are the same as the matching rule field names of the master index matching model; arranging and combining each target field to obtain a combination mode with a field weight sum greater than the matching threshold.

4. The method of claim 3, wherein, The method further comprises: extracting target inner containers corresponding to each target field in the nested Map container according to the target fields contained in each combination mode under the current combination mode; The method further comprises: The method further comprises:

5. The method according to any one of claims 1 to 4, characterized in that, The method further comprises: If the intersection of each target value is empty, it is determined that there is no patient master index data matched with the patient medical record data to be matched, and a new patient master index serial number is generated for the patient medical record data to be matched. The new patient master index serial number obtained is combined with the patient basic information field in the patient medical record data to be matched, and the combined patient master index data is used as the patient medical record data to be matched, and the patient master index data is added to the first list container.

6. The method according to any one of claims 1 to 4, characterized in that, After the target historical patient master index data in the intersection is used as the patient master index data of the patient medical record data to be matched, the method further comprises: In the first list container, the patient basic information non-empty field value in the patient medical record data to be matched is used to cover the corresponding field of the target historical patient master index data.

7. The method of claim 5, wherein, The method further comprises: According to the patient master index data of the patient medical record data to be matched in the first list container, the storage record of the nested Map container is updated.

8. The method of claim 5, wherein, The method further comprises: The patient master index data of the patient medical record data to be matched is stored in a preset second list container, and the second list container is used to store the newly matched patient master index data. When the second list container reaches the preset data length, all the patient master index data stored in the second list container is batch saved to the preset database.

9. A memory-based patient master index fast matching device, characterized by, The device comprises: A first storage module is configured to create a first list container for storing patient master index data in the memory, and store historical patient master index data in the first list container, wherein each historical patient master index data comprises a patient master index serial number and a plurality of patient identity information fields. A second storage module is configured to traverse the first list container to store the historical patient master index data in the first list container in a preset nested Map container in the memory, wherein the nested Map container comprises an outer container and an inner container, the key of the outer container is a matching rule field name of a preset master index matching model, the matching rule field is a field for identifying patient identity information, the value corresponding to each key of the outer container is an inner container, the key of the inner container is the field value of the matching rule field in the historical patient master index data corresponding to the key of the outer container, and the value corresponding to each key of the inner container is a coordinate set of the record in the container list with the same value as the key of the inner container in the historical patient master index data. A first matching module is configured to obtain a target field in the patient medical record data to be matched, which is the same as the matching rule field name of the master index matching model. The second matching module is configured to determine target inner-layer containers corresponding to the target fields, match in the target inner-layer containers corresponding to the target fields respectively according to values of the target fields to find target keys with values being values of the current target fields, and extract target values corresponding to the target keys respectively; The calculating module is configured to take coordinates in the intersection of the target values as patient main index data of the patient medical record data to be matched, which are pointed to by the target historical patient main index data in the first list container.

10. A computer device, comprising: A computer program product comprising a memory, a processor and a computer program stored on the memory and loadable on the processor; The computer program product is configured to implement the steps of the method according to any one of claims 1-8 when executed by the processor.

Images