Cross-mechanism medical data docking method and system

Abstract

The invention relates to the technical field of data interconnection, in particular to a cross-institution medical data docking method and system, and the method comprises the following steps: obtaining a patient number and adding an institution identifier, matching an institution code to generate an affiliation path, constructing a structural path field to count hop difference, and marking a violation request to generate an examination result. According to the method, mechanism identification codes are added before patient numbering to serve as prefixes, an identity structure format with cross-mechanism uniqueness is established, an affiliation path chain table is established through mechanism code matching, a node sequence is defined, path fields are combined into a structure path conforming to a standard model, and structured expression of data flow directions is achieved. According to the method, the number change in the path is extracted, the hop count is counted, dynamic judgment is executed according to the hop count difference value and the permission threshold value, unauthorized access behaviors are screened, illegal items are marked, identity distinguishing, path pointing, behavior recognition and permission management and control are enhanced, and the accurate recognition, path tracing and access compliance capabilities are improved in multi-mechanism high-frequency interaction.

Description

Technical Field

[0001] The present invention relates to the field of data interconnection technology, and in particular to a cross-institutional medical data docking method and system. Background Art

[0002] The field of data interconnection technology encompasses methods for data exchange and integration between diverse information systems. Its core focus is on efficiently sharing and connecting multi-source, heterogeneous data across systems and platforms. It is widely used in multi-organization, multi-node data collaboration environments in industries such as government, finance, and healthcare. The focus is on achieving the interconnection and dynamic management of data resources through standardized data format conversion, protocol adaptation, access control, and data security mechanisms. Data interconnection technology in the healthcare industry is particularly focused on privacy protection, unified data standards, and fine-grained control of access rights. Its development trend emphasizes the collaborative application of distributed data structures, trusted data interaction mechanisms, and standardized data semantic models.

[0003] The cross-institutional medical data docking method refers to a data interaction technology solution based on standardized data formats and unified interface protocols, which is proposed to meet the data docking needs between independent information systems of multiple institutions in the medical industry. It includes semantic mapping and data modeling of structured medical data such as electronic medical records, medical records, and examination and testing information, adopting a unified medical data coding system for data format conversion, and realizing the unique identification of patients across institutions through a record association method based on identifier matching. In addition, it also uses an access request verification method based on permission control to standardize the data requester's access to the recipient's data resources, ensuring the legal retrieval and use of data during the docking process.

[0004] In existing medical data integration processes, identification fields are often constructed based on local numbering structures or customized institutional coding methods during data identity processing. This lacks a unified structural identifier design between fields, which can easily lead to identity conflicts in the presence of duplicate numbers and increase the risk of record misidentification. In the path attribution process, source attributes are often marked using static institutional mapping, which fails to support the dynamic expression of data flow links. The path pointing lacks structural integrity, making it difficult to trace the transmission trajectory during data interaction and weakening the ability to audit access compliance. Permission judgment mechanisms generally lack quantitative behavioral indicators, and transmission path changes are not systematically extracted and identified, resulting in insufficient granular control over access behavior. For example, if there are short-term authorization or link changes between different institutions, the existing permission mechanism cannot dynamically determine compliance based on path changes, posing a potential risk of unauthorized access. Permission configuration relies on static role relationships and ignores the complex jump logic in data access paths, creating a control gap and making it difficult to support the compliance management needs of highly sensitive data interaction scenarios. Summary of the Invention

[0005] The purpose of the present invention is to solve the shortcomings of the existing technology and propose a cross-institutional medical data docking method.

[0006] To achieve the above objectives, the present invention adopts the following technical solution: a method for inter-institutional medical data docking, comprising the following steps: S1: Obtain the patient ID and registration number of the medical institution's practice license from the medical institution in the region, append the institution's unique identification code to the front of the patient ID as a prefix, and generate a list of standard identity field formats; S2: performing an equal value match based on the prefix field in the standard identity field format list, the institution code field of the regional health information platform, and the index field of the local institution mutual recognition code table, to determine the attribution path and generate an attribution institution location index chain table; S3: Based on the organization number field recorded in the home organization location index linked table and the current requesting organization number, the current organization is determined to be the path endpoint node, and the paths are combined into the HL7 reference information model structure path fields in the transmission order, and the access nodes and the home relationships are recorded to generate the path call structure set of the current organization; S4: extracting numbers item by item according to the content and arrangement order of the path call structure set of the organization, counting the number of number changes according to adjacent organization number fields, and generating a path hop count structure detail table; S5: Based on the path hop count structure detailed table, the hop count difference between the two fields is counted, and the docking request that exceeds the maximum hop count threshold is marked as a violation entry, and a cross-institutional medical data docking review result is generated.

[0007] As a further solution of the present invention, the standard identity field format list includes a unified prefix structure, a standard numbering format, and identity extension rules; the affiliated institution location index linked list includes an institution index sequence, a path sequence mark, and affiliated confirmation information; the local institution path call structure set includes an HL7 path field, a node access identifier, and an affiliated node mark; the path hop structure details table includes hop records, institution sequence differences, and path segment division information; the cross-institutional medical data docking review results include authority compliance status, violation item identifier, and hop threshold classification results.

[0008] As a further solution of the present invention, the steps for obtaining the standard identity field format list are specifically as follows: S111: Based on the data content provided by the medical institutions connected in the region, the original patient number field and the medical institution practice license registration number field are obtained, the medical institution practice license registration number is used as a participating item, and is appended as a string prefix to the front of the corresponding original patient number to generate a prefix appended number result; S112: Based on the prefixed numbering result and the original patient number field, all number value lengths, character rules, and uniqueness are screened. The screening is based on whether the number of characters meets the standard numbering length range and whether there are illegal symbols in the character composition, and a unified number set after screening is obtained. S113: Based on the correspondence table between the unified number set after screening 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.

