Physical examination item mutual exclusion and correlation configuration and order checking method and system

Abstract

The present application relates to the technical field of physical examination information system, and discloses a physical examination item mutual exclusion and correlation relationship configuration and order checking method and system. The method maintains mutual exclusion relationship table, correlation relationship table and exception white list, forms a relationship rule library which can be adjusted online and takes effect immediately; when a main item with an association mark is selected, the associated items are automatically brought out and included in the cost; when items are added one by one and the order is saved, mutual exclusion detection and correlation integrity detection are performed, and mutual exclusion detection is skipped for effective exception items and a trace is left; item change events are recorded, the difference between the refund, the additional charge and the price adjustment is automatically calculated, and the order file with traceable changes is formed. The present application can reduce the conflict of item combination and the omission of associated items, improve the order checking efficiency, and realize the whole process trace of exception exemption, cost recalculation and item change.

Description

Technical Field

[0001] This invention relates to the field of information management and business rule verification technology, specifically to the configuration and maintenance of mutual exclusion relationships, association relationships and exception rules of items in a physical examination information system, as well as methods and systems for real-time verification of invoices, automatic population of associated items, tracking of item changes and automatic recalculation of costs.

[0002] This invention also relates to rule base behavior consistency verification, local context risk analysis, and incremental cost recalculation technology based on the location of the impact range of changes. Background Technology

[0003] In a health checkup information system, order registration serves as the data entry point for business processes such as item selection, cost generation, examination execution, and result archiving. Operators typically need to select multiple health checkup items from a database and generate an order. Since different items may have different constraints in terms of examination methods, execution time, sample requirements, and combination dependencies, whether the item combination conforms to preset business rules will affect the accuracy of subsequent order execution and cost settlement.

[0004] Existing technologies typically complete order processing through a project library and project selection interface. The mutual exclusion and association relationships between projects are mainly determined by operators based on experience, or implemented through static suggestion lists or fixed program conditions. For associated projects, operators need to select the main project and then search for and add the corresponding project; for mutually exclusive projects, manual verification is required to check for conflicts between the selected projects and the projects to be added in the current order. Although some systems can provide mutual exclusion suggestions, their relationship conditions are usually fixed in the program, requiring program adjustments and redeployment when relationships are added, modified, or deactivated.

[0005] As the project library and relationship rules accumulate over time, the number of relationship records will continue to increase. Rules formed at different maintenance stages may also exhibit duplication, transitive implication, coexistence of mutual exclusion and association, or circular associations. When performing validation by traversing each rule one by one, the validation time tends to increase with the number of rules. Relying solely on the registered precise relationship records makes it difficult to provide auxiliary prompts for project combinations that have not yet been included in the rule library but show a high risk of conflict in historical orders. Furthermore, in business scenarios with valid exception conditions, systems lacking exception configuration and the use of logging mechanisms struggle to balance unified validation with special business processing.

[0006] Therefore, the existing technology has at least the following problems: First, there is a lack of a unified, online maintainable and immediately effective structured rule carrier for mutual exclusion, association and exception conditions of projects. There is also a lack of a real-time verification mechanism for connecting projects and saving orders. This can easily lead to problems such as mutually exclusive projects entering orders at the same time, missing associated projects, or the exception release process being untraceable. Second, after a project is discontinued, replaced, price adjusted or detailed adjustments are made, it is difficult to accurately locate the affected orders and automatically calculate the corresponding refunds, supplements and price differences. There is a lack of complete association records between the reasons for the change, the cost details and the order version. Summary of the Invention

[0007] The technical problem to be solved by this invention is to provide a method and system for configuring and verifying the mutual exclusion and association relationships of physical examination items, transforming mutual exclusion relationships, association relationships, and exception whitelists into a configurable, maintainable, and immediately effective relationship rule library, and performing verification at two triggering stages: item addition and order saving, so as to reduce the possibility of mutually exclusive items entering the order at the same time, the omission of associated items, and the untraceability of the exception release process; at the same time, it records item change events, locates affected orders, and automatically calculates cost changes, so that item changes, cost recalculation, and order version can be traced and linked.

[0008] To address the aforementioned technical problems, this invention provides a method for configuring mutual exclusion and association relationships for physical examination items and for verifying order placement. The method includes: maintaining a mutual exclusion table, an association table, and an exception whitelist based on medical business rules and an item library to obtain an online adjustable and immediately effective relationship rule library; automatically populating associated items and calculating their costs when a main item with an association marker is selected on the order placement interface, based on the relationship rule library, to obtain an associated item combination; performing mutual exclusion checks when adding items and saving orders, based on the associated item combination, the mutual exclusion table, and the exception whitelist, prompting and blocking when a mutual exclusion record is found, skipping the mutual exclusion check for items in the exception whitelist and leaving a record, thus obtaining an effective physical examination order; and recording the content before and after the change and the operator to form a change history library based on the item change operation, and automatically recalculating the cost changes of the effective physical examination order based on the change history library, thus obtaining a traceable order file.

[0009] Furthermore, the step of maintaining a mutual exclusion table, an association table, and an exception whitelist based on medical business rules and a project library to obtain an online adjustable and immediately effective relationship rule library includes: establishing the mutual exclusion table based on the medical business rules and the project library, with project pairs as the recording unit; the mutual exclusion table records mutually exclusive project pairs, mutual exclusion types, and effective status; the mutual exclusion types include same-day mutual exclusion and same-item mutual exclusion; and establishing the association table based on the composite dependency requirements in the medical business rules, with the main project and related projects as the recording units; the association table records the related projects automatically populated when the main project is selected. Output quantity; based on exemption requirements for special medical scenarios, establish the exception whitelist with projects or project pairs as recording units, the exception whitelist specifying the exception reason and validity period; provide the add operation interface, modify operation interface and deactivate operation interface for the mutual exclusion relationship table, the association relationship table and the exception whitelist, the mutual exclusion relationship table, the association relationship table and the exception whitelist are collectively referred to as the relationship configuration table; collect the relationship configuration table after being adjusted by the add operation interface, modify operation interface and deactivate operation interface, and make the adjustment result of the relationship configuration table take effect immediately in the order verification to obtain the relationship rule base.

[0010] Furthermore, based on the medical business rules and the project library, a mutual exclusion table is established using project pairs as recording units. The mutual exclusion table records mutually exclusive project pairs, mutual exclusion types, and effective status. The mutual exclusion types include same-day mutual exclusion and same-item mutual exclusion. This includes: filtering project pairs with conflicting examination methods and project pairs with conflicting sampling requirements from the project library; project pairs with conflicting examination methods are those containing a specific examination method; and project pairs with conflicting sampling requirements are those with opposite pre-sample collection status requirements; and arranging the filtered project pairs in ascending order of project number as project pair keys. The project key is used as the record identifier of the mutual exclusion table; for records with the mutual exclusion type of same-day mutual exclusion, the same physical examination date of the examinee is used as the conflict determination range; for records with the mutual exclusion type of same-order mutual exclusion, the same physical examination order is used as the conflict determination range; an effective status field is set for each record in the mutual exclusion table, and only records with the effective status field being enabled participate in the order verification; a maintenance time field and a maintenance person field are set for each record in the mutual exclusion table, and a maintenance log comparing the values ​​before and after the change is generated when the mutual exclusion table is changed, thus obtaining the mutual exclusion table.

[0011] Furthermore, the step of automatically extracting related items and adding them to the cost when a main item with an association tag is selected on the order page based on the relationship rule base, to obtain a combination of related items, includes: receiving an item selection operation on the order page; determining whether the selected item has the association tag in the relationship table; if the association tag exists, searching the relationship table to determine the related items corresponding to the main item and the number extracted; writing the related items into the current order item set according to the number extracted, and accumulating the order cost according to the unit price of the related items; marking the source of the extracted items as the main item, and providing manual confirmation and removal operations for the related items, and simultaneously deducting the order cost corresponding to the related items when the removal operation is performed; and aggregating the main item and the related items retained by the manual confirmation operation into a complete set to obtain the combination of related items.

[0012] Further, when the associated marker exists, retrieving the association table to determine the associated projects and the number of items to be taken out corresponding to the main project includes: retrieving the association table using the project number of the main project as the key to obtain all associated records with the main project as the record unit; reading the associated project number and the number of items to be taken out from all the associated records, and filtering the associated records in the all associated records whose effective status is disabled; determining whether the project corresponding to the read associated project number already exists in the current order project set, and if it already exists, it will not be taken out again, and if it does not exist, it will be included in the project set to be taken out; predicting the mutual exclusion conflict between the projects in the project set to be taken out and the current order project set according to the mutual exclusion records of the projects in the project set to be taken out in the mutual exclusion table, and marking the projects in the project set to be taken out as pending manual confirmation when the mutual exclusion conflict exists; and determining the associated projects and the number of items to be taken out corresponding to the main project according to the project set to be taken out and the number of items to be taken out.

