CN110457425B - Case storage method, device, equipment and storage medium - Google Patents

Abstract

The application discloses a case storage method, a case storage device and a case storage medium. On the basis, any block chain node can classify fault cases in the current block chain network according to fault types, so that a plurality of feature cases can be obtained, fault information and corresponding repair information can be comprehensively recorded in the obtained feature cases, and the comprehensive recording of the feature cases can be realized. Further, determining feature key characters in the feature cases as retrieval indexes, and updating a retrieval index library according to the retrieval indexes; the updated index library and the plurality of feature cases are stored in the current blockchain network, so that all blockchain nodes accessing the current blockchain network can share the feature cases, and related feature cases can be searched through the index if necessary.

Description

Case storage method, device, equipment and storage medium

Technical Field

The present application relates to the field of blockchain technology, and in particular to a case storage method, device, equipment and storage medium.

Background technique

Normally, people are used to storing special faults of machines or other objects and the repair information of the special faults as classic cases. When encountering the corresponding fault again, they can refer to the historical cases to repair the current fault. However, the existing recording method only records individual cases, and there will be missing records of historical faults of a certain object, which reduces the authenticity and comprehensiveness of the case records, resulting in a decrease in the reference value of the case.

Summary of the invention

In view of this, the purpose of this application is to provide a case storage method, device, equipment and storage medium to obtain comprehensive and real cases and realize case sharing. The specific scheme is as follows:

To achieve the above objectives, on the one hand, the present application provides a case storage method, which is applied to any blockchain node, including:

Obtaining fault cases of multiple objects in the current blockchain network; the fault cases include: at least one fault information of the current object and corresponding repair information;

Classifying the plurality of fault cases according to the fault type to obtain a plurality of characteristic cases; each characteristic case records the fault information and corresponding repair information of at least one object;

Determine the characteristic key characters in the plurality of characteristic cases as a search index, and update the search index library according to the search index;

The updated retrieval index library and the plurality of feature cases are stored in the current blockchain network.

In another aspect, the present application further provides a case storage device, applied to any blockchain node, comprising:

An acquisition module is used to acquire fault cases of multiple objects in the current blockchain network; the fault cases include: at least one fault information of the current object and corresponding repair information;

A classification module, used to classify the plurality of fault cases according to the fault type to obtain a plurality of characteristic cases; each characteristic case records the fault information and corresponding repair information of at least one object;

An updating module, used to determine the characteristic key characters in the plurality of characteristic cases as a retrieval index, and update the retrieval index library according to the retrieval index;

A storage module is used to store the updated retrieval index library and the plurality of feature cases in the current blockchain network.

On the other hand, the present application also provides an electronic device, comprising a processor and a memory; wherein the memory is used to store a computer program, and the computer program is loaded and executed by the processor to implement the case storage method disclosed above.

On the other hand, the present application also provides a storage medium, in which computer executable instructions are stored. When the computer executable instructions are loaded and executed by a processor, the case storage method disclosed above is implemented.

This application is applied to any blockchain node, that is, any blockchain node can execute the case storage method provided by this application. Among them, the current blockchain network stores fault cases of multiple objects. Since the blockchain has information disclosure and high security, the use of the blockchain network to store fault cases can realize the full network sharing of fault cases, while ensuring the security and non-tamperability of the fault cases. On this basis, any blockchain node can also classify the fault cases in the current blockchain network according to the fault type, so that multiple feature cases can be obtained, and the feature cases obtained in this way will comprehensively record the fault information and corresponding repair information of a certain object or multiple objects. Further, the feature key characters in the multiple feature cases are determined as retrieval indexes, and the retrieval index library is updated according to the retrieval index; the updated retrieval index library and multiple feature cases are stored in the current blockchain network, so that all blockchain nodes connected to the current blockchain network can share the feature cases. When a certain object fails, the relevant feature cases can be retrieved through the retrieval index, thereby providing a reliable, true and comprehensive reference case for the repair of the current fault.

Correspondingly, the case storage device, equipment and storage medium provided by this application also have the above-mentioned technical effects.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

FIG1 is a schematic diagram of a case storage system architecture provided by the present application;

FIG2 is a flow chart of the first case storage method provided by the present application;

FIG3 is a flow chart of a second case storage method provided by the present application;

FIG4 is a flow chart of a third case storage method provided by the present application;

FIG5 is a schematic diagram of a blockchain network provided by the present application;

FIG6 is a flow chart of a medical case storage method provided by the present application;

FIG7 is a schematic diagram of a natural person case record provided by the present application;

FIG8 is a schematic diagram of a first characteristic case record provided by the present application;

FIG9 is a schematic diagram of a second characteristic case record provided by the present application;

FIG10 is a schematic diagram of a search result provided by the present application;

FIG11 is a schematic diagram of a case storage device provided by the present application;

FIG12 is a structural diagram of a server provided by the present application;

FIG13 is a diagram of a terminal structure provided by the present application.

Detailed ways

At present, the existing recording method only records individual cases, and there will be missing records of historical failures of a certain object, which reduces the authenticity and comprehensiveness of the case records, resulting in a decrease in the reference value of the case. In view of the above-mentioned problems, this application proposes a case storage solution, through which comprehensive and real cases can be obtained and case sharing can be achieved.

For ease of understanding, the system architecture applicable to the technical solution disclosed in this application is introduced below. Please refer to Figure 1, which shows a system architecture applicable to this application.

