Method and system for centralized management of value sets in multi-industry scenarios

Abstract

The application provides a system and method for centralized management of value sets in a multi-industry scenario, comprising: a value set warehouse management module for hierarchical management of value sets through a preset warehouse; a value set item root management module for establishing a value set item root library to standardize management of value set details; a business label management module for maintaining all value sets under one or more business labels; and a value set permission management module for role permission control of the constructed value set warehouse and range authorization by superimposing business labels.

Description

Technical Field

[0001] This invention relates to the field of unified master data management technology, specifically to a method and system for centralized management of value sets in multi-industry scenarios, and more specifically to a technical method for unified management of value sets in multi-industry and cross-domain scenarios, adapting to various heterogeneous applications. This invention can be widely applied to unified master data management and data sharing scenarios in group enterprises. Background Technology

[0002] In existing technologies, under a unified industrial internet architecture, interoperability and integration across industries and bases are constructed. This promotes a cross-spatial interoperability and integration system with a "one headquarters, multiple bases" structure. It achieves collaboration between specialized management and existing regional management, improving management efficiency. Through the integration of "operation, inspection, maintenance, and adjustment," cross-human-machine interface interoperability and integration are realized. Against this backdrop, unified data governance across systems is particularly important. The unified management of value sets within the systems serves as a unified language for business technologies. Strong control and unification are required to ensure consistent data language across systems, eliminate information gaps, and reduce the difficulty of data cleaning during subsequent data analysis. This addresses the pain points of redundant component construction in the original independent and decentralized management model, and the need for offline synchronization or relative synchronization through mapping relationships across multiple systems.

[0003] To address the issues of independently and dispersed management of numerous related business systems across multiple industries in the system construction of large group enterprises, avoidance of redundant value set maintenance, lack of unified standards for common value set code, and inconsistent coding specifications, a unified, centralized, and standardized management system for value set code is constructed across industries and domains. This system supports the convenient use of value sets in complex, customized, and lightweight applications, forming an important foundational reference data asset for group enterprises.

[0004] Patent document CN110913023A (application number: 201911380057.8) discloses a big data management platform for industrial parks. This platform includes a dynamic data acquisition system, an infrastructure sub-control system, an environmental monitoring system, a resource reporting system, an Internet of Things system, a comprehensive management system, and a security early warning system. The platform aggregates various data within the park and monitors the park from multiple aspects such as dynamic data, infrastructure, environment, and resources. The data has greater granularity and coverage. At the same time, the data acquisition, reporting, and processing analysis on this platform are all carried out through network channels, resulting in stronger data timeliness and better meeting the current needs for grid-based, refined, and digital data management. Summary of the Invention

[0005] To address the shortcomings of existing technologies, the purpose of this invention is to provide a method and system for centralized management of value sets in multi-industry scenarios.

[0006] According to the present invention, a system for centralized management of value sets in a multi-industry scenario includes:

[0007] Value Set Warehouse Management Module: Enables hierarchical management of value sets through different preset warehouses;

[0008] Value set item radical management module: Establish a value set item radical library and use the value set item radical library to manage value set details in a standardized manner;

[0009] Business tag management module: Maintains all value sets under one or more business tags;

[0010] Value set permission management module: Controls role-based permissions for the built value set repository and adds business tags for scope authorization.

[0011] Preferably, in the value set warehouse management module, a hierarchical management system for value sets is established, including a public library, a business domain library, and an application private library.

[0012] The public library is used to manage common value set codes;

[0013] The business domain library is used to divide the common value set code for different industries or fields;

[0014] The application's private library is used to manage private value sets of code that do not have shared attributes.

[0015] Preferably, in the value set item root management module, the root is the most basic element in the meaning of the value set details item. The definition of each details item is derived through the root, and the meaning of the details item is automatically detected. When it does not conform to the preset rules, it is marked accordingly to ensure the standardization of the meaning of the details item.

[0016] Preferably, in the value set permission management module, the permission control roles for value sets include creators and editors; the creator has the permissions to add, modify, and delete all value sets under the corresponding business tag scope; the editor supports adding, modifying, and deleting detailed items under the value set.

[0017] Preferably, the value set management system uses value sets by employing both remote direct call mode and local cache call mode;

[0018] The remote direct call mode is to remotely call the value set service by passing the value set code through a POST request, and pull the detailed item information under the corresponding value set.