[0013] Furthermore, the step of performing mutual exclusion checks when adding items and saving orders based on the associated item combinations, the mutual exclusion table, and the exception whitelist, prompting and blocking when a mutual exclusion record is hit, and skipping the mutual exclusion check for items in the exception whitelist while leaving a record, to obtain an effective health check order, includes: when adding items one by one, combining each item in the current order item set with the item to be added to obtain a set of item pairs to be verified; indexing the mutual exclusion table by item number, and detecting item pairs in the set of item pairs to be verified that have a mutual exclusion record with an enabled status. For the matched items, a pop-up prompt will appear listing the conflicting items, preventing the items to be added from being added to the order; for items listed in the exception whitelist and within the validity period, the mutual exclusion check will be skipped and allowed, while an exception usage record will be generated; when the order is saved, the mutual exclusion check will be repeated, and an association integrity check will be performed, which verifies that each associated item corresponding to the main item in the associated item combination exists in the current order item set; after both the mutual exclusion check and the association integrity check pass, the order will be set as the effective medical examination order.

[0014] Further, the step of skipping the mutual exclusion check and allowing entry for items included in the exception whitelist and within the validity period, while generating an exception usage record, includes: before performing the mutual exclusion check, determining one by one whether the items in the set of items to be verified are included in the exception whitelist; for items included in the exception whitelist, comparing the current system time with the validity period corresponding to the included items in the exception whitelist, and determining that the exception is established when the current system time is within the validity period; when the exception is established, the combination of the included items and any item in the current order item set skips the mutual exclusion check and is allowed; generating the exception usage record, which includes the operator identifier, the release time, the exception reason, and the released item pair; archiving the exception usage record with the order number, and automatically resuming the mutual exclusion check for the included items after the validity period expires.

[0015] Furthermore, the process of recording the content before and after the change and the operator based on the project change operation to form a change history database, and automatically recalculating the cost changes of the effective medical examination order based on the change history database to obtain a traceable order file, includes: when a discontinuation operation, replacement operation, price adjustment operation, or detailed item adjustment operation occurs in the project database, collecting the project content before the change and the project content after the change; writing the project content before the change, the project content after the change, the reason for the change, the change time, and the operator's identifier into the change history database to form a change event record; comparing the change event record with the project set of the effective medical examination order to determine the removed items, added items, and price adjustment items in the effective medical examination order; calculating the refund amount for the removed items, the supplementary fee amount for the added items, and the price difference before and after the change for the price adjustment items, accumulating them to obtain the cost change, and updating the receivable amount of the effective medical examination order; associating the details of the cost change with the version number of the effective medical examination order for archiving, and pushing the change notification to the examinee and the billing process to obtain the traceable order file.

[0016] Furthermore, the method further includes: performing behavior sampling on the relation rule base using randomly generated item set samples, recording the mutual exclusion interception results and association carry-out results output by the relation rule base under each item set sample, and obtaining the rule base behavior benchmark; for each rule in the relation rule base, removing the tested rule and re-performing all the behavior sampling, when the output of all the item set samples is consistent with the rule base behavior benchmark, determining that the tested rule is a redundant rule implied by other rules and adding it to the redundant rule list; identifying the transitive implication chain composed of mutual exclusion relationships and association relationships, and merging the rules implied by upstream rules in the transitive implication chain. The merged rule set is obtained; conflict detection is performed on the merged rule set to detect records where mutually exclusive and associated relationships coexist on the same item pair, records where the associated relationship leads to a cycle, and records where mutually exclusive closed chains contradict each other, and a rule conflict detection report is output; the item pair relationships in the rule set after processing the rule conflict detection report are encoded into a bitmap index structure, and the bitmap index structure is directly indexed to match the rules during order verification, replacing the traversal of each rule, to obtain a compressed indexed relational rule library; the compressed indexed relational rule library is verified against the rule library behavior benchmark, and the output of all the item set samples is consistent with the rule library behavior benchmark before going online.

[0017] Furthermore, the method also includes: based on historical order data and on-site inspection conflict records, statistically analyzing the frequency of co-occurrence of the same order for each item pair, the frequency of on-site rescheduling or cancellation after co-occurrence, and the risk markers reported by departments; obtaining a weighted summation of the contextual risk scores for each item pair to form a local contextual risk channel; constructing a precise rule channel from the mutual exclusion table; outputting a deterministic conflict conclusion when the mutual exclusion record is hit; directly intercepting when the precise rule channel hits and the local contextual risk channel does not participate in the judgment; accumulating the contextual risk scores of each item pair in the current order item set to obtain a combined risk score; adaptively adjusting the precise rule channel based on the interception accuracy feedback of the precise rule channel and the local contextual risk channel within a set period. The fusion weight and interception threshold of the rule channel and the local context risk channel are determined. When the number of false alarms in the local context risk channel reaches the first threshold, the interception threshold is increased. After confirmation, the missed alarm combinations in the local context risk channel are included in the mutual exclusion table and taken over by the precise rule channel. Soft interception is performed on project combinations whose combined risk scores exceed the interception threshold, and a risk warning and alternative project suggestions are displayed. Operators then perform release or adjustment operations. Project combinations that have undergone the release operation are added to the observation list. When the number of release operations reaches the second threshold, the context risk score of the project combination is decreased. When the number of adjustment operations reaches the third threshold, the project combination is proposed to be included in the mutual exclusion record. Both the second threshold and the third threshold are greater than zero.

[0018] Furthermore, the method also includes: performing forward impact propagation starting from the change event record, determining the direct impact set and indirect impact set along the order level, project level, and cost level, wherein the direct impact set is a set of orders containing the change project, and the indirect impact set is orders containing the associated project due to coupling between the association table and the change project, as well as orders due to conflicts between the mutual exclusion table and the replacement item, thus obtaining a change impact scope set; performing reverse location tracing for each order in the change impact scope set, reversely determining the cause chain of each order being affected, wherein the cause chain includes the involved change event record, the relationship record traversed, and the involved cost item, generating an order-level impact cause description, thus obtaining a result with a cause chain. A list of affected orders is generated. Incremental cost recalculation is performed only on orders in the affected order list with cause chains. The cost change is calculated based on the refund amount of the removed items, the supplementary fee amount of the added items, and the price difference of the adjusted items. Orders not included in the affected order list with cause chains are not recalculated. A change impact report is generated based on the results of the incremental cost recalculation and the cause chains. The change impact report includes the number of affected orders, the total cost change, the cost change details of each order, and the corresponding cause chains. The change impact report is pushed to the billing process and the inspected object, and the change impact report is associated with the change event records in the change history database and archived to obtain a change impact file.

[0019] This invention also provides a system for configuring and verifying the mutual exclusion and association relationships of physical examination items, including: a relationship configuration maintenance module, used to maintain a mutual exclusion relationship table, an association relationship table, and an exception whitelist based on medical business rules and an item library, to obtain a relationship rule library that can be adjusted online and takes effect immediately; an associated item extraction module, used to automatically extract associated items and include them in the cost when a main item with an association mark is selected in the order interface based on the relationship rule library, to obtain an associated item combination; a mutual exclusion verification and interception module, used to perform mutual exclusion detection when adding items one by one and saving orders based on the associated item combination, the mutual exclusion relationship table, and the exception whitelist, prompting and intercepting when a mutual exclusion record is hit, skipping the mutual exclusion detection for items in the exception whitelist and leaving a trace, to obtain an effective physical examination order; and a change traceability and recalculation module, used to record the content before and after the change and the operator to form a change history library based on the item change operation, and automatically recalculate the cost change of the effective physical examination order based on the change history library, to obtain a change traceable order file.

[0020] Because a relational rule base composed of mutual exclusion tables, association tables, and exception whitelists is used, which can be adjusted online and take effect immediately, and mutual exclusion checks and association integrity checks are performed when adding items and saving orders, item relationships no longer rely on operators to memorize them item by item, reducing the possibility of mutual exclusion items entering orders simultaneously and the omission of association items. By performing conditional skip checks on valid exception items and generating exception usage records, the release needs of special business scenarios can be met while maintaining unified rule constraints. Furthermore, through rule base behavior benchmarks, redundant rule detection, conflict detection, and bitmap index structure, the impact of redundant rules on verification efficiency can be reduced while maintaining consistent verification behavior. Through complementary judgment of precise rule channels and local context risk channels, auxiliary prompts can be provided for risk combinations that have not yet been included in the mutual exclusion table.

