Cross-institutional medical data interfacing method and system

Abstract

The present application relates to the technical field of data interconnection, in particular to a cross-agency medical data docking method and system, comprising the following steps: obtaining a patient number and adding an agency identifier, matching an agency code to generate an attribution path, constructing a structure path field to count the number of hops, marking a violation request to generate an examination result. In the present application, an agency identifier code is added as a prefix before the patient number to establish an identity structure format with cross-agency uniqueness, an attribution path linked list is constructed by matching the agency code, the node order is clarified, the path field is combined into a structure path conforming to the standard model, the structured expression of data flow is realized, the number change in the path is extracted and the number of hops is counted, dynamic judgment is performed according to the number of hops and the permission threshold, the unauthorized access behavior is screened and the violation item is marked, the identity differentiation, path pointing, behavior recognition and permission control are strengthened, and the accurate identification, path tracing and access compliance capability are improved in the high-frequency interaction of multiple agencies.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data interconnection, in particular to a cross-institutional medical data docking method and system. BACKGROUND

[0002] The field of data interconnection technology includes data exchange and integration methods between different information systems. The core of this field is to solve the efficient sharing and docking of multi-source heterogeneous data in cross-system and cross-platform environments. It is widely used in multi-organization and multi-node data collaboration environments in industries such as government affairs, finance, and medical care. The focus is on realizing the interconnection and dynamic management of data resources through standardized data format conversion, protocol adaptation, access control, and data security guarantee mechanisms. In the medical industry, data interconnection technology pays particular attention to privacy protection, data standardization, and fine-grained access control. Its development trend emphasizes the collaborative application of distributed data structures, trusted data interaction mechanisms, and standardized data semantic models.

[0003] Among them, the cross-institutional medical data docking method refers to a data interaction technology solution based on standardized data formats and unified interface protocols to meet the data docking needs between multiple independent information systems in the medical industry. It includes semantic mapping and data modeling of structured medical data such as electronic medical records, diagnosis and treatment records, and examination information. A unified medical data coding system is used for data format conversion, and a record association method based on identifier matching is used to realize the unique identification of patients across institutions. In addition, an access request verification method based on permission control is used to standardize the access behavior of data requesters to receiving party data resources, ensuring the legal retrieval and use of data during the docking process.

[0004] In the existing medical data docking process, the identification field is constructed based on local numbering structure or institution-defined coding method during data identity processing. There is a lack of uniform structure identifier design between fields, which may cause identity conflicts and increase the risk of record misidentification in the case of repeated numbering. In the path attribution link, static institution mapping is often used to mark the source attribute, which cannot support dynamic expression of data flow transfer links. The path pointing lacks structural integrity, making it difficult to trace the transmission track in data interaction and weakening the audit capability of access compliance. In the permission judgment mechanism, there is a lack of behavior quantification indicators, and the transmission path changes are not systematically extracted and identified, resulting in insufficient control of access behavior granularity. For example, if there is short-term authorization or link change between different institutions, the existing permission mechanism cannot dynamically judge compliance according to path changes, and there is a potential risk of unauthorized access. The permission configuration relies on static role relationships and ignores the complex jump logic in data access paths, resulting in control gaps and difficulty in supporting compliance management requirements in high-sensitivity data interaction scenarios. SUMMARY

[0005] The application aims to solve the problems in the prior art and provides a cross-institutional medical data docking method.

[0006] To achieve the above-mentioned purpose, the application adopts the following technical scheme: a cross-institutional medical data docking method, comprising the following steps:

[0007] S1: obtaining the patient number of an access medical institution in a region and the medical institution practice license registration number, adding the institution number as a prefix to the front end of the patient number, and generating a standard identity field format list;

[0008] S2: performing equivalent matching based on the regional health information platform institution coding field and the local institution mutual recognition coding table index field according to the prefix field in the standard identity field format list, determining the attribution path, and generating an attribution institution location index linked list;

[0009] S3: determining that the current institution is the path end node based on the recorded institution number field in the attribution institution location index linked list and the current request institution number, combining the transmission order into an HL7 reference information model structure path field, recording the access node and the attribution relationship, generating an institution path call structure set;

[0010] S4: according to the institution path call structure set, extracting the number item by item according to the content in the arrangement order, and generating a path hop count structure detail table according to the adjacent institution number field statistical number change times;

[0011] S5: based on the path hop count structure detail table, counting the difference between the two field hop counts, marking the docking request exceeding the maximum hop count allowed threshold as a violation entry, and generating a cross-institutional medical data docking review result.

[0012] As a further scheme of the application, the standard identity field format list includes a unified prefix structure, a standard number format, and an identity extension rule, the attribution institution location index linked list includes an institution index sequence, a path order mark, and attribution confirmation information, the institution path call structure set includes an HL7 path field, a node access mark, and an attribution node mark, the path hop count structure detail table includes hop count records, institution sequence differences, and path segment division information, and the cross-institutional medical data docking review result includes permission compliance status, violation entry identification, and hop count threshold classification results.

[0013] As a further scheme of the application, the standard identity field format list acquisition step specifically comprises:

[0014] S111: Based on the data content provided by the access medical institutions in the region, the original patient number field and the medical institution license registration number field are obtained, the medical institution license registration number is taken as the participation item, and the medical institution license registration number is taken as the participation item. The original patient number is added in front of the corresponding original patient number as a prefix in the form of a string, and a prefix added number result is generated;

[0015] S112: According to the prefix added number result and the original patient number field, all number value lengths, character rules and uniqueness states are screened, and the screening judgment basis is whether the character bit number meets the number standard length range and whether the character composition exists illegal symbol. A uniform number set after screening is obtained;

[0016] S113: Based on the corresponding relationship table of the uniform number set after screening and the original number field, the number mapping field structure is constructed, all records in the original patient number field are mapped and replaced, and a standard identity field format list is established.

[0017] As a further scheme of the application, the obtaining step of the home institution position index chain table is specifically:

[0018] S211: Based on the prefix field in the standard identity field format list, the prefix field value in the standard identity field is matched with the code field value in the regional platform in combination with the institution code field corresponding to each institution in the regional health information platform, and an equal value matching number index result is generated;

[0019] S212: According to the equal value matching number index result, the mutual recognition code field content under the same index value is obtained in combination with the mutual recognition code table index field in the local institution code table, the corresponding home path order position of the same institution in different platforms is judged, the path position of the institution with repeated home path is compared, the home path offset degree is calculated, and path matching offset data is generated.

[0020] S213: Based on the mapping relationship between the path matching offset data and the original institution index number, the abnormal records with offset degree greater than the home path offset tolerance threshold are screened out, the sequential number identification processing is performed on all legal path structure records, and a home institution position index chain table is established.

[0021] As a further scheme of the application, the obtaining step of the home institution position index chain table is specifically:

[0022] S311: Based on the institution number field recorded in the home institution position index chain table and the request institution number field recorded in the current request target field, the equal value comparison is performed, whether the request number is equal to the end node number is judged, if the matching is successful, the current institution is marked as the end node of the path, the node identification information and the path termination state mark are combined, and a path end point identification item is generated.

[0023] S312: According to the path end identification item, arranging in record order, and performing structure connection operation, merging the institution number field into a unified structure expression string in sequence, setting the path connector according to the HL7 reference information model specification and embedding the standard structure syntax, calculating the path structure balance value, verifying whether the path string structure meets the hierarchical matching rule, saving the output standard path field;

[0024] S313: According to the standard path field of each institution node structure, record the access node number and path ownership identification in the corresponding field, and mark the access permission identification bit for each subsegment in the field in turn, and combine the institution number field with the node permission table to perform field ownership mapping operation, and establish the institution path call structure set.

[0025] As a further scheme of the application, the path hop count structure detail table obtaining step is specifically:

[0026] S411: Based on the institution path call structure set, obtain the institution number string connected by the connector in the path field, perform string segmentation operation, cut the path field into an ordered number sequence according to the connector, record the number field position index, and establish the path number sequence;

[0027] S412: Based on the path number sequence, according to the adjacent institution number fields in the sequence, difference judgment is performed in turn two by two, the judgment standard is whether the number field content exists character inconsistency, length change or structure displacement, the change characteristics between numbers are compared and the number of changes is accumulated, the number difference point and change direction are recorded, and the number change cumulative result is obtained;

[0028] S413: According to the number change cumulative result, a node jump record table is established for the number field sequence in the path, each jump number change content, starting number, target number, change type and change amplitude are recorded, each change is assigned a unique index and the difference type is marked, and the path hop count structure detail table is established.

[0029] As a further scheme of the application, the cross-institution medical data docking review result obtaining step is specifically:

[0030] S511: Based on the field content in the path hop count structure detail table, the path number corresponding to each path is extracted, and the hop count field corresponding to the corresponding number is obtained, the path number and the corresponding hop count are combined, the path number is checked, and the corresponding relationship between the number and the hop count is established, and the path hop count data set is generated;

[0031] S512: According to the path number field in the path hop count data set, the maximum hop count allowed threshold field in the matching authority matrix table is extracted, the maximum hop count value in each record is extracted, and the path number is used as the key value to perform bit merging operation, the path hop count and the maximum allowed hop count are combined into the comparison field item, and the hop count threshold comparison record table is generated.

[0032] S513: According to each record in the hop count threshold comparison record table, the actual hop count field and the maximum allowed hop count field are extracted, and the field value difference judgment operation is performed, if the path hop count is greater than the maximum allowed hop count, the record is recorded as a violation entry, otherwise, the record is recorded as a compliance entry, and the cross-institutional medical data docking review result is generated.

[0033] A cross-institutional medical data docking system comprises:

[0034] The identity code splicing module acquires the original patient number field and the practice license registration number field, calls the latter to splice to the front end of the former, constructs an extended structure, and generates a standard identity field format list;

[0035] The institution index matching module reads the platform institution code and the local mutual recognition field based on the encoding prefix of the standard identity field format list, performs equivalent matching, and generates a home institution location index linked list;

[0036] The path structure combination module judges the path end node according to the home institution location index linked list, splices the path field, and generates a local path call structure set;

[0037] The hop count path extraction module extracts the institution number based on the path field in the local path call structure set, judges the adjacent number difference and accumulates the hop count, and generates a path hop count structure detail table;

[0038] The authority path verification module performs hop count difference judgment and marks compliance according to the hop count field in the path hop count structure detail table in combination with the maximum hop count allowed threshold, and generates a cross-institutional medical data docking review result.

[0039] Compared with the prior art, the application has the advantages and positive effects that:

[0040] In this invention, by adding an institution identification code as a prefix to the patient's number, a unique identity structure format with cross-institutional characteristics is established, eliminating identification ambiguity. A path chain is constructed by matching institution codes to clarify the node order and enhance the clarity of path expression. The path fields are combined into a structured path that conforms to a standard model, realizing a structured expression of data flow. The number changes in the path are extracted and the number of hops is counted to establish a basis for behavior quantification. Dynamic judgment is performed based on the difference in the number of hops and the permission threshold to screen for unauthorized access behavior and mark violations. This strengthens identity differentiation, path pointing, behavior recognition, and permission control, improving the ability to accurately identify, trace paths, and ensure access compliance in high-frequency interactions among multiple institutions. Attached Figure Description