[0019] The local cache call mode involves subscribing to specified repository value set information through a value set push list, pulling the relevant value set data, caching it locally, and then using it through the cache.

[0020] Preferably, the value set code management module includes value set code maintenance, service management, version management, change history management, filter management, and push list management;

[0021] The value set code maintenance refers to the editing and management of value set codes. Value set codes include ordinary value sets and cascaded value sets. Ordinary value sets are based on a code-meaning format for detail item mapping. Cascaded value sets consist of multiple cascaded sub-details, supporting fixed detail item associations to form a tree structure, creating a clear, non-dynamically changing cascaded value set; or multiple ordinary value sets can be nested to form multi-level dynamic cascaded value sets, supporting nested relationships between value sets. After defining a cascaded value set, it is associated with an ordinary value set. Then, each detail item under an ordinary value set is associated with other ordinary value sets, forming multi-level dynamic cascaded value sets. When value sets change, the corresponding ordinary value set details are modified, and the cascaded relationships are automatically and dynamically mapped. The meaning corresponding to the code of each value set detail item is obtained through value set item root management.

[0022] Service management refers to the publicly available list of services and interface documentation provided by the value set management system.

[0023] Value set version management is a versioned management of value set content. It determines whether the content has changed by calculating the hash value of the value set details. When a change occurs, it triggers the saving of a new version. If the hash values ​​before and after the modification are the same, it is determined that no content has changed and no redundant version saving operation is performed.

[0024] Change history management records the addition, deletion, modification, and query audit items of core data in the value set management platform to ensure the traceability of data operations and meet data security requirements;

[0025] Filter management is for scenarios where a large set of values ​​is split into multiple smaller sets of values ​​based on different conditions, thereby reducing the construction of duplicate value sets;

[0026] Push list management is designed for scenarios where value sets use local caching. It creates value set push lists at the application level for multiple applications to subscribe to, enabling data retrieval from local caches. Event listening via message queues triggers the synchronization of value set data within the list to various application systems. When value set content changes, a message queue mechanism is used for message transmission, and application systems listen for events, triggering the retrieval of value set code data information from the subscribed list scope and synchronizing it locally. The value set push list is directly associated with the repository information to be subscribed to. When retrieving the value set list, the repository is associated with the value sets managed within that repository for unified data retrieval.

[0027] Preferably, the analysis audit management module generates audit items based on the operation behavior log;

[0028] The operation behavior log includes the operation behavior log records of the value set code management module.

[0029] A method for centralized management of value sets in a multi-industry scenario, provided by the present invention, includes:

[0030] Step S1: The value set warehouse management module manages value sets hierarchically through different preset warehouses;

[0031] Step S2: The value set item radical management module establishes a value set item radical library and uses the value set item radical library to standardize the management of value set details;

[0032] Step S3: The business tag management module maintains all value sets under one or more business tags;

[0033] Step S4: The value set permission management module performs role-based permission control on the constructed value set repository and adds business tags for scope authorization.

[0034] Preferably, in the value set warehouse management module, a hierarchical management system for value sets is established, including a public library, a business domain library, and an application private library.

[0035] The public library is used to manage common value set codes;

[0036] The business domain library is used to divide the common value set code for different industries or fields;

[0037] The application's private library is used to manage its own private value set code that does not have shared attributes;

[0038] In the value set item root management module, the root is the most basic element in the meaning of the value set details. The definition of each details item is derived through the root. The meaning of the details item is automatically detected. When it does not conform to the preset rules, it is marked accordingly to ensure the standardization of the meaning of the details item.

[0039] In the value set permission management module, the permission control roles for value sets include creators and editors; creators have the permissions to add, modify, and delete all value sets under the corresponding business tag scope; editors support adding, modifying, and deleting detailed items under the value set.

[0040] Preferably, the value set management system uses value sets by employing both remote direct call mode and local cache call mode;

[0041] The remote direct call mode is to remotely call the value set service by passing the value set code through a POST request, and pull the detailed item information under the corresponding value set.

[0042] The local cache call mode subscribes to the specified repository value set information through the value set push list, pulls the relevant value set data, caches it locally, and then uses it through the cache.

[0043] The value set code management module includes value set code maintenance, service management, version management, change history management, filter management, and push list management;

