CN110597946B - Case storage method, device, equipment and storage medium - Google Patents
Case storage method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN110597946B CN110597946B CN201910853432.XA CN201910853432A CN110597946B CN 110597946 B CN110597946 B CN 110597946B CN 201910853432 A CN201910853432 A CN 201910853432A CN 110597946 B CN110597946 B CN 110597946B
- Authority
- CN
- China
- Prior art keywords
- fault
- feature
- case
- cases
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 63
- 230000008439 repair process Effects 0.000 claims abstract description 79
- 238000010586 diagram Methods 0.000 claims description 22
- 238000004806 packaging method and process Methods 0.000 claims description 10
- 238000004422 calculation algorithm Methods 0.000 claims description 9
- 238000007635 classification algorithm Methods 0.000 claims description 9
- 238000004590 computer program Methods 0.000 claims description 9
- 238000012856 packing Methods 0.000 claims description 9
- 238000012795 verification Methods 0.000 claims description 8
- 230000000694 effects Effects 0.000 claims description 7
- 238000007637 random forest analysis Methods 0.000 claims description 4
- 238000012706 support-vector machine Methods 0.000 claims description 4
- 238000000605 extraction Methods 0.000 claims description 2
- 230000000875 corresponding effect Effects 0.000 claims 36
- 238000007689 inspection Methods 0.000 claims 4
- 238000003745 diagnosis Methods 0.000 claims 2
- 201000010099 disease Diseases 0.000 description 25
- 208000037265 diseases, disorders, signs and symptoms Diseases 0.000 description 25
- 238000011282 treatment Methods 0.000 description 20
- 238000004891 communication Methods 0.000 description 10
- 238000012545 processing Methods 0.000 description 9
- 238000004458 analytical method Methods 0.000 description 8
- 208000024891 symptom Diseases 0.000 description 8
- 239000003814 drug Substances 0.000 description 6
- 208000024780 Urticaria Diseases 0.000 description 5
- 208000019622 heart disease Diseases 0.000 description 5
- 241001465754 Metazoa Species 0.000 description 3
- 206010012601 diabetes mellitus Diseases 0.000 description 3
- 239000000243 solution Substances 0.000 description 3
- 208000003251 Pruritus Diseases 0.000 description 2
- 238000013473 artificial intelligence Methods 0.000 description 2
- 210000004369 blood Anatomy 0.000 description 2
- 239000008280 blood Substances 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 239000013598 vector Substances 0.000 description 2
- 230000002776 aggregation Effects 0.000 description 1
- 238000004220 aggregation Methods 0.000 description 1
- 230000001174 ascending effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004820 blood count Methods 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 229940079593 drug Drugs 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000002347 injection Methods 0.000 description 1
- 239000007924 injection Substances 0.000 description 1
- 210000000265 leukocyte Anatomy 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
- G06F16/31—Indexing; Data structures therefor; Storage structures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
- G06F16/33—Querying
- G06F16/3331—Query processing
- G06F16/334—Query execution
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
- G06F16/33—Querying
- G06F16/338—Presentation of query results
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
- G06F16/35—Clustering; Classification
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H10/00—ICT specially adapted for the handling or processing of patient-related medical or healthcare data
- G16H10/60—ICT specially adapted for the handling or processing of patient-related medical or healthcare data for patient-specific data, e.g. for electronic patient records
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computational Linguistics (AREA)
- Software Systems (AREA)
- Health & Medical Sciences (AREA)
- Epidemiology (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Primary Health Care (AREA)
- Public Health (AREA)
- Medical Treatment And Welfare Office Work (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
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
The application relates to a case storage method, a device, equipment and a storage medium, which are filed on 2019, 08 and 05, and are respectively filed on patent application with the application number of 201910717999.4 and the application name of the patent application.
Technical Field
The present application relates to the field of blockchain technologies, and in particular, to a case storage method, apparatus, device, and storage medium.
Background
In general, people are used to store a special fault of a machine or other objects and repair information of the special fault as a classical case, and when the corresponding fault is encountered again, the current fault can be repaired by referring to a historical case. However, the existing recording method only records individual cases, and the information such as the history fault of a certain object is also recorded and missing, so that the authenticity and the comprehensiveness of the case records are reduced, and the reference value of the cases is also reduced.
Disclosure of Invention
Accordingly, the present application is directed to a case storage method, apparatus, device and storage medium, so as to obtain comprehensive and real cases and realize case sharing. The specific scheme is as follows:
to achieve the above object, in one aspect, the present application provides a case storage method applied to any blockchain node, including:
Acquiring fault cases of a plurality of objects in a current blockchain network; the fault case includes: at least one piece of fault information and corresponding repair information of the current object;
Classifying a plurality of fault cases according to fault types to obtain a plurality of characteristic cases; each feature case records fault information and corresponding repair information of at least one object;
Determining feature key characters in a plurality of feature cases as retrieval indexes, and updating a retrieval index library according to the retrieval indexes;
storing the updated search index library and a plurality of the feature cases to the current blockchain network;
receiving new fault information and corresponding repair information of a target object sent by a user;
if the new feature cases corresponding to the fault information and the corresponding repair information do not exist in the current blockchain network, creating corresponding feature cases in the current blockchain network, and adding the new fault information and the corresponding repair information to the newly created feature cases.
In yet another aspect, the present application further provides a case storage device applied to any blockchain node, including:
The acquisition module is used for acquiring fault cases of a plurality of objects in the current blockchain network; the fault case includes: at least one piece of fault information and corresponding repair information of the current object;
The classification module is used for classifying the plurality of fault cases according to the fault types to obtain a plurality of characteristic cases; each feature case records fault information and corresponding repair information of at least one object;
The updating module is used for determining the characteristic key characters in the plurality of characteristic cases as retrieval indexes and updating a retrieval index library according to the retrieval indexes;
The storage module is used for storing the updated retrieval index library and a plurality of the feature cases to the current blockchain network;
The third receiving module is used for receiving new fault information and corresponding repair information of the target object sent by the user;
The creation module is used for creating a corresponding feature case in the current blockchain network if the feature case corresponding to the new fault information and the corresponding repair information does not exist in the current blockchain network, and adding the new fault information and the corresponding repair information to the newly created feature case.
In yet another aspect, the present application also provides an electronic device including 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 previously disclosed case storage method.
In yet another aspect, the present application further provides a storage medium having stored therein computer executable instructions that, when loaded and executed by a processor, implement the previously disclosed case storage method.
The application is applicable to any blockchain node, that is, any blockchain node can execute the case storage method provided by the application. The current blockchain network stores fault cases of a plurality of objects, and because the blockchain has information disclosure and higher security, the fault cases are stored by using the blockchain network, so that the whole network sharing of the fault cases can be realized, and meanwhile, the security and the non-tamper property of the fault cases are ensured. On the basis, any block chain node can classify the fault cases in the current block chain network according to the fault types, so that a plurality of characteristic cases can be obtained, and the obtained characteristic cases can comprehensively record fault information and corresponding repair information of one or a plurality of objects. 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. When a certain object fails, the relevant characteristic cases can be searched through the search index, so that a reliable, real and comprehensive reference case is provided for repairing the current failure. Meanwhile, after the feature cases are obtained, when new fault information and corresponding repair information of a target object sent by a user are received and the feature cases corresponding to the new fault information and the corresponding repair information do not exist in the current blockchain network, the corresponding feature cases are created in the current blockchain network, and the new fault information and the corresponding repair information are added to the newly created feature cases, so that the obtaining efficiency and timeliness of the feature cases are improved.
Correspondingly, the case storage device, the case storage equipment and the case storage medium have the technical effects.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required to be used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only embodiments of the present application, and that other drawings can be obtained according to the provided drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic diagram of a case storage system architecture according to the present application;
fig. 2 is a flowchart of a first case storing method provided by the present application;
Fig. 3 is a flowchart of a second case storing method provided by the present application;
fig. 4 is a flowchart of a third case storing method provided by the present application;
FIG. 5 is a block chain network diagram according to the present application;
Fig. 6 is a flowchart of a medical case storage method provided by the present application;
FIG. 7 is a schematic diagram of a natural human case record provided by the present application;
Fig. 8 is a schematic diagram of a first feature case record provided in the present application;
Fig. 9 is a schematic diagram of a second feature case record provided in the present application;
FIG. 10 is a diagram of a search result provided by the present application;
fig. 11 is a schematic diagram of a case storage device according to the present application;
FIG. 12 is a diagram of a server according to the present application;
fig. 13 is a diagram of a terminal structure according to the present application.
Detailed Description
At present, the existing recording mode only records individual cases, and the information such as the history fault of a certain object is also recorded and missing, so that the authenticity and the comprehensiveness of case records are reduced, and the reference value of the cases is also reduced. In view of the above-mentioned problems existing at present, the present application proposes a case storage scheme by which comprehensive and real cases can be obtained and case sharing can be achieved.
For easy understanding, a system architecture to which the technical solution disclosed in the present application is applicable is described below. Referring to fig. 1, a system architecture to which the present application is applicable is shown.
As shown in fig. 1, the disclosed case storage system architecture may include a user terminal 11, a server 12, and a blockchain network 13.
The user terminal 11 may be a pre-installed client, and the user may input a fault case to be uploaded on the man-machine interaction interface. After obtaining the fault case, the user terminal 11 sends the fault case to the server 12, and the server 12 uploads the fault case to the corresponding blockchain node. It is understood that the user terminal 11 in the present application includes, but is not limited to, a smart phone, a tablet computer, a wearable device, a desktop computer, etc. in which the above-described client is installed. The user terminal 11 may also be used to query for fault cases stored in the blockchain network 13.
In the present application, the server 12 may specifically refer to a dedicated server for implementing a single service, and different servers 12 are respectively used for implementing different services. The server 12 establishes a communication connection with the user terminal 11 through a 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 by the application. It is to be understood that the server 12 in this embodiment includes, but is not limited to, a cloud server, a physical server, a virtual server, and the like.
It is understood that the blockchain network 13 includes a plurality of blockchain nodes 130. When a failure case submitted by the server 12 is successfully uploaded to any blockchain node 130, the failure case is quickly transferred to other blockchain nodes 130 for storage within a second time period, and each blockchain node 130 shares the stored failure case. In the present application, a block identifier, a case storage record, and a hash value corresponding to a failure case may be recorded in any one of the blocks of the blockchain network 13.
The block identifier may be an identifier obtained after hash processing is performed on a block header of a previous block, or may be a block height of a current block; the case storage records may include fault cases and corresponding time stamps, etc.
It is to be understood 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, and the like.
It should be noted that, the network connecting the user terminal 11, the server 12 and the blockchain network 13, and the network between the blockchain link points in the blockchain network 13 may be determined according to the network condition and the application requirement in the practical application process, and may be a wireless communication network, such as a mobile communication network or a WIFI network, or may be a wired communication network; the network may be a wide area network or a local area network as the case may be. Of course, the user terminal 11 may also communicate directly with the blockchain network 13, so that the server 12 may not be needed, which may save computer resources.
Fig. 2 is a flowchart of a first case storing method according to an embodiment of the present application. Referring to fig. 2, the case storage method applied to any blockchain node may include the following steps:
S201, obtaining fault cases of a plurality of objects in a current blockchain network; the fault cases include: at least one fault information and corresponding repair information of the current object.
In the current blockchain network, the failure cases may be stored with the identification information of the object as a key. Wherein, the object may be: equipment, people, animals, plants and the like, wherein when the objects are people, animals, plants, the fault cases are natural human cases, the faults are disease information, and the repair information is disease treatment information; the identification information may be identity information of a person, a name of an animal or plant, etc. If the object is a device, the fault information may include: a failed component, and a cause of the failure; the identification information of the device may be a factory code of the device or the like.
If the object is a person, the cases are stored by the identity information key of the person, so that the corresponding treatment information, laboratory sheet information and the like of the same patient (namely the natural person) can be uniformly stored into one case, thus not only enriching the cases, enabling the cases of the patient to be comprehensively recorded, but also being convenient for the patient and doctor to inquire the cases. Thereby providing convenience for obtaining comprehensive, real and reliable characteristic cases.
S202, classifying a plurality of fault cases according to fault types to obtain a plurality of characteristic cases; each feature case records fault information and corresponding repair information for at least one object.
In a specific embodiment, the fault cases may be classified according to the fault type by using a classification algorithm, and the classification algorithm is a naive bayes algorithm, a random forest algorithm or a support vector machine, to obtain a plurality of feature cases. Of course, other classification algorithms may also be used for classification, such as: clustering algorithm.
If the fault cases are natural human cases, it can be understood that, since there may be a plurality of diseases suffered by one natural human, after the fault cases are classified according to the disease types, the diseases suffered by the same natural human may be classified into different feature cases. For example: two kinds of disease information and treatment information of heart disease and diabetes are recorded in the natural human A case, and then the disease information and treatment information of the heart disease which are recorded in the natural human A case are classified into heart disease characteristic cases when classified; the disease information and treatment information about diabetes recorded in natural human a cases will be categorized into diabetes characteristic cases. Since the fault cases also record laboratory sheet information and the like, the laboratory sheet information and the like are classified into corresponding feature cases when the disease classification is performed. The treatment information can comprise medicine information of oral administration, external application and/or injection, corresponding medicine effect and the like. Of course, identity information of natural people, information of places and times of sick consultation, and the like can also be recorded in the characteristic cases.
If there are multiple records of disease information and treatment information concerning a dirty disease in a fault case, each record can be considered as a treatment record. When sorting, the treatment time of the treatment records is recorded respectively, and the treatment records are regarded as relevant information of the heart disease of the current natural person. That is, these treatment records are collectively regarded as current cases of heart disease in natural persons.
S203, determining the feature key characters in the feature cases as retrieval indexes, and updating a retrieval index library according to the retrieval indexes.
S204, storing the updated index library and the plurality of feature cases into the current blockchain network.
In this embodiment, before storing the updated index library and the plurality of feature cases in the current blockchain network, the method further includes: for any one of the feature cases, adding fault information with the same type of repair information to the same fault group; a plurality of fault groups are included in any one of the feature cases.
In each feature case, a plurality of fault groups are provided, and fault information of the same type of repair information is recorded in each fault group. Taking the characteristic cases obtained after classification of natural human cases as an example, assume that there are 2 fault groups (i.e., case groups) in the characteristic cases of urticaria, and the first fault group is used for recording information such as symptoms, treatment effects, etc. of taking a medicine; the second trouble group is used for recording information of illness symptoms, treatment effects and the like of taking another medicine. Therefore, the treatment effects of different medicines and different treatment modes on the same disease can be clearly seen from the characteristic cases; it can also be seen quickly from the characteristic cases that there are several treatments and modes for the current disease.
To facilitate retrieval and querying, corresponding retrieval indexes may be constructed for the feature cases. The search index may be any feature key character in the feature case, where the feature key character is as follows: fault name, location, cause of the fault, etc. If the fault case is a natural human case, the characteristic key character may be a disease name or abbreviation, such as: urticaria; or characteristic disease symptoms, etc., such as: wind-mass, which is the characteristic symptom of urticaria.
Storing the updated index library and the plurality of feature cases in the current blockchain network, namely sharing the index library and the feature cases in the current blockchain network. Thus, any block link point can query the related characteristic cases by using the retrieval index.
It should be noted that other implementation steps in the present embodiment are the same as or similar to those in the above embodiment, so that the description of the present embodiment is omitted here.
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 the present application. The current blockchain network stores fault cases of a plurality of objects, and because the blockchain has information disclosure and higher security, the fault cases are stored by using the blockchain network, so that the whole network sharing of the fault cases can be realized, and meanwhile, the security and the non-tamper property of the fault cases are ensured. On the basis, any block chain node can classify the fault cases in the current block chain network according to the fault types, so that a plurality of characteristic cases can be obtained, and the obtained characteristic cases can comprehensively record fault information and corresponding repair information of one or a plurality of objects. 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. When a certain object fails, the relevant characteristic cases can be searched through the search index, so that a reliable, real and comprehensive reference case is provided for repairing the current failure.
Fig. 3 is a flowchart of a second case storing method according to an embodiment of the present application. Referring to fig. 3, the case storage method applied to any blockchain node may include the following steps:
S301, obtaining fault cases of a plurality of objects in a current blockchain network; the fault cases include: at least one fault information and corresponding repair information of the current object.
S302, classifying a plurality of fault cases according to fault types to obtain a plurality of characteristic cases; each feature case records fault information and corresponding repair information for at least one object.
S303, determining the feature key characters in the feature cases as retrieval indexes, and updating a retrieval index library according to the retrieval indexes.
S304, storing the updated index library and the plurality of feature cases into the current blockchain network.
S305, receiving a search request sent by a user.
It is understood that the user may submit the retrieval request through the human-machine interface. The target retrieval index in the retrieval request can be preset information of a human-computer interaction interface, and can also be information input by a user.
S306, extracting a target retrieval index in the retrieval request.
S307, the similarity between the target retrieval index and a plurality of feature cases in the current blockchain network is respectively determined.
The similarity can be determined by adopting a calculation mode such as semantic similarity, cosine similarity and the like. When the cosine similarity is adopted to determine the similarity between the target retrieval index and the feature case, the target retrieval index and the feature case are converted into vectors, and then the similarity between the two vectors is calculated.
And S308, determining the feature case corresponding to the maximum similarity as a retrieval result and returning.
It can be understood that the similarity between the target search index and the plurality of feature cases is determined respectively, and the similarity between the target search index and each feature case needs to be calculated respectively, so as to obtain the similarity corresponding to each feature case. And determining the feature case corresponding to the maximum similarity as a retrieval result of the current retrieval request and returning.
In a specific embodiment, for any feature case, determining the similarity of the target search index and the current feature case includes: 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; and weighting and summarizing the multiple sub-similarities to obtain the similarity between the target retrieval index and the current feature case.
Still taking natural human cases as an example. For example: the key indexes in the characteristic cases of urticaria are wind cluster, skin itch and blood convention, and the weights respectively correspond to 40%, 40% and 20%. Then the similarity between the target retrieval index and the wind group is calculated, so that a first sub-similarity A can be obtained; calculating the similarity between the target retrieval index and the skin itch, so that a second sub-similarity B can be obtained; calculating the similarity between the target retrieval index and blood convention, so as to obtain a third sub-similarity C; then the three sub-similarities are weighted together and then: w=a×40% +b×40% +c×20%, then W is the similarity between the target search index and the urticaria feature case.
In a specific embodiment, determining the feature case corresponding to the maximum similarity as the search result and returning the search result includes: the method comprises the steps of arranging a plurality of feature cases in a descending order according to the similarity to obtain a feature case sequence; and determining the feature case sequence as a retrieval result and returning.
The similarity between the target retrieval index and each feature case can be calculated through the mode, so that the feature cases can be arranged in a descending order according to the similarity, and a feature case sequence can be obtained; and then the feature case sequence can be used as a search result and returned. If the feature case sequence contains more feature cases, the first N of the feature cases can be selected as the retrieval result and returned. Of course, the feature cases may be arranged in an ascending order according to the similarity, and then the last N in the feature case sequence may be selected as the search result and returned. Of course, the search result may also be presented at the client for user reference.
It should be noted that, to avoid malicious reference to the feature case, the authority of the user to submit the search request through the client may be limited, for example: only if the correct physician's license code is entered, the retrieval request is allowed to be submitted. Of course, the cryptographic technique can also be used to avoid malicious querying and retrieval of feature cases.
It should be noted that other implementation steps in the present embodiment are the same as or similar to those in the above embodiment, so that the description of the present embodiment is omitted here.
After the feature cases are stored in the blockchain network, when a search request is received, extracting target search indexes in the search request, and further respectively determining the similarity between the target search indexes and the plurality of feature cases, so that search results corresponding to the search request are determined according to the similarity, returned and displayed. Thus, the user can inquire about the related cases in real time, thereby providing reliable and comprehensive basis for repairing the current faults.
Fig. 4 is a flowchart of a third case storing method according to an embodiment of the present application. Referring to fig. 4, the case storage method applied to any blockchain node may include the following steps:
s401, fault information and corresponding repair information of a plurality of objects sent by a user are received.
In one embodiment, the user may send the failure information and the corresponding repair information to the blockchain node at different times to enable the blockchain node to synchronously store the failure information and the corresponding repair information in the whole network.
S402, generating a fault 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 fault case.
S403, establishing an association relation between the fault case and the ID, and storing the association relation, the fault case and the ID to the current block chain network.
In this embodiment, storing the association, the failure case, and the ID to the current blockchain network includes: broadcasting the association, the failure case and the ID in the current blockchain network so that other blockchain nodes in the current blockchain network verify the association, the failure case and the ID; and if the verification is passed, packaging the association relation, the fault case and the ID into a second block, and broadcasting a packaging message of the second block in the current block chain network.
Of course, the execution time of the classification failure case may also be set in the current blockchain network, for example: the execution period is set, and the sorting operation is performed every 10 minutes or every 1 hour. And each blockchain node collects new fault information and corresponding repair information and synchronizes the new fault information and the corresponding repair information to the whole network, and when the classification execution time point is reached, the fault information and the corresponding repair information collected from the previous classification execution time point to the current classification execution time point are classified. After the new feature cases are obtained by classification, if the new feature cases exist in the block chain network, the new feature cases and the old feature cases are combined and then shared; if the new feature case does not exist in the blockchain network, the new feature case is stored and shared.
S404, obtaining fault cases of a plurality of objects in the current blockchain network; the fault cases include: at least one fault information and corresponding repair information of the current object.
S405, classifying the plurality of fault cases according to fault types to obtain a plurality of characteristic cases; each feature case records fault information and corresponding repair information for at least one object.
S406, determining the feature key characters in the feature cases as retrieval indexes.
S407, judging whether a search index exists in the search index library; if yes, then execute S408; if not, S409 is performed.
S408, determining the original retrieval index library as an updated retrieval index library;
S409, adding the search index to the search index library to obtain an updated search index library, and executing S410.
S410, broadcasting the updated 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 index library and the plurality of feature cases.
S411, if the verification is passed, the updated index library and the plurality of feature cases are packaged into a first block, and a packaging message of the first block is broadcasted in the current blockchain network.
S412, receiving new fault information and corresponding repair information of the target object sent by the user.
S413, adding the new fault information and the corresponding repair information into the corresponding feature cases according to the fault type of the new fault information.
In this embodiment, after a plurality of feature cases are classified in the blockchain network and sharing operation is completed, if the current blockchain network receives new fault information and corresponding repair information again, the new fault information and the corresponding repair information may be directly added to the corresponding feature cases. If no new feature case corresponding to the fault information and the corresponding repair information exists in the current blockchain network, a corresponding feature case can be created in the current blockchain network, and the new fault information and the corresponding repair information are added into the newly created feature case.
It should be noted that other implementation steps in the present embodiment are the same as or similar to those in the above embodiment, so that the description of the present embodiment is omitted here.
Therefore, after the feature cases are obtained by classification, when the fault cases are collected again, the newly collected fault cases can be classified, so that the fault cases in the blockchain network can be classified timely to obtain the feature cases for the related personnel to inquire and refer.
The case storage method provided by the application is described below through a specific application scenario example. Referring to fig. 5, fig. 5 is a schematic diagram of a blockchain network according to an embodiment of the present application. In fig. 5, any medical institution can be used as a block chain link point to access a block chain network, each medical institution can upload natural human cases to its corresponding block chain node, and the block chain link point shares the uploaded natural human cases to other nodes, so that the whole network shared storage of the natural human cases can be realized.
Meanwhile, the blockchain node corresponding to any medical institution can also be used as an analysis summary node. The analysis and summarization node classifies natural human cases in the whole network according to disease types, so that a plurality of characteristic cases can be obtained, all relevant information of the patient suffering from the current disease can be comprehensively recorded by the obtained characteristic cases, and the comprehensive recording of the characteristic 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 medical institutions accessing the current blockchain network can share the feature cases, and related feature cases can be searched through the index if necessary.
To reduce the data throughput of each blockchain node, an analysis summary node may be provided in the blockchain network. The analysis summary node may be provided in plural, that is, the analysis node 1 and the analysis node 2 in fig. 5. This analysis summary node is only used to implement the case storage scheme provided by the present application. That is, the block link points corresponding to the medical institutions are used for collecting and sharing the natural human cases, and the analysis and aggregation nodes are used for classifying the collected natural human cases and then sharing the characteristic cases.
Referring to fig. 6, fig. 6 is a flowchart of a medical case storage method according to an embodiment of the present application. The medical case storage method shown in fig. 6 may include the steps of:
s601, the target blockchain node acquires a natural human case in the current blockchain network.
In this embodiment, the failure case is a natural human case. Before the target blockchain point obtains the natural human case in the current blockchain network, the method further comprises: all block chain link points in the current block chain network collect natural human cases respectively, and meanwhile, the collected natural human cases are packed into blocks, namely, the whole-network sharing storage of the natural human cases is carried out.
Specifically, please refer to fig. 7 for storage and display of natural human cases, and fig. 7 is a schematic diagram of natural human case records provided in an embodiment of the present application. The time points in fig. 7 are the time points of each visit by the patient. The natural person ID in fig. 7 may be patient identity information.
S602, classifying natural human cases according to disease types by the target block chain link points to obtain a plurality of characteristic cases.
Wherein, each characteristic case records at least one of the illness information and the corresponding treatment information of the natural person. The disease type corresponds to the above-mentioned fault type.
S603, the target block link points determine feature key characters in the feature cases as retrieval indexes, and update a retrieval index library according to the retrieval indexes.
Wherein, the characteristic key characters can be the name of the disease, the symptom of the disease, and the like.
Specifically, referring to fig. 8 to fig. 9 for storage and display of feature cases, fig. 8 is a schematic diagram of a first feature case record provided in an embodiment of the present application, and fig. 9 is a schematic diagram of a second feature case record provided in an embodiment of the present application. The specific method in fig. 9 is to take medicine information or other treatment information for the current disease, and the corresponding case number is the case number with the same treatment information, and the above-mentioned case group may be referred to herein. The characteristic cases in fig. 8 and 9 are disease cases.
S604, broadcasting the updated index library and the plurality of feature cases to other block chain nodes by the target block chain link point.
Wherein the target blockchain node and the other blockchain nodes together form the current blockchain network.
S605, other block chain nodes are used for carrying out consensus on the updated index library and a plurality of feature cases.
And S606, if the consensus passes, other blockchain nodes broadcast the consensus passing message in the whole network.
The updated index library and the plurality of feature cases can be identified by adopting a common identification method, for example: PBFT, POW, POS, DPOS, et al.
S607, the target block link point packages the updated index library and the plurality of feature cases into blocks.
S608, the target blockchain node broadcasts a blockgeneration message in the whole network.
It should be noted that, the implementation steps in this embodiment are the same as or similar to those in the above embodiments, and specific reference may be made to any of the above embodiments, so that the description of this embodiment is omitted here.
If the index is a symptom of illness and a result of examination (e.g., white blood cell count), then when the feature cases in the blockchain network are queried using the symptom and the result of examination, the obtained index results are shown in fig. 10. Fig. 10 is a schematic diagram of a search result provided in an embodiment of the present application. In fig. 10, all similar cases are arranged in descending order according to the degree of similarity to symptoms and examination results. The case ID in fig. 8, 9 and 10 may be the name of the disease corresponding to the current feature case.
It can be seen that this embodiment enables any one medical institution to access the blockchain network as a blockchain node and upload natural human cases. The natural human cases are stored in the blockchain network by natural artificial keys, and then the natural human cases are classified by taking the disease types as keys, so that unified storage of the patient cases of different medical institutions is realized, and convenience is provided for retrieval and inquiry of the feature cases.
Referring to fig. 11, fig. 11 is a schematic diagram of a case storage device according to an embodiment of the present application, which is applied to any blockchain node, and includes:
An obtaining module 1101, configured to obtain failure cases of a plurality of objects in a current blockchain network; the fault cases include: at least one piece of fault information and corresponding repair information of the current object;
The classification module 1102 is configured to classify the plurality of fault cases according to the fault type to obtain a plurality of feature cases; each feature case records fault information and corresponding repair information of at least one object;
An updating module 1103, configured to determine feature key characters in the feature cases as a search index, and update a search index library according to the search index;
A storage module 1104 is configured to store the updated index library and the plurality of feature cases in the current blockchain network.
In one specific embodiment, the method further comprises:
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;
and the retrieval module is used for retrieving the feature cases corresponding to the target retrieval index in the current blockchain network and returning retrieval results.
In one embodiment, the retrieval module comprises:
the first determining unit is used for determining the similarity between the target retrieval index and a plurality of feature cases in the current blockchain network respectively;
and the second determining unit is used for determining the feature case corresponding to the maximum similarity as a retrieval result and returning the retrieval result.
In a specific embodiment, the first determining unit is specifically configured to:
Aiming at any feature case, the similarity of the target retrieval index and each feature key character in the current feature case is respectively determined, and a plurality of sub-similarities are obtained; and weighting and summarizing the multiple sub-similarities to obtain the similarity between the target retrieval index and the current feature case.
In a specific embodiment, the second determining unit is specifically configured to:
the method comprises the steps of arranging a plurality of feature cases in a descending order according to the similarity to obtain a feature case sequence; and determining the feature case sequence as a retrieval result and returning.
In one specific embodiment, the method further comprises:
the first adding module is used for adding fault information with the same type of repair information to the same fault group aiming at any feature case; a plurality of fault groups are included in any one of the feature cases.
In one embodiment, the update module includes:
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 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 one embodiment, a memory module includes:
The first broadcasting unit is used for broadcasting 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 verify the updated retrieval index library and the plurality of feature cases;
and the first packing unit is used for packing the updated search index library and the plurality of feature cases into a first block if the verification is passed, and broadcasting a packing message of the first block in the current block chain network.
In one specific embodiment, the method further comprises:
the second receiving module is used for receiving fault information and corresponding repair information of a plurality of objects sent by a user;
The generating module is used for generating a fault 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 fault case;
And the execution module is used for establishing the association relation between the fault case and the ID and storing the association relation, the fault case and the ID into the current block chain network.
In one embodiment, the execution module includes:
The second broadcasting unit is used for broadcasting the association relation, the fault case and the ID in the current block chain network so as to enable other block chain nodes in the current block chain network to verify the association relation, the fault case and the ID;
And the second packing unit is used for packing the association relation, the fault 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 block chain network.
In one specific embodiment, the method further comprises:
The third receiving module is used for receiving new fault information and corresponding repair information of the target object sent by the user;
and the second adding module is used for adding the new fault information and the corresponding repair information into the corresponding characteristic cases according to the fault type of the new fault information.
In one embodiment, the classification module is specifically configured to:
And classifying the fault cases according to the fault types by using a classification algorithm to obtain a plurality of feature cases, wherein the classification algorithm is a naive Bayesian algorithm, a random forest algorithm or a support vector machine.
The more specific working process of each module and unit in this embodiment may refer to the corresponding content disclosed in the foregoing embodiment, and will not be described herein.
It can be seen that the present embodiment provides a case storage device, comprising: the device comprises an acquisition module, a classification module, an updating module and a storage module. Firstly, an acquisition module acquires fault cases of a plurality of objects in a current blockchain network; the fault cases include: at least one piece of fault information and corresponding repair information of the current object; then, the classification module classifies the multiple fault cases according to the fault types to obtain multiple feature cases; each feature case records fault information and corresponding repair information of at least one object; the updating module further determines the feature key characters in the feature cases as retrieval indexes, and updates a retrieval index library according to the retrieval indexes; and finally, the storage module stores the updated index library and the plurality of feature cases into the current blockchain network. Therefore, the modules work separately and cooperate, and the functions of the modules are all the same, so that real and comprehensive characteristic cases can be obtained, and the sharing of the characteristic cases is realized.
Further, the embodiment of the application also provides electronic equipment. The electronic device may be the server 50 shown in fig. 12 or the terminal 60 shown in fig. 13. Fig. 12 and 13 are each a structural diagram of an electronic device shown in this embodiment, and the contents in the drawings should not be construed as limiting the scope of use of the present application in any way.
Fig. 12 is a schematic structural diagram of a server according to 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. Wherein the memory 52 is configured to store a computer program that is loaded and executed by the processor 51 to implement the relevant steps in the case store disclosed in any of the foregoing embodiments.
In this embodiment, the power supply 53 is configured to provide an operating voltage for each hardware device on the server 50; the communication interface 54 can create a data transmission channel between the server 50 and an external device, and the communication protocol to be followed is any communication protocol applicable to the technical solution of the present application, which is not specifically limited herein; the input/output interface 55 is used for acquiring external input data or outputting external output data, and the specific interface type thereof may be selected according to the specific application needs, which is not limited herein.
The memory 52 may be a carrier for storing resources, such as a read-only memory, a random access memory, a magnetic disk, or an optical disk, and the resources stored thereon include an operating system 521, a computer program 522, and data 523, and the storage may be temporary storage or permanent storage.
The operating system 521 is used for managing and controlling various hardware devices on the Server 50 and the computer program 522 to implement the operation and processing of the data 523 in the memory 52 by the processor 51, which may be Windows Server, netware, unix, linux, etc. The computer program 522 may further comprise a computer program that can be used to perform other specific tasks in addition to the computer program that can be used to perform the case storage methods disclosed in any of the previous embodiments. The data 523 may include data such as a feature case in addition to data such as a fault case.
Fig. 13 is a schematic structural diagram of a terminal according to an embodiment of the present application, and the terminal 60 may specifically include, but is not limited to, a smart phone, a tablet computer, a notebook computer, a desktop computer, or the like.
Generally, the terminal 60 in this embodiment includes: a processor 61 and a memory 62.
Processor 61 may include one or more processing cores, such as a 4-core processor, an 8-core processor, etc. The processor 61 may be implemented in at least one hardware form of DSP (DIGITAL SIGNAL Processing), FPGA (Field-Programmable gate array), PLA (Programmable Logic Array ). The processor 61 may also include a main processor, which is a processor for processing data in an awake state, also called a CPU (Central Processing Unit ), and a coprocessor; a coprocessor is a low-power processor for processing data in a standby state. In some embodiments, the processor 61 may integrate a GPU (Graphics Processing Unit, image processor) for rendering and drawing of content required to be displayed by the display screen. In some embodiments, the processor 61 may also include an AI (ARTIFICIAL INTELLIGENCE ) processor for processing computing operations related to machine learning.
Memory 62 may include one or more computer-readable storage media, which may be non-transitory. Memory 62 may also include high-speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In this embodiment, the memory 62 is at least used for storing a computer program 621, which, when loaded and executed by the processor 61, is capable of implementing the relevant steps in the case storage method executed by the terminal side as disclosed in any of the foregoing embodiments. In addition, the resources stored by the memory 62 may also include an operating system 622, data 623, and the like, and the storage manner may be transient storage or permanent storage. Wherein the operating system 622 may include Windows, unix, linux, etc. The 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 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 is not limiting of the terminal 60 and may include more or fewer components than shown.
Further, the embodiment of the application also discloses a storage medium, wherein the storage medium stores computer executable instructions, and when the computer executable instructions are loaded and executed by a processor, the case storage method disclosed in any embodiment is realized. For specific steps of the method, reference may be made to the corresponding contents disclosed in the foregoing embodiments, and no further description is given here.
It should be noted that the foregoing is only a preferred embodiment of the present application, and is not intended to limit the present application, but any modification, equivalent replacement, improvement, etc. which fall within the spirit and principles of the present application should be included in the scope of the present application.
In this specification, each embodiment is described in a progressive manner, and each embodiment is mainly described in a different point from other embodiments, so that the same or similar parts between the embodiments are 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 points refer to the description of the method section.
The principles and embodiments of the present application have been described herein with reference to specific examples, the description of which is intended only to assist in understanding the methods of the present application and the core ideas thereof; meanwhile, as those skilled in the art will have variations in the specific embodiments and application scope in accordance with the ideas of the present application, the present description should not be construed as limiting the present application in view of the above.
Claims (20)
1. A case storage method applied to any blockchain node, comprising:
Receiving fault information and corresponding repair information of a plurality of objects sent by a user;
generating a fault case of each object according to the identification information of different objects, and taking the identification information of the object as the ID of the fault case, wherein the fault case comprises at least one piece of fault information and corresponding repair information of the current object;
establishing an association relationship between the fault case and the ID;
Broadcasting the association, the failure case and the ID in a current blockchain network so that other blockchain nodes in the current blockchain network verify the association, the failure case and the ID;
if the verification is passed, packaging the association relationship, the fault case and the ID into a second block, and broadcasting a packaging message of the second block in the current block chain network;
Acquiring fault cases of a plurality of objects in a current blockchain network; the fault case includes: at least one piece of fault information and corresponding repair information of the current object, wherein the fault information comprises a faulty component and a fault cause;
Classifying a plurality of fault cases according to fault types to obtain a plurality of characteristic cases; each feature case records fault information and corresponding repair information of at least one object;
Determining feature key characters in a plurality of feature cases as retrieval indexes, and updating a retrieval index library according to the retrieval indexes, wherein the feature key characters comprise any one of fault names, positions and fault reasons;
For any one of the feature cases, fault information with the same type of repair information is added to the same fault group, wherein any one of the feature cases comprises a plurality of fault groups, the plurality of fault groups comprise different repair schemes and corresponding effects, all relevant information of the current fault is recorded by the obtained feature case to realize comprehensive recording of the feature cases, a feature case record schematic diagram comprises the fault information, an inspection record, a diagnosis conclusion, the repair information and the corresponding effects, or the feature case record schematic diagram comprises the fault information, the inspection index and the repair method, and the repair method comprises specific repair information, repair effects and the number of cases;
storing the updated search index library and a plurality of the feature cases to the current blockchain network;
receiving new fault information and corresponding repair information of a target object sent by a user;
if the new feature cases corresponding to the fault information and the corresponding repair information do not exist in the current blockchain network, creating corresponding feature cases in the current blockchain network, and adding the new fault information and the corresponding repair information to the newly created feature cases.
2. The case storage method of claim 1, wherein after storing the updated index library and the plurality of feature cases to the current blockchain network, further comprising:
Receiving a search request sent by a user;
Extracting a target retrieval index in the retrieval request;
and searching the feature cases corresponding to the target search index in the current block chain network, and returning a search result.
3. The case storage method according to claim 2, wherein retrieving the feature case corresponding to the target retrieval index in the current blockchain network and returning a retrieval result includes:
Respectively determining the similarity between the target retrieval index and a plurality of the characteristic cases in the current blockchain network;
and determining the feature case corresponding to the maximum similarity as the retrieval result and returning.
4. The case storage method of claim 3, wherein determining the similarity of the target search index to 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;
and weighting and summarizing the sub-similarity to obtain the similarity between the target retrieval index and the current feature case.
5. The case storage method according to claim 3, wherein determining the feature case corresponding to the maximum similarity as the search result and returning the search result includes:
the feature cases are arranged in a descending order according to the similarity, and a feature case sequence is obtained;
And determining the feature case sequence as the retrieval result and returning.
6. The case storage method of claim 1, wherein updating the search index library based on 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.
7. The case storage method of claim 1, wherein the storing the updated index library and the plurality of feature cases to the current blockchain network comprises:
Broadcasting the updated 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 index library and the plurality of feature cases;
and if the verification is passed, packaging the updated index library and a plurality of feature cases into a first block, and broadcasting a packaging message of the first block in the current blockchain network.
8. The case storage method according to claim 1, wherein after receiving the new fault information and the corresponding repair information of the target object sent by the user, the method further comprises:
If the characteristic cases corresponding to the new fault information and the corresponding repair information exist in the current blockchain network, adding the corresponding characteristic cases to the new fault information and the corresponding repair information according to the fault type of the new fault information.
9. The case storage method according to claim 1, wherein the classifying the fault case according to the fault type to obtain a plurality of feature cases includes:
and classifying the fault cases according to the fault types by using a classification algorithm to obtain a plurality of feature cases, wherein the classification algorithm is a naive Bayesian algorithm, a random forest algorithm or a support vector machine.
10. A case storage device for any blockchain node, comprising:
the second receiving module is used for receiving fault information and corresponding repair information of a plurality of objects sent by a user;
The generating module is used for generating a fault case of each object according to the identification information of different objects, and taking the identification information of the object as the ID of the fault case, wherein the fault case comprises at least one fault information and corresponding repair information of the current object;
the execution module is used for establishing an association relationship between the fault case and the ID;
the second broadcasting module is used for broadcasting the association relation, the fault case and the ID in the current blockchain network so that other blockchain nodes in the current blockchain network verify the association relation, the fault case and the ID;
The second packaging module is used for packaging the association relation, the fault case and the ID into a second block if the verification is passed, and broadcasting a packaging message of the second block in the current block chain network;
The acquisition module is used for acquiring fault cases of a plurality of objects in the current blockchain network; the fault case includes: at least one piece of fault information and corresponding repair information of the current object, wherein the fault information comprises a faulty component and a fault cause;
The classification module is used for classifying the plurality of fault cases according to the fault types to obtain a plurality of characteristic cases; each feature case records fault information and corresponding repair information of at least one object;
The updating module is used for determining the characteristic key characters in the plurality of characteristic cases as retrieval indexes and updating a retrieval index library according to the retrieval indexes, wherein the characteristic key characters comprise any one of fault names, positions and fault reasons;
The first adding module is used for adding fault information with the same type of repair information to the same fault group aiming at any one of the feature cases, wherein any one of the feature cases comprises a plurality of fault groups, the plurality of fault groups comprise different repair schemes and corresponding effects, all relevant information of the current fault is recorded by the obtained feature case to realize comprehensive recording of the feature cases, a feature case record schematic diagram comprises the fault information, the inspection record, the diagnosis conclusion, the repair information and the corresponding effects, or the feature case record schematic diagram comprises the fault information, the inspection index and the repair method, and the repair method comprises specific repair information, repair effects and case numbers;
The storage module is used for storing the updated retrieval index library and a plurality of the feature cases to the current blockchain network;
The third receiving module is used for receiving new fault information and corresponding repair information of the target object sent by the user;
The creation module is used for creating a corresponding feature case in the current blockchain network if the feature case corresponding to the new fault information and the corresponding repair information does not exist in the current blockchain network, and adding the new fault information and the corresponding repair information to the newly created feature case.
11. The case storage device of claim 10, wherein the device further comprises:
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;
And the retrieval module is used for retrieving the feature cases corresponding to the target retrieval index in the current blockchain network and returning retrieval results.
12. The case storage device of claim 11, wherein the retrieval module comprises:
A first determining unit, configured to determine similarities between the target search index and a plurality of the feature cases in the current blockchain network, respectively;
and the second determining unit is used for determining the feature case corresponding to the maximum similarity as the search result and returning the search result.
13. The case storage device of claim 12, wherein the first determining unit is specifically configured to:
Aiming at any feature case, the similarity of the target retrieval index and each feature key character in the current feature case is respectively determined, and a plurality of sub-similarities are obtained;
and weighting and summarizing the sub-similarity to obtain the similarity between the target retrieval index and the current feature case.
14. The case storage device of claim 12, wherein the second determining unit is specifically configured to:
the feature cases are arranged in a descending order according to the similarity, and a feature case sequence is obtained;
And determining the feature case sequence as the retrieval result and returning.
15. The case storage device of claim 10, 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.
16. The case storage device of claim 10, wherein the storage module comprises:
A first broadcasting unit, configured to broadcast the updated 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 index library and the plurality of feature cases;
And the first packing unit is used for packing the updated search index library and the plurality of feature cases into a first block if the verification is passed, and broadcasting a packing message of the first block in the current block chain network.
17. The case storage device of claim 10, wherein the device further comprises:
The third receiving module is used for receiving new fault information and corresponding repair information of the target object sent by the user;
and the second adding module is used for adding the new fault information and the corresponding repair information into the corresponding characteristic cases according to the fault type of the new fault information.
18. The case storage device of claim 10, wherein the classification module is specifically configured to:
and classifying the fault cases according to the fault types by using a classification algorithm to obtain a plurality of feature cases, wherein the classification algorithm is a naive Bayesian algorithm, a random forest algorithm or a support vector machine.
19. 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 9.
20. 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 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910853432.XA CN110597946B (en) | 2019-08-05 | 2019-08-05 | Case storage method, device, equipment and storage medium |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910853432.XA CN110597946B (en) | 2019-08-05 | 2019-08-05 | Case storage method, device, equipment and storage medium |
| CN201910717999.4A CN110457425B (en) | 2019-08-05 | 2019-08-05 | Case storage method, device, equipment and storage medium |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910717999.4A Division CN110457425B (en) | 2019-08-05 | 2019-08-05 | Case storage method, device, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110597946A CN110597946A (en) | 2019-12-20 |
| CN110597946B true CN110597946B (en) | 2024-04-23 |
Family
ID=68484947
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910717999.4A Active CN110457425B (en) | 2019-08-05 | 2019-08-05 | Case storage method, device, equipment and storage medium |
| CN201910853432.XA Active CN110597946B (en) | 2019-08-05 | 2019-08-05 | Case storage method, device, equipment and storage medium |
Family Applications Before (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910717999.4A Active CN110457425B (en) | 2019-08-05 | 2019-08-05 | Case storage method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN110457425B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110993112B (en) * | 2019-11-20 | 2023-04-18 | 泰康保险集团股份有限公司 | Tumor treatment case management method, system, medium and electronic device based on block chain |
| CN111275349A (en) * | 2020-02-07 | 2020-06-12 | 武汉科技大学 | Remanufacturing process planning method based on block chain and instance reasoning |
| CN112085380B (en) * | 2020-09-07 | 2023-10-17 | 杭州叙简科技股份有限公司 | Block chain-based safety production accident case management method |
| CN113139709A (en) * | 2020-12-31 | 2021-07-20 | 上海明品医学数据科技有限公司 | Evaluation system and evaluation method for medical information |
| CN112989255B (en) * | 2021-04-15 | 2021-08-03 | 中国电子信息产业集团有限公司第六研究所 | Identification analysis system |
| CN113435307A (en) * | 2021-06-23 | 2021-09-24 | 国网天津市电力公司 | Operation and maintenance method, system and storage medium based on visual identification technology |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170011187A1 (en) * | 2014-03-27 | 2017-01-12 | Fujifilm Corporation | Similar case search device, similar case search method, and non-transitory computer readable medium |
| CN109659936A (en) * | 2018-12-29 | 2019-04-19 | 国电南瑞科技股份有限公司 | A kind of smart grid Dispatching Control System failure method of disposal and system |
| CN110019235A (en) * | 2017-12-29 | 2019-07-16 | 百度在线网络技术（北京）有限公司 | Data storage, restoration methods, device, equipment and medium based on block chain |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105590146A (en) * | 2016-02-29 | 2016-05-18 | 上海带来科技有限公司 | Power plant device intelligent prediction overhaul method and power plant device intelligent prediction overhaul system based on big data |
| CN108959945B (en) * | 2018-07-06 | 2020-05-05 | 腾讯科技（深圳）有限公司 | Medical data sharing method and device, computer readable medium and electronic equipment |
-
2019
- 2019-08-05 CN CN201910717999.4A patent/CN110457425B/en active Active
- 2019-08-05 CN CN201910853432.XA patent/CN110597946B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170011187A1 (en) * | 2014-03-27 | 2017-01-12 | Fujifilm Corporation | Similar case search device, similar case search method, and non-transitory computer readable medium |
| CN110019235A (en) * | 2017-12-29 | 2019-07-16 | 百度在线网络技术（北京）有限公司 | Data storage, restoration methods, device, equipment and medium based on block chain |
| CN109659936A (en) * | 2018-12-29 | 2019-04-19 | 国电南瑞科技股份有限公司 | A kind of smart grid Dispatching Control System failure method of disposal and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110457425A (en) | 2019-11-15 |
| CN110597946A (en) | 2019-12-20 |
| CN110457425B (en) | 2024-05-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110597946B (en) | Case storage method, device, equipment and storage medium | |
| Kumar et al. | Big data analytics for healthcare industry: impact, applications, and tools | |
| US20090240523A1 (en) | Optimizing pharmaceutical treatment plans across multiple dimensions | |
| Lyu et al. | Past, present, and future of emergency general surgery in the USA | |
| US11574075B2 (en) | Distributed machine learning technique used for data analysis and data computation in distributed environment | |
| CN109542966B (en) | Data fusion method and device, electronic equipment and computer readable medium | |
| Bahga et al. | Healthcare data integration and informatics in the cloud | |
| CN115497631A (en) | Clinical scientific research big data analysis system | |
| Sarkar et al. | A conceptual distributed framework for improved and secured healthcare system | |
| CN114049927A (en) | Disease data processing method and device, electronic equipment and readable medium | |
| CN111883251A (en) | Medical misdiagnosis detection method and device, electronic equipment and storage medium | |
| CN109360615A (en) | A kind of medical resource sharing method, device, equipment and storage medium | |
| CN108710644A (en) | One kind is about government affairs big data processing method | |
| CN114649074A (en) | Medical record data processing method, platform and device | |
| Tan et al. | Big data architecture for pervasive healthcare: a literature review | |
| Chrimes et al. | Towards a real-time big data analytics platform for health applications | |
| CN114830079A (en) | Efficient data processing for identifying information and reformatting data files and applications thereof | |
| CN103871010A (en) | Method, device and medical information system for prompting medication safety | |
| CN111046085B (en) | Data tracing processing method and device, medium and equipment | |
| CN113380414B (en) | Data acquisition method and system based on big data | |
| CN114168544B (en) | Clinical trial data processing method, device, computer equipment and storage medium | |
| CN116095110A (en) | Medical information safety management system and method based on blockchain technology | |
| Aijing et al. | Design of the hospital integrated information management system based on cloud platform | |
| CN107391936A (en) | A kind of ophthalmology image based on distributed website integrates and dissemination method | |
| CN112835489A (en) | Service data processing method, device, storage medium and equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 40014885 Country of ref document: HK |
|
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |