Medical term management system and method, electronic equipment and medium

Abstract

The invention provides a medical term management system and method, electronic equipment and a medium, and relates to the field of medical data management, and the system can improve the type and quantity of medical term data and standardize the industrial standard based on the medical standard. The enterprise standard medical term data makes up the blank that the medical standard data volume is not perfect to a certain extent. And the field which cannot be covered by the medical standard is standardized, so that the data volume is systematic, scientific and normative. Seamless switching is carried out among different medical term coding systems in the same concept domain, so that system data are accessed uniformly and used normatively, clinical data are standardized and perfected, and possibility is provided for expansion of data volume.

Description

Technical Field

[0001] The present application relates to the field of medical data management, and in particular, to a management system, method, electronic device and medium for medical terminology. Background Art

[0002] With the continuous development of medical technology, more and more regions are promoting the "common language" of medical information data to achieve interoperability and data recognition of medical information, so as to provide the possibility for medical big data analysis, and provide decision-making support for the formulation of policies such as medical insurance financing, benefit guarantee, payment system, bidding and procurement of drugs and consumables, and fund supervision.

[0003] Up to now, due to the different frequencies and methods of use of medical information data by different users, the huge amount of medical information data cannot be normalized and standardized to achieve data docking. Summary of the invention

[0004] The purpose of the embodiments of the present application is to provide a medical terminology management system, method, electronic device and medium to solve the above-mentioned problems existing in the prior art and to achieve data mutual recognition among multiple regions or multiple systems of medical information data.

[0005] In a first aspect, a medical terminology management system is provided, which may include: a storage unit, an acquisition unit, and a matching unit;

[0006] The acquisition unit is used to acquire user-defined medical terminology data and send the medical terminology data to the matching unit; the medical terminology data includes a preset medical terminology concept domain ID, a custom medical terminology coding system ID, a custom medical terminology ID and a medical terminology text, and a corresponding relationship between the custom medical terminology ID and the medical terminology text;

[0007] The matching unit is used to obtain the medical term text in the medical term data, and match the medical term text with the standard medical term text in the configured preset medical term concept domain; if the match is successful, the successfully matched medical term text, the corresponding custom medical term ID, the custom medical term coding system ID and the corresponding relationship between the custom medical term ID and the medical term text are sent to the storage unit, wherein the preset medical term concept domain is the concept domain corresponding to the preset medical term concept domain ID;

[0008] The storage unit is used to store the custom medical term coding system ID, the custom medical term ID and the medical term text.

[0009] In a possible implementation, the system further includes a mapping unit;

[0010] The acquisition unit is further configured to acquire a request for switching medical term coding including a coding system keyword, and send the coding system keyword to the mapping unit;

[0011] The mapping unit is used to determine the target coding system in the preset medical term concept domain based on the received coding system keyword; match any current medical term text currently displayed with the target medical term text in the target coding system; if the match is successful, obtain the target medical term code of the successfully matched target medical term text in the target coding system through a preset Levenshtein distance algorithm.

[0012] In a possible implementation, the storage unit is further used to store a standard medical terminology coding system ID under a standard coding system and the standard medical terminology text.

[0013] In a possible implementation, the storage unit includes a whitelist module and a blacklist module;

[0014] The whitelist module is used to store a first medical term text and a first medical term ID, and a correspondence between the first medical term ID and the first medical term text; the first medical term ID includes a continuously used standard medical term ID and a continuously used custom medical term ID; the first medical term text includes a standard medical term text corresponding to the continuously used standard medical term ID and a medical term text corresponding to the continuously used custom medical term ID;

[0015] The blacklist module is used to store the abandoned standard medical term IDs and the abandoned custom medical term IDs, as well as the standard medical term texts corresponding to the abandoned standard medical term IDs and the medical term texts corresponding to the abandoned custom medical term IDs.

[0016] In a possible implementation, the matching unit is further configured to push a prompt message including a failure to match the medical term text with the standard medical term text to a processor if the matching fails.

[0017] In a possible implementation, the preset medical terminology concept domain includes multiple target medical terminology coding system IDs.

[0018] In a possible implementation, the storage unit is further used to store a plurality of preset medical terminology concept domains.

[0019] In a second aspect, a method for managing medical terminology is provided, which may include:

[0020] Acquire user-defined medical terminology data; the medical terminology data includes a custom medical terminology coding system ID, a custom medical terminology ID and a medical terminology text, and a corresponding relationship between the custom medical terminology ID and the medical terminology text;

[0021] Matching the medical terminology text with standard medical terminology text in a configured preset medical terminology concept domain;

[0022] If the match is successful, the successfully matched medical term text, the corresponding custom medical term ID, the custom medical term coding system ID and the corresponding relationship between the custom medical term ID and the medical term text are stored.

[0023] In a third aspect, an electronic device is provided, the electronic device comprising a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus;

[0024] Memory, used to store computer programs;

[0025] The processor is used to implement any method step described in the second aspect when executing the program stored in the memory.

[0026] In a fourth aspect, a computer-readable storage medium is provided, wherein a computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, any method step described in the second aspect is implemented.

[0027] The present application provides a medical terminology management system that can improve the types and quantities of medical terminology data and standardize industry standards based on medical standards. The enterprise standard medical terminology data, to a certain extent, fills the gap of the incomplete data volume of medical standards. It also standardizes the areas that medical standards fail to cover, making the data volume systematic, scientific and standardized. By seamlessly switching between different medical terminology coding systems under the same concept domain, the system data is uniformly accessed and used in a standardized manner, which not only standardizes and improves clinical data, but also provides the possibility for expanding the data volume. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments of the present application will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0029] Figure 1A schematic diagram of the structure of a medical terminology management system provided in an embodiment of the present application;

[0030] Figure 2 A timing diagram of the cloud platform publishing medical terms provided in an embodiment of the present application;

[0031] Figure 3 A flowchart of a method for managing medical terms provided in an embodiment of the present application;

[0032] Figure 4 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0033] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments of the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0034] With the continuous development of medical technology, all regions attach great importance to the standardization and informatization of medical insurance, implement "full vertical integration and full horizontal coverage", promote the formation of a "common language" for the exchange of medical insurance information and data from top to bottom across the country, realize the interconnection and data mutual recognition of medical insurance information across the country, provide the possibility for the development of medical insurance big data analysis, and provide decision-making support for the formulation of policies such as medical insurance financing, benefit guarantee, payment system, bidding and procurement of drugs and consumables, and fund supervision.

[0035] So far, relevant departments have issued 15 national unified medical insurance business coding standards, established a coding standard database and dynamic maintenance platform. Four major standard database information have been announced. Among them, there are about 33,000 disease diagnosis codes, about 13,000 surgical operation codes, 11,190 medical service project codes, more than 93,000 medical insurance drug codes, more than 36,000 medical consumables codes, and more than 10 million actual specifications and models. The huge amount of medical information data needs to be standardized and standardized to achieve the connection between medical information data and the mutual recognition of medical information data between systems, which led to the emergence of terminology.

[0036] Therefore, in order to solve the problems of incomplete medical information data, lack of unified application specifications, difficulty in upgrading clinical business data, and inability to connect with other systems, the present application proposes a medical terminology management system, method, electronic device and medium to solve the above-mentioned problems existing in the prior art, and to achieve data mutual recognition among multiple regions or multiple systems of medical information data.

[0037] The preferred embodiments of the present application are described below in conjunction with the drawings in the specification. It should be understood that the preferred embodiments described herein are only used to illustrate and explain the present application, and are not used to limit the present application. In addition, the embodiments and features in the embodiments of the present application may be combined with each other if there is no conflict.

[0038] Figure 1 This is a schematic diagram of the structure of a medical term management system provided in an embodiment of the present application. Figure 1 As shown, the system may include: a storage unit, a matching unit, an acquisition unit and a mapping unit.

[0039] The acquisition unit is used to acquire the medical terminology data defined by the user and send the medical terminology data to the matching unit.

[0040] Among them, the medical terminology data includes a preset medical terminology concept domain ID, a custom medical terminology coding system ID, a custom medical terminology ID and a medical terminology text, and a corresponding relationship between the custom medical terminology ID and the medical terminology text.

[0041] Users of this system can customize the codes for corresponding medical terms or add customized medical terms and corresponding customized codes for customized medical terms according to actual usage requirements.

[0042] A matching unit is used to obtain medical terminology texts in the medical terminology data, and match the medical terminology texts with standard medical terminology texts under the standard coding system ID in the configured preset medical terminology concept domain. It should be noted that there are multiple preset medical terminology concept domains. In the matching process, only the standard coding systems in the preset medical terminology concept domain corresponding to the preset medical terminology concept domain ID provided in the medical terminology data are matched;