As shown in FIG. 1 , the case storage system architecture disclosed in the present application may include a user terminal 11 , a server 12 , and a blockchain network 13 .

Among them, the user terminal 11 can be a pre-installed client, and the user can enter the fault case to be uploaded on the human-computer interaction interface. Among them, after obtaining the fault case, the user terminal 11 sends the fault case to the server 12, and then the server 12 uploads the fault case to the corresponding blockchain node. It can be understood that the user terminal 11 in this application includes but is not limited to smartphones, tablet computers, wearable devices, and desktop computers installed with the above-mentioned client. Among them, the user terminal 11 can also be used to query the fault cases stored in the blockchain network 13.

In this application, the server 12 may specifically refer to a dedicated server for implementing a single business, and different servers 12 are used to implement different businesses. The server 12 establishes a communication connection with the user terminal 11 through the network. After the server 12 obtains the fault case sent by the user terminal 11 and uploads the fault case to the corresponding blockchain node, the blockchain node can execute the case storage method provided in this application. It can be understood that the server 12 in this embodiment includes but is not limited to a cloud server, a physical server, and a virtual server.

It is understandable that the blockchain network 13 includes multiple blockchain nodes 130. When the fault case submitted by the server 12 is successfully uploaded to any blockchain node 130, the fault case will be quickly transmitted to other blockchain nodes 130 for storage within a second period, and each blockchain node 130 shares and stores the fault case. In the present application, any block of the blockchain network 13 can record a block identifier, a case storage record, and a hash value corresponding to the fault case.

The block identifier may refer to an identifier obtained by hashing a block header of a previous block, or may refer to a block height of a current block; the case storage record may include a fault case and a corresponding timestamp, etc.

It is understandable that the node device types of the blockchain node 130 in the present application include but are not limited to various types of servers, personal computers, handheld terminals, etc.

It should be noted that the network connecting the user terminal 11, the server 12 and the blockchain network 13, as well as the network between the blockchain nodes in the blockchain network 13, can be determined according to the network conditions and application requirements in the actual application process, and can be a wireless communication network, such as a mobile communication network or a WIFI network, or a wired communication network; it can be a wide area network, and a local area network can also be used when the situation permits. Of course, the user terminal 11 can also communicate directly with the blockchain network 13, so that there is no need to set up the server 12, which can save computer resources.

FIG2 is a flow chart of the first case storage method provided in the embodiment of the present application. Referring to FIG2, the case storage method is applied to any blockchain node and may include the following steps:

S201. Obtain fault cases of multiple objects in the current blockchain network; the fault cases include: at least one fault information of the current object and corresponding repair information.

In the current blockchain network, fault cases can be stored with the identification information of the object as the key. The object can be: equipment, people, animals, plants, etc. When the object is a person, animal, or plant, its fault case is a natural person case, the fault is the disease information, and the repair information is the disease treatment information; the identification information can be the identity information of the person, the name of the animal or plant, etc. If the object is a device, its fault information can include: the faulty component and the cause of the fault; the identification information of the device can be the factory code of the device, etc.

If the object is a person, the case is stored with the person's identity information key. In this way, for the same patient (i.e. a natural person), the corresponding medical information, test order information, etc. can be stored in one case. This not only enriches the case and makes the patient's case fully recorded, but also makes it easier for patients and doctors to query the case. This facilitates obtaining comprehensive, true, and reliable feature cases.

S202. Classify multiple fault cases according to fault types to obtain multiple characteristic cases; each characteristic case records fault information and corresponding repair information of at least one object.

In a specific implementation, a classification algorithm can be used to classify fault cases according to fault types to obtain multiple characteristic cases, and the classification algorithm is a naive Bayes algorithm, a random forest algorithm or a support vector machine. Of course, other classification algorithms can also be used for classification, such as a clustering algorithm.

If the fault case is a natural person case, it is understandable that since a natural person may suffer from multiple diseases, after the fault case is classified according to the disease type, the diseases suffered by the same natural person may be divided into different characteristic cases. For example: the case of natural person A records two disease information and treatment information of heart disease and diabetes. Then, when classifying, the disease information and treatment information about heart disease recorded in the case of natural person A will be classified into the characteristic case of heart disease; the disease information and treatment information about diabetes recorded in the case of natural person A will be classified into the characteristic case of diabetes. Among them, since the fault case also records the information of the test report, etc., when classifying the disease, the information of the test report will also be classified into the corresponding characteristic case. Among them, the treatment information can include the information of oral, external and/or injected drugs, the corresponding medication effects, etc. Of course, the identity information of the natural person, the place and time of the medical treatment, etc. can also be recorded in the characteristic case.

If the fault case records multiple cases of disease information and treatment information related to heart disease, each record can be regarded as a treatment record. When classifying, the treatment time of these treatment records is recorded separately, and these treatment records are regarded as relevant information about the current natural person suffering from heart disease. In other words, these treatment records are uniformly regarded as a case of the current natural person suffering from heart disease.

S203: Determine the characteristic key characters in the plurality of characteristic cases as retrieval indexes, and update the retrieval index library according to the retrieval indexes.

S204: Store the updated search index library and multiple feature cases in the current blockchain network.

In this embodiment, before storing the updated retrieval index library and multiple feature cases in the current blockchain network, it also includes: for any feature case, adding fault information with the same type of repair information to the same fault group; any feature case includes multiple fault groups.

In each characteristic case, there are multiple fault groups, and each fault group records fault information with the same type of repair information. Still taking the characteristic case obtained after the classification of natural person cases as an example, assuming that there are 2 fault groups (that is, case groups) in the characteristic case of urticaria, the first fault group is used to record the symptoms of illness, treatment effects and other information after taking a certain medicine; the second fault group is used to record the symptoms of illness, treatment effects and other information after taking another medicine. In this way, it is possible to clearly see from the characteristic cases the treatment effects of different medicines and different treatment methods for the same disease; it is also possible to quickly see from the characteristic cases how many treatment methods and methods the current disease can have.

In order to facilitate retrieval and query, a corresponding retrieval index can be constructed for the characteristic case. The retrieval index can be any characteristic key characters in the characteristic case, such as fault name, location, fault cause, etc. If the fault case is a natural person case, the characteristic key characters can be the name or abbreviation of the disease, such as urticaria; or a unique symptom of the disease, such as wheal, which is a unique symptom of urticaria.

The updated search index library and multiple feature cases are stored in the current blockchain network, that is, the search index library and feature cases are shared in the current blockchain network. In this way, any blockchain node can use the search index to query related feature cases.

It should be noted that other implementation steps in this embodiment are the same or similar to those in the above embodiment, so they will not be described in detail in this embodiment.

The method disclosed in this embodiment is applied to any blockchain node, that is, any blockchain node can execute the case storage method provided by this application. Among them, the current blockchain network stores fault cases of multiple objects. Since the blockchain has information disclosure and high security, the use of the blockchain network to store fault cases can realize the full network sharing of fault cases, while ensuring the security and non-tamperability of the fault cases. On this basis, any blockchain node can also classify the fault cases in the current blockchain network according to the fault type, so that multiple feature cases can be obtained. The feature cases obtained in this way will comprehensively record the fault information and corresponding repair information of a certain object or multiple objects. Further, the feature key characters in the multiple feature cases are determined as retrieval indexes, and the retrieval index library is updated according to the retrieval index; the updated retrieval index library and multiple feature cases are stored in the current blockchain network, so that all blockchain nodes connected to the current blockchain network can share the feature cases. When a certain object fails, the relevant feature cases can be retrieved through the retrieval index, thereby providing a reliable, true and comprehensive reference case for the repair of the current fault.

FIG3 is a flow chart of a second case storage method provided in an embodiment of the present application. Referring to FIG3, the case storage method is applied to any blockchain node and may include the following steps:

S301. Obtain fault cases of multiple objects in the current blockchain network; the fault cases include: at least one fault information of the current object and corresponding repair information.

S302. Classify multiple fault cases according to fault types to obtain multiple characteristic cases; each characteristic case records fault information and corresponding repair information of at least one object.

S303: Determine the characteristic key characters in the plurality of characteristic cases as retrieval indexes, and update the retrieval index library according to the retrieval indexes.

S304: Store the updated search index library and multiple feature cases in the current blockchain network.

S305: Receive a search request sent by a user.

It is understandable that the user can submit a search request through the human-computer interaction interface. The target search index in the search request can be preset information of the human-computer interaction interface or information input by the user.

S306: Extract the target search index in the search request.

S307. Determine the similarity between the target retrieval index and multiple feature cases in the current blockchain network respectively.

The similarity can be determined by using semantic similarity, cosine similarity, etc. When using cosine similarity to determine the similarity between the target retrieval index and the feature case, it is necessary to first convert the target retrieval index and the feature case into vectors, and then calculate the similarity between the two vectors.

S308: Determine the feature case corresponding to the maximum similarity as the search result and return it.

It is understandable that to determine the similarity between the target search index and multiple feature cases respectively, it is necessary to calculate the similarity between the target search index and each feature case respectively, so as to obtain the similarity corresponding to each feature case. The feature case corresponding to the maximum similarity is determined as the search result of the current search request and returned.

In a specific implementation, for any feature case, the similarity between the target retrieval index and the current feature case is determined, including: separately determining the similarity between the target retrieval index and each feature keyword in the current feature case to obtain multiple sub-similarity; weighted aggregation of the multiple sub-similarities to obtain the similarity between the target retrieval index and the current feature case.

Still taking the case of a natural person as an example. For example: the key indicators in the characteristic case of urticaria are wheals, skin itching, and blood routine tests, and their corresponding weights are 40%, 40%, and 20%, respectively. Then calculate the similarity between the target retrieval index and the wheals, so as to obtain the first sub-similarity A; calculate the similarity between the target retrieval index and skin itching, so as to obtain the second sub-similarity B; calculate the similarity between the target retrieval index and the blood routine test, so as to obtain the third sub-similarity C; then add the weighted sum of these three sub-similarity, and we have: W = A × 40% + B × 40% + C × 20%, then W is the similarity between the target retrieval index and the characteristic case of urticaria.

In a specific implementation, determining the feature case corresponding to the maximum similarity as the search result and returning it includes: arranging multiple feature cases in descending order according to the similarity to obtain a feature case sequence; determining the feature case sequence as the search result and returning it.