[0021] By recording the project content before and after the change, the reason for the change, the time of the change, and the operator's identification, and by archiving the details of cost changes in association with the order version number, the project changes and cost adjustments have traceable data basis. By determining the scope of the change's impact through forward impact propagation and generating the cause chain through reverse location tracing, and by performing incremental cost recalculation only on the affected orders, the processing overhead caused by irrelevant orders participating in the recalculation can be reduced. At the same time, the refund amount, the supplementary fee amount, and the price difference amount can all be mapped to the specific change event, relationship record, and cost item. Attached Figure Description

[0022] Figure 1 This is a schematic diagram of the overall process of configuring mutual exclusion and association relationships of physical examination items and verifying order issuance provided in an embodiment of the present invention.

[0023] Figure 2 This is a schematic diagram of the configuration and maintenance process for the project relationship rule base provided in an embodiment of the present invention;

[0024] Figure 3 This is a schematic diagram of the automatic item population and cost linkage process provided in an embodiment of the present invention;

[0025] Figure 4 This is a schematic diagram of the dual-trigger mutual exclusion verification and exception exemption process provided in an embodiment of the present invention;

[0026] Figure 5 This is a schematic diagram of the project change tracking and automatic cost recalculation process provided in an embodiment of the present invention;

[0027] Figure 6 This is a schematic diagram of the module structure of the system for configuring mutual exclusion and association of physical examination items and verifying order issuance, provided in an embodiment of the present invention. Detailed Implementation

[0028] The present invention will be further described below with reference to the accompanying drawings and embodiments. It should be understood that the following embodiments are used to illustrate the technical solutions of the present invention, and are not intended to limit the scope of protection of the present invention. Where there is no conflict, the technical features of the various embodiments can be combined with each other.

[0029] Example 1

[0030] like Figure 1 As shown, this embodiment provides a method for configuring mutual exclusion and association relationships of physical examination items and for verifying order issuance, including the following steps:

[0031] S1. Based on medical business rules and project library, maintain mutual exclusion relationship table, association relationship table and exception whitelist to obtain a relationship rule library that can be adjusted online and take effect immediately;

[0032] The project library stores project attributes such as project number, project name, project unit price, effective status, and project execution requirements. The mutual exclusion table describes the constraint that two projects cannot both enter an order within a preset conflict judgment range; the association table describes the associated projects that need to be included when selecting the main project and the quantity included; the exception whitelist describes projects or project pairs that do not participate in the corresponding mutual exclusion detection within a preset validity period.

[0033] In one implementation, the system stores each relationship configuration table in a relational database and updates the rule version number when a relationship configuration table is added, modified, or deactivated. The order verification service refreshes the in-memory relational rule database by subscribing to rule version change messages, periodically reading the version number, or receiving proactive pushes from the configuration service, so that the adjustment results are immediately applied to subsequent project additions and order saving operations.

[0034] S2. Based on the relationship rule base, when a main item with an association tag is selected in the order opening interface, the associated items are automatically populated and the costs are included to obtain a combination of associated items;

[0035] The system retrieves the association table using the project number of the selected project. If a valid association record exists, it reads the corresponding associated project and the quantity to be removed. After excluding projects already existing in the current order project set, the remaining associated projects are written to the current order project set. For each associated project, the system records its source so that the project quantity and order cost can be processed synchronously when the main project is removed, the association relationship changes, or an operator performs a manual removal operation.

[0036] In one implementation, the order cost can be expressed as:

[0037] Equation (1)

[0038] in, This indicates the amount receivable for the current order. This indicates the number of items in the current order item set. Indicates the first The number of projects Indicates the first The unit price of each item. After the associated items are written into the current order item set, the system updates the amount receivable according to their quantity and unit price.

[0039] S3. Based on the associated project combination, the mutual exclusion relationship table and the exception whitelist, perform mutual exclusion detection when adding projects and saving orders one by one. When a mutual exclusion record is hit, prompt and block it. Skip the mutual exclusion detection for projects in the exception whitelist and leave a trace to obtain an effective physical examination order.

[0040] When adding items one by one, the system pairs the item to be added with each item in the current order's item set, and sorts the item numbers in the pair to form the pair key. The system first checks if a valid exception whitelist record exists for the corresponding item or pair; if no valid exception record exists, it then uses the pair key to search the mutual exclusion table. If a mutual exclusion record in the enabled state is found, the system outputs the conflicting item pair and conflict type, and prevents the item to be added from entering the order.

[0041] When an order is saved, the system re-executes mutual exclusion checks on the set of order items and performs integrity checks on the associated items corresponding to each main item. By performing pre-validation during the item addition phase and final validation during the order saving phase, the possibility of item combinations that fail validation taking effect due to concurrent modifications, manual removal of associated items, or temporary rule adjustments can be reduced.

[0042] When a valid exception record is used, the system records at least the operator's identifier, release time, exception reason, released item pair, and order number. Because exception releases have validity period checks and usage records, unified mutual exclusion constraints can be executed together with the preset exception handling mechanism, and the specific release process can be traced based on the order number.

[0043] S4. Based on the project change operation, record the content before and after the change and the operator to form a change history database, and automatically recalculate the cost change of the effective physical examination order according to the change history database to obtain the order file with traceable change.

[0044] Project change operations include deactivation, replacement, price adjustment, and detailed adjustment. The system encapsulates each operation as an independent change event record, saving the content before the change, the content after the change, the reason for the change, the change time, and the operator's identifier. For effective medical examination orders affected by the changes, the system identifies removed items, added items, and price-adjusted items, calculating the refund amount, supplementary fee amount, and price difference amount respectively.

[0045] Cost changes can be expressed as:

[0046] Equation (2)

[0047] in, Indicates changes in costs, This indicates the supplementary fee amount corresponding to the newly added item. This indicates the refund amount corresponding to the removed item. This indicates the price difference amount for the adjusted item. The updated receivable amount is the sum of the receivable amount before the change and the aforementioned cost change.

[0048] The system generates a new order version number for each recalculation and archives the change event record, cost change details and order version number together, thereby forming an order file that can trace the reasons for project changes and the basis for cost calculation.

[0049] Example 2

[0050] like Figure 2 As shown, this embodiment, based on embodiment 1, further defines the configuration and maintenance process of the relational rule base, including:

[0051] S1.1. Based on the medical business rules and the project library, establish the mutual exclusion relationship table with project pairs as the recording unit. The mutual exclusion relationship table records mutually exclusive project pairs, mutual exclusion types and effective status. The mutual exclusion types include same-day mutual exclusion and same-item mutual exclusion.

[0052] In one specific implementation, each mutually exclusive record includes at least a first item number, a second item number, an item key, a mutual exclusion type, an effective status, a maintenance time, and a maintainer. The item key is generated by concatenating the two item numbers in a preset order to eliminate duplicate records of the same item pair due to different item number orders.

[0053] Same-day mutual exclusion is used to restrict two items from coexisting on the same medical examination date for the same examinee, while same-order mutual exclusion is used to restrict two items from coexisting within the same order. The system can select the appropriate query range based on the mutual exclusion type, without having to apply the same time or order boundary to all mutually exclusive records.

[0054] S1.2. Based on the combination dependency requirements in the medical business rules, establish the association table with the main item and related items as the recording unit. The association table records the related items automatically brought out when the main item is selected and the number of items brought out.

[0055] The relationship table can further include the relationship record number, main project number, related project number, quantity to be pulled out, effective status, and maintenance information. A main project can correspond to one or more related projects, and the same related project can be referenced by multiple main projects. To prevent related projects from being written to the order repeatedly, the system verifies whether the corresponding project already exists in the current order project set before performing the pull-out operation.

[0056] S1.3. Based on the exemption requirements of special medical scenarios, establish the exception whitelist with projects or project pairs as the recording unit, and specify the exception reason and validity period in the exception whitelist;

[0057] The exception whitelist can be divided into project-level exception records and project-pair-level exception records. Project-level exception records indicate that when a corresponding project is combined with projects in the current order project set during its validity period, mutual exclusion checks are skipped according to a preset method. Project-pair-level exception records indicate that mutual exclusion checks are skipped only for specified project pairs. The validity period includes at least the start and end times, and exception records can only participate in the determination if the current system time is within this time range.

[0058] S1.4. Provide an interface for adding, modifying, and disabling the mutual exclusion table, the association table, and the exception whitelist. The mutual exclusion table, the association table, and the exception whitelist are collectively referred to as the relationship configuration table.

