Method, system, device and product for realizing CDA standardized shared document

Abstract

The invention discloses a method, system, device and product for realizing a CDA standardized shared document, and belongs to the technical field of shared document processing, and the method comprises the following steps: obtaining an XSD architecture, a CDA data set standard and a value domain code, and carrying out preprocessing operation on the XSD architecture, the CDA data set standard and the value domain code to obtain a shared document standard class; obtaining business data of different patients in the database, and inputting the business data into the shared document standard class to obtain a shared document class matched with the patient; and serializing the shared document class matched with the patient to generate a CDA standardized shared document. According to the method, the XSD architecture, the CDA data set standard and the value domain code are preprocessed, so that the input of the business data does not damage the internal architecture of the shared document and does not influence the generation and subsequent operation of the CDA standardized shared document, and meanwhile, the business data can be operated, so that the quality and the generation efficiency of the generated shared document are improved, and the user experience is improved. And sharing among team members is facilitated.

Description

Technical Field

[0001] The present invention belongs to the technical field of shared document processing, and particularly relates to a method, system, device and product for realizing CDA standardized shared documents. Background Art

[0002] At present, with the rapid development of network technology, in order to facilitate different members to edit the same document, shared documents are often used for operation. As a medium for transmitting data, shared documents play a very important role in data sharing and application, and can improve the collaborative efficiency of team members. A shared document refers to storing a document in a central location and sharing it with others through a network so that multiple people can access and edit these documents simultaneously. CDA (Clinical Document Architecture) is the national interconnection CDA standard, which is an electronic medical record document exchange format based on the HL7 standard formulated by the National Health Commission of China.

[0003] In the prior art, the common way to generate shared documents is to copy a shared document template and then fill the queried data into the corresponding positions in the template. However, the above method has the following deficiencies: (1) Since the shared document is in XML format, directly writing data into the template content is likely to damage the XML format, affecting the generation and parsing of the shared document; (2) Directly using the template generation method is not easy to control whether the data meets the standard requirements and the data is prone to omission, resulting in the lack of closed-loop for the data quality of the shared document and affecting data sharing; (3) Using the template method, it is impossible to split and merge shared documents, and the operation is relatively inconvenient.

[0004] Therefore, there is a need to provide a method, system, device and product for realizing CDA standardized shared documents to overcome the above technical problems. Summary of the Invention

[0005] The object of the present invention is to provide a method, system, device and product for realizing CDA standardized shared documents to solve the above problems existing in the prior art.

[0006] To achieve the above object, the present invention adopts the following technical solutions: In the first aspect, the present invention provides a method for realizing CDA standardized shared documents, including: Obtain an XSD schema, CDA dataset standards and value domain codes, and perform preprocessing operations on the XSD schema, CDA dataset standards and value domain codes to obtain a shared document standard class; Obtain the business data of different patients in the database, and input the business data into the shared document standard class to obtain a shared document class matching the patient; Serialize the shared document class that matches the patient to generate a CDA-standardized shared document.

[0007] In a possible design, the shared document standard class includes a shared document entity class, a shared document data class, and a first data class; obtain the XSD schema, the CDA dataset standard, and the value domain code, and perform preprocessing operations on the XSD schema, the CDA dataset standard, and the value domain code to obtain the shared document standard class, including: Obtain multiple XSD schemas, perform deserialization operations on the multiple XSD schemas to obtain multiple shared document entity classes; Obtain the value domain code, define the value domain code in an enumerated type to obtain the first data class; Obtain the CDA dataset standard, encapsulate the first data class and the CDA dataset standard into multiple shared document entity classes to obtain the shared document standard class.

[0008] In a possible design, input the business data into the shared document standard class, including: Calculate the integrity of the business data, and the expression for calculating the integrity of the business data is:

[0009] In the above formula, represents the integrity of the business data, represents the parameter value instantiated according to the business data of different patients, represents the total number of data elements in the preset standard dataset; Judge whether the integrity of the business data is greater than or equal to a preset threshold. If so, input the business data into the shared document standard class.

