CN110597946A - Case storage method, device, equipment and storage medium - Google Patents
Case storage method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN110597946A CN110597946A CN201910853432.XA CN201910853432A CN110597946A CN 110597946 A CN110597946 A CN 110597946A CN 201910853432 A CN201910853432 A CN 201910853432A CN 110597946 A CN110597946 A CN 110597946A
- Authority
- CN
- China
- Prior art keywords
- case
- cases
- fault
- characteristic
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims description 62
- 230000008439 repair process Effects 0.000 claims abstract description 60
- 238000004590 computer program Methods 0.000 claims description 10
- 238000004422 calculation algorithm Methods 0.000 claims description 7
- 238000007635 classification algorithm Methods 0.000 claims description 7
- 238000012795 verification Methods 0.000 claims description 6
- 238000004806 packaging method and process Methods 0.000 claims description 5
- 238000007637 random forest analysis Methods 0.000 claims description 3
- 238000012706 support-vector machine Methods 0.000 claims description 3
- 201000010099 disease Diseases 0.000 description 27
- 208000037265 diseases, disorders, signs and symptoms Diseases 0.000 description 27
- 238000010586 diagram Methods 0.000 description 15
- 238000004891 communication Methods 0.000 description 11
- 238000012545 processing Methods 0.000 description 10
- 238000004458 analytical method Methods 0.000 description 8
- 208000024891 symptom Diseases 0.000 description 8
- 208000024780 Urticaria Diseases 0.000 description 6
- 239000003814 drug Substances 0.000 description 6
- 208000019622 heart disease Diseases 0.000 description 6
- 230000000694 effects Effects 0.000 description 5
- 238000012856 packing Methods 0.000 description 5
- 229940079593 drug Drugs 0.000 description 4
- 206010012601 diabetes mellitus Diseases 0.000 description 3
- 241001465754 Metazoa Species 0.000 description 2
- 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
- 238000009533 lab test Methods 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 230000001052 transient effect Effects 0.000 description 2
- 239000013598 vector Substances 0.000 description 2
- 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
- 238000005516 engineering process Methods 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 238000000605 extraction Methods 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
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000009877 rendering Methods 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
In the scheme, the block chain network is utilized to realize the whole network sharing of the fault case, and simultaneously, the safety and the non-tamper property of the fault case are ensured. On the basis, any block chain link point can classify fault cases in the current block chain network according to fault types, so that a plurality of characteristic cases can be obtained, the obtained characteristic cases can comprehensively record fault information and corresponding repair information, and comprehensive recording of the characteristic cases can be realized. Further, determining the characteristic key characters in the characteristic cases as retrieval indexes, and updating a retrieval index base according to the retrieval indexes; and storing the updated retrieval index library and the plurality of feature cases into the current blockchain network, so that all blockchain nodes accessed into the current blockchain network can share the feature cases, and related feature cases can be retrieved through the retrieval index if necessary.
Description
The application is a divisional application which is filed in 2019, 08 and 05 and has the application number of 201910717999.4 and the invention name of 'case storage method, device, equipment and storage medium'.
Technical Field
The present application relates to the field of blockchain technologies, and in particular, to a method, an apparatus, a device, and a storage medium for storing cases.
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 classic case, and when a 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 history failure and other information of a certain object are also lack of record, so that the authenticity and comprehensiveness of case record are reduced, and the reference value of the case is also reduced.
Disclosure of Invention
In view of the above, an object of the present application is to provide a method, an apparatus, a device and a storage medium for storing cases, so as to obtain comprehensive and real cases and achieve sharing of the cases. 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 block chain network; the fault cases include: at least one fault information and corresponding repair information of a current object;
classifying the plurality of fault cases according to fault types to obtain a plurality of characteristic cases; each characteristic case records fault information and corresponding repair information of at least one object;
determining the characteristic key characters in the characteristic cases as retrieval indexes, and updating a retrieval index base according to the retrieval indexes;
storing the updated retrieval index base and the plurality of 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 fault information and the corresponding repair information corresponding to the feature case do not exist in the current blockchain network, creating the corresponding feature case in the current blockchain network, and adding the new fault information and the corresponding repair information to the newly created feature case.
In another aspect, the present application further provides a case storage apparatus, applied to any blockchain node, including:
the acquisition module is used for acquiring fault cases of a plurality of objects in the current block chain network; the fault cases include: at least one fault information and corresponding repair information of a current object;
the classification module is used for classifying the fault cases according to fault types to obtain a plurality of characteristic cases; each characteristic 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 characteristic cases as retrieval indexes and updating a retrieval index base according to the retrieval indexes;
a storage module, configured to store the updated search index database and the plurality of 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;
and the creating module is used for creating a corresponding characteristic case in the current blockchain network and adding the new fault information and the corresponding repair information to the newly created characteristic case if the new fault information and the corresponding characteristic case corresponding to the repair information do not exist in the current blockchain network.
In yet another aspect, the present application further provides an electronic device comprising a processor and a memory; wherein the memory is used for storing a computer program which is loaded and executed by the processor to implement the case storing method disclosed in the foregoing.
In yet another aspect, the present application further provides a storage medium having stored therein computer-executable instructions, which when loaded and executed by a processor, implement the case storage method disclosed above.
The present application is applicable 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 safety, the blockchain network stores the fault cases, so that the whole network sharing of the fault cases can be realized, and the safety and the non-tamper property of the fault cases are ensured. On the basis, any block chain link point can also classify fault cases in the current block chain network according to 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 object or a plurality of objects. Further, determining the characteristic key characters in the characteristic cases as retrieval indexes, and updating a retrieval index base according to the retrieval indexes; and storing the updated retrieval index library and the plurality of feature cases into the current blockchain network, so that all blockchain nodes accessed into the current blockchain network can share the feature cases. When a certain object fails, the related characteristic cases can be retrieved through the retrieval index, so that a reliable, real and comprehensive reference case is provided for repairing the current failure. Meanwhile, after the characteristic cases are obtained, when new fault information and corresponding repair information of a target object sent by a user are received and the characteristic cases corresponding to the new fault information and the corresponding repair information do not exist in the current blockchain network, the corresponding characteristic cases are created in the current blockchain network, and the new fault information and the corresponding repair information are added to the newly created characteristic cases, so that the obtaining efficiency and timeliness of the characteristic cases are improved.
Accordingly, the case storage device, the equipment and the storage medium provided by the application also 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 needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a schematic diagram of a case storage system architecture provided herein;
fig. 2 is a flowchart of a first case storage method provided in the present application;
fig. 3 is a flowchart of a second case storage method provided in the present application;
fig. 4 is a flowchart of a third case storage method provided in 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 herein;
FIG. 7 is a schematic illustration of a natural human case record provided by the present application;
fig. 8 is a schematic view of a first characteristic case record provided herein;
fig. 9 is a schematic view of a second characteristic case record provided by the present application;
FIG. 10 is a diagram illustrating a search result provided by the present application;
FIG. 11 is a schematic view of a case storage device provided herein;
FIG. 12 is a block diagram of a server provided by the present application;
fig. 13 is a structural diagram of a terminal according to the present application.
Detailed Description
At present, only individual cases are recorded in the existing recording mode, and information such as historical faults of a certain object is also lost, so that the authenticity and comprehensiveness of case recording are reduced, and the reference value of the cases is reduced. In view of the above problems, the present application provides a case storage scheme, by which a comprehensive and real case can be obtained and sharing of the case can be achieved.
For ease of understanding, the following describes a system architecture to which the technical solution disclosed in the present application is applied. Referring to fig. 1, a system architecture for the present application is shown.
As shown in fig. 1, the case storage system architecture disclosed herein 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 the fault case to be uploaded on the human-computer interaction interface. After acquiring 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 block link point. 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, and the like, in which the client is installed. The user terminal 11 may also be used to query the blockchain network 13 for stored failure cases.
In this 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. The server 12 obtains the fault case sent by the user terminal 11, and uploads the fault case to the corresponding block link point, and then the block link point can execute the case storage method provided by the application. It is understood that the server 12 in the present 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. After a fault case submitted by the server 12 is successfully uplinked on any blockchain node 130, the fault case is quickly transferred to other blockchain nodes 130 for storage within a second-level time period, and each blockchain node 130 shares the stored fault 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 block of the blockchain network 13.
The block identifier may refer to an identifier obtained after performing hash processing on a block header of a previous block, or may refer to a block height of a current block; the case storage records may include the failure cases and corresponding time stamps, etc.
It is 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 each blockchain link point in the blockchain network 13 may be determined according to the network status and the application requirement in the actual application process, and may be a wireless communication network, such as a mobile communication network or a WIFI network, or a wired communication network; either a wide area network or a local area network may be used as circumstances warrant. Of course, the user terminal 11 can also communicate directly with the blockchain network 13, so that the server 12 does not need to be provided, which can save computer resources.
Fig. 2 is a flowchart of a first case storage 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 block chain network; the failure cases include: at least one fault information and corresponding repair information for the current object.
In the current blockchain network, the fault case can be stored with the identification information of the object as a key. Wherein, the object can be: when the object is human, animal or plant, the failure case is natural human case, the failure is 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 a plant, or the like. If the object is a device, the fault information may include: the component that failed, and the cause of the failure; the identification information of the device may be a factory code of the device, etc.
If the object is a person, the case is stored by the identity information key of the person, so that the corresponding doctor seeing information, laboratory sheet information and the like of the same patient (namely, a natural person) can be uniformly stored in one case, and therefore, the case is enriched, the patient case is comprehensively recorded, and the patient and a doctor can conveniently inquire the case. Thereby providing convenience for obtaining comprehensive, real and reliable characteristic cases.
S202, 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.
In a specific implementation manner, the fault cases can be classified according to fault types by using a classification algorithm to obtain a plurality of feature cases, wherein the classification algorithm is a naive bayes algorithm, a random forest algorithm or a support vector machine. Of course, other classification algorithms may also be used for classification, such as: and (4) clustering algorithm.
If the failure cases are natural human cases, it can be understood that since there are many diseases suffered by one natural human, after classifying the failure cases according to the disease types, the diseases suffered by the same natural human may be classified into different characteristic cases. For example: the natural person A case records two kinds of disease information and treatment information of heart disease and diabetes, so that the disease information and treatment information about the heart disease recorded in the natural person A case are classified into heart disease characteristic cases during classification; disease information and treatment information about diabetes recorded in natural human a cases will be classified into diabetes characteristic cases. Since the fault cases also record laboratory test report information and the like, the laboratory test report information and the like are classified into corresponding characteristic cases when the diseases are classified. The treatment information may include information of orally taken, externally applied and/or injected medicines, corresponding medication effect, and the like. Of course, the identity information of natural people, the location and time of the patient can be recorded in the characteristic case.
If a plurality of disease information and treatment information relating to a heart disease are recorded in a fault case, each recording can be regarded as a treatment recording. When the classification is carried out, the treatment time of the treatment records is recorded respectively, and the treatment records are regarded as the related information of the current natural human suffering from the heart disease. That is, these treatment records are collectively considered as the current case of a natural person suffering from heart disease.
S203, determining the characteristic key characters in the plurality of characteristic cases as retrieval indexes, and updating a retrieval index base according to the retrieval indexes.
And S204, storing the updated retrieval index library and the plurality of characteristic cases to the current blockchain network.
In this embodiment, before storing the updated search index database and the plurality of feature cases to the current blockchain network, the method further includes: adding fault information with the same type of repair information to the same fault group for any one characteristic case; any one of the feature cases includes a plurality of failure groups.
In each characteristic case, a plurality of fault groups are provided, and fault information with the same type of repair information is recorded in each fault group. Still taking the characteristic cases obtained after natural human cases are classified as an example, suppose that there are 2 fault groups (namely case groups) in the characteristic cases of urticaria, the first fault group is used for recording information such as diseased symptoms and treatment effects of taking a medicine; the second failure group is used to record information on disease symptoms, treatment effects, etc. of taking another drug. Therefore, the treatment effect of different medicines and different treatment modes on the same disease can be clearly seen from the characteristic cases; it can also be quickly seen from the characteristic cases that there are several treatment means and ways for the current disease.
To facilitate retrieval and querying, a corresponding retrieval index may be constructed for the feature cases. Wherein, the retrieval index can be any feature key character in the feature case, and the feature key character is as follows: name of failure, location, cause of failure, etc. If the failure case is a natural human case, the feature key character can be a disease name or abbreviation, such as: urticaria; or characteristic disease symptoms, etc., such as: wind mass, the characteristic symptom of wind mass in urticaria.
And storing the updated retrieval index base and the plurality of feature cases to the current block chain network, namely sharing the retrieval index base and the feature cases to the current block chain network. Thus, any blockchain node can query the relevant characteristic case by using the retrieval index.
It should be noted that other implementation steps in this embodiment are the same as or similar to those in the above embodiment, and therefore, the description of this 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 safety, the blockchain network stores the fault cases, so that the whole network sharing of the fault cases can be realized, and the safety and the non-tamper property of the fault cases are ensured. On the basis, any block chain link point can also classify fault cases in the current block chain network according to 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 object or a plurality of objects. Further, determining the characteristic key characters in the characteristic cases as retrieval indexes, and updating a retrieval index base according to the retrieval indexes; and storing the updated retrieval index library and the plurality of feature cases into the current blockchain network, so that all blockchain nodes accessed into the current blockchain network can share the feature cases. When a certain object fails, the related characteristic cases can be retrieved through the retrieval 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 storage 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 block chain network; the failure cases include: at least one fault information and corresponding repair information for the current object.
S302, 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.
S303, determining the characteristic key characters in the plurality of characteristic cases as retrieval indexes, and updating a retrieval index base according to the retrieval indexes.
And S304, storing the updated retrieval index library and the plurality of characteristic cases to the current blockchain network.
S305, receiving a retrieval request sent by a user.
It will be appreciated 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 or information input by a user.
S306, extracting the target retrieval index in the retrieval request.
And S307, respectively determining the similarity between the target retrieval index and the plurality of characteristic cases in the current block chain network.
The similarity can be determined by adopting calculation modes such as semantic similarity and cosine similarity. 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 need to be converted into vectors, and then the similarity between the two vectors is calculated.
And S308, determining the characteristic case corresponding to the maximum similarity as a retrieval result and returning.
It can be understood that, determining the similarity between the target retrieval index and the plurality of feature cases respectively requires calculating the similarity between the target retrieval index and each feature case respectively, so as to obtain the similarity corresponding to each feature case. And determining the characteristic case corresponding to the maximum similarity as the retrieval result of the current retrieval request and returning.
In one embodiment, for any one of the feature cases, determining the similarity between the target retrieval index and the current feature case includes: respectively determining the similarity between 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 plurality of sub-similarity to obtain the similarity between the target retrieval index and the current characteristic case.
Natural human cases are still taken as an example. For example: the key indexes in the urticaria characteristic case are wheal, skin itch and blood convention, which respectively correspond to the weights of 40%, 40% and 20%. Calculating the similarity of the target retrieval index and the wind cluster so as to obtain a first sub-similarity A; 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 of the target retrieval index and the blood routine, thereby obtaining a third sub-similarity C; then the weighted summary of these three sub-similarities is: w is a × 40% + B × 40% + C × 20%, which is the similarity between the target search index and the urticaria feature case.
In a specific embodiment, determining and returning the feature case corresponding to the maximum similarity as a search result includes: arranging the plurality of characteristic cases in a descending order according to the similarity to obtain a characteristic case sequence; and determining the characteristic case sequence as a retrieval result and returning.
The similarity between the target retrieval index and each feature case can be calculated through the method, and then the feature cases can be arranged in a descending order according to the similarity, so that a feature case sequence can be obtained; and then the characteristic case sequence can be used as a retrieval result and returned. If the characteristic case sequence contains more characteristic cases, the first N characteristic cases can be selected as the retrieval result and returned. Of course, the feature cases may be further arranged in an ascending order according to the similarity, and then the last N of the feature case sequences may be selected as the search result and returned. Of course, the retrieval result can also be presented at the client for the user to refer to.
It should be noted that, in order to avoid the user to refer to the feature case maliciously, the permission of the user to submit the retrieval request through the client may be limited, for example: only if the correct doctor's certificate of authority code is entered is the search request allowed to be submitted. Of course, it is also possible to avoid malicious querying and retrieval of feature cases using cryptographic techniques.
It should be noted that other implementation steps in this embodiment are the same as or similar to those in the above embodiment, and therefore, the description of this embodiment is omitted here.
After the feature cases are stored in the blockchain network, when a retrieval request is received, the method disclosed by the embodiment extracts the target retrieval index in the retrieval request, and further determines the similarity between the target retrieval index and the plurality of feature cases respectively, so that the retrieval result corresponding to the retrieval request is determined according to the similarity, returned and displayed. Therefore, the user can immediately inquire the relevant case, thereby providing a reliable and comprehensive basis for repairing the current fault.
Fig. 4 is a flowchart of a third case storage 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 block link point at different times, so that the block link point may store the failure information and the corresponding repair information in the entire network synchronously.
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.
And S403, establishing an incidence relation between the fault case and the ID, and storing the incidence relation, the fault case and the ID to the current blockchain network.
In this embodiment, storing the association relationship, the fault case, and the ID to the current blockchain network includes: broadcasting the association relation, the fault case and the ID in the current block chain network so that other block chain link points in the current block chain network verify the association relation, the fault case and the ID; and if the verification is passed, packaging the incidence relation, the fault case and the ID into a second block, and broadcasting a packaged message of the second block in the current blockchain network.
Of course, the execution time for classifying the fault case may also be set in the current blockchain network, for example: an execution cycle is set to execute the sorting operation every 10 minutes or every 1 hour. That is, each blockchain node collects new fault information and corresponding repair information and synchronizes to the whole network, and when a classification execution time point is reached, the fault information and the corresponding repair information collected from the last classification execution time point to the current classification execution time point are classified. After new characteristic cases are obtained through classification, if the new characteristic cases exist in the block chain network, the new characteristic cases and the old characteristic cases are combined and 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 block chain network; the failure cases include: at least one fault information and corresponding repair information for 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.
And S406, determining the characteristic key characters in the plurality of characteristic cases as retrieval indexes.
S407, judging whether a retrieval index exists in the retrieval index library or not; if yes, go to S408; if not, S409 is executed.
S408, determining the original retrieval index library as an updated retrieval index library;
and S409, adding the retrieval index to the retrieval index library, obtaining an updated retrieval index library, and executing S410.
And S410, broadcasting the updated retrieval index base and the plurality of feature cases in the current block chain network so that other block chain nodes in the current block chain network verify the updated retrieval index base and the plurality of feature cases.
S411, if the verification is passed, packaging the updated retrieval index base and the plurality of feature cases into a first block, and broadcasting a packaging message of the first block in the current block chain network.
S412, receiving new fault information and corresponding repair information of the target object sent by the user.
And S413, adding the new fault information and the corresponding repair information into the corresponding characteristic case according to the fault type of the new fault information.
In this embodiment, after the plurality of feature cases are obtained by classification in the blockchain network and the sharing operation is completed, if the current blockchain network receives new failure information and corresponding repair information again, the new failure information and the corresponding repair information may be directly added to the corresponding feature cases. If the new fault information and the corresponding characteristic case corresponding to the repair information do 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 the corresponding repair information are added to the newly created characteristic case.
It should be noted that other implementation steps in this embodiment are the same as or similar to those in the above embodiment, and therefore, the description of this embodiment is omitted here.
Therefore, after the characteristic cases are obtained through classification, when the fault cases are collected again, the newly collected fault cases can be classified, so that the fault cases in the block chain network can be classified in time, and the characteristic cases are obtained for the query and reference of related personnel.
The case storage method provided by the application is described below by a specific application scenario example. Referring to fig. 5, fig. 5 is a block chain network diagram according to an embodiment of the present disclosure. In fig. 5, any one of the medical institutions may be used as a block link point to access a block link network, each medical institution may upload a natural person case to its corresponding block link point, and the block link point may share the uploaded natural person case with other nodes, so that the entire network sharing storage of the natural person case may be implemented.
Meanwhile, the block link points corresponding to any one medical institution can also be used as analysis and summary nodes. The analysis and summary 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 current disease of a patient can be comprehensively recorded by the obtained characteristic cases, and the comprehensive recording of the characteristic cases can be realized. Further, determining the characteristic key characters in the characteristic cases as retrieval indexes, and updating a retrieval index base according to the retrieval indexes; and storing the updated retrieval index library and the plurality of feature cases into the current blockchain network, so that all medical institutions accessing the current blockchain network can share the feature cases, and can retrieve the related feature cases through the retrieval index if necessary.
In order to reduce the data processing amount of each blockchain node, an analysis summary node can be arranged in the blockchain network. The analysis summary node may be provided in plurality, i.e., the analysis node 1 and the analysis node 2 in fig. 5. This analysis summary node is only used to execute the case storage schema provided by the present application. That is, the block link points corresponding to each medical institution are used for collecting and sharing natural human cases, and the analysis summary 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, where the fourth case storage method is provided in combination with the blockchain network shown in fig. 5. The medical case storage method shown in fig. 6 may include the steps of:
s601, the target block chain node acquires a natural human case in the current block chain network.
In the present embodiment, the failure case is a natural human case. Before the target blockchain node acquires the natural human case in the current blockchain network, the method further comprises the following steps: when the current block chain network collects all the natural human cases, the link points of all the blocks in the current block chain network respectively collect the natural human cases, and simultaneously pack the collected natural human cases 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 by the embodiment of the present application. The time points in fig. 7 are the time points of each visit of the patient. The natural person ID in fig. 7 may be patient identification 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 disease information of the natural person and the corresponding treatment information. The type of disease corresponds to the type of failure mentioned above.
S603, determining the feature key characters in the feature cases as retrieval indexes by the target block chain node, and updating a retrieval index base according to the retrieval indexes.
Wherein, the characteristic key characters can be names of diseases, symptoms of diseases and the like.
Specifically, please refer to fig. 8-9 for storing and displaying the feature cases, fig. 8 is a schematic diagram of a first feature case record provided by an embodiment of the present application, and fig. 9 is a schematic diagram of a second feature case record provided by the 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 number of cases, that is, the number of cases with the same treatment information, and reference may be made to the above-mentioned case groups. The characteristic cases in fig. 8 and 9 are disease cases.
S604, broadcasting the updated retrieval index base and the plurality of characteristic cases to other block chain nodes by the target block chain node.
And the target block chain node and other block chain nodes jointly form the current block chain network.
And S605, commonly identifying the updated retrieval index base and the plurality of characteristic cases by the other block chain link points.
And S606, if the consensus passes, other block chain nodes broadcast the consensus passing message in the whole network.
The updated search index library and the plurality of feature cases can be commonly identified by a common consensus method, such as: common methods such as PBFT, POW, POS, and DPOS.
S607, the target block chain node packs the updated index base and the plurality of feature cases into blocks.
S608, the target block chain node broadcasts the block generation message in the whole network.
It should be noted that, implementation steps in this embodiment are the same as or similar to those in the above embodiments, and reference may be made to any of the above embodiments specifically, so that details of this embodiment are not repeated herein.
If the search index is the disease symptoms and the examination results (such as white blood cell count), the search results obtained when querying the feature cases in the blockchain network by using the symptoms and the examination results are shown in fig. 10. Fig. 10 is a schematic diagram of a search result according to an embodiment of the present application. In fig. 10, all similar cases are sorted in descending order according to the magnitude 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 characteristic case.
It can be seen that in the embodiment, any one medical institution accesses the blockchain network as a blockchain link point and uploads a natural human case. The natural person cases are stored in the block chain network by using the natural person keys, and then the disease types are used as keys to classify the natural person cases, so that the unified storage of the patient cases of different medical institutions is realized, and convenience is provided for the retrieval and query of the characteristic cases.
Referring to fig. 11, fig. 11 is a schematic diagram of a case storage device according to an embodiment of the present application, applied to any blockchain node, including:
an obtaining module 1101, configured to obtain fault cases of multiple objects in a current block chain network; the failure cases include: at least one fault information and corresponding repair information of a current object;
the classification module 1102 is configured to classify the multiple fault cases according to fault types to obtain multiple feature cases; each characteristic case records fault information and corresponding repair information of at least one object;
an updating module 1103, configured to determine the feature key characters in the multiple feature cases as a retrieval index, and update a retrieval index library according to the retrieval index;
a storage module 1104, configured to store the updated search index database and the plurality of feature cases in the current blockchain network.
In a specific embodiment, the method further comprises the following steps:
the first receiving module is used for receiving a retrieval 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 characteristic cases corresponding to the target retrieval index in the current block chain network and returning a retrieval result.
In one embodiment, the retrieval module comprises:
the first determining unit is used for respectively determining the similarity between the target retrieval index and a plurality of characteristic cases in the current block chain network;
and the second determining unit is used for determining the characteristic 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:
respectively determining the similarity between the target retrieval index and each feature key character in the current feature case aiming at any feature case to obtain a plurality of sub-similarities; and weighting and summarizing the plurality of sub-similarity to obtain the similarity between the target retrieval index and the current characteristic case.
In a specific embodiment, the second determining unit is specifically configured to:
arranging the plurality of characteristic cases in a descending order according to the similarity to obtain a characteristic case sequence; and determining the characteristic case sequence as a retrieval result and returning.
In a specific embodiment, the method further comprises the following steps:
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 characteristic case; any one of the feature cases includes a plurality of failure groups.
In one embodiment, the update module includes:
the judging unit is used for judging whether a retrieval index exists in the retrieval index library or not;
and the updating unit is used for adding the retrieval index to the retrieval index base to obtain an updated retrieval index base if the retrieval index does not exist in the retrieval index base.
In one embodiment, a memory module comprises:
the first broadcasting unit is used for broadcasting the updated retrieval index base and the plurality of characteristic cases in the current block chain network so as to verify the updated retrieval index base and the plurality of characteristic cases by other block chain nodes in the current block chain network;
and the first packing unit is used for packing the updated retrieval index base 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 blockchain network.
In a specific embodiment, the method further comprises the following steps:
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 an incidence relation between the fault case and the ID and storing the incidence relation, the fault case and the ID to the current blockchain network.
In one embodiment, the execution module comprises:
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 verify the association relation, the fault case and the ID by other block chain link points in the current block chain network;
and the second packing unit is used for packing the incidence relation, the fault case and the ID into a second block if the verification is passed, and broadcasting a packed message of the second block in the current blockchain network.
In a specific embodiment, the method further comprises the following steps:
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 case according to the fault type of the new fault information.
In a specific 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 characteristic cases, wherein the classification algorithm is a naive Bayes algorithm, a random forest algorithm or a support vector machine.
For more specific working processes of each module and unit in this embodiment, reference may be made to corresponding contents disclosed in the foregoing embodiments, and details are not described here again.
As can be seen, the present embodiment provides a case storage device, including: 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 block chain network; the failure cases include: at least one fault information and corresponding repair information of a current object; then, the classification module classifies the plurality of fault cases according to fault types to obtain a plurality of characteristic cases; each characteristic case records fault information and corresponding repair information of at least one object; the updating module determines the characteristic key characters in the characteristic cases as retrieval indexes and updates a retrieval index base according to the retrieval indexes; and finally, the storage module stores the updated retrieval index base and the plurality of characteristic cases to the current blockchain network. Thus, all modules are in work and cooperation and each takes its own role, so that real and comprehensive characteristic cases can be obtained, and 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 block diagram of an electronic device shown in the present embodiment, and the contents in the diagrams should not be construed as any limitation to the scope of use of the present application.
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 used for storing 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 foregoing embodiments.
In this embodiment, the power supply 53 is used to provide 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 followed by the communication interface is any communication protocol applicable to the technical solution of the present application, and is not specifically limited herein; the input/output interface 55 is configured to obtain external input data or output data to the outside, and a specific interface type thereof may be selected according to specific application requirements, which is not specifically limited herein.
The memory 52 may be a read-only memory, a random access memory, a magnetic disk, an optical disk, or the like as a carrier for storing resources, the resources stored thereon include an operating system 521, a computer program 522, data 523, and the like, and the storage manner may be a transient storage or a permanent storage.
The operating system 521 is used for managing and controlling hardware devices and computer programs 522 on the Server 50 to realize the operation and processing of the processor 51 on the data 523 in the memory 52, and may be a Windows Server, Netware, Unix, Linux, or the like. The computer program 522 may further include 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 method disclosed in any of the foregoing 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 disclosure, where the terminal 60 may specifically include, but is not limited to, a smart phone, a tablet computer, a notebook computer, or a desktop computer.
In general, the terminal 60 in the present embodiment includes: a processor 61 and a memory 62.
The processor 61 may include one or more processing cores, such as a 4-core processor, an 8-core processor, and the like. The processor 61 may be implemented in at least one hardware form of a DSP (Digital Signal Processing), an FPGA (Field-Programmable Gate Array), and a PLA (Programmable Logic Array). The processor 61 may also include a main processor and a coprocessor, where the main processor is a processor for processing data in an awake state, and is also called a Central Processing Unit (CPU); a coprocessor is a low power processor for processing data in a 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 required to be displayed on the display screen. In some embodiments, the processor 61 may further 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. The 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, wherein after being loaded and executed by the processor 61, the computer program can realize relevant steps in the case storage method executed by the terminal side disclosed in any one of the foregoing embodiments. In addition, the resources stored in the memory 62 may also include an operating system 622 and data 623, etc., which may be stored in a transient or persistent manner. 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 also 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 configuration shown in fig. 13 is not intended to be limiting of terminal 60 and may include more or fewer components than those shown.
Further, an embodiment of the present application further discloses a storage medium, where the storage medium stores computer-executable instructions, and the computer-executable instructions are loaded and executed by a processor to implement the case storage method disclosed in any of the foregoing embodiments. For the specific steps of the method, reference may be made to the corresponding contents disclosed in the foregoing embodiments, which are not described herein again.
It should be noted that the above-mentioned embodiments are only preferred embodiments of the present application, and are not intended to limit the present application, and any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present application should be included in the protection scope of the present application.
The embodiments are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same or similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.
The principle and the implementation of the present application are explained herein by applying specific examples, and the above description of the embodiments is only used to help understand the method and the core idea of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.
Claims (15)
1. A case storage method is applied to any blockchain node and comprises the following steps:
acquiring fault cases of a plurality of objects in a current block chain network; the fault cases include: at least one fault information and corresponding repair information of a current object;
classifying the plurality of fault cases according to fault types to obtain a plurality of characteristic cases; each characteristic case records fault information and corresponding repair information of at least one object;
determining the characteristic key characters in the characteristic cases as retrieval indexes, and updating a retrieval index base according to the retrieval indexes;
storing the updated retrieval index base and the plurality of 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 fault information and the corresponding repair information corresponding to the feature case do not exist in the current blockchain network, creating the corresponding feature case in the current blockchain network, and adding the new fault information and the corresponding repair information to the newly created feature case.
2. The case storage method of claim 1, wherein after storing the updated search index repository and the plurality of feature cases to the current blockchain network, further comprising:
receiving a retrieval request sent by a user;
extracting a target retrieval index in the retrieval request;
and searching the characteristic case corresponding to the target search index in the current block chain network, and returning a search result.
3. The case storage method of claim 2, wherein the retrieving the feature case corresponding to the target retrieval index in the current blockchain network and returning a retrieval result comprises:
respectively determining similarity of the target retrieval index and a plurality of the feature cases in the current block chain network;
and determining the characteristic 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 retrieval index to the current feature case for any feature case comprises:
respectively determining the similarity between 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 characteristic case.
5. The case storage method according to claim 3, wherein the determining and returning the feature case corresponding to the maximum similarity as the search result includes:
arranging the plurality of characteristic cases in a descending order according to the similarity to obtain a characteristic case sequence;
and determining the characteristic case sequence as the retrieval result and returning.
6. The case storage method according to any one of claims 1 to 5, wherein before storing the updated search index database and the plurality of feature cases into the current blockchain network, further comprising:
adding fault information with the same type of repair information to the same fault group for any one characteristic case; any one of the feature cases includes a plurality of failure groups.
7. The case storage method of claim 1, wherein said updating a search index repository based on said search index comprises:
judging whether the retrieval index exists in a retrieval index library or not;
and if not, adding the retrieval index to the retrieval index library to obtain the updated retrieval index library.
8. The case storage method of claim 1, wherein storing the updated search index repository and the plurality of feature cases to the current blockchain network comprises:
broadcasting the updated search index base and the plurality of feature cases in the current block chain network so that other block link points in the current block chain network verify the updated search index base and the plurality of feature cases;
and if the verification is passed, packaging the updated retrieval index base and the plurality of feature cases into a first block, and broadcasting a packaged message of the first block in the current block chain network.
9. Case storage method according to any of claims 1 to 5, wherein before the obtaining of the fault cases of the plurality of objects in the current blockchain network, further 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 objects as the ID of the fault case;
and establishing an incidence relation between the fault case and the ID, and storing the incidence relation, the fault case and the ID to the current blockchain network.
10. The case storage method of claim 9, wherein the storing the association, the failed case, and the ID to the current blockchain network comprises:
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 incidence relation, the fault case and the ID into a second block, and broadcasting a packaged message of the second block in the current block chain network.
11. The case storage method according to claim 9, after receiving new failure information and corresponding repair information of the target object sent by the user, further comprising:
and if the new fault information and the corresponding characteristic case corresponding to the repair information exist in the current block chain network, adding the corresponding characteristic case to the new fault information and the corresponding repair information according to the fault type of the new fault information.
12. The case storage method according to claim 1, wherein the classifying the fault cases according to fault types to obtain a plurality of feature cases comprises:
and classifying the fault cases according to fault types by using a classification algorithm to obtain a plurality of characteristic cases, wherein the classification algorithm is a naive Bayes algorithm, a random forest algorithm or a support vector machine.
13. A case storage apparatus, applied to any blockchain node, comprising:
the acquisition module is used for acquiring fault cases of a plurality of objects in the current block chain network; the fault cases include: at least one fault information and corresponding repair information of a current object;
the classification module is used for classifying the fault cases according to fault types to obtain a plurality of characteristic cases; each characteristic 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 characteristic cases as retrieval indexes and updating a retrieval index base according to the retrieval indexes;
a storage module, configured to store the updated search index database and the plurality of 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;
and the creating module is used for creating a corresponding characteristic case in the current blockchain network and adding the new fault information and the corresponding repair information to the newly created characteristic case if the new fault information and the corresponding characteristic case corresponding to the repair information do not exist in the current blockchain network.
14. An electronic device, comprising a processor and a memory; wherein the memory is for storing a computer program which is loaded and executed by the processor to implement the case storage method of any of claims 1 to 12.
15. A storage medium having stored thereon computer-executable instructions which, when loaded and executed by a processor, implement the case storage method of any one of claims 1 to 12.
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 true CN110597946A (en) | 2019-12-20 |
| CN110597946B CN110597946B (en) | 2024-04-23 |
Family
ID=68484947
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910853432.XA Active CN110597946B (en) | 2019-08-05 | 2019-08-05 | Case storage method, device, equipment and storage medium |
| CN201910717999.4A Active CN110457425B (en) | 2019-08-05 | 2019-08-05 | Case storage method, device, equipment and storage medium |
Family Applications After (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) | CN110597946B (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111275349A (en) * | 2020-02-07 | 2020-06-12 | 武汉科技大学 | Remanufacturing process planning method based on block chain and instance reasoning |
| CN112085380A (en) * | 2020-09-07 | 2020-12-15 | 杭州叙简科技股份有限公司 | Safety production accident case management method based on block chain |
| CN113139709A (en) * | 2020-12-31 | 2021-07-20 | 上海明品医学数据科技有限公司 | Evaluation system and evaluation method for medical information |
| CN113806092A (en) * | 2021-09-18 | 2021-12-17 | 济南浪潮数据技术有限公司 | Storage device management method, system, device and medium |
Families Citing this family (3)
| 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 |
| CN112989255B (en) * | 2021-04-15 | 2021-08-03 | 中国电子信息产业集团有限公司第六研究所 | Identification analysis system |
| CN113435307B (en) * | 2021-06-23 | 2024-06-25 | 国网天津市电力公司城东供电分公司 | Operation and maintenance method, system and storage medium based on visual recognition 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 CN201910853432.XA patent/CN110597946B/en active Active
- 2019-08-05 CN CN201910717999.4A patent/CN110457425B/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 |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111275349A (en) * | 2020-02-07 | 2020-06-12 | 武汉科技大学 | Remanufacturing process planning method based on block chain and instance reasoning |
| CN112085380A (en) * | 2020-09-07 | 2020-12-15 | 杭州叙简科技股份有限公司 | Safety production accident case management method based on block chain |
| 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 |
| CN113806092A (en) * | 2021-09-18 | 2021-12-17 | 济南浪潮数据技术有限公司 | Storage device management method, system, device and medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110457425B (en) | 2024-05-03 |
| CN110457425A (en) | 2019-11-15 |
| CN110597946B (en) | 2024-04-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110597946B (en) | Case storage method, device, equipment and storage medium | |
| CN111258989B (en) | Database migration evaluation method and device, storage medium and computer equipment | |
| US20220309053A1 (en) | Method and apparatus of auditing log, electronic device, and medium | |
| CN112800095B (en) | Data processing method, device, equipment and storage medium | |
| US9798762B2 (en) | Real time big data master data management | |
| US20190243912A1 (en) | Rapid design, development, and reuse of blockchain environment and smart contracts | |
| CN113257383B (en) | Matching information determination method, display method, device, equipment and storage medium | |
| CN104050223A (en) | Pivot facets for text mining and search | |
| CN112529100B (en) | Training method and device for multi-classification model, electronic equipment and storage medium | |
| CN108710644A (en) | One kind is about government affairs big data processing method | |
| JP2020533666A (en) | Context-aware diff algorithm for genomic files | |
| CN106933859A (en) | The moving method and device of a kind of medical data | |
| US20240220976A1 (en) | Method and system for communication between blockchains on heterogeneous blockchain networks | |
| CN110618999A (en) | Data query method and device, computer storage medium and electronic equipment | |
| CN109684172A (en) | Log method for pushing, system, equipment and storage medium based on access frequency | |
| CN116095110A (en) | Medical information safety management system and method based on blockchain technology | |
| CN114168544B (en) | Clinical trial data processing method, device, computer equipment and storage medium | |
| EP3899776A1 (en) | System and method for computerized synthesis of simulated health data | |
| CN113900955A (en) | Automatic testing method, device, equipment and storage medium | |
| CN111046085B (en) | Data tracing processing method and device, medium and equipment | |
| CN111933241A (en) | Medical data analysis method, medical data analysis device, electronic device, and storage medium | |
| CN116628088A (en) | Enterprise operation data management method, enterprise operation data management device, computer equipment and storage medium | |
| US20200243172A1 (en) | Cognitive care plan recommendation system | |
| CN113380414B (en) | Data acquisition method and system based on big data | |
| CN113849520B (en) | Intelligent recognition method and device for abnormal SQL, electronic equipment and storage medium |
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 |