The similarity between the target search index and each feature case can be calculated in the above manner, and the feature cases can be arranged in descending order according to the similarity, so as to obtain a feature case sequence; and then this feature case sequence can be used as a search result and returned. Among them, if the feature case sequence contains many feature cases, the first N of them can be selected as the search result and returned. Of course, the feature cases can also be arranged in ascending order according to the similarity, and the last N in the feature case sequence can be selected as the search result and returned. Of course, the search results can also be displayed on the client for user reference.

It should be noted that in order to prevent users from maliciously referring to characteristic cases, the user's authority to submit search requests through the client can be restricted. For example, only when the correct physician's practice certificate code is entered can the search request be submitted. Of course, cryptographic technology can also be used to prevent malicious query and acquisition of characteristic cases.

It should be noted that other implementation steps in this embodiment are the same or similar to those in the above embodiment, so they will not be described in detail in this embodiment.

After storing the characteristic cases in the blockchain network, the method disclosed in this embodiment extracts the target search index in the search request when receiving a search request, and then determines the similarity between the target search index and multiple characteristic cases respectively, and then returns and displays the search results corresponding to the search request according to the similarity. In this way, users can query related cases immediately, thus providing a reliable and comprehensive basis for repairing the current fault.

FIG4 is a flow chart of a third case storage method provided in an embodiment of the present application. Referring to FIG4 , the case storage method is applied to any blockchain node and may include the following steps:

S401: Receive fault information and corresponding repair information of multiple objects sent by a user.

In a specific implementation, a user can send fault information and corresponding repair information to a blockchain node at different times, so that the blockchain node synchronously stores the fault information and the corresponding repair information in the entire network.

S402: Generate a fault case for each object according to identification information of different objects, and use the identification information of the object as the ID of the fault case.

S403: Establish an association relationship between the fault case and the ID, and store the association relationship, the fault case and the ID in the current blockchain network.

In this embodiment, the association relationship, fault case and ID are stored in the current blockchain network, including: broadcasting the association relationship, fault case and ID in the current blockchain network, so that other blockchain nodes in the current blockchain network can verify the association relationship, fault case and ID; if the verification passes, the association relationship, fault case and ID are packaged into a second block, and the packaged message of the second block is broadcast in the current blockchain network.

Of course, you can also set the execution time of the classified fault cases in the current blockchain network, for example, set the execution cycle to perform the classification operation every 10 minutes or every 1 hour. That is, each blockchain node collects new fault information and corresponding repair information and synchronizes them to the entire network. When the classification execution time point is reached, the fault information and corresponding repair information collected between the last classification execution time point and the current classification execution time point are classified. After the classification obtains a new feature case, if the new feature case already exists in the blockchain network, the new feature case is merged with the old feature case and shared; if the new feature case does not exist in the blockchain network, the new feature case is stored and shared.

S404. Obtain fault cases of multiple objects in the current blockchain network; the fault cases include: at least one fault information of the current object and corresponding repair information.

S405. Classify the multiple fault cases according to the fault type to obtain multiple characteristic cases; each characteristic case records the fault information and corresponding repair information of at least one object.

S406: Determine the characteristic key characters in the plurality of characteristic cases as retrieval indexes.

S407, determine whether there is a search index in the search index library; if so, execute S408; if not, execute S409.

S408, determining the original search index library as the updated search index library;

S409, adding the search index to the search index library, obtaining an updated search index library, and executing S410.

S410. Broadcast the updated retrieval index library and multiple feature cases in the current blockchain network, so that other blockchain nodes in the current blockchain network can verify the updated retrieval index library and multiple feature cases.

S411. If the verification is successful, the updated retrieval index library and multiple feature cases are packaged into a first block, and the packaging message of the first block is broadcast in the current blockchain network.

S412: Receive new fault information and corresponding repair information of the target object sent by the user.

S413. According to the fault type of the new fault information, the new fault information and the corresponding repair information are added with corresponding feature cases.

In this embodiment, after multiple characteristic cases have been classified and obtained in the blockchain network and the sharing operation has been completed, if the current blockchain network receives new fault information and corresponding repair information again, the new fault information and corresponding repair information can be directly added to the corresponding characteristic case. If the characteristic case corresponding to the new fault information and corresponding repair information does not exist in the current blockchain network, the corresponding characteristic case can be created in the current blockchain network, and the new fault information and corresponding repair information can be added to the newly created characteristic case.

It should be noted that other implementation steps in this embodiment are the same or similar to those in the above embodiment, so they will not be described in detail in this embodiment.

It can be seen that after classifying characteristic cases, this embodiment can classify and process the newly collected fault cases when fault cases are collected again, so that the fault cases in the blockchain network can be classified in time and characteristic cases can be obtained for reference by relevant personnel.

The case storage method provided by the present application is described below through a specific application scenario example. Please refer to Figure 5, which is a schematic diagram of a blockchain network provided by an embodiment of the present application. In Figure 5, any medical institution can access the blockchain network as a blockchain node, and each medical institution can upload natural person cases to its corresponding blockchain node. At the same time, the blockchain node will share the uploaded natural person cases with other nodes, thereby realizing the full network shared storage of natural person cases.

At the same time, the blockchain node corresponding to any medical institution can also be used as an analysis and summary node. The analysis and summary node classifies the natural person cases in the entire network according to the disease type, so that multiple characteristic cases can be obtained. The characteristic cases obtained in this way will comprehensively record all relevant information of the patient's current disease, thereby realizing a comprehensive record of the characteristic cases. Furthermore, the characteristic key characters in the multiple characteristic cases are determined as retrieval indexes, and the retrieval index library is updated according to the retrieval index; the updated retrieval index library and multiple characteristic cases are stored in the current blockchain network, so that all medical institutions connected to the current blockchain network can share characteristic cases, and can retrieve relevant characteristic cases through the retrieval index when necessary.