[0010] In a possible design, before obtaining the business data of different patients in the database and inputting the business data into the shared document standard class to obtain the shared document class that matches the patient, the method further includes: Receive the relationships of different categories of shared document classes preset, so as to process the business data based on the relationships of different categories of shared document classes and the shared document standard class to obtain different categories of shared document classes that match the patient.

[0011] In a possible design, the method further includes: parsing the shared documents generated by other institutions, including: Obtain the shared documents generated by other institutions, parse the shared documents generated by other institutions to obtain a parsing result, and the parsing result includes a parsing sub-result and the finally parsed shared document; Generate a parsing report according to the parsing sub-result; Add the finally parsed shared document to the pre-built database.

[0012] In a possible design, the shared documents produced by the other institution include multiple data sets; parsing the shared documents generated by the other institution to obtain a parsing result, the parsing result includes a parsing sub-result and the finally parsed shared document, including: Deserialize the shared documents generated by the other institution to generate a deserialization result, the deserialization result is either deserialization success or deserialization failure. If the deserialization result is deserialization failure, generate a deserialization error record; if the deserialization result is deserialization success, verify the deserialization result based on the XSD schema to generate an XSD verification result, the XSD verification result is either XSD verification success or XSD verification failure; If the XSD verification result is XSD verification failure, generate an XSD verification error record; if the XSD verification result is XSD verification success, judge the structure in the shared document according to the preset shared document structure standard to obtain a structure verification result, the structure verification result includes: structure verification success or structure verification failure; If the structure verification result is structure verification failure, generate a structure verification error record; when the structure verification result is structure verification success, perform data standardization verification on the instances in the shared document to obtain a verification result, the verification result is either verification success or verification failure; If the verification result is verification failure, generate a verification error record, and use the deserialization error record, XSD verification error record, structure verification error record and verification error record as the parsing sub-result; Count the number of all instances with successful verification in the data set of the verification result to obtain the first set number corresponding to the shared document. Determine the integrity of the shared document according to the first set number and the total number of data elements in the preset standard data set. Use the shared document with integrity greater than or equal to the preset threshold as the finally parsed shared document.

[0013] In a possible design, determine the integrity of the shared document according to the first set number and the total number of data elements in the preset standard data set. Among them, the expression for calculating the integrity of the shared document is:

[0014] In the above formula, represents the integrity of the shared document, represents the first set number; when is greater than or equal to the preset threshold, it means the shared document is complete.

[0015] In a possible design, the method further includes: merging any at least two shared documents, and the merging of any at least two shared documents includes: Receive any at least two shared documents, parse the at least two shared documents, and obtain at least two instantiated shared document classes; Compare the at least two instantiated shared document classes, merge the parts with different contents in the at least two instantiated shared document classes to form a new shared document instance class, and input the new shared document instance class into the database; Serialize the new shared document instance class to generate a CDA-standardized shared document.

[0016] In a second aspect, the present invention provides a system for implementing a CDA-standardized shared document, including: A preprocessing module for obtaining an XSD schema, a CDA dataset standard, and value domain codes, and performing preprocessing operations on the XSD schema, the CDA dataset standard, and the value domain codes to obtain a shared document standard class; A processing module communicatively connected to the preprocessing module for obtaining business data of different patients in the database, inputting the business data into the shared document standard class, and obtaining a shared document class matching the patient; A result generation module communicatively connected to the processing module for serializing the shared document class matching the patient to generate a CDA-standardized shared document.

[0017] In a third aspect, the present invention provides a device for implementing a CDA-standardized shared document, including a memory, a processor, and a transceiver that are communicatively connected in sequence. Among them, the memory is used to store a computer program, the transceiver is used to send and receive messages, and the processor is used to read the computer program and execute the method for implementing a CDA-standardized shared document as described in any one of the above.

[0018] In a fourth aspect, the present invention provides a computer program product containing instructions, which when run on a computer, cause the computer to execute the method for implementing a CDA-standardized shared document as described in any one of the above.