[0044] The value set code maintenance refers to the editing and management of value set codes. Value set codes include ordinary value sets and cascaded value sets. Ordinary value sets are based on a code-meaning format for detail item mapping. Cascaded value sets consist of multiple cascaded sub-details, supporting fixed detail item associations to form a tree structure, creating a clear, non-dynamically changing cascaded value set; or multiple ordinary value sets can be nested to form multi-level dynamic cascaded value sets, supporting nested relationships between value sets. After defining a cascaded value set, it is associated with an ordinary value set. Then, each detail item under an ordinary value set is associated with other ordinary value sets, forming multi-level dynamic cascaded value sets. When value sets change, the corresponding ordinary value set details are modified, and the cascaded relationships are automatically and dynamically mapped. The meaning corresponding to the code of each value set detail item is obtained through value set item root management.

[0045] Service management refers to the publicly available list of services and interface documentation provided by the value set management system.

[0046] Value set version management is a versioned management of value set content. It determines whether the content has changed by calculating the hash value of the value set details. When a change occurs, it triggers the saving of a new version. If the hash values ​​before and after the modification are the same, it is determined that no content has changed and no redundant version saving operation is performed.

[0047] Change history management records the addition, deletion, modification, and query audit items of core data in the value set management platform to ensure the traceability of data operations and meet data security requirements;

[0048] Filter management is for scenarios where a large set of values ​​is split into multiple smaller sets of values ​​based on different conditions, thereby reducing the construction of duplicate value sets;

[0049] Push list management is designed for scenarios where value sets use local caching. It creates value set push lists at the application level for multiple applications to subscribe to, enabling data retrieval from local caches. Event listening via message queues triggers the synchronization of value set data within the list to various application systems. When the value set content changes, a message queue mechanism is used for message transmission. Application systems listen for events, triggering the retrieval of value set code data information from the subscribed list scope and synchronizing it locally. The value set push list is directly associated with the repository information to be subscribed to. When retrieving the value set list, the repository is associated with the value sets managed within that repository for unified data retrieval.

[0050] The analysis and audit management module generates audit items based on operation behavior logs;

[0051] The operation behavior log includes the operation behavior log records of the value set code management module.

[0052] Compared with the prior art, the present invention has the following beneficial effects:

[0053] 1. This invention forms a unified value set management system for the group, realizing a unified management model for key business reference data across industries and heterogeneous systems, reducing the interaction costs between systems and redundant construction investment.

[0054] 2. By leveraging technologies such as message queues, ELK log collection, and centralized containerized deployment, unified, centralized, tagged, traceable, and standardized management of value set code across various industries and business lines is achieved. This solves the problem of unifying value set languages ​​across multiple business lines and heterogeneous systems across industries. It also reduces language conversion and mapping work during system data interaction. Attached Figure Description

[0055] Other features, objects, and advantages of the present invention will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings:

[0056] Figure 1 This is a diagram illustrating the overall functional structure of value set management.

[0057] Figure 2 The process for applying for a value set repository.

[0058] Figure 3 For the cascaded value set model one - direct association of ordinary detail items.

[0059] Figure 4 For the cascaded value set model two – ordinary value set associated with ordinary value set.

[0060] Figure 5 A version control scheme for value sets.

[0061] Figure 6 Use the overall scheme for the value set. Detailed Implementation

[0062] The present invention will now be described in detail with reference to specific embodiments. These embodiments will help those skilled in the art to further understand the present invention, but do not limit the invention in any way. It should be noted that those skilled in the art can make several changes and improvements without departing from the concept of the present invention. These all fall within the protection scope of the present invention.

[0063] Example 1

[0064] According to the present invention, a system for centralized management of value sets in a multi-industry scenario includes:

[0065] Value Set Warehouse Management Module: Enables hierarchical management of value sets through different preset warehouses;

[0066] Value set item radical management module: Establish a value set item radical library and use the value set item radical library to manage value set details in a standardized manner;

[0067] Business tag management module: Maintains all value sets under one or more business tags;

[0068] Value set permission management module: Controls role-based permissions for the built value set repository and adds business tags for scope authorization.

[0069] Specifically, in the value set warehouse management module, a hierarchical management system for value sets is established, including a public library, a business domain library, and an application private library.

[0070] The public library is used to manage common value set codes;

[0071] The business domain library is used to divide the common value set code for different industries or fields;

[0072] The application's private library is used to manage private value sets of code that do not have shared attributes.

[0073] Specifically, in the value set item root management module, the root is the most basic element in the meaning of the value set details item. The definition of each details item is derived through the root, and the meaning of the details item is automatically detected. When it does not conform to the preset rules, it is marked accordingly to ensure the standardization of the meaning of the details item.