[0043] If the match is successful, it indicates that the medical terminology text provided this time also exists under the standard coding system, and the successfully matched medical terminology text, the corresponding custom medical terminology ID, the custom medical terminology coding system ID and the correspondence between the custom medical terminology ID and the medical terminology text are sent to the storage unit.

[0044] If the match is not successful, it indicates that the medical terminology text provided this time does not exist under the standard coding system. The unmatched medical terminology text is semantically processed according to the configured semantic rules to obtain the custom medical terminology text; then, the custom medical terminology text, the corresponding custom medical terminology ID, the custom medical terminology coding system ID and the correspondence between the custom medical terminology ID and the custom medical terminology text are sent to the storage unit.

[0045] In some embodiments, the matching method may adopt a preset matching model to match the medical term text with the standard medical term text under the standard coding system in the configured preset medical term concept domain, which may specifically include:

[0046] Through one-hot encoding, medical terminology text is converted into text high-dimensional vectors, and standard medical terminology text is converted into standard term high-dimensional vectors.

[0047] Through the DNN deep learning model, the high-dimensional text vector is converted into the low-dimensional text vector, and the high-dimensional vector of standard term is converted into the low-dimensional vector of standard term.

[0048] The cosine value between the text low-dimensional vector and the standard term low-dimensional vector is calculated to obtain the target similarity. The target similarity can be understood as the distance between the text low-dimensional vector and the standard term low-dimensional vector.

[0049] When there is a target similarity greater than a preset similarity, it is determined that the medical term text matches the standard medical term text successfully, and the standard medical term text corresponding to the target similarity at this time is determined as the standard medical term text corresponding to the medical term text.

[0050] In some embodiments, the construction of the standard coding system corresponding to the standard coding system ID includes: first, collecting standard medical terms, mainly relying on crawler tools to capture, and tracking the target links one by one. The data is processed in combination with commonly used data preprocessing methods (filtering, cleaning, etc.), and then imported into the database. Secondly, manual screening conditions are added to perform secondary verification on the collected medical terms. Finally, the medical terms are encoded through the medical insurance business coding standards to obtain a standard coding system.

[0051] The storage unit is used to store the medical term text and the corresponding custom medical term ID or the custom medical term text and the corresponding custom medical term ID under the custom medical term coding system corresponding to the existing custom medical term coding system ID when it is determined that the custom medical term coding system ID exists in the current preset medical term concept domain.

[0052] Furthermore, it is used to create a custom medical terminology coding system including the custom medical terminology coding system ID when it is determined that the custom medical terminology coding system ID does not exist in the current preset medical terminology concept domain, and store the medical terminology text or the custom medical terminology text and the corresponding custom medical terminology ID under the custom medical terminology coding system corresponding to the custom medical terminology coding system ID.

[0053] In some embodiments, in order to prevent the arbitrary creation of a custom medical terminology coding system, when it is determined that the custom medical terminology coding system ID does not exist in the current preset medical terminology concept domain, the processor needs to generate an approval request including the custom medical terminology coding system ID, the custom medical terminology ID, the custom medical terminology text or the medical terminology text through the terminal, and send the approval request to the corresponding approver (the relevant personnel of the information department review the general medical terminology, and the department teacher reviews the clinical terminology). After obtaining the approval result, the storage unit stores it. This method can be understood as the process of the hospital side publishing the custom medical terminology text and the custom medical terminology ID.

[0054] Among them, the storage unit is also used to store multiple preset medical terminology concept domains, and there are multiple medical terminology coding systems in each preset medical terminology concept domain, for example, the standard coding system corresponding to the standard coding system ID mentioned above and the custom medical terminology coding system corresponding to the custom medical terminology coding system ID. Simply put, the concept domain abstracts medical terms; each system consists of a complete set of term values. For example: the "route of administration" concept domain can be defined by the National Health Commission as coding system 249990, and can also be defined by Weining Health as coding system 97829. In other words, in each system, there is a unique system ID; each medical term text under each system has a corresponding medical term ID.

[0055] In some embodiments, the medical term text under any medical term coding system in the storage unit has no duplicate values, and the corresponding medical term ID also has no duplicate values. With the update of medical terms, there is a problem of updating medical term text. In order to avoid concept confusion and track medical terms, any medical term coding system in the storage unit includes a whitelist module and a blacklist module;

[0056] A whitelist module is used to store a first medical term text and a first medical term ID, as well as a correspondence between the first medical term ID and the first medical term text; the first medical term ID includes a standard medical term ID that is continuously used and a custom medical term ID that is continuously used; the first medical term text includes a standard medical term text corresponding to the standard medical term ID that is continuously used, and a medical term text corresponding to the custom medical term ID that is continuously used;

[0057] The blacklist module is used to store the deprecated standard medical terminology IDs and the deprecated custom medical terminology IDs, as well as the standard medical terminology texts corresponding to the deprecated standard medical terminology IDs and the medical terminology texts corresponding to the deprecated custom medical terminology IDs.

[0058] Furthermore, when you need to access or transfer medical terms, you should also use the medical term ID and medical term coding system ID as the basis. When you need to obtain values ​​in batches, use Map<Long,String> forValueDesc(Long[]soids,Collection <long>valueIds) can also be obtained in batches through the Optional method <valuesetdto>forValue(Long[]soids,Long valueId) single acquisition.

[0059] The acquisition unit is further used to acquire a request for switching medical terminology coding initiated by a user through a terminal, and send the coding system keyword to the mapping unit, wherein the request for switching medical terminology coding includes the coding system keyword.

[0060] Before generating a request to switch medical terminology coding, at the front end of the system provided by this application, the operation process of the relevant personnel is as follows:

[0061] 1. Select the mapping task, specify the target reference system (target coding system) and the source reference system (the coding system currently displayed);

[0062] 2. Trigger the [Term Mapping] button and switch to the Term Mapping tab;

[0063] 3. Trigger the [Add Term Mapping] button, search and select "Target Source Coding System" and "Source Coding System";

[0064] 4. Triggering [OK] will only save the data; clicking [Smart Mapping] will intelligently match the data according to the algorithm and perform mapping association;

[0065] 5. On the term mapping editing page, you can manually maintain the mapping relationship.

[0066] Mapping rules include smart mapping and manual mapping; smart mapping implements batch management of mappings, and manual mapping implements customized management of mappings.

[0067] The mapping unit is used to determine the target coding system in the preset medical term concept domain according to the received coding system keywords; match any current medical term text currently displayed with the target medical term text in the target coding system; if the match is successful, obtain the target medical term code of the successfully matched target medical term text in the target coding system through the preset Levenshtein distance algorithm.

[0068] This method is to switch the coding system according to actual usage needs. In simple terms, the standard terminology and the enterprise standard terminology are switched. Furthermore, some terms cannot be fully mapped to appropriate terms, which can be achieved through manual mapping. Mapping can enable multiple sets of coding systems to be fully switched to fill the gap in intelligent mapping.

[0069] The term mapping allows data to be transmitted to different systems. By building a "mapping" bridge, the interconnection of systems can be achieved.

[0070] Among them, the preset Levenshtein distance algorithm means that after the current medical term text and the target medical term text are successfully matched, the current medical term code (00123) corresponding to the current medical term text and the target medical term code (01123) corresponding to the target medical term text are converted. Specifically, the distance between the corresponding character strings of the two is calculated to obtain the minimum number of encodings required to convert a character into a corresponding character, that is, to replace one character with another character or insert a character or delete a character. For example: if any encoding operation is required to replace 0 in the first position with 0, and 1 in the second position with 0, the corresponding encoding operation needs to be performed, and the replacement is performed in sequence; finally, "01123" replaces "00123".

[0071] Levenshtein distance algorithm, specific analysis process:

[0072] For example, there are two strings abc and abe;

[0073] The strings abc and abe are displayed in the structure of Table 1. Among them, the A value is the value to be calculated.

[0074] Table 1

[0075] String abc a b c abe 0 1 2 3 a 1 A b 2 e 3

[0076] The calculation method of A value is: A value depends on: 1 on the left, 1 on the top, and 0 in the upper left corner.

[0077] First, the value on the top and the value on the left are both required to be added by 1, so that 1+1=2 is obtained. At this time, the value on the top and the value on the left are 2 respectively.

[0078] Secondly, since the corresponding position of A in the two strings is a, the value of the upper left corner is added by 0. This gives 0+0=0, and the value of the upper left corner is 0.