[0019] The beneficial effects of the present invention are as follows: The present invention discloses a method, system, device and product for implementing CDA standardized shared documents, including: obtaining an XSD schema, CDA dataset standards and value domain codes, and performing preprocessing operations on the XSD schema, CDA dataset standards and value domain codes to obtain a shared document standard class; obtaining business data of different patients in a database, inputting the business data into the shared document standard class to obtain a shared document class matching the patient; serializing the shared document class matching the patient to generate a CDA standardized shared document. By performing preprocessing operations on the XSD schema, CDA dataset standards and value domain codes, the present invention ensures that the input of business data does not damage the internal structure of the shared document, does not affect the generation and subsequent operations of the CDA standardized shared document, and at the same time can operate on the business data, facilitating the detection of business data, improving the quality and generation efficiency of the generated shared document, facilitating sharing among team members, being easy to operate, promoting the sharing and application of medical information, and being convenient for popularization and application. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 FIG. is a flowchart of a method for implementing CDA standardized shared documents provided in Embodiment 1 of the present application; Figure 2 FIG. is a block diagram of a system for implementing CDA standardized shared documents provided in Embodiment 2 of the present application; Figure 3 FIG. is a schematic structural diagram of a device for implementing CDA standardized shared documents provided in Embodiment 3 of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0021] In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the present invention in combination with the drawings and the descriptions of the embodiments or the prior art. Obviously, the following descriptions of the structures of the drawings are only some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts. It should be noted here that the descriptions of these embodiments are used to help understand the present invention, but do not constitute a limitation to the present invention.

[0022] It should be understood that although terms such as first and second may be used herein to describe various objects, these objects should not be limited by these terms. These terms are only used to distinguish one object from another. For example, the first object can be called the second object, and similarly, the second object can be called the first object, without departing from the scope of the exemplary embodiments of the present invention.

[0023] It should be understood that the terms used herein are only for describing specific embodiments and are not intended to limit the exemplary embodiments of the present invention. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms unless the context clearly dictates otherwise. It should also be understood that when the terms "comprises", "comprising", "includes" and / or "including" are used herein, they specify the presence of the stated features, integers, steps, operations, units and / or components, and do not preclude the presence or addition of one or more other features, quantities, steps, operations, units, components and / or their combinations.

[0024] Embodiment 1: As Figure 1 shown, this embodiment provides a method for implementing a CDA standardized shared document, which can be, but is not limited to, executed by a computer device or virtual machine with certain computing resources, such as an electronic device such as a personal computer or a smart phone, or a virtual machine; the intelligent distributed data scraping method based on big data can, but is not limited to, include the following steps: S1. Obtain the XSD schema, CDA dataset standard, and value domain code, and perform preprocessing operations on the XSD schema, CDA dataset standard, and value domain code to obtain the shared document standard class; Furthermore, the shared document standard class includes a shared document entity class, a shared document data class, and a first data class.

[0025] Specifically, in step S1, obtaining the XSD schema, CDA dataset standard, and value domain code, and performing preprocessing operations on the XSD schema, CDA dataset standard, and value domain code to obtain the shared document standard class includes: S11. Obtain multiple XSD schemas, perform deserialization operations on the multiple XSD schemas to obtain multiple shared document entity classes; Specifically, the overall architecture of the shared document is generated based on the XSD schema. The XSD schema (XML Schema Definition, Extensible Markup Language Schema) is a language used to define the structure of an XML document, which describes the types, attributes, data types of elements in the XML document, as well as the relationships and constraints between them.

[0026] S12. Obtain the value domain code, define the value domain code in an enumeration type to obtain the first data class; Furthermore, the value domain code is often used to limit the values allowed in a certain column and provides a concise and maintainable way to define the valid range of data. In this embodiment, the value domain code mainly targets finite value domain codes, excluding ICD-10 and ICD-9-CM3.

[0027] S13. Obtain the CDA dataset standard, encapsulate the first data class and the CDA dataset standard into multiple shared document entity classes to obtain the shared document standard class.