[0074] Specifically, in the value set permission management module, the permission control roles for value sets include creators and editors; creators have the permissions to add, modify, and delete all value sets under the corresponding business tag scope; editors support adding, modifying, and deleting detailed items under the value set.

[0075] Specifically, the value set management system uses value sets by employing both remote direct call mode and local cache call mode;

[0076] The remote direct call mode is to remotely call the value set service by passing the value set code through a POST request, and pull the detailed item information under the corresponding value set.

[0077] The local cache call mode involves subscribing to specified repository value set information through a value set push list, pulling the relevant value set data, caching it locally, and then using it through the cache.

[0078] Specifically, the value set code management module includes value set code maintenance, service management, version management, change history management, filter management, and push list management;

[0079] The value set code maintenance refers to the editing and management of value set codes. Value set codes include ordinary value sets and cascaded value sets. Ordinary value sets are based on a code-meaning format for detail item mapping. Cascaded value sets consist of multiple cascaded sub-details, supporting fixed detail item associations to form a tree structure, creating a clear, non-dynamically changing cascaded value set; or multiple ordinary value sets can be nested to form multi-level dynamic cascaded value sets, supporting nested relationships between value sets. After defining a cascaded value set, it is associated with an ordinary value set. Then, each detail item under an ordinary value set is associated with other ordinary value sets, forming multi-level dynamic cascaded value sets. When value sets change, the corresponding ordinary value set details are modified, and the cascaded relationships are automatically and dynamically mapped. The meaning corresponding to the code of each value set detail item is obtained through value set item root management.

[0080] Service management refers to the publicly available list of services and interface documentation provided by the value set management system.

[0081] Value set version management is a versioned management of value set content. It determines whether the content has changed by calculating the hash value of the value set details. When a change occurs, it triggers the saving of a new version. If the hash values ​​before and after the modification are the same, it is determined that no content has changed and no redundant version saving operation is performed.

[0082] Change history management records the addition, deletion, modification, and query audit items of core data in the value set management platform to ensure the traceability of data operations and meet data security requirements;

[0083] Filter management is for scenarios where a large set of values ​​is split into multiple smaller sets of values ​​based on different conditions, thereby reducing the construction of duplicate value sets;

[0084] Push list management is designed for scenarios where value sets use local caching. It creates value set push lists at the application level for multiple applications to subscribe to, enabling data retrieval from local caches. Event listening via message queues triggers the synchronization of value set data within the list to various application systems. When value set content changes, a message queue mechanism is used for message transmission, and application systems listen for events, triggering the retrieval of value set code data information from the subscribed list scope and synchronizing it locally. The value set push list is directly associated with the repository information to be subscribed to. When retrieving the value set list, the repository is associated with the value sets managed within that repository for unified data retrieval.

[0085] Specifically, the audit management module analyzes and generates audit items based on operation behavior logs;

[0086] The operation behavior log includes the operation behavior log records of the value set code management module.

[0087] A method for centralized management of value sets in a multi-industry scenario, provided by the present invention, includes:

[0088] Step S1: The value set warehouse management module manages value sets hierarchically through different preset warehouses;

[0089] Step S2: The value set item radical management module establishes a value set item radical library and uses the value set item radical library to standardize the management of value set details;

[0090] Step S3: The business tag management module maintains all value sets under one or more business tags;

[0091] Step S4: The value set permission management module performs role-based permission control on the constructed value set repository and adds business tags for scope authorization.

[0092] Specifically, in the value set warehouse management module, a hierarchical management system for value sets is established, including a public library, a business domain library, and an application private library.

[0093] The public library is used to manage common value set codes;

[0094] The business domain library is used to divide the common value set code for different industries or fields;

[0095] The application's private library is used to manage private value sets of code that do not have shared attributes.

[0096] Specifically, in the value set item root management module, the root is the most basic element in the meaning of the value set details item. The definition of each details item is derived through the root, and the meaning of the details item is automatically detected. When it does not conform to the preset rules, it is marked accordingly to ensure the standardization of the meaning of the details item.

[0097] Specifically, in the value set permission management module, the permission control roles for value sets include creators and editors; creators have the permissions to add, modify, and delete all value sets under the corresponding business tag scope; editors support adding, modifying, and deleting detailed items under the value set.

[0098] Specifically, the value set management system uses value sets by employing both remote direct call mode and local cache call mode;