[0079] Finally, there are currently three values: the value on the top is 2, the value on the left is 2, and the value in the upper left corner is 0. The value of A takes the smallest value among them, 0, that is, the value of A is 0, as shown in Table 2.

[0080] Table 2

[0081] String abc a b c abe 0 1 2 3 a 1 0 b 2 B e 3

[0082] Combined with Table 2, the B value is calculated in the same way:

[0083] The initial value of B is also three values, including: the value on the left is 3, and the value on the top is 1; since the characters of B in the corresponding positions of the two strings are different (a and b), the value of the upper left corner is added by 1 based on the current value, so that 1+1=2 is obtained, and the smallest one is selected from (3,1,2) as the value of B, that is, the value of B is 1, as shown in Table 3.

[0084] Table 3

[0085] String abc a b c abe 0 1 2 3 a 1 0 b 2 1 e 3 C

[0086] The calculation process of the C value is: the value on the top is 2, the value on the left is 4, and since a and e in the upper left corner are different, add 1, that is, 2+1, and the value in the upper left corner is 3.

[0087] The smallest value among (2,4,3) is the C value, that is, the C value is 2.

[0088] Further, the D value to the I value in Table 4 are calculated in sequence.

[0089] Table 4

[0090] String abc a b c abe 0 1 2 3 a 1 A＝0 D＝1 G＝2 b 2 B＝1 E＝0 H＝1 e 3 C＝2 F＝1 I＝1

[0091] I: Indicates that abc and abe have one operation that needs to be edited.

[0092] At the same time, some additional data is also obtained.

[0093] A: Indicates that a and a are the same string, and 0 operations are required.

[0094] B: Indicates that ab and a need to have 1 operation.

[0095] C: Indicates that abe and a require 2 operations.

[0096] D: Indicates that a and ab require 1 operation.

[0097] E: Indicates that ab and ab strings are the same, and 0 operations are required.

[0098] F: Indicates that abe and ab need to have 1 operation.

[0099] G: Indicates that a and abc require 2 operations.

[0100] H: Indicates that ab and abc require 1 operation.

[0101] I: Indicates that abe and abc require 1 operation.

[0102] After that, the similarity is calculated. Specifically, the maximum value maxLen of the lengths of the two strings is taken, and 1-(required number of operations / maxLen) is used to obtain the similarity.

[0103] For example, abc and abe require one operation with a length of 3, so the similarity is 1-1 / 3=0.666.

[0104] If floatValue(similarity)=1, it is directly mapped and the mapping status is mapped;

[0105] If the value floatValue<1, it means that there is only one match that is not verified. When there are multiple matches, the maximum mapping is taken when the difference between the maximum mapping degree and the second mapping degree is greater than 0.7, and the mapping status is unverified. In other cases, no mapping is performed.

[0106] It should be noted that the above-mentioned units can be set up in the cloud platform to achieve the distribution of medical terms and the storage of medical terms on the cloud platform.

[0107] Combination Figure 2 As shown, the cloud platform (cloud operation platform and cloud operation and maintenance platform) publishes medical terminology, adds a new login method in the authentication type, maintains value coding, value meaning and other attributes, from the "standard development", "standard review", "data submission" to "patch upgrade" of medical terminology, and finally publishes it to various sites (users, which can also be understood as the hospital side).

[0108] The cloud operation platform maintains the newly added login methods in the authentication type, and maintains attributes such as value coding and value set registration. Register the newly added or modified standard medical terminology coding system and / or the corresponding standard medical terminology ID, as well as the standard medical terminology text; then, conduct a standardized review of the above registration content; after the review is passed, generate a data patch including the above content, and submit the data patch to the cloud operation and maintenance platform. The hospital-side management system MDM enables the newly added values ​​(standard medical terminology coding system ID, standard medical terminology ID in the standard medical terminology coding system, and standard medical terminology text) to the outpatient doctor station, and publishes the newly added values ​​to the resident doctor station. The outpatient doctor station and the resident doctor station are configured with the subscription authentication type code in advance.

[0109] Both the cloud platform and the hospital side can register and issue medical terms to complete the storage of medical terms. The differences between the two are as follows:

[0110] 1. The cloud platform completes the standardization of medical terminology and initializes the hospital side to complete the storage of customized medical terminology, realizing the hospital's customization needs.

[0111] 2. Custom medical terms can be edited, imported, deleted, activated, and deactivated; terms issued by the cloud platform cannot be edited or deleted.