[0059] The "Add" interface is used to enter new relationship records; the "Modify" interface is used to adjust mutual exclusion types, outgoing quantities, exception reasons, or validity periods; the "Disable" interface is used to set records that are no longer participating in validation to a disabled state, instead of directly deleting historical data. Access control can be set for each interface, ensuring that only personnel with the appropriate maintenance permissions can submit relationship adjustments.

[0060] S1.5. Collect the relationship configuration table after it has been adjusted by the new operation interface, the modified operation interface and the deactivated operation interface, and make the adjustment result of the relationship configuration table take effect immediately in the order verification to obtain the relationship rule library.

[0061] Specifically, after the relationship configuration adjustment passes the data integrity check, the system commits the transaction, generates a new rule version number, and causes the order verification service to refresh the corresponding records or reload the corresponding indexes. When using incremental refresh, only the changed relationship records are updated; when using full reload, a new version of the relationship rule base can be built in the backup storage area first, and then the new version of the relationship rule base can be made effective through version switching, so as to reduce the possibility of incomplete rule states during the update.

[0062] Example 3

[0063] This embodiment, based on embodiment 2, further defines the process of establishing the mutual exclusion table, including:

[0064] S1.1.1. Filter out the project pairs with conflicting inspection methods and project pairs with conflicting sampling requirements from the project library. The project pairs with conflicting inspection methods are project pairs that also include radioactive inspections. The project pairs with conflicting sampling requirements are project pairs with opposite fasting requirements for blood collection.

[0065] The filtering can be performed by maintenance personnel based on project attributes, or the system can generate candidate project pairs based on the inspection method and sampling requirement fields in the project library, which are then confirmed by operators with maintenance permissions. Only after confirmation can the candidate project pairs be written into the mutual exclusion record of the enabled status.

[0066] S1.1.2. Arrange the selected item pairs in ascending order by item number as item pair keys, and use the item pair keys as record identifiers for the mutual exclusion relation table;

[0067] For example, if two items are numbered P102 and P035 respectively, the system will construct the item pair key as P035-P102 in ascending order. Regardless of which item is selected first when creating an order, the same item pair key will be used to retrieve the mutual exclusion table, thus avoiding the need to save two mutually exclusive records with the same content in both the forward and reverse directions.

[0068] S1.1.3. For records with the same-day mutual exclusion type, the same physical examination date of the examinee shall be used as the scope of conflict determination; for records with the same-order mutual exclusion type, the same physical examination order shall be used as the scope of conflict determination.

[0069] When performing a same-day mutual exclusion check, the system queries for effective orders and current orders under the same examinee ID and the same examination date; when performing a same-order mutual exclusion check, the system only queries the current order item set. Therefore, different mutual exclusion types can be executed within their respective judgment ranges.

[0070] S1.1.4. Set an effective status field for each record in the mutual exclusion relationship table, and only records with the effective status field set to enabled participate in the order verification;

[0071] The effective status field can include enabled and disabled. For records that need to be temporarily excluded from verification but whose historical basis still needs to be preserved, they are set to disabled instead of being physically deleted. In other implementations, a pending review status can also be set so that unreviewed records do not participate in formal invoice verification.

[0072] S1.1.5. Set a maintenance time field and a maintainer field for each record in the mutual exclusion table, and generate a maintenance log comparing the values ​​before and after the change when the mutual exclusion table is changed, thus obtaining the mutual exclusion table.

[0073] The maintenance log should at least record the mutual exclusion record identifier, the changed fields, the values ​​before the change, the values ​​after the change, the maintenance time, and the maintainer. This allows us to trace back all adjustments to the record based on the mutual exclusion record identifier and determine the rule version used when a specific order was generated.

[0074] Example 4

[0075] like Figure 3 As shown, this embodiment, based on embodiment 1, further defines the process of automatically populating related items and linking costs, including:

[0076] S2.1. Receive the item selection operation on the order opening interface, and determine whether the selected item has the association mark in the association table;

[0077] The association marker can be directly stored in the project library, or it can be dynamically generated based on whether there is an enabled record in the association table where the selected project is the main project. When the selected project does not have an association marker, the system writes it into the current order project set as a regular project; when an association marker exists, the associated project retrieval process is initiated.

[0078] S2.2. When the associated marker exists, retrieve the association table to determine the associated items and the number of items brought out corresponding to the main item;

[0079] The system reads all active association records, excluding deactivated records and items already existing in the current order item set. For items to be removed that have potential mutual exclusion conflicts with the current order item set, they can be marked as requiring manual confirmation instead of being directly written as ordinary association items.

[0080] S2.3. Write the associated items into the current order item set according to the quantity brought out, and accumulate the order cost according to the unit price of the associated items;

[0081] When writing to the current order item set, the system saves the associated record number, the main item number, and the quantity to be carried out. If the quantity to be carried out is... The unit price of related items is The incremental cost generated by this related project is The fee increment is added to the current order's receivable amount and then included in the subsequent mutual exclusion detection scope.

[0082] S2.4. Mark the source of the associated item as the main item, and provide manual confirmation and removal operations for the associated item. When the removal operation is performed, the order fee corresponding to the associated item is deducted simultaneously.

[0083] When a related item is brought out by multiple main items, multiple bring-out sources or reference counts can be saved for that related item. The system only deletes the related item from the order item collection when all bring-out sources are invalid and the operator confirms the removal. This avoids mistakenly deleting related items that are still depended on by another main item when removing a main item.

[0084] S2.5. Combine the main item and the associated items retained by the manual confirmation operation into a complete set of associated items to obtain the associated item combination.

[0085] The associated project combination is submitted to the mutual exclusion verification process. When the order is saved, the system checks again whether the associated projects required by each main project still exist. If the operator has removed the necessary associated projects, an association integrity prompt is output, and the order is prevented from taking effect directly until the corresponding associated projects are restored or the processing is completed according to preset permissions.

[0086] Example 5

[0087] This embodiment, based on embodiment 4, further defines the process for determining associated items and the number of items brought out, including:

[0088] S2.2.1. Retrieve the association table using the project number of the main project as the key to obtain all associated records with the main project as the record unit;

[0089] Specifically, a composite index can be created for the relationship table, with the main item number as the first column. When a main item corresponds to multiple related records, the system can retrieve all related records in a single query, reducing repeated access to the relationship table.

[0090] S2.2.2. Read the associated item number and the number of items to be taken out from all the associated records, and filter the associated records in the all associated records whose active status is disabled;

[0091] Filtering operations can also include verifying whether the associated item itself is in an optional state. If the associated record is enabled but the associated item is disabled, the system can mark the record as having a configuration error and output a prompt to the rule maintenance terminal.

[0092] S2.2.3. Determine whether the project corresponding to the read associated project number already exists in the current order project set. If it already exists, it will not be brought out again. If it does not exist, it will be added to the project set to be brought out.

[0093] The system can use a hash set or a bitmap set composed of project numbers for the determination. For existing projects, the system can supplement the source information to be extracted, but will not double-count the project quantity and cost; for non-existent projects, they will be added to the set of projects to be extracted.

[0094] S2.2.4. Based on the mutual exclusion records of the items in the set of items to be taken out in the mutual exclusion relationship table, predict the mutual exclusion conflict between the items in the set of items to be taken out and the current order item set. If the mutual exclusion conflict exists, mark the items in the set of items to be taken out as pending manual confirmation.

[0095] The prediction process can simultaneously check the mutual exclusion relationships between the items to be extracted. If an item to be extracted matches a mutual exclusion record with a current order item or another item to be extracted, the system displays the main item, related items, conflicting items, and mutual exclusion type for operators to confirm and adjust.

[0096] S2.2.5. Based on the set of items to be brought out and the number of items to be brought out, determine the associated items corresponding to the main item and the number of items to be brought out.

[0097] Therefore, the automatic order dumping process performs deduplication, status filtering, and conflict prediction before writing the order, which can reduce redundant processing caused by mutual exclusion checks and rollbacks after related items are written. In other implementations, a temporary order set can be written first, and then merged into the formal current order item set after the conflict prediction is passed.

[0098] Example 6

[0099] like Figure 4 As shown, this embodiment, based on embodiment 1, further defines the dual-trigger mutual exclusion verification and exception exemption process, including:

[0100] S3.1. When adding items one by one, combine the items in the current order item set with the items to be added in pairs to obtain a set of item pairs to be verified;

[0101] Let the current order item set be The items to be added are The set of items to be verified is .in, This represents the current set of order items. Indicates the first One project, Indicates the quantity of items in the current order. This indicates items to be added. This represents the set of items to be verified.