[0028] In this embodiment, the CDA dataset standard is a standard used to describe and exchange patient medical information in an electronic health record system. It defines a set of structures, format specifications, terms, and coding systems to achieve the standardization of patient information. Examples of dataset standards include "Basic Datasets of Health Records of Urban and Rural Residents (WS 365-2011)" and "Basic Datasets of Electronic Medical Records (WS 445-2014)".

[0029] Before step S2 of this embodiment, the method further includes: receiving the relationships of preset different categories of shared document classes, so as to process business data based on the relationships of different categories of shared document classes and the shared document standard class to obtain different categories of shared document classes that match the patient.

[0030] For example, if the shared document type is a medical record, a case summary needs to be generated; if the shared document type is a traditional Chinese medicine medical institution, a traditional Chinese medicine medical record front page needs to be generated, which is convenient for subsequently obtaining the business data of different patients in the database and obtaining the shared document classes that match the patients according to the business data.

[0031] S2. Obtain the business data of different patients in the database, input the business data into the shared document standard class to obtain the shared document class that matches the patient; Among them, in step S2, inputting the business data into the shared document standard class includes: S21. Calculate the integrity of the business data. The expression for calculating the integrity of the business data is:

[0032] In the above formula, represents the integrity of the business data, represents the parameter value instantiated according to the business data of different patients, represents the total number of data elements in the preset standard dataset; Judge whether the integrity of the business data is greater than or equal to the preset threshold. If so, input the business data into the shared document standard class.

[0033] Specifically, the preset threshold can be set to 60%. When the integrity of the transmitted service data is greater than or equal to 60%, it indicates that the transmitted service data is complete. The total number of data elements in the standard dataset is released by the state and is a fixed value. For example, the medical record summary dataset has 71 data elements, and the front page of the medical record dataset has 147 data elements. The service data of different patients is different, and the parameter values after instantiation are also different. Taking the medical record summary as an example, to ensure the integrity of the data, 43 out of 71 data elements must be assigned values so that the transmitted service data can be complete.

[0034] S3. Serialize the shared document class that matches the patient to generate a CDA-standardized shared document.

[0035] In this embodiment, the operation of serializing the shared document class enables the shared document class to be saved in XML format and transmitted to other institutions, where the shared document meets the CDA standard.

[0036] S4. Parse the shared document generated by other institutions; Among them, in step S4, parsing the shared document generated by other institutions includes: S41. Obtain the shared document generated by other institutions, parse the shared document generated by other institutions to obtain a parsing result, and the parsing result includes a parsing sub-result and the finally parsed shared document; among them, other institutions include various medical institutions, and the shared documents produced by other institutions include multiple datasets; Among them, in step S41, parsing the shared document generated by other institutions to obtain a parsing result, and the parsing result includes a parsing sub-result and the finally parsed shared document, includes: S411. Deserialize the shared document generated by other institutions to generate a deserialization result. The deserialization result is either successful deserialization or failed deserialization. If the deserialization result is failed deserialization, a deserialization error record is generated; if the deserialization result is successful deserialization, verify the deserialization result based on the XSD schema to generate an XSD verification result, and the XSD verification result is either successful XSD verification or failed XSD verification; S412. If the XSD verification result is failed XSD verification, an XSD verification error record is generated; if the XSD verification result is successful XSD verification, judge the structure in the shared document according to the preset shared document structure standard to obtain a structure verification result, and the structure verification result is either successful structure verification or failed structure verification; Specifically, the preset shared document structure standards include, but are not limited to, "WS / T 483-2016 Specification for Health Record Shared Documents" and "WS / T 500-2016 Specification for Electronic Medical Record Shared Documents", and the structure of the shared document is judged according to the above specifications.

[0037] S413. If the structure verification result is that the structure verification fails, generate a structure verification error record; if the structure verification result is that the structure verification is successful, perform data standardization verification on the instances in the shared document to obtain a verification result, and the verification result is verification success and verification failure; S414. If the verification result is verification failure, generate a verification error record, and use the deserialization error record, XSD verification error record, structure verification error record, and verification error record as the parsing sub-results; S415. Count the number of all instances with successful verification results in the dataset to obtain the first set number corresponding to the shared document, determine the integrity of the shared document according to the first set number and the total number of data elements in the preset standard dataset, and use the shared document with an integrity greater than or equal to the preset threshold as the finally parsed shared document.