In order to reduce the amount of data processing of each blockchain node, an analysis and summary node can be set in the blockchain network. Multiple analysis and summary nodes can be set, namely, analysis node 1 and analysis node 2 in Figure 1. This analysis and summary node is only used to execute the case storage solution provided by this application. In other words, the blockchain nodes corresponding to each medical institution are used to collect and share natural person cases, and the analysis and summary node is used to classify the collected natural person cases and share characteristic cases.

In conjunction with the blockchain network shown in FIG5 , the present application embodiment provides a fourth case storage method, see FIG6 , which is a flow chart of a medical case storage method provided by the present application embodiment. The medical case storage method shown in FIG6 may include the following steps:

S601. The target blockchain node obtains natural person cases in the current blockchain network.

In this embodiment, the fault case is a natural person case. Before the target blockchain node obtains the natural person case in the current blockchain network, it also includes: all blockchain nodes in the current blockchain network collect the natural person cases respectively, and pack the collected natural person cases into blocks, that is, the natural person cases are shared and stored in the whole network.

Specifically, the storage and display of natural person cases can be seen in Figure 7, which is a schematic diagram of a natural person case record provided in an embodiment of the present application. The time point in Figure 7 is the time point of each visit of the patient. The natural person ID in Figure 7 can be the patient's identity information.

S602. The target blockchain node classifies the natural person cases according to the disease type to obtain multiple characteristic cases.

Each characteristic case records at least one natural person's illness information and corresponding treatment information. The disease type corresponds to the fault type mentioned above.

S603. The target blockchain node determines the characteristic key characters in the multiple characteristic cases as retrieval indexes, and updates the retrieval index library according to the retrieval indexes.

The characteristic key characters may be the name of the disease, symptoms of the disease, etc.

Specifically, please refer to Figures 8-9 for the storage and display of characteristic cases. Figure 8 is a schematic diagram of the first characteristic case record provided in the embodiment of the present application, and Figure 9 is a schematic diagram of the second characteristic case record provided in the embodiment of the present application. The specific method in Figure 9 is that for the medication information or other treatment information of the current disease, the corresponding number of cases is the number of cases with the same treatment information. Here, you can refer to the case group mentioned above. The characteristic cases in Figures 8 and 9 are disease cases.

S604: The target blockchain node broadcasts the updated retrieval index library and multiple feature cases to other blockchain nodes.

Among them, the target blockchain node and other blockchain nodes together constitute the current blockchain network.

S605. Other blockchain nodes reach consensus on the updated retrieval index library and multiple feature cases.

S606. If the consensus is passed, other blockchain nodes broadcast the consensus passing message in the entire network.

Among them, commonly used consensus methods can be used to reach consensus on the updated retrieval index library and multiple feature cases, such as: PBFT, POW, POS, DPOS and other consensus methods.

S607. The target blockchain node packages the updated retrieval index library and multiple feature cases into blocks.

S608. The target blockchain node broadcasts the block generation message in the entire network.

It should be noted that the implementation steps in this embodiment are the same as or similar to those in the above embodiments. For details, please refer to any of the above embodiments, so this embodiment will not be repeated here.

If the search index is the symptoms of the disease and the test results (such as the white blood cell count), then when the symptoms and test results are used to query the characteristic cases in the blockchain network, please refer to Figure 10 for the search results obtained. Figure 10 is a schematic diagram of a search result provided by an embodiment of the present application. In Figure 10, all similar cases are arranged in descending order according to the degree of similarity with the symptoms and test results. The case ID in Figures 8, 9 and 10 can be the name of the disease corresponding to the current characteristic case.

It can be seen that this embodiment enables any medical institution to access the blockchain network as a blockchain node and upload natural person medical records. Natural person records are stored in the blockchain network with natural person as the key, and then the natural person records are classified with disease type as the key. This not only realizes the unified storage of patient records of different medical institutions, but also facilitates the retrieval and query of characteristic cases.

Please refer to FIG. 11 , which is a schematic diagram of a case storage device provided in an embodiment of the present application, which is applied to any blockchain node and includes:

The acquisition module 1101 is used to acquire fault cases of multiple objects in the current blockchain network; the fault case includes: at least one fault information of the current object and corresponding repair information;

The classification module 1102 is used to classify multiple fault cases according to fault types to obtain multiple characteristic cases; each characteristic case records the fault information and corresponding repair information of at least one object;

An updating module 1103 is used to determine the characteristic key characters in the plurality of characteristic cases as a retrieval index, and update the retrieval index library according to the retrieval index;

The storage module 1104 is used to store the updated retrieval index library and multiple feature cases in the current blockchain network.

In a specific embodiment, it also includes:

A first receiving module, used for receiving a search request sent by a user;

An extraction module, used for extracting a target search index in a search request;

The retrieval module is used to retrieve feature cases corresponding to the target retrieval index in the current blockchain network and return the retrieval results.

In a specific implementation, the search module includes:

A first determination unit, used to respectively determine the similarity between the target retrieval index and a plurality of feature cases in the current blockchain network;