[0009] As a further solution of the present invention, the steps for obtaining the home institution location index linked list are specifically as follows: S211: Based on the prefix field in the standard identity field format list and in combination with the institution code field corresponding to 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 to generate an equal value matching number index result; S212: Based on the equal-value matching number index result, combined with the institution mutual recognition code table index field in the local institution code table, the mutual recognition code field content under the same index value is obtained, the attribution path sequence position corresponding to the same institution in different platforms is determined, and the path position comparison is performed for institutions with duplicate attribution paths, the attribution path offset is calculated, and path matching offset data is generated; S213: Based on the mapping relationship between the path matching offset data and the original institution index number, filter out abnormal records with an offset greater than the belonging path offset tolerance threshold, perform sequential number identification processing on all legal path structure records, and establish a belonging institution location index chain list.

[0010] As a further solution of the present invention, the steps for obtaining the path call structure set of the mechanism are specifically as follows: S311: Based on the organization number field recorded in the home organization location index linked list, a comparison is performed with the request organization number field recorded in the current request target field to determine whether the request number is equal to the end node number in the linked list structure. If a match is successful, the current organization is marked as the end node of this path, and the node identification information is combined with the path termination status mark to generate a path end identification item; S312: Based on the path endpoint identifier, the records are arranged in the order of the records in the attribution chain, and a structural connection operation is performed to sequentially merge the organization number fields into a unified structural expression string. The path connector is defined using the HL7 reference information model specification and embedded in the standard structure syntax. The path structure balance value is calculated, and it is verified whether the path string structure meets the hierarchical matching rules. The output standard path field is saved. S313: According to each organization node structure in the standard path field, record the access node number and path ownership identifier in the corresponding field, mark the access permission identifier for each sub-segment in the field in turn, and perform field ownership mapping operations in combination with the organization number field and the node authority comparison table to establish the organization path call structure set.

[0011] As a further solution of the present invention, the steps of obtaining the path hop count structure detailed table are specifically as follows: S411: Based on the structure path field in the organization path call structure set, obtain the organization number string connected by the connector in the path field, perform a string segmentation operation, split the path field into an ordered number sequence according to the connector, record the number field position index, and establish a path number sequence; S412: Based on the path number sequence, adjacent organization number fields in the sequence are sequentially judged for differences. The judgment criteria are whether there are character inconsistencies, length changes, or structural displacements in the number fields. The change characteristics between the numbers are compared one by one, and the number of changes is accumulated and counted. The number difference points and change directions are recorded to obtain the cumulative number change results. S413: Based on the accumulated results of the numbering changes, a node jump record table is established for the numbering field sequence in the path, and the content, starting number, target number, change type and change range of each jump number change are recorded one by one. A unique index is assigned to each change and the difference type is marked to establish a detailed table of the path hop structure.

[0012] As a further solution of the present invention, the steps for obtaining the cross-institutional medical data docking review results are specifically as follows: S511: Based on the field contents in the path hop count structure detailed table, extract the path number corresponding to each path, obtain the hop count field corresponding to the corresponding number, combine the path number with the corresponding hop count, check the path number, establish a correspondence between the number and the hop count, and generate a path hop count dataset; S512: Based on the path number field in the path hop count data set, the maximum hop count threshold field in the matching authority matrix table is matched, the maximum hop count value in each record is extracted, and a bitwise merge operation is performed using the path number as the key value. 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: Compare each record in the record table according to the hop count threshold, extract the actual hop count field and the maximum allowed hop count field, and perform a field value difference judgment operation. 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 a cross-institutional medical data docking review result is generated.

[0013] A cross-institutional medical data docking system, comprising: The identity code 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, builds an extended structure, and generates a list of standard identity field formats; The institution index matching module reads the platform institution code and the local mutual recognition field based on the code prefix of the standard identity field format list, performs equivalence matching, and generates an attribution institution location index chain table; The path structure combination module determines the path end node according to the home institution position index linked list and the requested target institution number field, splices the path fields, and generates the path call structure set of the current institution; The hop count path extraction module extracts the organization number based on the path field in the organization path call structure, determines the difference between adjacent numbers and accumulates the hop count to generate a path hop count structure detailed table; The authority path verification module performs hop difference judgment and marks compliance based on the hop field in the path hop structure details table, combined with the maximum hop allowable threshold, and generates a cross-institutional medical data docking review result.

[0014] Compared with the prior art, the advantages and positive effects of the present invention are: In the present invention, by adding the institution identification code as a prefix before the patient number, an identity structure format with cross-institutional uniqueness is established to eliminate identification ambiguity, and an attribution path list is constructed through institution code matching to clarify the node order and enhance the clarity of path expression. The path fields are combined into a structural path that conforms to the standard model to achieve structured expression of data flow, extract the number changes in the path and count the number of hops, establish a behavior quantification basis, perform dynamic judgment based on the hop difference and the authority threshold, screen for unauthorized access behavior and mark violations, strengthen identity differentiation, path pointing, behavior identification and authority management, and improve accurate identification, path traceability and access compliance capabilities in high-frequency interactions among multiple institutions. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 It is a flow chart of the main steps of the present invention; Figure 2 Obtaining a flow chart for the standard identity field format list of the present invention; Figure 3 A flowchart for obtaining the location index linked list of the affiliated institution of the present invention; Figure 4 Obtaining a flow chart for the path call structure set of the present invention; Figure 5 Obtaining a flow chart for the path hop count structure detailed table of the present invention; Figure 6 This is a flow chart for obtaining the review results of cross-institutional medical data docking in the present invention. DETAILED DESCRIPTION