[0038] Among them, in step S415, the integrity of the shared document is determined according to the first set number and the total number of data elements in the preset standard dataset. The expression for calculating the integrity of the shared document is:

[0039] In the above formula, represents the integrity of the shared document, represents the first set number; when is greater than or equal to the preset threshold, it means the shared document is complete.

[0040] Specifically, the preset threshold can be set to 60%. When the integrity of the passed value dataset elements is greater than or equal to 60%, it means the shared document is complete. Among them, the total number of data elements in the standard dataset is released by the country and is a fixed value. For example, the medical record summary dataset has 71 data elements, and the medical record front page dataset has 147 data elements. Taking the medical record summary as an example, to ensure the integrity of the shared document, at least 43 non-empty value data elements need to be obtained from the shared document to meet the integrity requirements of the shared document.

[0041] S42. Generate a parsing report according to the parsing sub-results; S43. Add the finally parsed shared document to the pre-built database.

[0042] S5. Merge any at least two shared documents.

[0043] Among them, in step S5, any at least two shared documents are merged. The merging of any at least two shared documents includes: S51. Receive any at least two shared documents, parse the at least two shared documents, and obtain at least two instantiated shared document classes; S52. Compare the at least two instantiated shared document classes, merge the parts with different contents in the at least two instantiated shared document classes to form a new shared document instance class, and input the new shared document instance class into the database; In a possible design, merging the parts with different contents in the at least two instantiated shared document classes includes: identifying the basic information in the two instantiated shared document classes based on machine learning technology, matching the two basic information, and if the matching rate is greater than a preset threshold, merging the different contents of the same part; In a possible design, merging the parts with different contents in the at least two instantiated shared document classes includes: directly merging the parts where data is replaced and added in the shared document class; In a possible design, merging the parts with different contents in the at least two instantiated shared document classes includes: the user determines whether the two instantiated shared document classes can be merged. If it is determined that they can be merged, merge the different contents of the same part; Furthermore, retain the original shared documents as a backup to prevent data loss caused by incorrect operations and improve the operation fault tolerance.

[0044] S53. Serialize the new shared document instance class to generate a CDA-standardized shared document.

[0045] In summary, a method for implementing a CDA standardized shared document provided in this embodiment includes obtaining an XSD schema, a CDA dataset standard, and value domain codes, and performing preprocessing operations on the XSD schema, the CDA dataset standard, and the value domain codes to obtain a shared document standard class; obtaining business data of different patients in a database, inputting the business data into the shared document standard class to obtain a shared document class matching the patient; serializing the shared document class matching the patient to generate a CDA standardized shared document; parsing the generated shared document; and merging any at least two shared documents. By performing preprocessing operations on the XSD schema, the CDA dataset standard, and the value domain codes, this embodiment ensures that the input of business data does not damage the internal structure of the shared document, does not affect the generation and parsing of the CDA standardized shared document, improves the correctness of data input, achieves a data error rate of 0, can operate on business data, facilitates the detection of business data, can perform splitting and merging operations on multiple shared documents, improves the quality and generation efficiency of the generated shared document, facilitates sharing among team members, is easy to operate, promotes the sharing and application of medical information, and is convenient for popularization and application.

[0046] Embodiment 2: This embodiment provides a system for implementing a CDA standardized shared document, including: A preprocessing module, configured to obtain an XSD schema, a CDA dataset standard, and value domain codes, and perform preprocessing operations on the XSD schema, the CDA dataset standard, and the value domain codes to obtain a shared document standard class; A processing module, communicatively connected to the preprocessing module, configured to obtain business data of different patients in a database, input the business data into the shared document standard class to obtain a shared document class matching the patient; A result generation module, communicatively connected to the processing module, configured to serialize the shared document class matching the patient to generate a CDA standardized shared document.