The second determining unit is used to determine the feature case corresponding to the maximum similarity as the search result and return it.

In a specific implementation, the first determining unit is specifically configured to:

For any feature case, the similarity between the target retrieval index and each feature key character in the current feature case is determined respectively to obtain multiple sub-similarity; the multiple sub-similarity are weighted and summarized to obtain the similarity between the target retrieval index and the current feature case.

In a specific implementation, the second determining unit is specifically configured to:

Arrange multiple feature cases in descending order according to the similarity to obtain a feature case sequence; determine the feature case sequence as a retrieval result and return it.

In a specific embodiment, it also includes:

The first adding module is used to add the fault information with the same type of repair information to the same fault group for any characteristic case; any characteristic case includes multiple fault groups.

In a specific implementation, the update module includes:

A judging unit, used to judge whether a search index exists in the search index library;

The updating unit is used to add the retrieval index to the retrieval index library if the retrieval index does not exist in the retrieval index library, so as to obtain an updated retrieval index library.

In a specific embodiment, the storage module includes:

A first broadcasting unit, configured to broadcast the updated retrieval index library and the plurality of feature cases in the current blockchain network, so that other blockchain nodes in the current blockchain network can verify the updated retrieval index library and the plurality of feature cases;

The first packaging unit is used to package the updated retrieval index library and multiple feature cases into a first block if the verification is passed, and broadcast the packaging message of the first block in the current blockchain network.

In a specific embodiment, it also includes:

A second receiving module, used to receive fault information and corresponding repair information of multiple objects sent by a user;

A generation module, used to generate a fault case for each object according to identification information of different objects, and use the identification information of the object as the ID of the fault case;

The execution module is used to establish the association relationship between the fault case and the ID, and store the association relationship, the fault case and the ID in the current blockchain network.

In a specific implementation, the execution module includes:

A second broadcasting unit, used to broadcast the association relationship, the fault case and the ID in the current blockchain network, so that other blockchain nodes in the current blockchain network can verify the association relationship, the fault case and the ID;

The second packaging unit is used to package the association relationship, the fault case and the ID into a second block if the verification is passed, and broadcast the packaging message of the second block in the current blockchain network.

In a specific embodiment, it also includes:

A third receiving module is used to receive new fault information and corresponding repair information of the target object sent by the user;

The second adding module is used to add corresponding feature cases to the new fault information and the corresponding repair information according to the fault type of the new fault information.

In a specific implementation, the classification module is specifically used to:

A classification algorithm is used to classify fault cases according to fault types to obtain multiple feature cases. The classification algorithm is a naive Bayes algorithm, a random forest algorithm, or a support vector machine.

Among them, for more specific working processes of each module and unit in this embodiment, reference can be made to the corresponding contents disclosed in the aforementioned embodiments, which will not be repeated here.

It can be seen that the present embodiment provides a case storage device, including: an acquisition module, a classification module, an update module and a storage module. First, the acquisition module acquires the fault cases of multiple objects in the current blockchain network; the fault cases include: at least one fault information of the current object and the corresponding repair information; then the classification module classifies the multiple fault cases according to the fault type to obtain multiple feature cases; each feature case records the fault information and corresponding repair information of at least one object; then the update module determines the feature key characters in the multiple feature cases as retrieval indexes, and updates the retrieval index library according to the retrieval index; finally, the storage module stores the updated retrieval index library and multiple feature cases in the current blockchain network. In this way, the modules work together and perform their respective duties, so that real and comprehensive feature cases can be obtained, and the sharing of feature cases can be realized.

Furthermore, an embodiment of the present application also provides an electronic device. The electronic device can be a server 50 as shown in FIG12 or a terminal 60 as shown in FIG13. FIG12 and FIG13 are both structural diagrams of electronic devices shown in the present embodiment, and the contents in the diagrams cannot be regarded as any limitation on the scope of use of the present application.

FIG12 is a schematic diagram of the structure of a server provided in an embodiment of the present application. The server 50 may specifically include: at least one processor 51, at least one memory 52, a power supply 53, a communication interface 54, an input/output interface 55, and a communication bus 56. The memory 52 is used to store a computer program, which is loaded and executed by the processor 51 to implement the relevant steps in the case storage disclosed in any of the aforementioned embodiments.

In this embodiment, the power supply 53 is used to provide working voltage for each hardware device on the server 50; the communication interface 54 can create a data transmission channel between the server 50 and external devices, and the communication protocol it follows is any communication protocol that can be applied to the technical solution of the present application, and is not specifically limited here; the input and output interface 55 is used to obtain external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs and is not specifically limited here.

In addition, the memory 52, as a carrier for storing resources, can be a read-only memory, a random access memory, a disk or an optical disk, etc. The resources stored thereon include an operating system 521, a computer program 522 and data 523, etc. The storage method can be temporary storage or permanent storage.

The operating system 521 is used to manage and control the hardware devices and computer programs 522 on the server 50, so as to realize the operation and processing of the data 523 in the memory 52 by the processor 51, and it can be Windows Server, Netware, Unix, Linux, etc. In addition to including computer programs that can be used to complete the case storage method disclosed in any of the above embodiments, the computer program 522 can also further include computer programs that can be used to complete other specific tasks. In addition to data such as fault cases, the data 523 can also include data such as feature cases.

FIG13 is a schematic diagram of the structure of a terminal provided in an embodiment of the present application. The terminal 60 may specifically include but is not limited to a smart phone, a tablet computer, a laptop computer or a desktop computer.