[0016] In order to make the purpose, technical solutions and advantages of the present invention more clearly understood, the present 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 only used to explain the present invention and are not intended to limit the present invention.

[0017] In the description of the present invention, it should be understood that the terms "length," "width," "up," "down," "front," "back," "left," "right," "vertical," "horizontal," "top," "bottom," "inside," "outside," and the like, indicating positions or relationships, are based on the positions or relationships shown in the accompanying drawings and are intended only to facilitate the description of the present invention and simplify the description. They do not indicate or imply that the devices or elements referred to must have a specific orientation, be constructed, or operate in a specific orientation. Therefore, they should not be construed as limiting the present invention. Furthermore, in the description of the present invention, "plurality" means two or more, unless otherwise expressly and specifically defined.

[0018] See also Figure 1 , a cross-institutional medical data docking method, comprising the following steps: S1: Obtain the original patient ID field and the medical institution practice license registration number field (the legal institution identifier issued by the Health Commission) of the medical institutions connected to the region, append the institution's unique identifier as a prefix to the front of the patient number based on string splicing, establish a standard unified format identity extension field structure, and generate a standard identity field format list; S2: Based on the prefix field in the standard identity field format list, perform an equal value matching operation based on the regional health information platform institution code (in accordance with the GB / T22239-2020 "Health Information Data Element Value Domain Code" standard) field and the institution mutual recognition code table index field in the local institution code table, determine the attribution path by matching the record index sequence, and generate an attribution institution location index chain table; S3: Based on the institution number field recorded in the affiliated institution location index list and the requested institution number recorded in the current request target field, the current institution is determined to be the path endpoint node. The institution number field in the path segment is extracted and combined into the HL7 reference information model (path description specification in the international standard for medical and health information exchange) structure path field in the transmission order. The field access node and the affiliated relationship are recorded to generate the path call structure set of the current institution. S4: Call the structure path field in the centralized structure according to the path of the organization, extract the number item by item in the order of arrangement according to the field content, perform difference judgment based on the adjacent organization number fields, count the number of number changes, and generate a detailed list of the path hop structure; S5: Based on the maximum hop count threshold field of each path hop count field in the path hop count structure details table and the corresponding field in the data permission matrix table (a permission management table based on the RBAC (role-based access control) model), logical judgment and record classification are performed based on the hop count difference between the two fields. The docking request with a hop count exceeding the maximum hop count threshold is marked as a violation entry, and the cross-institutional medical data docking review result is generated.

[0019] The standard identity field format list includes a unified prefix structure, a standard numbering format, and identity extension rules; the affiliated institution location index linked list includes an institution index sequence, a path sequence mark, and affiliated confirmation information; the institution path call structure set includes an HL7 path field, a node access identifier, and an affiliated node mark; the path hop structure details table includes hop records, institution sequence differences, and path segment division information; the cross-institutional medical data docking review results include authority compliance status, violation item identifier, and hop threshold classification results.

[0020] See also Figure 2 , S1 step is: S111: Based on the data content provided by the medical institutions connected in the region, the original patient number field and the medical institution practice license registration number field are obtained, the medical institution practice license registration number is used as a participating item, and is appended as a string prefix to the front of the corresponding original patient number to generate a prefix appended number result; Based on the data content provided by the access medical institutions in the region, the medical institution practice license registration number field and the original patient number field are first extracted. For the institution number "XY001" and the patient number "A123", the institution number is added as a prefix to the front of the patient number to form a structured number "XY001A123". Before splicing, the original number field is standardized, including unifying the field length, removing non-character types, and 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", "-" is removed through regular expressions to ensure a unified structure format. During the splicing process, a line-by-line traversal method is used to read the institution number and patient number field values, and a string splicing operation is performed to form a new field "appended number". For example, if the medical institution number is "XY002" and the original patient number is "B234", the splicing result is "XY002B234". After the splicing is completed, the original patient number field and the additional number field are associated with the field mapping, and the results are recorded to generate a number mapping table for subsequent judgment and screening operations, and finally the prefix additional number result is obtained.

[0021] S112: Based on the prefix additional number result and the original patient number field, all number value lengths, character rules, and uniqueness are screened. The screening judgment is based on whether the number of characters meets the standard number length range and whether there are illegal symbols in the character composition, and a unified number set after screening is obtained; According to the prefix additional number result and the original patient number field, the character composition test and standard structure judgment are performed. First, the overall length of the spliced ​​number is judged, and 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 considered an unqualified number; secondly, the legitimacy of the characters is judged, and the number items containing illegal characters are filtered out through regular expressions. Illegal characters are defined as symbols that are not English letters and numbers, such as "@", "#", "!", etc. If "XY004D@56" appears in the field, it is marked as unqualified. It is recorded as an illegal record. Subsequently, the character overlap is calculated. Taking "XY001A123" and the original number "A123" as an example, the common characters and their positional relationship are compared. The number of characters that overlap is 4, accounting for 40% of the total length of 10 digits. If the overlap ratio is less than 30%, it is excluded. Finally, the degree of offset is calculated to determine whether the original number characters have drifted in a large range. If the character "A" is displaced by more than 2 digits in the spliced ​​number, it is marked as a structural deviation item. All calculated items are summarized in the screening condition judgment table. The number data that meets the requirements is retained to obtain a unified number set after screening. The screening data is shown in the table below: Table 1 Sample screening number structure Original patient number Medical institution number Append number Number length Illegal symbol detection Number of characters overlapping Total character length A123 XY001 XY001A123 10 0 4 10 B234 XY002 XY002B234 10 0 3 10 C345 XY003 XY003C345 10 0 4 10 D456 XY004 XY004D456 10 1 2 10 As shown in Table 1, the number "XY004D456" is removed because of the illegal symbol detection value of 1, while the remaining three records meet the number length, character composition and structure judgment requirements and are retained for mapping replacement.