[0102] S3.2. Index the mutual exclusion table by project number, detect the project pairs in the set of project pairs to be verified that have a mutual exclusion record with an enabled status, pop up a prompt for the matched project pairs and list the conflicting project pairs, and prevent the project to be added from being added to the order;

[0103] The system standardizes each pair of items to be verified into item-key pairs and retrieves the mutual exclusion index. For mutually exclusive records within the same order, the system directly performs the judgment based on the current order; for mutually exclusive records on the same day, it also queries other effective orders of the examined object on the same medical examination date. Upon a match, the prompt message includes at least the item to be added, the conflicting item, and the mutual exclusion type.

[0104] S3.3. For items listed in the exception whitelist and within the validity period, skip the mutual exclusion detection and allow passage, while generating an exception usage record;

[0105] Exception handling is performed before the mutual exclusion relationship is formally blocked. Mutual exclusion checks are skipped only if the exception record is enabled, the current system time is valid, and the project scope matches. The generated exception records are saved as order audit information to prevent exception releases from being separated from specific orders and operators.

[0106] S3.4. When saving an order, repeat the mutual exclusion check and perform an association integrity check, wherein the association integrity check verifies that each of the main items in the associated item combination has an associated item in the current order item set;

[0107] The final verification of orders uses the currently effective rule version. If the relationship rule base is adjusted after an item is added, the final verification can re-examine the order according to the adjusted rules. For association integrity checks, the corresponding associated items and quantities can be verified item by item based on the effective association records of the main item.

[0108] S3.5. After both the mutual exclusion test and the association integrity test pass, the order is set as the effective medical examination order.

[0109] When an order is set to active status, the system saves the rule version number used during verification, the verification time, and a summary of the verification results. Since verification is performed separately during the project addition and order saving phases, the former can promptly prevent obvious conflicts, while the latter can eliminate verification omissions caused by project or rule changes during order editing.

[0110] Example 7

[0111] This embodiment, based on embodiment 6, further defines the determination and usage tracking process of the exception whitelist, including:

[0112] S3.3.1. Before performing the mutual exclusion detection, determine one by one whether the items to be verified are included in the exception whitelist;

[0113] The system can first query project-level exception records by project number, and then query project-pair-level exception records by standardized project key. If no corresponding exception record is found, the system continues to perform regular mutual exclusion checks.

[0114] S3.3.2. For items included in the exception whitelist, compare the current system time with the validity period corresponding to the item included in the exception whitelist. If the current system time is within the validity period, the exception is determined to be valid.

[0115] The validity period determination can consider the start time, end time, effective status, and rule version simultaneously. If the current system time is earlier than the start time, later than the end time, or the record is deactivated, the exception is deemed invalid.

[0116] S3.3.3. When the exception is met, the combination of the listed items and any item in the current order item set will skip the mutual exclusion detection and be allowed;

[0117] In other implementations that employ project-to-project exception records, only the corresponding project pair skips mutual exclusion checks; other project combinations not covered by the exception record still undergo regular mutual exclusion checks. Therefore, project-level or project-to-project pair-level allowances can be selected based on the actual configuration granularity.

[0118] S3.3.4. Generate the exception usage record, which includes the operator's identifier, release time, exception reason, and the released item pair;

[0119] Exception usage records may also include the exception record number, order number, rule version number, and terminal identifier. Once generated, exception usage records are not overwritten by subsequent modifications to the exception whitelist records, thus preserving the original basis for the release.

[0120] S3.3.5. The exception usage record is archived in association with the order number, and the mutual exclusion detection for the listed items is automatically restored after the expiration of the validity period.

[0121] The system can use scheduled tasks, cache expiration mechanisms, or real-time comparison with the current system time during each verification to prevent expired exception records from participating in the judgment. In other implementations, a reminder can be sent to maintenance personnel when the validity period is about to expire, but this reminder does not change the processing logic of resuming mutual exclusion detection after the validity period expires.

[0122] Example 8

[0123] like Figure 5 As shown, this embodiment, based on embodiment 1, further defines the process of project change tracking and automatic cost recalculation, including:

[0124] S4.1. When a project is deactivated, replaced, price-adjusted, or its details are adjusted in the project library, collect the project content before and after the change.

[0125] The content before and after the change can be saved as structured snapshots. For deactivation operations, the content after the change includes the deactivation status; for replacement operations, the content after the change includes the replacement item number; for price adjustment operations, the content before and after the change includes the original unit price and the new unit price; for detailed adjustment operations, the content before and after the change includes the set of adjusted detailed items.

[0126] S4.2. Write the project content before the change, the project content after the change, the reason for the change, the time of the change, and the operator's identification into the change history database to form a change event record;

[0127] Each change event record has a unique event identifier. If a maintenance operation involves multiple projects, a change event record can be generated for each project separately, and multiple change event records can be associated with a batch identifier to support tracing by single project and by change batch.

[0128] S4.3. Based on the change event record, compare the item set of the effective medical examination order to determine the removed items, added items, and price adjustment items in the effective medical examination order;

[0129] For deactivation operations, the corresponding items in the affected orders can be identified as removal items; for replacement operations, the original items are identified as removal items and the replacement items are identified as addition items; for price adjustment operations, the corresponding items in the order are identified as price adjustment items. For detailed adjustment operations, the removal and addition items are determined based on the differences between the detailed items before and after the adjustment.

[0130] S4.4. Calculate the refund amount based on the removed items, the supplementary fee amount based on the added items, and the price difference between the unit price before and after the change based on the price adjustment items. Summate them up to obtain the fee change and update the receivable amount of the effective medical examination order.

[0131] Cost changes can be further expressed as:

[0132] Equation (3)

[0133] in, This indicates a change in order costs. Indicates the number of newly added items. and They represent the first The quantity and unit price of each new item Indicates the number of items removed. and They represent the first The quantity and original unit price of each removed item. Indicates the quantity of price adjustment items. Indicates the first The number of price adjustment items, and These represent the unit price after the change and the unit price before the change, respectively.

[0134] In one example, an order removes an item originally priced at 80 yuan, adds a replacement item priced at 100 yuan, and adjusts the price of another item (quantity 2) from 30 yuan to 35 yuan. The resulting cost change is: Yuan. This value is only used to illustrate the cost calculation process and does not constitute a limitation on the project price.

[0135] S4.5. The details of the fee changes are associated with the version number of the effective medical examination order and archived. The change notification is pushed to the examinee and the billing process to obtain the order file with traceable changes.

[0136] Each recalculation of fees generates a new version based on the original order version, while retaining a snapshot of the old version. Fee change details must record at least the fee item, change type, amount before change, amount after change, corresponding change event identifier, and calculation time, enabling the billing process to complete subsequent processing based on the same details.

[0137] Example 9

[0138] This embodiment, based on embodiment 1, provides a method for compressing and detecting conflict in a relational rule base based on behavior alignment. The method further includes:

[0139] The behavior of the relation rule base is sampled using randomly generated project set samples, and the mutual exclusion interception results and association carry-out results output by the relation rule base under each project set sample are recorded to obtain the rule base behavior benchmark.

[0140] Project set samples can be generated according to the project library size, project category distribution, and the distribution of project quantity in historical orders. The output of each sample includes whether mutual exclusion interception occurred, the matched mutual exclusion records, and the automatically populated set of related projects. The rule base behavior benchmark is used to characterize the external validation behavior of the relational rule base on each sample before compression.

[0141] For each rule in the relation rule base, after removing the rule being inspected, all the behavior sampling is re-executed. When the output of all the item set samples is consistent with the behavior benchmark of the rule base, the rule being inspected is determined to be a redundant rule implied by other rules and is added to the redundant rule list.

[0142] In one implementation, the first... The behavioral variance of each rule being inspected is:

[0143] Equation (4)

[0144] in, Indicates the removal of the first The behavioral difference following the implementation of the rule being inspected. Indicates the number of samples in the project set. This is an indicator function that takes a value of 1 if the condition is true and 0 otherwise. Indicates the first The output of a sample set of items in the rule base behavior benchmark. Indicates the removal of the first The first rule after the inspection The output of a sample of each item set. When At that time, the first The rule being inspected is included in the list of redundant rules.

[0145] Identify the transitive implication chain composed of mutual exclusion and association relationships, merge the rules implied by upstream rules in the transitive implication chain, and obtain the merged rule set;

[0146] Specifically, the system treats projects as nodes and mutual exclusion and association relationships as typed connections. It identifies transitive implication chains that produce the same behavioral results along the association direction and mutual exclusion constraints. During merging, upstream rules that can reproduce the original validation behavior are retained, and the mapping relationship between the merged rules and the retained rules is recorded for subsequent traceability.