[0099] The remote direct call mode is to remotely call the value set service by passing the value set code through a POST request, and pull the detailed item information under the corresponding value set.

[0100] The local cache call mode involves subscribing to specified repository value set information through a value set push list, pulling the relevant value set data, caching it locally, and then using it through the cache.

[0101] Specifically, the value set code management module includes value set code maintenance, service management, version management, change history management, filter management, and push list management;

[0102] The value set code maintenance refers to the editing and management of value set codes. Value set codes include ordinary value sets and cascaded value sets. Ordinary value sets are based on a code-meaning format for detail item mapping. Cascaded value sets consist of multiple cascaded sub-details, supporting fixed detail item associations to form a tree structure, creating a clear, non-dynamically changing cascaded value set; or multiple ordinary value sets can be nested to form multi-level dynamic cascaded value sets, supporting nested relationships between value sets. After defining a cascaded value set, it is associated with an ordinary value set. Then, each detail item under an ordinary value set is associated with other ordinary value sets, forming multi-level dynamic cascaded value sets. When value sets change, the corresponding ordinary value set details are modified, and the cascaded relationships are automatically and dynamically mapped. The meaning corresponding to the code of each value set detail item is obtained through value set item root management.

[0103] Service management refers to the publicly available list of services and interface documentation provided by the value set management system.

[0104] Value set version management is a versioned management of value set content. It determines whether the content has changed by calculating the hash value of the value set details. When a change occurs, it triggers the saving of a new version. If the hash values ​​before and after the modification are the same, it is determined that no content has changed and no redundant version saving operation is performed.

[0105] Change history management records the addition, deletion, modification, and query audit items of core data in the value set management platform to ensure the traceability of data operations and meet data security requirements;

[0106] Filter management is for scenarios where a large set of values ​​is split into multiple smaller sets of values ​​based on different conditions, thereby reducing the construction of duplicate value sets;

[0107] Push list management is designed for scenarios where value sets use local caching. It creates value set push lists at the application level for multiple applications to subscribe to, enabling data retrieval from local caches. Event listening via message queues triggers the synchronization of value set data within the list to various application systems. When value set content changes, a message queue mechanism is used for message transmission, and application systems listen for events, triggering the retrieval of value set code data information from the subscribed list scope and synchronizing it locally. The value set push list is directly associated with the repository information to be subscribed to. When retrieving the value set list, the repository is associated with the value sets managed within that repository for unified data retrieval.

[0108] Specifically, the audit management module analyzes and generates audit items based on operation behavior logs;

[0109] The operation behavior log includes the operation behavior log records of the value set code management module.

[0110] Example 2

[0111] Example 2 is a preferred example of Example 1.

[0112] This invention addresses the current situation of fragmented and inconsistent management of value set codes by proposing a design scheme based on unified and centralized value set management and on-demand data distribution. It helps enterprises achieve unified and standardized management of value sets across various heterogeneous systems across industries, based on a unified value set management component. This design scheme mainly includes modules such as value set repository management, value set item root management, value set permission management, value set code management, and analysis and audit management. It centrally manages value set codes from various industries and business lines in a unified, centralized, tagged, and standardized manner. This solves the problem of unified value set languages ​​across multiple business lines and various heterogeneous systems across industries, reducing language conversion and mapping work during system data interaction. The overall functional architecture is as follows: Figure 1 As shown.

[0113] Value set repository management uses repositories to manage value sets hierarchically. Repositories are divided into three categories: public repositories, business domain repositories, and application private repositories. Public repositories manage common value set codes, such as fixed universal value set codes for countries, provinces, and currencies. These are maintained and managed uniformly by the value set administrator. Business domain repositories are used to divide public value set codes into different industries or fields, and the repository administrator is responsible for managing the shared value set codes for the corresponding sub-fields within the repository. Application private repositories are used by the system to manage private value set codes that do not have shared attributes.

[0114] Value set warehouse management is the entry point for the entire value set management system; warehouse application approval... Figure 2 Once the process is complete, users first register their identity on the platform through application access to obtain an identity identifier. Then, they apply for a warehouse, which is approved by the value set administrator before warehouse space is allocated. The role permissions of personnel within the warehouse space are assigned and managed by the warehouse administrator.