[0022] S113: Based on the correspondence table between the unified number set after screening 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; Based on the unified number set obtained after screening, a standard number mapping structure is further constructed. First, a field mapping relationship table is created, and the mapping relationship between each original patient number and the corresponding appended number is read. The field content is compared and a replacement operation is performed. For example, the number "A123" is replaced with "XY001A123". During the replacement process, the field index needs to be called to ensure accurate mapping. There must be no situation where duplicate numbers point to multiple prefix numbers. The processing process adopts a record comparison method to replace line by line and verify in real time. The lower limit of the consistency coverage is set to 95%. That is, if there are 1,000 original patient numbers, at least 950 must be successfully replaced to be considered a successful replacement. If the coverage rate is lower than the threshold, an exception prompt is output, and the unsuccessful matching items are recorded in the exception form and revised. Finally, the number field data after the replacement is output and stored in the list structure table as the basic field for subsequent data standardization to obtain a standard identity field format list.

[0023] See also Figure 3 , step S2 is: S211: Based on the prefix field in the standard identity field format list and in combination with the institution code field corresponding to 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 to generate an equal value matching number index result; 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", and "XY004", which correspond to the coding field of each medical institution in the regional health information platform. This field should be constructed using the GB / T22239-2020 standard and comply with the coding format starting with "HSP", such as "HSP001", "HSP002", and "HSP003". When performing the equal value matching operation, the prefix field is compared one by one with the regional platform machine. The code is fully matched. If the prefix field "XY001" can find a corresponding "HSP001" that fully matches its code in the platform, the match is successful and the sequential index value is assigned "1". "XY002" and "HSP002" are matched and assigned "2", and "XY003" and "HSP003" are matched and assigned "3". If there is no matching item for a certain number, such as "XY004" corresponding to "No HSP004", the match fails and is marked as a null value in the index field. After the comparison, the following matching structure is obtained: Table 2 Matching number sequence structure table Standard identity prefix Regional platform organization code Matching Status Matching Order XY001 HSP001 success 1 XY002 HSP002 success 2 XY003 HSP003 success 3 XY004 HSP004 fail NaN As shown in Table 2, the three records are successfully matched and sequenced, and finally the equal matching number index result is obtained.

[0024] S212: Based on the equal value matching number index result, combined with the institution mutual recognition code table index field in the local institution code table, obtain the mutual recognition code field content under the same index value, determine the corresponding attribution path sequence position of the same institution in different platforms, and compare the path positions of institutions with duplicate attribution paths using the formula: ; Calculate the deviation degree of the home path , generate path matching offset data, where, It is the first regional platform The institution index value of the record, It is the local mutual recognition code table The matching index value of the record, Indicates the Item No. Bit path character consistency identifier, For the The matching difference value of the bit character, is the total number of path comparison bits; Based on the equivalent number index results "1", "2", and "3" obtained from the above matching, the corresponding index structure record positions in the local mutual recognition code table are called respectively. The structure path field that matches the above index sequence is searched in the mutual recognition code field. The local paths are set to "M001", "M002", and "M006", and the regional paths are set to "HSP001", "HSP002", and "HSP003". The offset is determined using the structure index position sequence. Comparing "1" with "1", "2" with "2", and "3" with "6", the index offsets are 0, 0, and 3, respectively. In addition to the position index, the structure content is also compared. The path character structure comparison method is used to count the number of differences in the path structure character positions. If "HSP003" and "M006" differ in the fourth position, "P" and "0", this is recorded as a one-bit difference. The total bit difference is set as the sum of the total number of character differences and the index offset. The path structure offset value is calculated for all records and substituted into the formula for calculation.

[0025] Taking the number "XY003" as an example, the area index is , the local index is , total number of path characters , where the characters are inconsistent at two positions, the number of digits of difference is 2, and the character difference 1, character consistency The difference bit is 0, and the consistent bit is 1, so the sum is , substituting into the formula we get: ; The deviation value is used to determine whether the deviation is abnormal and obtain the path matching offset data.

[0026] The attribution path deviation degree indicates the degree of overall structural difference generated in the process of matching the attribution path of an institution record in the regional health information platform with the local mutual recognition coding table structure path. The deviation degree comprehensively measures two core factors: one is the position difference between the two in the institution index order, that is, whether the attribution order of the institutions in different systems is consistent; the other is the degree of consistency between the two in the character structure of the path field, that is, whether there are significant changes in the path content or structural differences such as character dislocation. Therefore, the attribution path deviation degree reflects the matching deviation between the logical structure and the actual coding level of the institution's attribution path. The larger the value, the lower the position matching and structural correspondence of the attribution path in the two systems. This indicator can be used to screen path mismatch records and structurally abnormal path nodes, providing an accuracy basis for the construction of the attribution chain.