[0147] Perform conflict detection on the merged rule set to detect records where the same item has both mutually exclusive and related relationships, records where the related relationships form a cycle, and records where the mutually exclusive closed chains contradict each other, and output a rule conflict detection report;

[0148] For relationships that lead to cycles, depth-first search, topological sorting, or strongly connected component detection can be used for identification. The rule conflict detection report includes the conflict type, involved items, related relationship records, and suggested handling methods. The rule maintainer will confirm and adjust the corresponding rules.

[0149] After processing the rule conflict detection report, the item pair relationship in the rule set is encoded into a bitmap index structure. When performing order verification, the bitmap index structure is directly indexed to match the rule by the item number, instead of traversing each rule one by one, resulting in a compressed indexed relation rule library.

[0150] For example, a mutual exclusion bitmap and an association bitmap can be created for each item, with the bit order in the bitmap corresponding to the internal index of other items. During order verification, a bitwise AND operation is performed between the mutual exclusion bitmap corresponding to the item to be added and the current order item bitmap to determine whether there is a matching mutual exclusion item.

[0151] The compressed, indexed relational rule base is validated against the rule base behavior benchmark. When the output of all the project set samples is consistent with the rule base behavior benchmark, the rule base is launched.

[0152] When inconsistencies are found during verification, instead of publishing a compressed, indexed relational rule base, the rules that were incorrectly deleted or merged are located based on the discrepancies and reprocessed. In other implementations, historical order samples and boundary item combination samples can be added in addition to the random item set samples to broaden the scope of behavioral consistency verification.

[0153] Example 10

[0154] This embodiment, based on embodiment 6, provides a verification method that complements precise rule channels and local context risk channels. The method further includes:

[0155] Based on historical order data and on-site inspection conflict records, the frequency of co-occurrence of the same order for each item pair, the frequency of on-site rescheduling or cancellation after co-occurrence, and the risk markers reported by the department are statistically analyzed. The contextual risk score of each item pair is obtained by weighted summation, which constitutes a local contextual risk channel.

[0156] For the project Its contextual risk score can be expressed as:

[0157] Equation (5)

[0158] in, Indicates project With the project Contextual risk scoring, This indicates the frequency with which the item is modified or withdrawn after co-occurrence. This indicates the frequency of co-occurrence of the same item pair. This prevents positive numbers with a denominator of zero. This indicates the risk marker value reported by the department. This represents the time decay correction value calculated based on recent records. , and These represent the weights of the corresponding statistics.

[0159] The mutual exclusion table is used to form a precise rule channel, which outputs a deterministic conflict conclusion when the mutual exclusion record is matched.

[0160] The precise rule channel performs hard interception only based on mutex records that are enabled. Since the items in this channel have already been configured and confirmed, there is no need for repeated judgment by the local context risk channel when a hit occurs.

[0161] When the precise rule channel is hit, it is directly intercepted and the local context risk channel is not involved in the judgment. When the precise rule channel is not hit, the context risk scores of each item pair in the current order item set are accumulated to obtain a combined risk score.

[0162] Suppose the current order item set contains If there are 1 pair of items to be evaluated, the portfolio risk score can be expressed as:

[0163] Equation (6)

[0164] in, Indicates portfolio risk score. Indicates the quantity of items to be evaluated. Indicates the first The fusion weight of each pair of projects to be evaluated Indicates the first Contextual risk score for each item to be evaluated.

[0165] Based on the interception accuracy feedback of the precise rule channel and the local context risk channel within a set period, the fusion weight and interception threshold of the precise rule channel and the local context risk channel are adaptively adjusted. When the number of false alarms of the local context risk channel reaches the first threshold, the interception threshold is increased. After the missed alarm combination of the local context risk channel is confirmed, it is included in the mutual exclusion table and taken over by the precise rule channel.

[0166] The initial threshold can be determined based on the number of orders within a set period and the acceptable frequency of alerts. If the value is too small, frequent adjustments to the interception threshold may be necessary due to a small number of occasional feedbacks; if the value is too large, the risk channel's response to feedback will be slow. Therefore, the initial threshold can be set in segments according to order volume, and a maximum change range can be set for each threshold adjustment.

[0167] For project combinations whose combined risk scores exceed the interception threshold, a soft interception is performed, and a risk warning and alternative project suggestions are displayed. The operator then performs a release operation or an adjustment operation.

[0168] Soft blocking differs from hard blocking in precise rule channels. It doesn't directly prohibit project combinations from entering an order; instead, it displays the source of risk and suggested alternative projects. Operators can choose to allow or adjust based on current business conditions, and these choices are used as data for subsequent risk scoring updates.

[0169] The project portfolio that has undergone the release operation is added to the observation list. When the number of release operations reaches the second threshold, the context risk score of the project portfolio is lowered. When the number of adjustment operations reaches the third threshold, the project portfolio is proposed to be included as the mutually exclusive record. Both the second threshold and the third threshold are greater than zero.

[0170] The second and third thresholds can be set separately. A threshold that is too low for the second instance may prematurely lower the risk score due to a small number of approval operations, while a threshold that is too low for the third instance may prematurely form formal mutually exclusive rules due to occasional adjustments; both thresholds that are too high will slow down the speed at which the rule base absorbs feedback. Therefore, the threshold can be configured in conjunction with the number of valid feedback requests within a set period, and the rule maintenance personnel should confirm the proposed combination of items for inclusion.

[0171] Example 11

[0172] This embodiment, based on embodiment 8, provides an incremental cost recalculation method based on forward impact propagation and reverse location tracing. The method further includes:

[0173] Starting from the change event record, a forward impact propagation is performed, and the direct impact set and indirect impact set are determined along the order level, project level and cost level. The direct impact set is the set of orders containing the change project, and the indirect impact set is the order containing the associated project due to the coupling of the association table with the change project and the order due to the conflict between the mutual exclusion table and the replacement item, thus obtaining the change impact range set.

[0174] The system first retrieves the order item index by the changed item number to obtain orders that directly contain the changed item. Then, it searches the relationship table to identify the main item or related item that has a carry-over relationship with the changed item, and finds orders that contain the corresponding coupled item. For replacement operations, it also retrieves the mutual exclusion relationship between the replacement item and the existing items in the order to obtain orders that may conflict due to the replacement.

[0175] The set of impacts of the change can be represented as:

[0176] Equation (7)

[0177] in, Indicates the set of areas affected by the change. This indicates the set that directly affects the data. This represents the set of indirect influences formed by the coupling of relationships. This represents the set of indirect effects caused by the mutually exclusive relationship between the replacement item and the existing items in the order.

[0178] For each order in the range of changes, reverse location tracing is performed to determine the cause chain of each order being affected. The cause chain includes records of the change events involved, records of the relationships involved, and the cost items involved. Order-level impact cause descriptions are generated to obtain a list of affected orders with cause chains.

[0179] During reverse tracing, starting with the affected expense item in the order, the process sequentially traces back to the project that triggered the change in that expense item, the relationship record connecting that project and the changed project, and the initial change event record. A cause chain directly affecting the order may only include change event records and expense items; a cause chain indirectly affecting the order may also include related or mutually exclusive relationship records.

[0180] Incremental cost recalculation is performed only for orders in the affected order list with cause chain. The cost change is calculated based on the difference between the refund amount of the removed item, the supplementary fee amount of the added item, and the price adjustment item. Orders not included in the affected order list with cause chain are not recalculated.

[0181] Incremental recalculation uses the affected expense items as the boundary, and does not recalculate other expense items in the order that are not affected by the change. This allows the calculation scope to be narrowed from all historical effective orders to the set of change-affected areas, and further narrowed to the affected expense items in each order.

[0182] Based on the results of the incremental cost recalculation and the cause chain, a change impact report is generated. The change impact report includes the number of affected orders, the total cost change, the cost change details for each order, and the corresponding cause chain.

[0183] The total amount of cost changes can be expressed as:

[0184] Equation (8)

[0185] in, This indicates the total amount of cost changes reported in the change impact report. Indicates the number of orders affected. Indicates the first Cost changes for each affected order.

[0186] The change impact report is pushed to the billing process and the inspected object, and the change impact report is associated with the change event record in the change history database and archived to obtain the change impact file.

[0187] In one implementation, the change impact report has a unique report number and records the generation time, processing status, and push status. When the incremental cost recalculation for a particular order fails, only that order can be retried without reprocessing the entire change impact set. In other implementations, a message queue can be used to process affected orders in batches to accommodate situations with a large number of orders.

[0188] Example 12

[0189] like Figure 6 As shown, this embodiment provides a system for configuring mutual exclusion and association relationships of physical examination items and for verifying order issuance, including:

[0190] The relationship configuration and maintenance module is used to maintain mutually exclusive relationship tables, related relationship tables, and exception whitelists based on medical business rules and project libraries, so as to obtain a relationship rule library that can be adjusted online and take effect immediately.

[0191] The relationship configuration maintenance module may include a mutual exclusion relationship maintenance unit, an association relationship maintenance unit, an exception whitelist maintenance unit, and a rule publishing unit. The rule publishing unit is used to update the rule version after the relationship configuration table is adjusted and to notify other modules to load the adjusted relationship rule library.

[0192] The associated project extraction module is used to automatically extract associated projects and include them in the cost when a main project with an associated tag is selected in the order opening interface, based on the relationship rule base, so as to obtain a combination of associated projects.

[0193] The associated item extraction module may include an associated tag judgment unit, an associated record retrieval unit, an item deduplication unit, a conflict prediction unit, and a cost linkage unit. The cost linkage unit updates the order receivable amount based on the extracted quantity and unit price of associated items, and simultaneously deducts the corresponding cost when an associated item is removed.

[0194] The mutual exclusion verification and interception module is used to perform mutual exclusion detection when adding items and saving orders based on the associated item combination, the mutual exclusion relationship table and the exception whitelist. When a mutual exclusion record is hit, it will prompt and intercept the mutual exclusion detection. For items in the exception whitelist, the mutual exclusion detection will be skipped and a record will be left, and an effective physical examination order will be obtained.

[0195] The mutual exclusion verification and interception module may include a project pair generation unit, a mutual exclusion record retrieval unit, an exception determination unit, an add-stage verification unit, a save-stage verification unit, and an exception logging unit. The add-stage verification unit is used to perform mutual exclusion checks before the project is written into the order, and the save-stage verification unit is used to re-execute mutual exclusion checks and association integrity checks before the order takes effect.

[0196] The change traceability and recalculation module is used to record the content before and after the change and the operator to form a change history database based on the project change operation, and automatically recalculate the cost changes of the effective medical examination order based on the change history database to obtain the order file with traceable changes.

[0197] The change tracking and recalculation module may include a change event collection unit, a change history storage unit, an order impact location unit, a cost recalculation unit, an order version management unit, and a change notification unit. The cost recalculation unit calculates the refund amount for removed items, the supplementary fee amount for added items, and the price difference amount for adjusted items; the order version management unit archives the cost change details along with the order version number.

[0198] In one implementation, the system is deployed on a server or server cluster, and the order placement terminal calls the configuration and maintenance interface, related project query interface, mutual exclusion verification interface, and cost recalculation interface provided by the system through a communication network. Each module can be implemented by an independent software service or integrated into the same physical examination information system.

[0199] The system may further include a rule base compression and conflict detection module, a fusion risk verification module, and an incremental recalculation module. The rule base compression and conflict detection module is used to establish rule base behavior benchmarks, identify redundant and conflicting rules, and form a bitmap index structure; the fusion risk verification module is used to calculate a combined risk score and perform soft blocking when a precise rule channel is not hit; the incremental recalculation module is used to determine the affected orders and cause chains through forward impact propagation and reverse location tracing, and only recalculates the costs for the affected orders.

[0200] The system described in this embodiment can be implemented by a processor executing a computer program stored in memory. The memory can store a project library, a relationship configuration table, a relationship rule library, a change history library, order files, and the computer program; when the processor executes the computer program, it implements the steps in any of the foregoing method embodiments. The computer program can also be stored in a non-transitory computer-readable storage medium and, when executed by the processor, implement the foregoing methods.

Claims

1. A method for configuring mutual exclusion and association relationships of physical examination items and for verifying order issuance, characterized in that, include: Based on medical business rules and project library, maintain mutual exclusion relationship table, association relationship table and exception whitelist to obtain a relationship rule library that can be adjusted online and take effect immediately; Based on the aforementioned relationship rule base, when a main item with an association tag is selected in the order creation interface, the associated items are automatically populated and their costs are included, resulting in a combination of associated items. Based on the associated project combination, the mutual exclusion relationship table and the exception whitelist, mutual exclusion detection is performed when adding projects and saving orders one by one. When a mutual exclusion record is hit, a prompt is made and the block is intercepted. For projects in the exception whitelist, the mutual exclusion detection is skipped and a trace is left, resulting in an effective physical examination order. Based on project change operations, the changes before and after the change are recorded along with the operator to form a change history database. The cost changes of the effective medical examination orders are automatically recalculated based on the change history database to obtain order files with traceable changes.

2. The method for configuring mutual exclusion and association relationships of physical examination items and verifying order issuance according to claim 1, characterized in that, Based on medical business rules and a project library, a mutual exclusion table, an association table, and an exception whitelist are maintained to obtain a relation rule library that can be adjusted online and takes effect immediately, including: Based on the medical business rules and the project library, a mutual exclusion table is established with project pairs as the recording unit. The mutual exclusion table records mutually exclusive project pairs, mutual exclusion types and effective status. The mutual exclusion types include same-day mutual exclusion and same-item mutual exclusion. Based on the combination dependency requirements in the medical business rules, the association table is established with the main item and related items as the recording units. The association table records the related items automatically brought out when the main item is selected and the number of items brought out. Based on the exemption requirements of special medical scenarios, the exception whitelist is established with projects or project pairs as the recording unit, and the exception whitelist specifies the reason for the exception and the validity period. The system provides an interface for adding, modifying, and disabling the mutual exclusion table, the association table, and the exception whitelist. The mutual exclusion table, the association table, and the exception whitelist are collectively referred to as the relationship configuration table. The relationship configuration table, after being adjusted by the new operation interface, the modified operation interface, and the deactivated operation interface, is collected, and the adjustment results of the relationship configuration table are made to take effect immediately in the order verification, thus obtaining the relationship rule library.

3. The method for configuring mutual exclusion and association relationships of physical examination items and verifying order issuance according to claim 2, characterized in that, Based on the medical business rules and the project library, a mutual exclusion table is established with project pairs as the recording unit. The mutual exclusion table records mutually exclusive project pairs, mutual exclusion types, and effective status. The mutual exclusion types include same-day mutual exclusion and same-item mutual exclusion, including: Filter out the project pairs with conflicting inspection methods and project pairs with conflicting sampling requirements from the project library. The project pairs with conflicting inspection methods are project pairs that also include radioactive inspections, and the project pairs with conflicting sampling requirements are project pairs with opposite fasting requirements for blood collection. The selected item pairs are sorted in ascending order by item number as item pair keys, and the item pair keys are used as record identifiers for the mutual exclusion relation table. For records with the same-day mutual exclusion type, the same physical examination date of the examinee shall be used as the scope of conflict determination; for records with the same-order mutual exclusion type, the same physical examination order shall be used as the scope of conflict determination. Set an activation status field for each record in the mutual exclusion relationship table, and only records with the activation status field set to "enabled" participate in the order verification. Set a maintenance time field and a maintainer field for each record in the mutual exclusion table, and generate a maintenance log comparing the values ​​before and after the change when the mutual exclusion table is modified, thus obtaining the mutual exclusion table.

4. The method for configuring mutual exclusion and association relationships of physical examination items and verifying order issuance according to claim 1, characterized in that, Based on the relationship rule base, when a main item with an association tag is selected on the order page, the associated items are automatically populated and their costs are calculated, resulting in a combination of associated items, including: The system receives a project selection operation on the order creation interface and determines whether the selected project has the associated marker in the association table. When the associated marker exists, the association table is retrieved to determine the associated items and the number of items brought out corresponding to the main item; Write the associated items into the current order item set according to the quantity brought out, and accumulate the order fee according to the unit price of the associated items; The associated project is marked with the source as the main project, and manual confirmation and removal operations are provided for the associated project. When the removal operation is performed, the order fee corresponding to the associated project is deducted simultaneously. The main item and the associated items retained through the manual confirmation operation are combined into a complete set to obtain the associated item combination.

5. The method for configuring mutual exclusion and association relationships of physical examination items and verifying order issuance according to claim 4, characterized in that, When the associated marker exists, the association table is retrieved to determine the associated items and the number of items brought out corresponding to the main item, including: The association table is retrieved by using the project number of the main project as the key, and all associated records with the main project as the record unit are obtained. Read the associated project number and the number of items to be taken out from all the associated records, and filter the associated records in the all associated records whose active status is disabled; Determine whether the project corresponding to the read associated project number already exists in the current order project set. If it already exists, it will not be brought out again. If it does not exist, it will be added to the project set to be brought out. Based on the mutual exclusion records of the items in the set of items to be taken out in the mutual exclusion relationship table, predict the mutual exclusion conflict between the items in the set of items to be taken out and the current order item set. If the mutual exclusion conflict exists, mark the items in the set of items to be taken out as pending manual confirmation. Based on the set of items to be brought out and the number of items to be brought out, determine the associated items corresponding to the main item and the number of items to be brought out.

6. The method for configuring mutual exclusion and association relationships of physical examination items and verifying order issuance according to claim 1, characterized in that, Based on the associated project combination, the mutual exclusion table, and the exception whitelist, mutual exclusion checks are performed when adding projects and saving orders. If a mutual exclusion record is found, a notification is issued and the process is blocked. For projects in the exception whitelist, the mutual exclusion check is skipped and a record is left, resulting in an effective medical examination order, including: When adding items one by one, the items in the current order item set are paired with the items to be added to obtain a set of item pairs to be verified. Index the mutual exclusion table by project number, detect the project pairs in the set of project pairs to be verified that have a mutual exclusion record with an enabled status, pop up a prompt for the matched project pairs and list the conflicting project pairs, and prevent the project to be added from being added to the order. For items included in the exception whitelist and within their validity period, the mutual exclusion detection is skipped and the items are allowed to pass, while an exception usage record is generated. When the order is saved, the mutual exclusion check is repeated, and the association integrity check is performed. The association integrity check verifies that the associated items corresponding to each main item in the associated item combination exist in the current order item set. After both the mutual exclusion test and the association integrity test pass, the order is set as the effective medical examination order.

7. The method for configuring mutual exclusion and association relationships of physical examination items and verifying order issuance according to claim 6, characterized in that, For items included in the exception whitelist and within their validity period, the mutual exclusion check is skipped and allowed to proceed, while an exception usage record is generated, including: Before performing the mutual exclusion detection, it is determined whether each item to be verified is included in the exception whitelist. For items included in the exception whitelist, the current system time is compared with the validity period corresponding to the item in the exception whitelist. If the current system time is within the validity period, the exception is determined to be valid. When the exception is met, the combination of the listed items and any item in the current order item set will skip the mutual exclusion check and be allowed; Generate the exception usage record, which includes the operator identifier, release time, exception reason, and the released item pair; The exception usage record is archived in association with the order number, and the mutual exclusion detection for the listed items is automatically restored after the expiration of the validity period.

8. The method for configuring mutual exclusion and association relationships of physical examination items and verifying order issuance according to claim 1, characterized in that, The process involves recording the changes before and after the project change, along with the operator, to create a change history database. Based on this database, the cost changes for the effective medical examination orders are automatically recalculated, resulting in traceable order files, including: When a project is deactivated, replaced, price-adjusted, or its details are adjusted in the project library, the project content before and after the change is collected. The project content before the change, the project content after the change, the reason for the change, the time of the change, and the operator's identification are written into the change history database to form a change event record; Based on the change event records, the items in the effective medical examination orders are compared to determine the removed items, added items, and price adjustment items in the effective medical examination orders; The refund amount is calculated based on the removed items, the supplementary fee amount is calculated based on the added items, and the price difference before and after the price change is calculated based on the adjusted items. The total amount is then added together to obtain the change in fees, and the amount receivable for the effective medical examination order is updated. The details of the fee changes are linked to the version number of the effective medical examination order and archived. The change notification is then pushed to the examinee and the billing process to obtain the order file with traceable changes.

9. The method for configuring mutual exclusion and association relationships of physical examination items and verifying order issuance according to claim 1, characterized in that, The method further includes: The behavior of the relation rule base is sampled using randomly generated project set samples, and the mutual exclusion interception results and association carry-out results output by the relation rule base under each project set sample are recorded to obtain the rule base behavior benchmark. For each rule in the relation rule base, after removing the rule being inspected, all the behavior sampling is re-executed. When the output of all the item set samples is consistent with the behavior benchmark of the rule base, the rule being inspected is determined to be a redundant rule implied by other rules and is added to the redundant rule list. Identify the transitive implication chain composed of mutual exclusion and association relationships, merge the rules implied by upstream rules in the transitive implication chain, and obtain the merged rule set; Perform conflict detection on the merged rule set to detect records where the same item has both mutually exclusive and related relationships, records where the related relationships form a cycle, and records where the mutually exclusive closed chains contradict each other, and output a rule conflict detection report; After processing the rule conflict detection report, the item pair relationship in the rule set is encoded into a bitmap index structure. When performing order verification, the bitmap index structure is directly indexed to match the rule by the item number, instead of traversing each rule one by one, resulting in a compressed indexed relation rule library. The compressed, indexed relational rule base is validated against the rule base behavior benchmark. When the output of all the project set samples is consistent with the rule base behavior benchmark, the rule base is launched.

10. The method for configuring mutual exclusion and association relationships of physical examination items and verifying order issuance according to claim 6, characterized in that, The method further includes: Based on historical order data and on-site inspection conflict records, the frequency of co-occurrence of the same order for each item pair, the frequency of on-site rescheduling or cancellation after co-occurrence, and the risk markers reported by the department are statistically analyzed. The contextual risk score of each item pair is obtained by weighted summation, which constitutes a local contextual risk channel. The mutual exclusion table is used to form a precise rule channel, which outputs a deterministic conflict conclusion when the mutual exclusion record is matched. When the precise rule channel is hit, it is directly intercepted and the local context risk channel is not involved in the judgment. When the precise rule channel is not hit, the context risk scores of each item pair in the current order item set are accumulated to obtain a combined risk score. Based on the interception accuracy feedback of the precise rule channel and the local context risk channel within a set period, the fusion weight and interception threshold of the precise rule channel and the local context risk channel are adaptively adjusted. When the number of false alarms of the local context risk channel reaches the first threshold, the interception threshold is increased. After the missed alarm combination of the local context risk channel is confirmed, it is included in the mutual exclusion table and taken over by the precise rule channel. For project combinations whose combined risk scores exceed the interception threshold, a soft interception is performed, and a risk warning and alternative project suggestions are displayed. The operator then performs a release operation or an adjustment operation. The project portfolio that has undergone the release operation is added to the observation list. When the number of release operations reaches the second threshold, the context risk score of the project portfolio is lowered. When the number of adjustment operations reaches the third threshold, the project portfolio is proposed to be included as the mutually exclusive record. Both the second threshold and the third threshold are greater than zero.

11. The method for configuring mutual exclusion and association relationships of physical examination items and verifying order issuance according to claim 8, characterized in that, The method further includes: Starting from the change event record, a forward impact propagation is performed, and the direct impact set and indirect impact set are determined along the order level, project level and cost level. The direct impact set is the set of orders containing the change project, and the indirect impact set is the order containing the associated project due to the coupling of the association table with the change project and the order due to the conflict between the mutual exclusion table and the replacement item, thus obtaining the change impact range set. For each order in the range of changes, reverse location tracing is performed to determine the cause chain of each order being affected. The cause chain includes records of the change events involved, records of the relationships involved, and the cost items involved. Order-level impact cause descriptions are generated to obtain a list of affected orders with cause chains. Incremental cost recalculation is performed only for orders in the affected order list with cause chain. The cost change is calculated based on the difference between the refund amount of the removed item, the supplementary fee amount of the added item, and the price adjustment item. Orders not included in the affected order list with cause chain are not recalculated. Based on the results of the incremental cost recalculation and the cause chain, a change impact report is generated. The change impact report includes the number of affected orders, the total cost change, the cost change details for each order, and the corresponding cause chain. The change impact report is pushed to the billing process and the inspected object, and the change impact report is associated with the change event record in the change history database and archived to obtain the change impact file.

12. A system for configuring mutual exclusion and association relationships of physical examination items and for verifying order issuance, characterized in that, include: The relationship configuration and maintenance module is used to maintain mutually exclusive relationship tables, related relationship tables, and exception whitelists based on medical business rules and project libraries, resulting in a relationship rule library that can be adjusted online and takes effect immediately. The associated project extraction module is used to automatically extract associated projects and include them in the cost when a main project with an associated tag is selected in the order opening interface, based on the relationship rule base, to obtain a combination of associated projects. The mutual exclusion verification and interception module is used to perform mutual exclusion detection when adding items and saving orders based on the associated item combination, the mutual exclusion relationship table and the exception whitelist. When a mutual exclusion record is hit, it will prompt and intercept the mutual exclusion detection. For items in the exception whitelist, the mutual exclusion detection will be skipped and a record will be left, and an effective physical examination order will be obtained. The change traceability and recalculation module is used to record the content before and after the change and the operator to form a change history database based on the project change operation, and automatically recalculate the cost changes of the effective medical examination order based on the change history database to obtain the order file with traceable changes.

Images