[0112] 3. The system data will also be sent through the cloud platform, which is the most basic data indispensable for the operation of the system.

[0113] The addition and modification of medical terms, as well as the creation of concepts for the values ​​under medical terms, are all completed by creating tasks and must be approved by relevant processors; they can be put online after multiple processes and various lines have been tested. The formation and circulation of medical terms have strict screening processes, approval processes, and testing processes. This ensures the standardization, scientificity, professionalism, and systematicness of medical terms.

[0114] In some embodiments, the server of the system of the present application will detect the usage frequency and scope of custom medical terms that exist in the custom medical terminology coding system and do not exist in the standard medical terminology coding system. When the usage scope and / or usage frequency are greater than preset conditions, the corresponding custom medical terms can be added to the standard medical terminology coding system.

[0115] The present application provides a medical terminology management system that can improve the types and quantities of medical terminology data and standardize industry standards based on medical standards. The enterprise standard medical terminology data, to a certain extent, fills the gap of the incomplete data volume of medical standards. It also standardizes the areas that medical standards fail to cover, making the data volume systematic, scientific and standardized. By seamlessly switching between different medical terminology coding systems under the same concept domain, the system data is uniformly accessed and used in a standardized manner, which not only standardizes and improves clinical data, but also provides the possibility for expanding the data volume.

[0116] Figure 3 The following is a flow chart of a method for managing medical terms provided in an embodiment of the present application. Figure 3 As shown, the method may include:

[0117] Step S310: Acquire user-defined medical terminology data.

[0118] Among them, the medical terminology data includes a preset medical terminology concept domain ID, a custom medical terminology coding system ID, a custom medical terminology ID and a medical terminology text, and a corresponding relationship between the custom medical terminology ID and the medical terminology text.

[0119] Step S320: Determine a storage method according to a matching result between the medical term text and a standard medical term text in a configured preset medical term concept domain.

[0120] Specifically, the medical term text is matched with the standard medical term text in the configured preset medical term concept domain; wherein the preset medical term concept domain is the concept domain corresponding to the preset medical term concept domain ID;

[0121] If the match is successful, the successfully matched medical term text, the corresponding custom medical term ID, the custom medical term coding system ID and the corresponding relationship between the custom medical term ID and the medical term text are stored.

[0122] If the match fails, a prompt message including the failure of the medical term text to match the standard medical term text is pushed to the processor, so that the processor generates an approval request including the custom medical term coding system ID, the custom medical term ID, the custom medical term text or the medical term text through the terminal, and sends the approval request to the corresponding approver. After obtaining the approval result, the storage unit stores it.

[0123] Each step of a medical terminology management method provided in the above embodiment of the present application can be implemented by the above units. Therefore, the specific working process and beneficial effects of each step in a medical terminology management method provided in the embodiment of the present application are not repeated here.

[0124] The present application also provides an electronic device, such as Figure 4 As shown, it includes a processor 410 , a communication interface 420 , a memory 430 and a communication bus 440 , wherein the processor 410 , the communication interface 420 , and the memory 430 communicate with each other via the communication bus 440 .

[0125] Memory 430, for storing computer programs;

[0126] The processor 410 is used to execute the program stored in the memory 430 to implement the following steps:

[0127] Get user-defined medical terminology data.

[0128] The storage mode is determined according to the matching result between the medical term text and the standard medical term text in the configured preset medical term concept domain.

[0129] The communication bus mentioned above can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The communication bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.

[0130] The communication interface is used for communication between the above electronic device and other devices.

[0131] The memory may include a random access memory (RAM) or a non-volatile memory (NVM), such as at least one disk memory. Optionally, the memory may also be at least one storage device located away from the aforementioned processor.

[0132] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0133] The implementation methods and beneficial effects of the components of the electronic device in the above embodiments to solve the problems can be seen in Figure 3 The various steps in the illustrated embodiment are implemented, therefore, the specific working process and beneficial effects of the electronic device provided by the embodiment of the present application are not repeated here.

[0134] In another embodiment provided in the present application, a computer-readable storage medium is provided, in which instructions are stored. When the computer-readable storage medium is executed on a computer, the computer executes a medical terminology management method described in any one of the above embodiments.

[0135] In another embodiment provided by the present application, a computer program product including instructions is also provided, and when the computer is run on the computer, the computer is enabled to execute a medical terminology management method described in any one of the above embodiments.