[0027] The calculation logic of the formula is based on the combination of two key factors affecting the attribution path offset: one is the direct deviation of the index position, and the other is the content difference between the path structure characters. It represents the absolute difference between the regional platform index value and the local mutual recognition index value, and is used to measure the degree of direct position deviation of the path attribution. It is a direct expression of the position error. The denominator constructs a standardized adjustment item for the structural content difference, and sets a constant 1 as the minimum scaling base to avoid the situation where the divisor is zero. At the same time, it introduces a cumulative weighting factor for the consistency of the path structure and the degree of difference. Indicates the coupling term of character consistency and difference, where the consistency index and the difference value After multiplication, it indicates whether there is a valid difference in the characters at the corresponding position in the path. The difference contributions of all character sites are then summarized and squared to smooth the amplifying effect of larger difference items on the overall result, thereby controlling the extent to which local deviations affect global judgment. This design achieves a coordinated measurement of the degree of institutional attribution deviation in the index dimension and the structural dimension through the combination of addition, multiplication and square root.

[0028] S213: Based on the mapping relationship between the path matching offset data and the original institution index number, abnormal records with an offset greater than the attribution path offset tolerance threshold are screened out, and sequential number identification processing is performed on all legal path structure records to establish an attribution institution location index chain table; According to the mapping relationship between the path matching offset data and the original number, the records with path offset values ​​less than or equal to 3 are included in the subsequent linked list organizational structure. First, the records with an offset greater than 3 are screened out. For example, the item "XY005" with an offset of 5.2 will be removed from the affiliation structure, and the remaining records will be retained. The sequential relationship structure between institutions is re-established. According to the path of the regional platform institution sequence "1→2→3", the corresponding local codes "M001→M002→M006" are respectively formed into a sequential numbering chain. When constructing the linked list, each node structure includes the standard prefix number, matching order, local code value and the previous and next node number fields. If there is an interrupted record, such as "XY004" without a matching order, it is marked as skipped. Finally, the hierarchical relationship of the organizational structure between nodes is completed, and the affiliation structure data chain is generated to form an affiliation institution position index linked list.

[0029] See also Figure 4 , S3 steps are: S311: Based on the organization number field recorded in the home organization location index linked list, a comparison is performed with the requested organization number field recorded in the current request target field to determine whether the requested number is equal to the end node number in the linked list structure. If a match is successful, the current organization is marked as the end node of this path, and the node identification information is combined with the path termination status flag to generate a path end identification item; Based on the organization number fields "XY001", "XY002", "XY003" and "XY004" recorded in the affiliated organization position index chain table, an equivalence match is performed with the requested organization number "XY004" in the current requested target field. A field-by-field comparison method is used to determine whether the two field values ​​are consistent. If the match is successful, it means that the requesting organization is at the end node position in the affiliated path structure. The matching number is recorded as the end node of the path structure, and the node status is set to the end state identification item. The matching operation adopts the structure consistency judgment and index end verification mechanism. The field matching adopts a one-to-one corresponding precise equivalence judgment method. At the same time, the matching success number and its path index information are retained to form a structured identification tag as shown in the following table: Table 3 Path structure end point identification table Path Number Field Request Number Field Matching results Node ID XY001 XY004 Mismatch — XY002 XY004 Mismatch — XY003 XY004 Mismatch — XY004 XY004 match End node As shown in Table 3, only XY004 is a matching item, and the path end point identification item is finally obtained.

[0030] S312: Based on the path endpoint identifier, the records are arranged in the order of the attribution chain and a structural connection operation is performed. The organization number fields are sequentially merged into a unified structural expression string. The path connector is set using the HL7 reference information model specification and embedded in the standard structural syntax. The formula is: ; Calculate the path structure equilibrium value , verify whether the path string structure meets the hierarchical matching rules, save the output standard path field, where, Indicates the The position weight of each institution in the path, is the first The actual position number of the path node of the item, Number its ideal target position in the standard template, Indicates the total number of nodes in the path segment, Indicates the The degree of grammatical deviation of the bit character, Indicates the number of nodes in the path structure; According to the path endpoint identifier "XY004", all its preceding number fields in the belonging chain are obtained, including "XY001", "XY002" and "XY003". The structure combination operation is performed to splice these number fields in the order of the path structure. The connection method adopts the structure connection format in the HL7 information model, and the connector is set to "→". The combined structure path string is "XY001→XY002→XY003→XY004". In order to verify whether there is a hierarchical dislocation or semantic offset problem in the path structure, a path structure balance check is performed. Set the total number of nodes , ideal number of each node position , actual number , structural grammatical deviation , position weight , substitute into the formula: ; Perform the calculation: ; ; The numerical results show that the nodes in the structural path are consistent with the ideal template position, the syntax deviation is within the low deviation tolerance range, and the structural standard is met. The path string "XY001→XY002→XY003→XY004" is retained as the standard path field to obtain the standard path field.

[0031] The path structure balance value represents the overall coordination of the structural position and semantic level of each organization node in the attribution path. It is an important metric to measure whether the path string conforms to the HL7 reference information model specification. This value comprehensively reflects the offset difference between the actual sorting position of each node and the standard template position, and is corrected in combination with the grammatical normative differences of the character structure in the path to determine whether the path construction has hierarchical dislocation, disordered order, or semantic deviation. The closer the balance value is to 0, the more stable the path structure is. Conversely, the larger the value, the greater the degree of structural incoordination. The path may have problems such as incorrect node order and abnormal structural splicing. Therefore, this value plays a key role in path quality verification, access control path construction, and cross-system information interaction.