[0047] In summary, a system for implementing CDA standardized shared documents provided in this embodiment obtains the XSD schema, CDA dataset standard, and value domain code through a preprocessing module, performs preprocessing operations on the XSD schema, CDA dataset standard, and value domain code to obtain a shared document standard class, and uploads the shared document standard class to a processing module. The processing module is communicatively connected to the preprocessing module, obtains the business data of different patients in a database, inputs the business data into the shared document standard class to obtain a shared document class matching the patient, and uploads the shared document class to a result generation module. The result generation module is communicatively connected to the processing module and is used to serialize the shared document class matching the patient to generate a CDA standardized shared document. By preprocessing the XSD schema, CDA dataset standard, and value domain code in this embodiment, the XML format is converted to a class in a computer language, and the class is filled and written without damaging the format of the original file, improving the integrity of shared document generation. Moreover, by using this embodiment, the input data can be monitored and controlled, the correctness of data input can be improved, and a data error rate of 0 can be achieved, facilitating team members to understand and study the data in the shared document and promoting the sharing and application of medical information.

[0048] Embodiment 3: This embodiment provides a device for implementing CDA standardized shared documents, including a memory, a processor, and a transceiver that are communicatively connected in sequence. Among them, the memory is used to store a computer program, the transceiver is used to send and receive messages, and the processor is used to read the computer program and execute the method for implementing CDA standardized shared documents as described in Embodiment 1.

[0049] Specifically, the memory may include, but is not limited to, random access memory (RAM), read-only memory (ROM), flash memory, first-in-first-out memory (FIFO), and / or first-in-last-out memory (FILO), etc.; the processor may not be limited to using a microprocessor of the STM32F105 series, an architecture processor such as ARM (Advanced RISC Machines), X86, or a processor integrated with an NPU (neural-network processing units); the transceiver may include, but is not limited to, a WiFi (Wireless Fidelity) wireless transceiver, a Bluetooth wireless transceiver, a General Packet Radio Service (GPRS) wireless transceiver, a ZigBee (a low-power local area network protocol based on the IEEE802.15.4 standard) wireless transceiver, a 3G transceiver, a 4G transceiver, and / or a 5G transceiver, etc.

[0050] For the working process, working details and technical effects of the device provided in this embodiment, reference may be made to the method for implementing a CDA standardized shared document described in the first aspect of the embodiment, which will not be elaborated herein.

[0051] Embodiment 4: This embodiment provides a computer program product, including a computer program or instruction, which, when executed by a computer, is used to implement the method for implementing a CDA standardized shared document described in the first aspect of the embodiment.

[0052] For the working process, working details and technical effects of the foregoing computer program product provided in this embodiment, reference may be made to the method for implementing a CDA standardized shared document described in the first aspect, which will not be elaborated herein.

[0053] Finally, it should be noted that the above are only the preferred embodiments of the present invention and are not intended to limit the protection scope of the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A method for implementing CDA standardized shared documents, characterized in that: include: Obtain the XSD architecture, CDA data set standard and value range code, and perform preprocessing operations on the XSD architecture, CDA data set standard and value range code to obtain a shared document standard class; Obtain the business data of different patients in the database, input the business data into the shared document standard class, and obtain the shared document class matching the patient; Serialize the shared document class that matches the patient to generate a CDA standardized shared document.

2. A method for implementing CDA standardized shared documents according to claim 1, characterized in that: The shared document standard class includes a shared document entity class, a shared document data class and a first data class; obtaining an XSD architecture, a CDA data set standard and a value range code, and performing a preprocessing operation on the XSD architecture, the CDA data set standard and the value range code to obtain a shared document standard class, including: Obtain multiple XSD schemas, deserialize the multiple XSD schemas, and obtain multiple shared document entity classes; Obtain a value range code, define the value range code in an enumeration type, and obtain a first data class; The CDA data set standard is obtained, and the first data class and the CDA data set standard are encapsulated into a plurality of shared document entity classes to obtain a shared document standard class.

3. A method for implementing CDA standardized shared documents according to claim 1, characterized in that: Enter business data into shared document standard classes, including: The integrity of the business data is calculated, and the expression for calculating the integrity of the business data is: In the above formula, Indicates the completeness of business data. Indicates the parameter value instantiated according to the business data of different patients. Indicates the total number of data elements in the preset standard data set; Determine whether the integrity of the business data is greater than or equal to a preset threshold. If so, enter the business data into the shared document standard class.