[0136] Those skilled in the art will appreciate that the embodiments in the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt a complete hardware embodiment, a complete software embodiment, or a form of an embodiment combining software and hardware. Moreover, the present application may adopt a form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0137] The embodiments of the present application are described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0138] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0139] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0140] Although the preferred embodiments of the present application have been described, those skilled in the art may make additional changes and modifications to these embodiments once they are aware of the basic creative concepts. Therefore, the present application embodiments are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the present application embodiments.

[0141] Obviously, those skilled in the art can make various changes and modifications to the embodiments in the present application without departing from the spirit and scope of the embodiments in the present application. Thus, if these modifications and variations of the embodiments in the present application are within the scope of the embodiments in the present application and their equivalents, the embodiments in the present application are also intended to include these modifications and variations.< / valuesetdto> < / long>

Claims

1. A medical terminology management system, It is characterized in that The system includes a storage unit, an acquisition unit and a matching unit; The acquisition unit is used to acquire user-defined medical terminology data and send the medical terminology data to the matching unit; the medical terminology data includes a preset medical terminology concept domain ID, a custom medical terminology coding system ID, a custom medical terminology ID and a medical terminology text, and a corresponding relationship between the custom medical terminology ID and the medical terminology text; The matching unit is used to obtain the medical term text in the medical term data, and match the medical term text with the standard medical term text in the configured preset medical term concept domain; if the match is successful, the successfully matched medical term text, the corresponding custom medical term ID, the custom medical term coding system ID and the corresponding relationship between the custom medical term ID and the medical term text are sent to the storage unit, wherein the preset medical term concept domain is the concept domain corresponding to the preset medical term concept domain ID; The storage unit is used to store the custom medical term coding system ID, the custom medical term ID and the medical term text.

2. The system according to claim 1, It is characterized in that The system also includes a mapping unit; The acquisition unit is further configured to acquire a request for switching medical term coding including a coding system keyword, and send the coding system keyword to the mapping unit; The mapping unit is used to determine the target coding system in the preset medical term concept domain based on the received coding system keyword; match any current medical term text currently displayed with the target medical term text in the target coding system; if the match is successful, obtain the target medical term code of the successfully matched target medical term text in the target coding system through a preset Levenshtein distance algorithm.

3. The system according to claim 1, It is characterized in that The storage unit is also used to store the standard medical terminology coding system ID under the standard coding system and the standard medical terminology text.

4. The system according to claim 1, It is characterized in that The storage unit includes a whitelist module and a blacklist module; The whitelist module is used to store a first medical term text and a first medical term ID, and a correspondence between the first medical term ID and the first medical term text; the first medical term ID includes a continuously used standard medical term ID and a continuously used custom medical term ID; the first medical term text includes a standard medical term text corresponding to the continuously used standard medical term ID and a medical term text corresponding to the continuously used custom medical term ID; The blacklist module is used to store the abandoned standard medical term IDs and the abandoned custom medical term IDs, as well as the standard medical term texts corresponding to the abandoned standard medical term IDs and the medical term texts corresponding to the abandoned custom medical term IDs.

5. The system according to claim 1, It is characterized in that The matching unit is further configured to push a prompt message including a failure in matching the medical term text with the standard medical term text to a processor if the matching fails.

6. The system of claim 1, It is characterized in that The preset medical terminology concept domain includes a plurality of target medical terminology coding system IDs.

7. The system of claim 1, It is characterized in that The storage unit is also used to store a plurality of preset medical term concept domains.

8. A method for managing medical terminology. It is characterized in that The method comprises: Acquire user-defined medical terminology data; the medical terminology data includes a custom medical terminology coding system ID, a custom medical terminology ID and a medical terminology text, and a corresponding relationship between the custom medical terminology ID and the medical terminology text; Matching the medical terminology text with standard medical terminology text in a configured preset medical terminology concept domain; If the match is successful, the successfully matched medical term text, the corresponding custom medical term ID, the custom medical term coding system ID and the corresponding relationship between the custom medical term ID and the medical term text are stored.

9. An electronic device, It is characterized in that The electronic device comprises a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus; Memory, used to store computer programs; The processor is used to implement the method steps described in claim 8 when executing the program stored in the memory.

10. A computer-readable storage medium, It is characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method steps of claim 8 are implemented.

Images