[0032] The operational logic of the formula is to comprehensively evaluate the degree of deviation between the actual position of each mechanism node in the structural path and the standard template position, and introduce the offset interference effect of the grammatical structure as a correction factor to measure the balance of the overall path structure. Specifically, the molecular part Indicates the offset of each path node Multiply by its corresponding structural weight , to amplify the contribution of the core nodes of the structure in the path offset. The more critical the node, the greater the impact of its offset. This term accumulates the weighted offsets of all path nodes by summing them up. The denominator consists of two parts. The first term It represents the square root of the path length, which is used to buffer the extreme impact of path length on balance and avoid the cumulative amplification of offset caused by more nodes. The second term It represents the average value of the offset of each node at the syntax level, and is used to evaluate whether the structural format of the path string has hierarchical deviation or splicing anomaly. It is used as a smoothing adjustment factor for the path. Finally, the path structure offset and syntax difference are normalized through additive combination. This formula not only reflects the overall consistency of the path structure position, but also introduces a quantitative judgment of the structural normativeness, forming an overall measurement of the rationality of the HL7 path field construction.

[0033] S313: Based on each organization node structure in the standard path field, record the access node number and path ownership identifier in the corresponding field, mark the access permission identifier bit for each sub-segment in the field in turn, and perform field ownership mapping operation based on the organization number field and the node permission comparison table to establish the organization path call structure set; According to the standard path field "XY001→XY002→XY003→XY004", access records are made for each path node one by one. Assuming the request number is still "XY004", the system assigns the access mark "✓" to this number and all the nodes before it, and records the "local" or "this organization" label in the path ownership mark field based on the ownership judgment. "XY004" in the path is the request target and is marked as "this organization", and the rest are marked as "local". The complete structural access mapping structure is as follows: Table 4 Structural path access relationship table Path node number Requesting institution number Node number Access ID Path attribution mark XY001 XY004 1 ✓ local XY002 XY004 2 ✓ local XY003 XY004 3 ✓ local XY004 XY004 4 ✓ This institution As shown in Table 4, each node has an access tag and a corresponding path attribution relationship label. Combined with the structure field, a field attribution mapping and a node access field table are established, and finally the path call structure set of this organization is formed.

[0034] See also Figure 5 , step S4 is: S411: Based on the path of the current organization, the structure path field in the structure set is called, and the organization number string connected by the connector "→" in the path field is obtained. The string segmentation operation is performed to split the path field into an ordered number sequence according to the connector, and the number field position index is recorded to establish a path number sequence. Get the structure path field content in the path call structure set of this organization. The read field format is 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 sequence number 1, XY002 is sequence number 2, and so on. Record the arrangement order of the path numbers and their positions. At the same time, generate a corresponding pair of starting numbers and target numbers to provide a basic data structure for subsequent jump identification and finally establish a path number sequence.

[0035] S412: Based on the path number sequence, adjacent organization number fields in the sequence are sequentially judged for differences. The judgment criteria are whether there are character inconsistencies, length changes, or structural displacements in the number field content. The change characteristics between the numbers are compared one by one and the number of changes is accumulated and counted. The number difference points and change directions are recorded to obtain the cumulative number change results. Based on the path number sequence, adjacent number pairs are sequentially checked for changes. The judgment criteria include character differences, length changes, and overall consistency of the number structure. If there is a difference in the character content of the two number fields, such as the different suffixes of "XY001" and "XY002", it is marked as "structure replacement". If the number change is only in the prefix of the number structure, it is marked as "prefix adjustment". If the two numbers are completely consistent, it is determined that there is no change. In each detection behavior, the starting number, target number, change situation, change type and change range, 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: Table 5 Path number jump example table Starting number Target Number Whether to change Type of change Range of change XY001 XY002 yes Structural replacement 2 XY002 XY003 yes Prefix Adjustment 1 XY003 XY004 no none 0 XY004 XY004 no none 0 As shown in Table 5, two field change records are generated, corresponding to hop indexes 1 and 2. The magnitude of each change reflects the degree of change. The overall change frequency of the path number is further accumulated to obtain the cumulative result of the number change.

[0036] S413: Based on the accumulated number change results, a node jump record table is created for the number field sequence in the path. The node jump record table records the number change content, starting number, target number, change type, and change range of each jump. Each change is assigned a unique index and the difference type is marked. A detailed table of the path hop count structure is created. Based on the cumulative numbering changes, the change details of each hop number field in the path are organized. The change items "XY001→XY002" and "XY002→XY003" in the path segments are recorded as jump events respectively. The change types are classified as structure replacement and prefix adjustment. The path jump frequency is calculated. The jump density is defined as the ratio of the number of changed hops to the total number of hops in the path. Here, the total number of hops is 3 and the number of changed hops is 2. The jump density is calculated as 2÷3≈0.67. At the same time, a unique index number is assigned to each hop change record, and a structured field index list is established. All changed segments in the path structure field set are set with identifiable tags. Finally, a number jump hierarchy table is constructed to generate a path hop count structure detailed table.

[0037] See also Figure 6 , step S5 is: S511: Based on the field contents in the path hop count structure detail table, extract the path number corresponding to each path, obtain the hop count field corresponding to the corresponding number, combine the path number with the corresponding hop count, check the path number, and establish a correspondence between the number and the hop count to generate a path hop count dataset; After obtaining the path number field in the path hop count structure details table, the system searches for each path information in order of number. For each path, the hop count field value is extracted through field comparison and recorded as the hop count value of the path. During 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 details table. If there are multiple hop count records for a certain path number, the number duplication is screened and the hop value of the last record is retained. The system stores the number and the corresponding hop count in the form of a key-value pair and completes this operation for all path numbers one by one. After completion, a complete path hop count dataset is constructed. Each record in the dataset consists of the path number and its corresponding hop value, which is suitable for subsequent permission verification scenarios. For example, in a medical system, the path number from institution A to institution B is set to A1001, and its corresponding hop count is 3. After the system retrieves and confirms that there are no duplications, it is recorded as A1001:3. The other paths execute the same processing flow in sequence to construct the data items shown in the following table: Table 6 Path hop count dataset Path number Hop Value A1001 3 A1002 2 B2003 4 C3005 1 As shown in Table 6, the table lists the paths and their hop count records extracted from the structure details table, and the data has completed the field mapping between the number and the hop count.