[0041] Figure 1 This is a flowchart of the main steps of the present invention;

[0042] Figure 2 This is a flowchart for obtaining the standard identity field format list of this invention;

[0043] Figure 3 This is a flowchart illustrating the process of obtaining the location index linked list of the organization to which this invention belongs;

[0044] Figure 4 This is a flowchart illustrating the process of obtaining the path call structure set for this invention.

[0045] Figure 5 This is a flowchart of the process for obtaining the path hop count structure details table of the present invention;

[0046] Figure 6 This is a flowchart illustrating the process of obtaining the review results of cross-institutional medical data integration in this invention. Detailed Implementation

[0047] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the invention.

[0048] In the description of this invention, it should be understood that the terms "length," "width," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," and "outer," etc., indicating orientation or positional relationships, are based on the orientation or positional relationships shown in the accompanying drawings and are only for the convenience of describing the invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of the invention. Furthermore, in the description of this invention, "a plurality of" means two or more, unless otherwise explicitly specified.

[0049] Please see Figure 1A cross-institutional medical data docking method, comprising the following steps:

[0050] S1: Obtain the original patient number field and the medical institution license registration number (legal institution identifier issued by the health commission) field of the access medical institution in the region, append the institution number as the prefix to the front end of the patient number based on the string splicing method, establish the identity extension field structure with standard unified format, and generate the standard identity field format list;

[0051] S2: According to the prefix field in the standard identity field format list, based on the regional health information platform institution code (in accordance with GB / T22239-2020 "Health Information Data Element Value Domain Code" standard) field and the mutual recognition coding table index field in the local institution coding table, Perform an equivalent matching operation, determine the attribution path through the matching record index sequence, and generate the attribution institution location index linked list;

[0052] S3: Based on the institution number field recorded in the attribution institution location index linked list and the request institution number recorded in the current request target field, determine that the current institution is the path end node, extract the institution number field in the path segment and combine it into the HL7 reference information model (path description specification in international standard of medical health information exchange) structure path field according to the transmission order, record the field access node and the attribution relationship, and generate the current institution path call structure set;

[0053] S4: According to the structure path field in the current institution path call structure set, extract the number according to the arrangement order item by item according to the field content, perform difference judgment according to the adjacent institution number field, count the number of number changes, and generate the path hop count structure detail table;

[0054] S5: Based on the maximum hop count allowed threshold field in the path hop count structure detail table and the corresponding field in the data authority matrix table (permission management table based on RBAC (role-based access control) model), based on the hop count difference between the two fields, perform logical judgment and record classification, mark the docking request whose hop count exceeds the maximum hop count allowed threshold as a violation entry, and generate the cross-institutional medical data docking review result.

[0055] The standard identity field format list includes unified prefix structure, standard number format, and identity extension rules, the attribution institution location index linked list includes institution index sequence, path order mark, and attribution confirmation information, the current institution path call structure set includes HL7 path field, node access identifier, and attribution node mark, the path hop count structure detail table includes hop count record, institution sequence difference, and path segment division information, and the cross-institutional medical data docking review result includes permission compliance state, violation entry identification, and hop count threshold classification result.

[0056] Please refer toFigure 2 S1 is:

[0057] S111: Based on the data content provided by the medical institutions in the region, the original patient number field and the medical institution license registration number field are obtained, the medical institution license registration number is taken as the participation item, and the corresponding original patient number is prefixed with a string as the prefix to generate the prefix added number result;

[0058] Based on the data content provided by the medical institutions in the region, first extract the medical institution license registration number field and the original patient number field, for the institution number "XY001" and the patient number "A123", the institution number is prefixed to the front of the patient number to form the structured number "XY001A123", before splicing, the original number field is standardized, including uniform field length, removing non-character types, checking for null values and illegal symbols, for example, if the original number is an integer type "1234", it needs to be converted to a string "1234", if it is "X-456", remove "-" through regular expression, ensure uniform structure format, in the splicing process, the institution number and patient number field values are read by using line-by-line traversal method, and string splicing operation is performed to form a new field "added number", for example, if the medical institution number is "XY002" and the original patient number is "B234", the splicing gets "XY002B234", after splicing, the original patient number field and the added number field are mapped and associated, the result is recorded to generate a number mapping table for subsequent judgment and screening operation, and finally the prefix added number result is obtained.

[0059] S112: According to the prefix added number result and the original patient number field, all number value lengths, character rules and uniqueness states are screened, the screening judgment basis is whether the character bit number meets the number standard length range and whether the character composition exists illegal symbol, and the screened uniform number set is obtained;

[0060] According to the prefix added number result and the original patient number field, character composition detection and standard structure judgment are performed. First, the overall length of the spliced number is judged. The length standard is set to 10 bits, and the allowable deviation is ±1 bit, that is, the qualified interval is 9 to 11 bits. If the number length is 12 bits, such as "XY004D4569", it is regarded as unqualified number. Second, the legality of characters is judged. The number items containing illegal characters are screened out through regular expression. Illegal characters are defined as symbols other than English letters and numbers, such as "@", "#", "!", etc. If "XY004D@56" appears in the field, it is marked as illegal record. Then, the character coincidence situation is calculated. Taking "XY001A123" and the original number "A123" as an example, the common characters and their position relationship are compared. The number of character coincidence bits is 4 bits, accounting for 40% of the total length of 10 bits. If the coincidence ratio is less than 30%, it is excluded. Finally, the offset degree is calculated to judge whether the original number characters are large-scale position drift. If the character "A" is shifted more than 2 bits in the spliced number, it is marked as structure deviation item. All calculation items are uniformly summarized in the screening condition judgment table. The number data meeting the requirements is reserved to obtain the screened unified number set. The screened data is shown in the following table:

[0061] Table 1 Screening number structure example table

[0062]

[0063] As shown in Table 1, the number "XY004D456" is detected as 1 due to the presence of illegal symbols and is excluded. The remaining 3 records all meet the number length, character composition and structure judgment requirements and are reserved for mapping replacement.

[0064] S113: Based on the corresponding relationship table of the screened unified number set and the original number field, the number mapping field structure is constructed. All records in the original patient number field are mapped and replaced to establish a standard identity field format list.

[0065] Based on the screening obtained after the unified numbering set, the standard numbering mapping structure is further constructed. First, create a field mapping table, read the mapping relationship between each original patient number and the corresponding additional number, compare the field content, and perform the replacement operation, such as replacing the number "A123" with "XY001A123". During the replacement process, the field index needs to be called to ensure accurate mapping, and there should be no situation of multiple prefix numbers pointing to a number. The processing process uses record comparison to replace line by line and real-time verification. The consistency coverage rate is set to 95%, that is, if there are 1000 original patient numbers, at least 950 or more need to be successfully replaced, otherwise it is considered to be successfully replaced. If the coverage rate is lower than the threshold, an abnormal prompt is output, and the unmatched items are recorded in the exception table and revised again. Finally, the replaced number field data is output and stored in the list structure table as the basis for subsequent data standardization, and the standard identity field format list is obtained.

[0066] Please refer to Figure 3 , S2 step is:

[0067] S211: Based on the prefix field in the standard identity field format list, combined with the institution code field of each institution in the regional health information platform, the prefix field value in the standard identity field is matched with the code field value in the regional platform, and the equivalent matching number index result is generated.

[0068] Based on the prefix field in the standard identity field format list, extract the prefix item in the number field, such as "XY001", "XY002", "XY003", "XY004", which corresponds to the medical institution code field in the regional health information platform. This field should adopt the structure of GB / T22239-2020 standard and conform to the "HSP" starting code format, such as "HSP001", "HSP002", "HSP003", etc. When performing equivalent matching operation, compare the prefix field with the regional platform institution code character by character. If the prefix field "XY001" can find a complete code corresponding relationship "HSP001" in the platform, the matching is successful and the order index value "1" is assigned. In turn, "XY002" and "HSP002" are assigned "2", "XY003" and "HSP003" are assigned "3". If there is no matching item such as "XY004" corresponding to "no HSP004", the matching fails and the index field is marked as null. After comparison, the following matching structure is obtained:

[0069] Table 2 matching number order structure table

[0070]

[0071] As shown in Table 2, three records successfully complete the matching and form an order, and finally obtain the equivalent matching number index result.

[0072] S212: According to the equivalent matching number index result, combined with the agency mutual recognition coding table index field in the local agency coding table, the mutual recognition coding field content under the same index value is obtained, the corresponding home path order position of the same agency in different platforms is judged, and the path position of the agency with repeated home path is compared, using the formula: ;

[0073] Calculate the home path offset , generate path matching offset data, where, is the agency index value of the first record in the regional platform, is the matching index value of the first record in the local mutual recognition coding table, represents the consistency of the first bit path character in the first , is the matching difference value of the first bit character, is the total number of path comparison bits;

[0074] According to the equivalent number index result "1", "2", "3" obtained by the foregoing matching, the index structure record position in the local mutual recognition coding table is called respectively, the structure path field in the mutual recognition coding field is found which matches the above index order, and the local path is set as "M001", "M002", "M006", and the regional path is set as "HSP001", "HSP002", "HSP003". The offset is judged by using the structure index position serial number, and the index offsets of "1" and "1", "2" and "2", and "3" and "6" are obtained, which are 0, 0, and 3 respectively. In addition to the position index, the structure content also needs to be compared, and the path character structure comparison method is used to count the difference bit number of the path structure in the character bit. If "HSP003" and "M006" are different in the structure of the fourth bit, "P" and "0" are different, and one bit difference is recorded. The total bit difference is set as the total number of character differences, the index offset, and the sum. The path structure offset value of all records is calculated and brought into the formula for calculation.

[0075] Taking the number "XY003" as an example, the regional index is , the local index is , and the total number of path characters is , in which there are two positions of inconsistent characters, and the difference bit number is 2. The character difference is 1, and the character consistency is 0 at the difference bit and 1 at the consistent bit. Therefore, the sum term is , and the formula is: ;

[0076] The offset degree is determined by the numerical value of the offset to determine whether the offset is abnormal, and path matching offset data is obtained.

[0077] The home path offset degree represents the overall structural difference degree of the home path recorded by an institution in the regional health information platform in the path matching process with the local mutual recognition coding table structure. The offset degree comprehensively measures two core factors: one is the position difference in the institution index order, that is, whether the home order of the institution in different systems is consistent, and the other is the consistency degree of the path field character structure, that is, whether there is a significant change or character misplacement in the path content. Therefore, the home path offset degree reflects the matching deviation of the home path in the logical structure and the actual coding level. The larger the numerical value is, the lower the position matching and structural correspondence degree of the home path in the two systems is. The index can be used to screen path mismatch records and structural abnormal path nodes, and provide accuracy basis for the construction of the home chain.

[0078] The operation logic of the formula is based on the combination processing of two key influencing factors of the home path offset: one is the direct deviation of the index position, and the other is the content difference between the path structure characters. In the formula, the numerator part represents the absolute difference between the index value of the regional platform and the index value of the local mutual recognition, which is used to measure the direct position offset degree of the path home, and belongs to the direct expression of the positional error; the denominator part constructs the standardization adjustment item of the structural content difference, sets the constant 1 as the minimum scaling base to avoid the case that the divisor is zero, and introduces the cumulative weight factor of the path structure consistency and the difference degree, which is represented by , wherein the consistency index is multiplied by the difference value to represent whether there is an effective difference in the corresponding position characters in the path, and then the sum of the difference contributions of all character sites is summed up, and the square root is taken to smooth the amplification effect of large difference items on the overall result, so as to control the degree of local deviation affecting global judgment. The design realizes the coordinated measurement of the index dimension and the structure dimension of the home offset degree of the institution through the joint mode of addition, multiplication and square root.

[0079] S213: Based on the mapping relationship between the path matching offset data and the original institution index number, the abnormal records with the offset degree greater than the home path offset tolerance threshold are screened out, the sequential number identification processing is performed on all legal path structure records, and the home institution position index linked list is established;

[0080] According to the path matching offset data and the original number mapping relationship, records with a path offset value less than or equal to 3 are included in the subsequent linked list organization structure. First, records with an offset greater than 3 are screened out, for example, the item "XY005" with an offset of 5.2 is excluded from the home structure, and the remaining records are retained. The order relationship structure between agencies is re-established. According to the path of the regional platform agency order "1→2→3", the corresponding local code "M001→M002→M006" is formed in sequence, and the linked list is constructed. Each node structure includes standard prefix number, matching order, local code value and front and rear node number field. If there is an interrupt record, such as "XY004" without matching order, it is marked as skipped. Finally, the hierarchical relationship between nodes is completed, the home structure data chain is generated, and the home agency position index linked list is formed.

[0081] Please refer to Figure 4 , S3 step is:

[0082] S311: Based on the agency number field recorded in the home agency position index linked list and the request agency number field recorded in the current request target field, an equal value comparison is performed to determine whether the request number is equal to the end node number. If the match is successful, the current agency is marked as the end node of the path, the node identification information and the path termination state marker are combined, and the path end identification item is generated;

[0083] Based on the agency number field "XY001" "XY002" "XY003" "XY004" recorded in the home agency position index linked list and the request agency number "XY004" in the current request target field, an equal value match is performed. If the match is successful, it means that the request agency is at the end node position in the home path structure. The matching number is recorded as the end node of the path structure, and the node state is set to the end state identification item. The matching operation uses a structure consistency judgment and index end check mechanism, and the field matching uses a one-to-one accurate equal value judgment method. At the same time, the matching successful number and its path index information are retained to form a structured identification marker as shown in the following table:

[0084] Table 3 Path structure end identification table

[0085]

[0086] As shown in Table 3, only XY004 is the matching item, and the path end identification item is finally obtained.

[0087] S312: According to the path end identification item, arrange the records in order and perform structure connection operation. The agency number field is combined into a unified structure expression string in order. The path connector is set according to the HL7 reference information model specification and embedded into the standard structure syntax, using the formula:

[0088] ;

[0089] path structure balance value , verifying whether the path string structure meets the hierarchical matching rule, saving the output standard path field, wherein, represents the position weight value of the th institution in the path, is the actual position number of the path node in the th item in the linked list, is the ideal target position number thereof in the standard template, represents the total number of nodes in the path segment, represents the degree of syntax deviation of the th character, represents the number of nodes in the path structure;

[0090] According to the path end identification item “XY004”, obtain all the preceding number fields in the home chain, including “XY001”, “XY002”, “XY003”, perform structure combination operation, splice these number fields in the order of path structure, adopt the structure connection format in the HL7 information model for connection, set the connection symbol as “→”, form the combined structure path string as “XY001→XY002→XY003→XY004”, in order to verify whether the path structure has hierarchical dislocation or semantic deviation problem, perform path structure balance degree check, set the total number of nodes , ideal number of each node position , actual number , structure syntax deviation degree , position weight , substitute into the formula:

[0091] ;

[0092] Perform calculation:

[0093] ;

[0094] ;

[0095] The numerical result shows that each node in the structure path is consistent with the ideal template position, the syntax deviation degree is in the low deviation tolerance range, meets the structure standard, the path string “XY001→XY002→XY003→XY004” is reserved as the standard path field, and the standard path field is obtained.

[0096] The path structure balance value represents the overall coordination degree of each agency node in the structure position and semantic level in the home path, which is an important measurement index for measuring whether the path string conforms to the HL7 reference information model specification. The value comprehensively reflects the offset difference between the actual ordering position of each node and the standard template position, and is corrected in combination with the syntax specification difference of the character structure in the path to determine whether the construction of the path exists level dislocation, sequence disorder or semantic offset phenomenon. The closer the balance value is to 0, the more consistent the arrangement order of all nodes in the path is with the template, the smaller the syntax deviation is, and the more stable the overall path structure is; on the contrary, the larger the value is, the higher the structural incoordination degree is, and the path may have problems such as node order error and structure splicing anomaly, so the value plays a key role in path quality checking, access control path construction and cross-system information interaction.

[0097] The operation logic of the formula aims to comprehensively evaluate the deviation degree of each agency node in the structure path between its actual position and the standard template position, and introduces the offset interference of the syntax structure as a correction factor, so as to measure the balance of the overall path structure. Specifically, the numerator part represents the offset of each path node multiplied by its corresponding structure weight to amplify the contribution of the structure core node in the path offset, the more critical the node is, the greater the influence of its offset is, and the item is accumulated by summing the weighted offsets of all path nodes; the denominator part consists of two parts, the first term represents the square root of the path length, which is used to buffer the extreme influence of the path length on the balance, to avoid the accumulation amplification of the offset caused by more nodes, and the second term represents the average offset of each node at the syntax level, which is used to evaluate whether the structure format of the path string exists level deviation or splicing anomaly, and is used as a smoothing adjustment factor of the path, finally the path structure offset and the syntax difference are combined by addition to realize the normalization processing, so that the formula not only reflects the overall consistency of the path structure position, but also introduces the quantitative judgment of the structure specification, forming the overall measurement of the rationality of the HL7 path field construction.

[0098] S313: According to the structure of each agency node in the standard path field, record the access node number and path home identification in the corresponding field, mark the access permission identification bit for each subsegment in the field in turn, and perform field home mapping operation in combination with the agency number field and the node permission table to establish the path calling structure set of the agency;

[0099] Based on the standard path field "XY001→XY002→XY003→XY004", each path node is accessed and recorded one by one. Assuming the request number is still "XY004", the system assigns an access mark "✓" to this number and all its preceding nodes. Based on the attribution determination, the system records either "Local" or "This Organization" in the path attribution mark field. In the path, "XY004" is the request target and is marked as "This Organization", while the rest are marked as "Local". The complete structured access mapping is shown below:

[0100] Table 4. Structure Path Access Relationship Table

[0101]

[0102] As shown in Table 4, each node has an access tag and a corresponding path affiliation label. Combining this structure field, a field affiliation mapping and a node access field table are established, ultimately forming the path call structure set of this organization.

[0103] Please see Figure 5 Step S4 is as follows:

[0104] S411: Based on the path call structure set of this organization, obtain the organization number string connected by the connector "→" in the path field, perform string splitting operation, divide the path field into an ordered number sequence according to the connector, record the position index of the number field, and establish the path number sequence;

[0105] Retrieve the path field content from the path call structure set of this organization. Read the field format as the standard path format "XY001→XY002→XY003→XY004", split it by the "→" connector, and parse it into a number sequence list [XY001, XY002, XY003, XY004]. Assign a sequential position index to each number, for example, XY001 is number 1, XY002 is number 2, and so on. Record the arrangement order of the path numbers and their positions. At the same time, generate a correspondence between the starting number and the target number to provide a basic data structure for subsequent jump recognition. Finally, establish the path number sequence.

[0106] S412: Based on the path number sequence, according to the adjacent institution number fields in the sequence, perform difference judgments on each pair in turn. The judgment criteria are whether there are inconsistencies in the characters, changes in length, or structural displacements in the number field content. Compare the change characteristics between the numbers one by one and accumulate the number of changes. Record the number difference points and the direction of change, and obtain the cumulative result of number changes.

[0107] Based on the path number sequence, adjacent number pairs are sequentially subjected to variation detection, and the judgment criteria include character difference, length change, and overall consistency of number structure. If two number fields differ in character content, such as "XY001" and "XY002" suffixes, it is marked as "structure replacement". If the number change is only in the prefix part of the number structure, it is marked as "prefix adjustment". If the two numbers are completely consistent, it is determined that there is no variation. In each detection behavior, the starting number, target number, variation, change type, and change amplitude, such as the number of changed characters and the change position, are recorded to form a structured comparison record result, as shown in the following table:

[0108] Table 5 Path number jump example table

[0109]

[0110] As shown in Table 5, two field variation records are generated, corresponding to jump index 1 and 2, and the respective change amplitude reflects the degree of variation. Further, the overall variation frequency of the path number is accumulated to obtain the number variation accumulation result.

[0111] S413: According to the number variation accumulation result, a node jump record table is established for the number field sequence in the path, and each jump number change content, starting number, target number, change type, and change amplitude are recorded. A unique index is assigned to each variation and the difference type is marked to establish a path jump structure detail table;

[0112] According to the number variation accumulation result, the change details of each jump number field in the path are sorted. The variation items "XY001→XY002" and "XY002→XY003" in the path segment are recorded as jump events, their change types are classified as structure replacement and prefix adjustment, and the path jump frequency is calculated. The jump density is defined as the ratio of the number of variation jump segments to the total number of path jump segments. Here, the total number of jump segments is 3, the number of variation jump segments is 2, and the jump density is calculated as 2÷3≈0.67. At the same time, a unique index number is assigned to each jump variation record, a structured field index list is established, all variation segments in the path structure field set are marked with identifiable markers, and finally a number jump hierarchy table is constructed to generate a path jump structure detail table.

[0113] Please refer to Figure 6 , the S5 step is:

[0114] S511: Based on the field content in the path jump structure detail table, the path number corresponding to each path is extracted, and the jump number field corresponding to the corresponding number is obtained. The path number and the corresponding jump number are combined, the path number is checked, and the correspondence between the number and the jump number is established to generate a path jump data set;

[0115] After obtaining the path number field in the path hop count structure detail table, the system retrieves each path information in sequence according to the number order. For each path, the hop count field value is extracted through field comparison and recorded as the hop count value of the path. In the extraction operation, it is necessary to verify whether the path number and the path hop count item have a one-to-one correspondence based on the field rules established in the structure detail table. If there are multiple hop count records for a path number, the number screening process is performed, and the hop count value of the last record is retained. The system stores the number and the corresponding hop count in the form of key-value pairs, and completes this operation for each path number. After completion, a complete path hop count dataset is formed, each record in the dataset consists of a path number and its corresponding hop count value, which is suitable for subsequent permission checking scenarios. For example, in a medical system, the path number from institution A to institution B is A1001, and the corresponding hop count is 3. After the system retrieves and confirms that there is no duplication, it records A1001:3. Other paths perform the same processing procedure to form the data items shown in the following table:

[0116] Table 6 Path hop count dataset table

[0117]

[0118] As shown in Table 6, the table lists each path and its hop count record extracted from the structure detail table. The data has completed the field mapping of number and hop count.

[0119] S512: According to the path number field in the path hop count dataset, match the maximum hop count threshold field in the permission matrix table, extract the maximum hop count value in each record, and perform a bit merging operation with the path number as the key value. Combine the path hop count and the maximum allowed hop count into a comparison field item to generate a hop count threshold comparison record table;

[0120] Based on the path number in the path hop count dataset, read the permission control rule field in the permission matrix table in sequence, match the maximum hop count threshold field content, retrieve the maximum hop count limit of each path number in the permission matrix table, and maintain the number consistency during the operation. Perform null filling and marking for missing items, then perform a row-by-row binding operation between the maximum hop count field and the aforementioned path hop count field to generate a structure-unified hop count threshold comparison record table. In this table, each record consists of a path number, an actual hop count, and a maximum allowed hop count. For example, the path number A1001 has a maximum allowed hop count of 2 in the permission matrix table, and the actual hop count in the path hop count dataset is 3. After merging, the A1001:3-2 item is formed. The system completes the field merging operation for each record in this way to provide comparison source data for the next step of judgment. The following table is constructed:

[0121] Table 7 Hop count threshold comparison record table

[0122]

[0123] Referring to Table 7, the table completes the splicing of the path number and the two types of hop number fields, and provides numerical basis for the logical judgment process.

[0124] S513: According to the hop threshold comparison record table, the actual hop number field and the maximum allowed hop number field are extracted, and the field value difference judgment operation is performed. If the path hop number is greater than the maximum allowed hop number, it is recorded as a violation entry, otherwise it is recorded as a compliance entry, and the cross-institution medical data docking review result is generated;

[0125] Based on the hop threshold comparison record table, the system calls the actual hop number corresponding to the path number and the maximum allowed hop number field content, performs item-by-item numerical comparison, and judges whether the actual hop number in each record is greater than the maximum allowed hop number. In the judgment process, a Boolean value identifier is constructed according to the field difference rule. If the result of the actual hop number minus the maximum hop number is greater than 0, it is marked as a violation entry, otherwise it is a compliance entry. Compliance and violation entries are recorded as different field sets and are indexed and marked by path number. After aggregation, a unified review result list is generated. In one example, if the actual hop number of path A1001 is 3 and the maximum allowed hop number is 2, the difference is 1, which is a violation record. The system writes A1001 into the violation entry set. Similar operations are performed on the remaining records to traverse and process, and the cross-institution medical data docking review result is constructed. The result is structured into groups according to the violation and compliance categories for subsequent system control response operations. The final result generated by this execution process is: cross-institution medical data docking review result.

[0126] A cross-institution medical data docking system, comprising:

[0127] The identity code splicing module obtains the original patient number field and the license registration number field, calls the latter to splice to the front end of the former, constructs an extended structure, and generates a standard identity field format list;

[0128] The institution index matching module reads the platform institution code and local mutual recognition field based on the coding prefix of the standard identity field format list, performs equivalent matching, and generates a home institution location index linked list;

[0129] The path structure combination module judges the path end node according to the home institution location index linked list, splices the path field, and generates a local path call structure set;

[0130] The hop path extraction module extracts the institution number based on the path field in the local path call structure set, judges the adjacent number difference and accumulates the hop number, and generates a path hop number structure detail table;

[0131] The authority path checking module performs a hop difference judgment and marks compliance according to a hop field in the path hop structure detail table in combination with a maximum hop allowed threshold, and generates a cross-institution medical data docking review result.

[0132] The above is only a preferred embodiment of the present application, and does not limit the present application in other forms. Any person skilled in the art can use the disclosed technical content to make changes or modifications into equivalent embodiments applied to other fields, but any simple modification, equivalent change and modification made according to the technical essence of the present application to the above embodiments without departing from the technical solution content of the present application still belongs to the protection scope of the technical solution of the present application.

Claims

1. A cross-institutional medical data interfacing method, characterized in that, Comprise the following steps: S1: Obtain the patient number of the access medical institution in the region and the medical institution license registration number, add the institution number as the prefix to the front of the patient number, generate the standard identity field format list; S2: According to the prefix field in the standard identity field format list, based on the regional health information platform institution coding field and local institution mutual recognition coding table index field, perform equivalent matching to determine the attribution path, and generate the attribution institution location index linked list; S311: Based on the institution number field recorded in the attribution institution location index linked list and the request institution number field recorded in the current request target field, perform equivalent comparison, judge whether the request number is equal to the end node number, if the matching is successful, mark the current institution as the end node of the path, combine the node identification information and the path termination state mark to generate the path end identification item; S312: According to the path end identification item, arrange in order, and perform structure connection operation, combine the institution number field into a unified structure expression string in order, set the path connector according to the HL7 reference information model specification and embed the standard structure syntax, calculate the path structure balance value, verify whether the path string structure satisfies the hierarchical matching rule, save the output standard path field; S313: According to the structure of each institution node in the standard path field, record the access node number and path attribution identification in the corresponding field, mark the access permission identification bit for each subsegment in the field in turn, and combine the institution number field with the node permission table to perform field attribution mapping operation, establish the path calling structure set of the institution; S411: Based on the path calling structure set of the institution, obtain the institution number string connected by the connector in the path field, perform string segmentation operation, cut the path field into ordered number sequence according to the connector, record the number field position index, and establish the path number sequence; S412: Based on the path number sequence, according to the adjacent institution number fields in the sequence, perform difference judgment in turn, the judgment standard is whether there is character inconsistency, length change or structure displacement in the number field content, compare the change characteristics between the numbers in pairs and accumulate the number of changes, record the number difference point and change direction, and obtain the number change accumulation result; S413: According to the number change accumulation result, establish the node jump record table for the number field sequence in the path, record the change content, starting number, target number, change type and change amplitude of each jump number in turn, mark the difference type for each change, and establish the path jump number structure detail table; S5: Based on the path jump number structure detail table, count the jump number difference of two fields, mark the docking request exceeding the maximum jump number allowed threshold as a violation item, and generate the cross-institution medical data docking review result.

2. The cross-agency medical data interfacing method of claim 1, wherein, The standard identity field format list includes a uniform prefix structure, a standard number format, and an identity extension rule, the home agency location index chain table includes an agency index sequence, a path order mark, and home confirmation information, the local agency path call structure set includes an HL7 path field, a node access mark, and a home node mark, the path hop count structure detail table includes a hop count record, an agency sequence difference, and path segment division information, and the cross-agency medical data docking review result includes a permission compliance state, a violation rule mark, and a hop count threshold classification result.

3. The cross-agency medical data interfacing method of claim 1, wherein, The obtaining of the standard identity field format list specifically comprises the following steps: S111: Based on the data content provided by the medical agencies in the region, the original patient number field and the medical agency business license registration number field are obtained, the medical agency business license registration number is taken as a participation item, and a prefix is added to the front end of the corresponding original patient number in the form of a string, to generate a prefix added number result; S112: According to the prefix added number result and the original patient number field, all number value lengths, character rules and uniqueness states are screened, the screening judgment basis is whether the character bit number meets the number standard length range and whether there are illegal symbols in the character composition, and a screened uniform number set is obtained; S113: Based on the correspondence table of the screened uniform number set and the original number field, a number mapping field structure is constructed, all records in the original patient number field are mapped and replaced, and a standard identity field format list is established.

4. The cross-agency medical data interfacing method of claim 1, wherein, The obtaining of the home agency location index chain table specifically comprises the following steps: S211: Based on the prefix field in the standard identity field format list, the prefix field value in the standard identity field is matched with the coding field value in the regional platform according to the agency coding field corresponding to each agency in the regional health information platform, to generate an equal value matching number index result; S212: According to the equal value matching number index result, the mutual recognition coding table index field in the local agency coding table is combined to obtain the mutual recognition coding field content under the same index value, the corresponding home path order position of the same agency in different platforms is judged, the path position of the agencies with repeated home paths is compared, the home path offset degree is calculated, and path matching offset data is generated; S213: Based on the mapping relationship between the path matching offset data and the original agency index number, abnormal records with an offset degree greater than the home path offset tolerance threshold are screened out, sequential number mark processing is performed on all legal path structure records, and a home agency location index chain table is established.

5. The cross-agency medical data interfacing method of claim 1, wherein, The obtaining of the cross-agency medical data docking review result specifically comprises the following steps: S511: Based on the field content in the path hop count structure detail table, the path number corresponding to each path is extracted, and the hop count field corresponding to the corresponding number is obtained, the path number and the corresponding hop count are combined, the path number is checked, the corresponding relationship between the number and the hop count is established, and a path hop count data set is generated; S512: According to the path number field in the path hop count data set, the maximum hop count allowed threshold field in the matching authority matrix table is extracted, the maximum hop count value in each record is extracted, and the path number is used as the key value to perform bit merging operation. The path hop count and the maximum allowed hop count are combined into a comparison field item to generate a hop count threshold comparison record table; S513: According to each record in the hop count threshold comparison record table, the actual hop count field and the maximum allowed hop count field are extracted, and a field value difference judgment operation is performed. If the path hop count is greater than the maximum allowed hop count, it is recorded as a violation entry, otherwise it is recorded as a compliance entry, and a cross-institution medical data docking review result is generated.

6. A cross-institutional medical data interfacing system, comprising: The system is used to implement the cross-institution medical data docking method of any one of claims 1-5, comprising: The identity coding splicing module obtains the original patient number field and the practice license registration number field, calls the latter to splice to the front end of the former, constructs an extended structure, and generates a standard identity field format list; The institution index matching module reads the platform institution code and the local mutual recognition field based on the coding prefix of the standard identity field format list, performs equivalent matching, and generates a home institution location index linked list; The path structure combination module determines the path endpoint node according to the home institution location index linked list in combination with the request target institution number field, splices the path field, and generates a local path call structure set; The hop count path extraction module extracts the institution number based on the path field in the local path call structure set, judges the adjacent number difference and accumulates the hop count, and generates a path hop count structure detail table; The authority path verification module performs hop count difference judgment and marks compliance according to the hop count field in the path hop count structure detail table in combination with the maximum hop count allowed threshold, and generates a cross-institution medical data docking review result.

Images