4. The method for implementing CDA standardized shared documents according to claim 1, characterized in that: The method further includes: parsing the shared documents generated by other institutions, including: Acquire a shared document generated by other organizations, parse the shared document generated by other organizations, and obtain a parsing result, wherein the parsing result includes a parsing sub-result and a final parsed shared document; Generate an analysis report based on the analysis results; Add the final parsed shared document to the pre-built database.

5. A method for implementing CDA standardized shared documents according to claim 4, characterized in that: The shared document generated by the other institution includes multiple data sets; the shared document generated by the other institution is parsed to obtain a parsing result, the parsing result includes a parsing sub-result and a final parsed shared document, including: Deserialize the shared documents generated by other organizations to generate a deserialization result, which is a deserialization success or a deserialization failure. If the deserialization result is a deserialization failure, generate a deserialization error record; if the deserialization result is a deserialization success, verify the deserialization result based on the XSD architecture to generate an XSD verification result, which is an XSD verification success or an XSD verification failure; If the XSD verification result is that the XSD verification fails, an XSD verification error record is generated; if the XSD verification result is that the XSD verification succeeds, the structure in the shared document is judged according to a preset shared document structure standard to obtain a structure verification result, and the structure verification result is a structure verification success or a structure verification failure; If the structure verification result is that the structure verification fails, a structure verification error record is generated; if the structure verification result is that the structure verification succeeds, a data standardization check is performed on the instance in the shared document to obtain a check result, wherein the check result is a check success or a check failure; If the verification result is verification failure, a verification error record is generated, and the deserialization error record, XSD verification error record, structure verification error record and verification error record are used as parsing sub-results; The statistical verification result is the number of all successfully verified instances in the data set, and a first set number corresponding to the shared document is obtained. The completeness of the shared document is determined based on the first set number and the total number of data elements in the preset standard data set, and the shared document with a completeness greater than or equal to a preset threshold is used as the final parsed shared document.

6. A method for implementing CDA standardized shared documents according to claim 5, characterized in that: The completeness of the shared document is determined according to the first set number and the total number of data elements in the preset standard data set, wherein the expression for calculating the completeness of the shared document is: In the above formula, Indicates the completeness of the shared document. Represents the first set number; when Y is greater than or equal to the preset threshold, it means that the shared document is complete.

7. The method for implementing CDA standardized shared documents according to claim 1, characterized in that: The method further includes: merging any at least two shared documents, wherein the merging any at least two shared documents includes: Receiving at least two shared documents, parsing the at least two shared documents, and obtaining at least two instantiated shared document classes; Comparing the at least two instantiated shared document classes, merging parts of the at least two instantiated shared document classes with different contents to form a new shared document instance class, and inputting the new shared document instance class into the database; Serialize the new shared document instance class to generate a CDA standardized shared document.

8. A system for implementing CDA standardized shared documents, characterized in that: include: A preprocessing module is used to obtain the XSD architecture, CDA data set standard and value range code, and perform preprocessing operations on the XSD architecture, CDA data set standard and value range code to obtain a shared document standard class; The processing module is communicatively connected to the preprocessing module and is used to obtain the business data of different patients in the database, input the business data into the shared document standard class, and obtain the shared document class matching the patient; The result generation module is communicatively connected to the processing module and is used to serialize the shared document class matching the patient to generate a CDA standardized shared document.

9. A device for implementing CDA standardized shared documents, characterized in that: The method comprises a memory, a processor and a transceiver which are sequentially communicatively connected, wherein the memory is used to store a computer program, the transceiver is used to send and receive messages, and the processor is used to read the computer program to execute the method for realizing CDA standardized shared documents according to any one of claims 1 to 7.

10. A computer program product comprising a computer program or instructions, characterized in that When the computer program or the instruction is executed by a computer, the method for implementing CDA standardized shared documents as claimed in any one of claims 1 to 7 is implemented.

Images