[0038] S512: Based on the path number field in the path hop count data set, the maximum hop count threshold field in the matching authority matrix table is matched. The maximum hop count value in each record is extracted, and a bitwise merge operation is performed using the path number as the key value. 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. Based on the path number in the path hop count dataset, the permission control rule fields in the permission matrix table are read in sequence, and the corresponding maximum hop count threshold field content is matched. The set hop count upper limit of each path number in the permission matrix table is retrieved. The number consistency must be maintained during the operation. Missing items are filled with null values ​​and marked. Then, the maximum hop count field is bound to the aforementioned path hop count field row by row to generate a unified hop count threshold comparison record table. In this table, each record consists of three items: path number, actual hop count, and maximum allowed hop count. For example, the maximum allowed hop count of path number A1001 in the permission matrix table is 2, which is merged with the actual hop count of 3 in the path hop count dataset to form A1001:3-2. The system completes the field merging operation for each record in this way, providing comparison source data for the next step of judgment, as shown in the following table: Table 7 Hop count threshold comparison record table Path number Actual hop count Maximum allowed hops A1001 3 2 A1002 2 2 B2003 4 3 C3005 1 1 See Table 7, which completes the splicing of the path number and the two types of hop number fields, providing a numerical basis for the logical judgment process.

[0039] S513: Compare each record in the record table according to the hop count threshold, extract the actual hop count field and the maximum allowed hop count field, and perform a field value difference determination operation. 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 a cross-institutional medical data connection review result is generated; Based on the hop count threshold, each path record in the record table is compared. The system calls the actual hop count corresponding to the path number and the maximum allowed hop count field content, performs a numerical comparison item by item, and determines whether the actual hop count in each record is greater than the maximum allowed hop count. During the judgment process, the field difference rule is used to construct a Boolean value flag. If the actual hop count minus the maximum hop count is greater than 0, the entry is marked as a violation; otherwise, it is a compliance entry. Compliance and violation entries are recorded as different field sets and indexed by path number. After aggregation, a unified review result list is generated. In one example, if the actual hop count of path A1001 is 3 and the maximum allowed hop count is 2, the difference is 1, indicating a violation record. The system writes A1001 to the violation entry set and traverses the remaining records in a similar manner to construct the cross-institutional medical data docking review results. The results are structured and grouped by violation and compliance categories for subsequent system control response operations. The final result generated by this execution process is: cross-institutional medical data docking review results.

[0040] A cross-institutional medical data docking system, comprising: The identity code 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, builds an extended structure, and generates a list of standard identity field formats; The institution index matching module reads the platform institution code and the local mutual recognition field based on the code prefix of the standard identity field format list, performs equal value matching, and generates an index chain list of the affiliated institution location; The path structure combination module determines the path endpoint node based on the location index linked list of the affiliated institution and the number field of the requested target institution, concatenates the path fields, and generates the path call structure set of the institution. The hop count path extraction module extracts the organization number based on the path field in the organization path call structure, determines the difference between adjacent numbers and accumulates the hop count to generate a path hop count structure detail table; The permission path verification module performs hop difference judgment and marks compliance based on the hop field in the path hop structure details table and the maximum hop allowable threshold, and generates cross-institutional medical data docking review results.

[0041] The above are merely preferred embodiments of the present invention and do not limit the present invention in any other form. Any technician familiar with the profession may use the technical content disclosed above to change or modify it into an equivalent embodiment with equivalent changes and apply it to other fields. However, any simple modification, equivalent change and modification made to the above embodiment based on the technical essence of the present invention without departing from the content of the technical solution of the present invention shall still fall within the scope of protection of the technical solution of the present invention.

Claims

1. A cross-institutional medical data docking method, characterized in that: The following steps are involved: S1: Obtain the patient ID and registration number of the medical institution's practice license from the medical institution in the region, append the institution's unique identification code to the front of the patient ID as a prefix, and generate a list of standard identity field formats; S2: performing an equal value match based on the prefix field in the standard identity field format list, the institution code field of the regional health information platform, and the index field of the local institution mutual recognition code table, to determine the attribution path and generate an attribution institution location index chain table; S3: Based on the organization number field recorded in the home organization location index linked table and the current requesting organization number, the current organization is determined to be the path endpoint node, and the paths are combined into the HL7 reference information model structure path fields in the transmission order, and the access nodes and the home relationships are recorded to generate the path call structure set of the current organization; S4: extracting numbers item by item according to the content and arrangement order of the path call structure set of the organization, counting the number of number changes according to adjacent organization number fields, and generating a path hop count structure detail table; S5: Based on the path hop count structure detailed table, the hop count difference between the two fields is counted, and the docking request that exceeds the maximum hop count threshold is marked as a violation entry, and a cross-institutional medical data docking review result is generated.