[0115] Value set item root management aims to standardize the meaning of value set item details by establishing a unified value set item root library for standardized management of value set details. Roots are the most fundamental element in the meaning of value set details, forming the basis for defining their meaning. Each detail item definition should be derived from a root. During information item maintenance, the system automatically detects details derived from roots; those that do not conform to the rules are highlighted and specifically identified, ensuring the standardization of detail item meanings.

[0116] Value set permission management involves controlling permissions after the value set repository is built. This control is applied to subsequent value set maintenance, with two roles: creators and editors. Business tags are also used for scoped authorization, achieving the goal of business-domain-based permission isolation and control within the repository. Creators have permissions to add, modify, and delete all value sets within their corresponding business tag scope. Editors only support adding, modifying, and deleting detailed items within a value set. This approach is suitable for scenarios where system personnel determine value set codes, and business personnel maintain sub-items, preventing accidental deletion of value sets from affecting related system functions.

[0117] Value set code management ensures that all value set code is stored in a unified repository built within the value set repository management system. All value sets must be maintained under one or more business tags, with subsequent editing and maintenance permissions controlled through these tags. Value set management includes value set code maintenance, service management, version management, change history management, filter management, and push list management.

[0118] Value set code maintenance primarily involves editing and managing value set codes, which are divided into two categories: ordinary value sets and cascading value sets. Ordinary value sets are simple item mappings (code-meaning (key-value) format). Cascading value sets support two models:

[0119] It consists of multiple cascading sub-items, with the following structural relationship: Figure 3 As shown, it supports the association of fixed detailed items to form a tree structure, creating a clear and static set of cascading values;

[0120] Multiple nested ordinary value sets form a multi-layered dynamic cascaded value set, with the structural relationship as follows: Figure 4 As shown, nested relationships between value sets are supported. After defining a cascading value set, it is associated with a parent value set (ordinary value set). Each detailed item under the parent value set is then associated with other value sets (ordinary value sets), forming a multi-layered dynamic cascading value set. When a value set changes, the corresponding ordinary value set details are modified, and the cascading relationship is automatically and dynamically mapped. For example, in a province-city cascading value set, "province" can be an independent value set library, not directly enumerated in the cascading value set. All detailed items under the "province" value set library are associated with an independent "city" value set library. When data changes in a municipality under a province, only the corresponding independent value set library of the "city" needs to be modified. This ensures that changing one value set dynamically keeps the related cascading value sets synchronized, guaranteeing the consistency of related value set data.

[0121] The meaning of the encoding for each value in the value set details comes from the root management of the value set items. The meaning of the encoding is managed through root standardization to prevent ambiguity.

[0122] Service management includes a list of publicly available services provided by the value set management system, as well as interface documentation, to facilitate integration and use by various systems.

[0123] Value set version management involves versioning the content of a value set. Versioning management modes include: Figure 5 As shown, the hash value of the detailed set of the value set is used to determine whether the content has changed. If it has changed, a new version is saved. If the hash value before and after the modification is the same, it is determined that the content has not changed and no redundant version saving operation is performed, thereby reducing redundant versions and improving overall efficiency.

[0124] Change history management records audit items such as additions, deletions, modifications, and queries of core data in the value set management platform to ensure the traceability of data operations and meet data security requirements.

[0125] Filter management allows for the splitting of large value sets into multiple smaller value sets based on different criteria, reducing the creation of duplicate value sets.

[0126] The system uses two modes when using value sets:

[0127] Remote direct invocation: This method uses a POST request to pass the value set encoding to remotely invoke the value set service and retrieve detailed item information from the corresponding value set. Suitable for lightweight applications.

[0128] Local cache calls subscribe to a specified repository value set information via a value set push list, retrieve the relevant value set data, cache it locally on the system, and then use it through the cache. Figure 6 The schematic diagram is suitable for medium to large-sized systems with high performance requirements.

[0129] Value set push list management addresses scenarios where value sets utilize local caching. It creates value set push lists at the application level for multiple applications to subscribe to, enabling data retrieval and local caching. The list is configured with a list administrator, who by default is the administrator of the application managed by the creator. List subscribers can also be managed. Event listening via message queues triggers the synchronization of value set data across various systems. When value set content changes, messages are passed through the message queue mechanism, and the system listens for events, triggering the retrieval of value set code data information from the subscribed list scope and synchronizing it locally. This achieves the goal of sharing a single list across multiple systems. The list is directly associated with the repository information to be subscribed to. When the caller retrieves the value set list, it associates the value sets managed within the repository for unified data retrieval, facilitating local caching and improving system call performance.