Generally, the terminal 60 in this embodiment includes: a processor 61 and a memory 62 .

Among them, the processor 61 may include one or more processing cores, such as a 4-core processor, an 8-core processor, etc. The processor 61 can be implemented in at least one hardware form of DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). The processor 61 may also include a main processor and a coprocessor. The main processor is a processor for processing data in the awake state, also known as a CPU (Central Processing Unit); the coprocessor is a low-power processor for processing data in the standby state. In some embodiments, the processor 61 may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the display screen. In some embodiments, the processor 61 may also include an AI (Artificial Intelligence) processor, which is used to process computing operations related to machine learning.

The memory 62 may include one or more computer-readable storage media, which may be non-transitory. The memory 62 may also include a high-speed random access memory, and a non-volatile memory, such as one or more disk storage devices, flash memory storage devices. In this embodiment, the memory 62 is at least used to store the following computer program 621, wherein, after the computer program is loaded and executed by the processor 61, it can implement the relevant steps in the case storage method executed by the terminal side disclosed in any of the aforementioned embodiments. In addition, the resources stored in the memory 62 may also include an operating system 622 and data 623, etc., and the storage method may be temporary storage or permanent storage. Among them, the operating system 622 may include Windows, Unix, Linux, etc. Data 623 may include, but is not limited to, fault cases and feature cases.

In some embodiments, the terminal 60 may further include a display screen 63 , an input/output interface 64 , a communication interface 65 , a sensor 66 , a power supply 67 , and a communication bus 68 .

Those skilled in the art will appreciate that the structure shown in FIG. 13 does not constitute a limitation on the terminal 60 , and may include more or fewer components than those shown in the figure.

Furthermore, the embodiment of the present application also discloses a storage medium, in which computer executable instructions are stored. When the computer executable instructions are loaded and executed by a processor, the case storage method disclosed in any of the above embodiments is implemented. For the specific steps of the method, reference can be made to the corresponding contents disclosed in the above embodiments, and no further description will be given here.

It should be pointed out that the above is only a preferred embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application should be included in the protection scope of the present application.

In this specification, each embodiment is described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the embodiments can be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part.

Specific examples are used herein to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea. At the same time, for those skilled in the art, according to the idea of the present application, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims (18)

1. A case storage method, applied to any blockchain node, comprising:

Receiving disease information and corresponding treatment information of a plurality of objects sent by a user;

Generating a case of each object according to the identification information of different objects, and taking the identification information of the objects as the ID of the case;

establishing an association relationship between the case and the ID, and storing the association relationship, the case and the ID to a current blockchain network;

acquiring cases of a plurality of objects in a current blockchain network; the cases include: at least one disease information and corresponding treatment information of the current subject;

Classifying a plurality of cases according to disease types to obtain a plurality of characteristic cases; each characteristic case records the disease information and the corresponding treatment information of a plurality of objects, the characteristic cases are displayed through a case record schematic diagram, the characteristic case record schematic diagram comprises the disease information, the examination record, the diagnosis conclusion, the treatment method and the corresponding effect, or the characteristic case record schematic diagram comprises the disease information, the examination index and the treatment method, and the treatment method comprises specific method information, the treatment effect and the case number;

Determining feature key characters in a plurality of feature cases as a retrieval index, and updating a retrieval index library according to the retrieval index, wherein the feature key words comprise any one of disease names, positions and disease causes;

storing the updated search index library and a plurality of the characteristic cases to the current blockchain network;

receiving a search request sent by a user;

Extracting a target retrieval index in the retrieval request;

Determining the similarity of the target search index and a plurality of the feature cases in the current blockchain network respectively, wherein determining the similarity of the target search index and the current feature case for any feature case comprises: respectively determining the similarity of the target retrieval index and each characteristic key character in the current characteristic case to obtain a plurality of sub-similarities; weighting and summarizing the sub-similarity to obtain the similarity between the target retrieval index and the current characteristic case;

and determining the feature case corresponding to the maximum similarity as a retrieval result and returning.

2. The case storage method according to claim 1, wherein determining the feature case corresponding to the maximum similarity as the search result and returning includes:

The characteristic cases are arranged in a descending order according to the similarity, and a characteristic case sequence is obtained;

and determining the characteristic case sequence as the retrieval result and returning.

3. The case storage method according to claim 1 or 2, wherein before storing the updated index library and the plurality of characteristic cases to the current blockchain network, further comprising:

For any one of the characteristic cases, adding disease information having the same type of treatment information to the same disease group; multiple disease groups are included in any one of the characteristic cases.

4. The case storage method of claim 1, wherein updating the search index base from the search index comprises:

Judging whether the search index exists in a search index library;

if not, adding the retrieval index to the retrieval index library to obtain the updated retrieval index library.

5. The case storage method of claim 1, wherein the storing the updated index library and the plurality of the characteristic cases to the current blockchain network comprises:

broadcasting the updated index library and the plurality of characteristic cases in the current blockchain network so that other blockchain nodes in the current blockchain network verify the updated index library and the plurality of characteristic cases;

And if the verification is passed, packaging the updated index library and a plurality of characteristic cases into a first block, and broadcasting a packaging message of the first block in the current blockchain network.

6. The case storage method of claim 1, wherein the storing the association relationship, the case, and the ID to the current blockchain network comprises:

Broadcasting the association, the case and the ID in the current blockchain network to enable other blockchain nodes in the current blockchain network to verify the association, the case and the ID;

And if the verification is passed, packaging the association relation, the case and the ID into a second block, and broadcasting a packaging message of the second block in the current blockchain network.

7. The case storage method according to claim 1, wherein after storing the updated index library and the plurality of the characteristic cases in the current blockchain network, further comprising:

receiving new disease information and corresponding treatment information of a target object sent by a user;

and adding the new disease information and the corresponding treatment information into the corresponding characteristic cases according to the disease type of the new disease information.

8. The case storage method according to claim 1, wherein the classifying the cases according to the disease type to obtain a plurality of characteristic cases includes:

and classifying the cases according to the disease types by using a classification algorithm to obtain a plurality of characteristic cases, wherein the classification algorithm is a naive Bayesian algorithm, a random forest algorithm or a support vector machine.

9. A case storage device for any blockchain node, comprising:

a second receiving unit, configured to receive disease information and corresponding treatment information of a plurality of objects sent by a user;

The generation module is used for generating a case of each object according to the identification information of different objects, and taking the identification information of the objects as the ID of the case;

the execution module is used for establishing an association relation between the case and the ID and storing the association relation, the case and the ID into a current blockchain network;

The acquisition module is used for acquiring cases of a plurality of objects in the current blockchain network; the cases include: at least one piece of disease information and corresponding treatment information of the current object, wherein the case is displayed through a case record schematic diagram, the case record schematic diagram comprises disease information, examination records, diagnosis conclusions, treatment methods and corresponding effects, or the case record schematic diagram comprises disease information, examination indexes and treatment methods, and the treatment methods comprise specific method information, treatment effects and case numbers;

the classification module is used for classifying the plurality of cases according to the disease types to obtain a plurality of characteristic cases; each characteristic case records disease information and corresponding treatment information of a plurality of objects;

The updating module is used for determining characteristic key characters in a plurality of characteristic cases as retrieval indexes and updating a retrieval index library according to the retrieval indexes, wherein the characteristic key words comprise any one of disease names, positions and disease causes;

the storage module is used for storing the updated retrieval index library and a plurality of characteristic cases into the current blockchain network;

the first receiving module is used for receiving a search request sent by a user;

the extraction module is used for extracting a target retrieval index in the retrieval request;

the retrieval module is used for retrieving the characteristic cases corresponding to the target retrieval index in the current blockchain network and returning retrieval results;

Wherein, the retrieval module includes:

The first determining unit is used for respectively determining the similarity of the target retrieval index and each characteristic key character in the current characteristic case aiming at any characteristic case to obtain a plurality of sub-similarities; weighting and summarizing the sub-similarity to obtain the similarity between the target retrieval index and the current characteristic case;

and the second determining unit is used for determining the characteristic case corresponding to the maximum similarity as the search result and returning the search result.

10. The apparatus according to claim 9, wherein the second determining unit is specifically configured to:

The characteristic cases are arranged in a descending order according to the similarity, and a characteristic case sequence is obtained; and determining the characteristic case sequence as the retrieval result and returning.

11. The apparatus according to claim 9 or 10, characterized in that the apparatus further comprises:

A first adding unit for adding disease information having the same type of treatment information to the same disease group for any one of the characteristic cases; multiple disease groups are included in any one of the characteristic cases.

12. The apparatus of claim 9, wherein the update module comprises:

the judging unit is used for judging whether the search index exists in the search index library;

And the updating unit is used for adding the retrieval index into the retrieval index library if the retrieval index does not exist in the retrieval index library, and obtaining the updated retrieval index library.

13. The apparatus of claim 9, wherein the storage module comprises:

A first broadcasting unit, configured to broadcast the updated search index library and the plurality of feature cases in the current blockchain network, so that other blockchain nodes in the current blockchain network verify the updated search index library and the plurality of feature cases;

And the first packing unit is used for packing the updated retrieval index library and a plurality of the characteristic cases into a first block if the verification is passed, and broadcasting the packing information of the first block in the current blockchain network.

14. The apparatus of claim 9, wherein the execution module comprises:

A second broadcasting unit configured to broadcast the association relationship, the case, and the ID in the current blockchain network, so that other blockchain nodes in the current blockchain network verify the association relationship, the case, and the ID;

and the second packing unit is used for packing the association relation, the case and the ID into a second block if the verification is passed, and broadcasting a packing message of the second block in the current blockchain network.

15. The apparatus of claim 9, wherein the apparatus further comprises:

a third receiving unit, configured to receive new disease information and corresponding treatment information of a target object sent by a user;

and a second adding unit, configured to add the new disease information and the corresponding treatment information to the corresponding characteristic case according to the disease type of the new disease information.

16. The apparatus of claim 9, wherein the classification module is specifically configured to:

and classifying the cases according to the disease types by using a classification algorithm to obtain a plurality of characteristic cases, wherein the classification algorithm is a naive Bayesian algorithm, a random forest algorithm or a support vector machine.

17. An electronic device comprising a processor and a memory; wherein the memory is for storing a computer program that is loaded and executed by the processor to implement the case storage method of any one of claims 1 to 8.

18. A storage medium having stored therein computer executable instructions which when loaded and executed by a processor implement the case storage method of any one of claims 1 to 8.