2. The cross-institutional medical data docking method according to claim 1, characterized in that: The standard identity field format list includes a unified prefix structure, a standard numbering format, and identity extension rules; the affiliated institution location index linked list includes an institution index sequence, a path sequence mark, and affiliated confirmation information; the institution path call structure set includes an HL7 path field, a node access identifier, and an affiliated node mark; the path hop structure details table includes hop records, institution sequence differences, and path segment division information; the cross-institutional medical data docking review results include authority compliance status, violation item identifier, and hop threshold classification results.

3. The cross-institutional medical data docking method according to claim 1, characterized in that: The steps for obtaining the standard identity field format list are as follows: S111: Based on the data content provided by the medical institutions connected in the region, the original patient number field and the medical institution practice license registration number field are obtained, the medical institution practice license registration number is used as a participating item, and is appended as a string prefix to the front of the corresponding original patient number to generate a prefix appended number result; S112: Based on the prefixed numbering result and the original patient number field, all number value lengths, character rules, and uniqueness are screened. The screening is based on whether the number of characters meets the standard numbering length range and whether there are illegal symbols in the character composition, and a unified number set after screening is obtained. S113: Based on the correspondence table between the unified number set after screening 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-institutional medical data docking method according to claim 1, characterized in that: The steps for obtaining the home institution location index linked list are specifically as follows: S211: Based on the prefix field in the standard identity field format list and in combination with the institution code field corresponding to 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 to generate an equal value matching number index result; S212: Based on the equal-value matching number index result, combined with the institution mutual recognition code table index field in the local institution code table, the mutual recognition code field content under the same index value is obtained, the attribution path sequence position corresponding to the same institution in different platforms is determined, and the path position comparison is performed for institutions with duplicate attribution paths, the attribution path offset is calculated, and path matching offset data is generated; S213: Based on the mapping relationship between the path matching offset data and the original institution index number, filter out abnormal records with an offset greater than the belonging path offset tolerance threshold, perform sequential number identification processing on all legal path structure records, and establish a belonging institution location index chain list.

5. The cross-institutional medical data docking method according to claim 1, characterized in that: The steps for obtaining the path call structure set of the institution are specifically as follows: S311: Based on the organization number field recorded in the home organization location index linked list, a comparison is performed with the request organization number field recorded in the current request target field to determine whether the request number is equal to the end node number in the linked list structure. If a match is successful, the current organization is marked as the end node of this path, and the node identification information is combined with the path termination status mark to generate a path end identification item; S312: Based on the path endpoint identifier, the records are arranged in the order of the records in the attribution chain, and a structural connection operation is performed to sequentially merge the organization number fields into a unified structural expression string. The path connector is defined using the HL7 reference information model specification and embedded in the standard structure syntax. The path structure balance value is calculated, and it is verified whether the path string structure meets the hierarchical matching rules. The output standard path field is saved. S313: According to each organization node structure in the standard path field, record the access node number and path ownership identifier in the corresponding field, mark the access permission identifier for each sub-segment in the field in turn, and perform field ownership mapping operations in combination with the organization number field and the node authority comparison table to establish the organization path call structure set.

6. The cross-institutional medical data docking method according to claim 1, characterized in that: The steps for obtaining the path hop count structure detailed table are specifically as follows: S411: Based on the structure path field in the organization path call structure set, obtain the organization number string connected by the connector in the path field, perform a string segmentation operation, split the path field into an ordered number sequence according to the connector, record the number field position index, and establish a path number sequence; S412: Based on the path number sequence, adjacent organization number fields in the sequence are sequentially judged for differences. The judgment criteria are whether there are character inconsistencies, length changes, or structural displacements in the number fields. The change characteristics between the numbers are compared one by one, and the number of changes is accumulated and counted. The number difference points and change directions are recorded to obtain the cumulative number change results. S413: Based on the accumulated results of the numbering changes, a node jump record table is established for the numbering field sequence in the path, and the content, starting number, target number, change type and change range of each jump number change are recorded one by one. A unique index is assigned to each change and the difference type is marked to establish a detailed table of the path hop structure.

7. The cross-institutional medical data docking method according to claim 1, characterized in that: The specific steps for obtaining the cross-institutional medical data docking review results are as follows: S511: Based on the field contents in the path hop count structure detailed table, extract the path number corresponding to each path, obtain the hop count field corresponding to the corresponding number, combine the path number with the corresponding hop count, check the path number, establish a correspondence between the number and the hop count, and generate a path hop count dataset; S512: Based on the path number field in the path hop count data set, the maximum hop count threshold field in the matching authority matrix table is matched, the maximum hop count value in each record is extracted, and a bitwise merge operation is performed using the path number as the key value. 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: Compare each record in the record table according to the hop count threshold, extract the actual hop count field and the maximum allowed hop count field, and perform a field value difference judgment operation. 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 a cross-institutional medical data docking review result is generated.

8. A cross-institutional medical data docking system, characterized by: The system is used to implement the cross-institutional medical data docking method according to any one of claims 1 to 7, comprising: The identity code 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, builds an extended structure, and generates a list of standard identity field formats; The institution index matching module reads the platform institution code and the local mutual recognition field based on the code prefix of the standard identity field format list, performs equivalence matching, and generates an attribution institution location index chain table; The path structure combination module determines the path end node according to the home institution position index linked list and the requested target institution number field, concatenates the path fields, and generates the path call structure set of the current institution; The hop count path extraction module extracts the organization number based on the path field in the organization path call structure, determines the difference between adjacent numbers and accumulates the hop count to generate a path hop count structure detailed table; The authority path verification module performs hop difference judgment and marks compliance based on the hop field in the path hop structure details table, combined with the maximum hop allowable threshold, and generates a cross-institutional medical data docking review result.

Images