[0130] The analysis and audit management system includes the operation behavior logs of the value set code management module and the value set push list management module, and audit items are generated based on these logs. This ensures the traceability of all system operations.

[0131] Those skilled in the art will understand that, in addition to implementing the system, apparatus, and their modules provided by this invention in purely computer-readable program code, the same program can be implemented in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers by logically programming the method steps. Therefore, the system, apparatus, and their modules provided by this invention can be considered a hardware component, and the modules included therein for implementing various programs can also be considered structures within the hardware component; alternatively, modules for implementing various functions can be considered both software programs implementing the method and structures within the hardware component.

[0132] Specific embodiments of the present invention have been described above. It should be understood that the present invention is not limited to the specific embodiments described above, and those skilled in the art can make various changes or modifications within the scope of the claims, which do not affect the essence of the present invention. Unless otherwise specified, the embodiments and features described in this application can be arbitrarily combined with each other.

Claims

1. A system for centralized management of value sets in a multi-industry scenario, characterized in that, include: Value Set Warehouse Management Module: Enables hierarchical management of value sets through different preset warehouses; Value set item radical management module: Establish a value set item radical library and use the value set item radical library to manage value set details in a standardized manner; Business tag management module: Maintains all value sets under one or more business tags; Value set permission management module: performs role-based permission control on the constructed value set repository, and adds business tags for scope authorization; In the value set warehouse management module, a hierarchical management system for value sets is established, including a public library, a business domain library, and an application private library. The public library is used to manage common value set codes; The business domain library is used to divide the common value set code for different industries or fields; The application's private library is used to manage private value sets of code that do not have shared attributes.

2. The system for centralized management of value sets in a multi-industry scenario according to claim 1, characterized in that, In the value set item root management module, the root is the most basic element in the meaning of the value set details. The definition of each details item is derived through the root. The meaning of the details item is automatically detected. When it does not conform to the preset rules, it is marked accordingly to ensure the standardization of the meaning of the details item.

3. The system for centralized management of value sets in a multi-industry scenario according to claim 1, characterized in that, In the value set permission management module, the permission control roles for value sets include creators and editors; the creator has the permissions to add, modify, and delete all value sets under the corresponding business tag scope; Editors can add, modify, and delete detailed items under a value set.

4. The system for centralized management of value sets in a multi-industry scenario according to claim 1, characterized in that, The value set management system uses value sets through both remote direct call mode and local cache call mode; The remote direct call mode is to remotely call the value set service by passing the value set code through a POST request, and pull the detailed item information under the corresponding value set. The local cache call mode involves subscribing to specified repository value set information through a value set push list, pulling the relevant value set data, caching it locally, and then using it through the cache.

5. The system for centralized management of value sets in a multi-industry scenario according to claim 1, characterized in that, The value set code management module includes value set code maintenance, service management, version management, change history management, filter management, and push list management; The value set code maintenance refers to the editing and management of value set codes. Value set codes include ordinary value sets and cascaded value sets. Ordinary value sets are detailed item comparisons based on encoding-meaning format. Cascaded value sets consist of multiple cascaded sub-details, supporting fixed detailed item associations to form a tree structure, creating explicit, non-dynamically changing cascaded value sets; or multiple ordinary value sets can be nested to form multi-level dynamic cascaded value sets, supporting nested relationships between value sets. After defining a cascaded value set, it is associated with an ordinary value set. Then, each detailed item under the ordinary value set is associated with other ordinary value sets, forming multi-level dynamic cascaded value sets. When value sets change, the corresponding ordinary value set details are modified, and the cascaded relationships are automatically and dynamically mapped. The meaning of the encoding of the value set details is obtained through the management of the value set item root; Service management refers to the publicly available list of services and interface documentation provided by the value set management system. Value set version management is a versioned management of value set content. It determines whether the content has changed by calculating the hash value of the value set details. When a change occurs, it triggers the saving of a new version. If the hash values ​​before and after the modification are the same, it is determined that no content has changed and no redundant version saving operation is performed. Change history management records the addition, deletion, modification, and query audit items of core data in the value set management platform to ensure the traceability of data operations and meet data security requirements; Filter management is for scenarios where a large set of values ​​is split into multiple smaller sets of values ​​based on different conditions, thereby reducing the construction of duplicate value sets; Push list management is designed for scenarios where value sets use local caching. It creates value set push lists at the application level for multi-application subscription lists and pulls data from local cache. Event listening via message queues triggers the synchronization of value set data under the list to various application systems. When the content of the value set changes, the message queue mechanism transmits messages, and the application system listens for events, triggering the retrieval of value set code data information through the subscribed list range and synchronizing it to the local machine. The value set push list is directly associated with the repository information that needs to be subscribed to. When retrieving the value set list, the value sets managed within the repository are associated with the repository for unified data retrieval.

6. The system for centralized management of value sets in a multi-industry scenario according to claim 1, characterized in that, The analysis and audit management module generates audit items based on operation behavior logs; The operation behavior log includes the operation behavior log records of the value set code management module.

7. A method for centralized management of value sets in a multi-industry scenario, characterized in that, include: Step S1: The value set warehouse management module manages value sets hierarchically through different preset warehouses; Step S2: The value set item radical management module establishes a value set item radical library and uses the value set item radical library to standardize the management of value set details; Step S3: The business tag management module maintains all value sets under one or more business tags; Step S4: The value set permission management module performs role-based permission control on the constructed value set repository and adds business tags for scope authorization; In the value set warehouse management module, a hierarchical management system for value sets is established, including a public library, a business domain library, and an application private library. The public library is used to manage common value set codes; The business domain library is used to divide the common value set code for different industries or fields; The application's private library is used to manage its own private value set code that does not have shared attributes; In the value set item root management module, the root is the most basic element in the meaning of the value set details. The definition of each details item is derived through the root. The meaning of the details item is automatically detected. When it does not conform to the preset rules, it is marked accordingly to ensure the standardization of the meaning of the details item. In the value set permission management module, the permission control roles for value sets include creators and editors; the creator has the permissions to add, modify, and delete all value sets under the corresponding business tag scope; Editors can add, modify, and delete detailed items under a value set.

8. The method for centralized management of value sets in a multi-industry scenario according to claim 7, characterized in that, The value set management system uses value sets through both remote direct call mode and local cache call mode; The remote direct call mode is to remotely call the value set service by passing the value set code through a POST request, and pull the detailed item information under the corresponding value set. The local cache call mode subscribes to specified repository value set information through a value set push list, pulls the relevant value set data, caches it locally, and then uses it through the cache. The value set code management module includes value set code maintenance, service management, version management, change history management, filter management, and push list management; The value set code maintenance refers to the editing and management of value set codes. Value set codes include ordinary value sets and cascaded value sets. Ordinary value sets are detailed item comparisons based on encoding-meaning format. Cascaded value sets consist of multiple cascaded sub-details, supporting fixed detailed item associations to form a tree structure, creating explicit, non-dynamically changing cascaded value sets; or multiple ordinary value sets can be nested to form multi-level dynamic cascaded value sets, supporting nested relationships between value sets. After defining a cascaded value set, it is associated with an ordinary value set. Then, each detailed item under the ordinary value set is associated with other ordinary value sets, forming multi-level dynamic cascaded value sets. When value sets change, the corresponding ordinary value set details are modified, and the cascaded relationships are automatically and dynamically mapped. The meaning of the encoding of the value set details is obtained through the management of the value set item root; Service management refers to the publicly available list of services and interface documentation provided by the value set management system. Value set version management is a versioned management of value set content. It determines whether the content has changed by calculating the hash value of the value set details. When a change occurs, it triggers the saving of a new version. If the hash values ​​before and after the modification are the same, it is determined that no content has changed and no redundant version saving operation is performed. Change history management records the addition, deletion, modification, and query audit items of core data in the value set management platform to ensure the traceability of data operations and meet data security requirements; Filter management is for scenarios where a large set of values ​​is split into multiple smaller sets of values ​​based on different conditions, thereby reducing the construction of duplicate value sets; Push list management is designed for scenarios where value sets use local caching. It creates value set push lists at the application level for multi-application subscription lists and pulls data from local cache. Event listening via message queues triggers the synchronization of value set data under the list to various application systems. When the content of the value set changes, the message queue mechanism transmits messages, and the application system listens for events, triggering the retrieval of value set code data information through the subscribed list range and synchronizing it to the local machine. The value set push list is directly associated with the repository information that needs to be subscribed to. When retrieving the value set list, the value sets managed within the repository are associated with the repository for unified data retrieval. The analysis and audit management module generates audit items based on operation behavior logs; The operation behavior log includes the operation behavior log records of the value set code management module.

Images