CN114171205A - Medical data processing method and device and digital model editor - Google Patents
Medical data processing method and device and digital model editor Download PDFInfo
- Publication number
- CN114171205A CN114171205A CN202111436539.8A CN202111436539A CN114171205A CN 114171205 A CN114171205 A CN 114171205A CN 202111436539 A CN202111436539 A CN 202111436539A CN 114171205 A CN114171205 A CN 114171205A
- Authority
- CN
- China
- Prior art keywords
- medical data
- fhir
- model
- data
- target
- 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.)
- Pending
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 19
- 238000013499 data model Methods 0.000 claims abstract description 170
- 238000000034 method Methods 0.000 claims abstract description 31
- 238000006243 chemical reaction Methods 0.000 claims abstract description 20
- 238000013507 mapping Methods 0.000 claims description 94
- 230000015654 memory Effects 0.000 claims description 35
- 238000013075 data extraction Methods 0.000 claims description 21
- 238000012795 verification Methods 0.000 claims description 16
- 238000012545 processing Methods 0.000 claims description 11
- 238000001914 filtration Methods 0.000 claims description 8
- 238000011161 development Methods 0.000 abstract description 3
- 238000010586 diagram Methods 0.000 description 6
- 230000008569 process Effects 0.000 description 6
- 230000001360 synchronised effect Effects 0.000 description 4
- 230000006870 function Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 238000009434 installation Methods 0.000 description 2
- 230000000007 visual effect Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000000605 extraction Methods 0.000 description 1
- 230000036541 health Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000010200 validation analysis Methods 0.000 description 1
Images
Classifications
-
- 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
- G16H50/00—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics
- G16H50/70—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics for mining of medical data, e.g. analysing previous cases of other patients
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/256—Integrating or interfacing systems involving database management systems in federated or virtual databases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/258—Data format conversion from or to a database
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Theoretical Computer Science (AREA)
- Public Health (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Biomedical Technology (AREA)
- Pathology (AREA)
- Epidemiology (AREA)
- General Health & Medical Sciences (AREA)
- Primary Health Care (AREA)
- Medical Treatment And Welfare Office Work (AREA)
Abstract
The embodiment of the invention relates to a medical data processing method, a device and a data model editor, wherein the method comprises the following steps: acquiring a target medical data model to be processed; and inputting the target medical data model into a pre-loaded data model editor to obtain an FHIR resource model which is output by the data model editor and corresponds to the target medical data model. Therefore, the medical data model in the non-FHIR format can be converted into the FHIR resource model meeting the FHIR standard, and any software manufacturer can load the data model editor, so that the data conversion is realized, the software manufacturer is not required to develop a data standard interface based on FHIR, and the development cost is saved.
Description
Technical Field
The embodiment of the invention relates to the field of medical treatment, in particular to a medical data processing method and device and a digital model editor.
Background
At present, in more and more medical systems, medical data standards established by different medical systems are different, which leads to various medical data formats, complex interfaces and difficult convergence of medical data of different medical systems.
Therefore, the convergence, intercommunication and sharing of medical data of different medical systems is called a technical problem to be solved urgently.
Disclosure of Invention
In view of the above, embodiments of the present invention provide a method and an apparatus for processing medical data, and a digital model editor.
In a first aspect, an embodiment of the present invention provides a medical data processing method, where the method includes:
acquiring a target medical data model to be processed;
and inputting the target medical data model into a pre-loaded data model editor to obtain an FHIR resource model which is output by the data model editor and corresponds to the target medical data model, wherein the data model editor comprises data information of a plurality of FHIR resource models, and the medical data model in a non-FHIR format is converted into the FHIR resource model based on the data information of the FHIR resource model.
In one possible embodiment, the inputting the target medical data model into a preloaded data model editor to obtain an FHIR resource model corresponding to the target medical data model output by the data model editor includes:
inputting the target medical data model into a data extraction component in a pre-loaded data model editor, and performing data extraction on the target medical data model through the data extraction component to obtain a plurality of medical data key value pairs;
inputting a plurality of medical data key value pairs obtained by the data extraction component into a mapping component in the data model editor, so that keys in the medical data key value pairs are mapped into resource model field values conforming to the FHIR standard based on data information of the FHIR resource model by the mapping component;
and inputting the plurality of medical data key-value pairs mapped by the mapping component into a loading component in the data model editor, so as to obtain the FHIR resource model according to the plurality of mapped medical data key-value pairs by the loading component.
In one possible embodiment, the mapping, by the mapping component, a key of a plurality of key-value pairs of the medical data to a resource model field value conforming to FHIR standard includes:
searching a target mapping relation set by using keys in the medical data key value pairs as keywords through the mapping component aiming at each medical data key value pair, wherein the target mapping relation set comprises a mapping relation between a field value conforming to the target message format and an FHIR resource model field value, and the target message format is a message format corresponding to the target medical data model;
if the keywords are found from the target mapping relation set, determining the FHIR resource model field value corresponding to the keywords as a target FHIR resource model field value;
mapping a key in the medical data key value pair to the target FHIR resource model field value.
In one possible embodiment, before the inputting the plurality of medical data key-value pairs mapped by the mapping component into the loading component in the data model editor, the method further includes:
verifying the mapped plurality of key-value pairs of medical data by the mapping component;
if the verification result shows that the mapped medical data key value pair does not accord with the FHIR standard, converting the mapped medical data key value pair to obtain the medical data key value pair which accords with the FHIR standard;
the obtaining, by the loading component, an FHIR resource model according to the mapped plurality of medical data key-value pairs includes:
and obtaining an FHIR resource model according to the plurality of key value pairs of the medical data which conform to the FHIR standard by the loading assembly.
In one possible embodiment, the verifying the mapped plurality of medical data key-value pairs by the mapping component includes:
determining, by the mapping component, for each mapped medical data key-value pair, whether a data type of a median of the mapped medical data key-value pair is consistent with a target data type defined by an FHIR standard;
and if not, determining that the verification result indicates that the mapped medical data key-value pair does not meet the FHIR standard.
In one possible embodiment, the converting the mapped medical data key-value pairs includes:
and if the data type of the median of the mapped medical data key-value pairs is determined to be inconsistent with the target data type defined by the FHIR standard, converting the data type of the median of the mapped medical data key-value pairs into the target data type.
In one possible embodiment, the method further comprises:
and if the keywords are not found from the target mapping relation set through the mapping component, deleting the medical data key value pairs through a filtering component in the data model editor.
In a second aspect, an embodiment of the present invention provides a data model editor, including:
the data extraction component is used for extracting data of the input target medical data model to obtain a plurality of medical data key value pairs;
a mapping component for mapping a key of a plurality of the medical data key value pairs to a resource model field value that conforms to FHIR standards;
and the loading component is used for obtaining the FHIR resource model according to the mapped plurality of medical data key-value pairs.
In one possible embodiment, the data model editor further includes:
and the filtering component is used for deleting the medical data key-value pairs which are mapped by the mapping component and fail.
In a third aspect, an embodiment of the present invention provides a medical data processing apparatus, including:
the target acquisition module is used for acquiring a target medical data model to be processed;
and the conversion module is used for inputting the target medical data model into a pre-loaded data model editor to obtain an FHIR resource model which is output by the data model editor and corresponds to the target medical data model, wherein the data model editor comprises data information of a plurality of FHIR resource models, and the medical data model in a non-FHIR format is converted into the FHIR resource model based on the data information of the FHIR resource model.
In a fourth aspect, an embodiment of the present invention provides an electronic device, including: a processor and a memory, the processor being configured to execute a medical data processing program stored in the memory to implement the medical data processing method of any one of the first aspect.
In a fifth aspect, embodiments of the present invention provide a storage medium storing one or more programs, which are executable by one or more processors to implement the medical data processing method according to any one of the first aspects.
The technical proposal provided by the embodiment of the invention obtains the target medical data model to be processed, inputs the target medical data model into the pre-loaded data model editor to obtain the data output by the data model editor, the FHIR resource model, corresponding to the target medical data model, enables conversion of the medical data model in non-FHIR format to an FHIR resource model that conforms to the FHIR standard, and, because the data conversion is realized by the data model editor, the data model editor supports instant installation and use, namely, any software manufacturer can load the data model editor, thereby realizing the data conversion without software manufacturers developing data standard interfaces based on FHIR, saving development cost and further, the method provides possibility for the operations of converging, intercommunicating and sharing the medical data with different formats provided by different medical systems.
Drawings
Fig. 1 is a schematic structural diagram of a data model editor provided in an embodiment of the present invention;
fig. 2 is a flowchart of an embodiment of a medical data processing method according to an embodiment of the present invention;
FIG. 3 is a flow chart of an embodiment of another medical data processing method according to an embodiment of the present invention;
fig. 4 is a block diagram of an embodiment of a medical data processing apparatus according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
To facilitate understanding of the embodiments of the present invention, the following first exemplifies a data model editor provided by the present invention:
first, the data model editor provided by the present invention covers the data information of each FHIR (Fast Health Interoperable Resources) resource model to the maximum extent, where the data information includes, but is not limited to, the definition (i.e. field value), type, storage format, etc. of each data included in the FHIR resource model. The data model editor may perform a data conversion on the non-FHIR formatted medical data to convert the non-FHIR formatted medical data to FHIR compliant medical data. In addition, the data model editor provided by the invention can be installed and used by an external system, so that the medical data in the external system can be directly converted.
Referring to fig. 1, a schematic structural diagram of a data model editor provided in an embodiment of the present invention is shown. The data model editor 100 as illustrated in fig. 1 comprises: system code adapter 101, data extraction component 102, mapping component 103, loading component 104, and filtering component 105.
The system coding adapter 101 is used for realizing communication connection between the data model editor 100 and an external system, so as to obtain the medical data model from the external system.
The data extraction component 102 is configured to perform data extraction on the medical data model input to the data model editor 100, that is, the medical data model obtained by the system coding adapter 101, to obtain a plurality of medical data key value pairs.
It should be noted that, the embodiment of the present invention is directed to converting the medical data model in non-FHIR format into FHIR resource model, and therefore, the message format of the medical data model input to the data model editor 100 may be in non-FHIR format, such as HL 7V 2 format, HL 7V 3 format, HL7 CDA format, etc., which is not limited by the embodiment of the present invention.
Optionally, the data extraction component 102 may use JSON parse-encoding classes to convert the extracted data into a JSON format, thereby obtaining a plurality of key-value pairs of the medical data.
The mapping component 103 is configured to map keys in the plurality of medical data key value pairs to resource model field values conforming to the FHIR standard based on the data information of the FHIR resource model, so that the JSON-formatted data can be converted into a JSON model of the FHIR resource.
Specifically, the mapping component 103 searches for a target mapping relationship set including mapping relationships between field values conforming to a target message format and FHIR resource model field values, where the target message format refers to a message format corresponding to the medical data model input to the data model editor 100, using keys in the medical data key-value pairs as keywords, for each medical data key-value pair.
And if the keyword is searched from the target mapping relation set, determining the FHIR resource model field value corresponding to the keyword as the target FHIR resource model field value, and mapping a key in the medical data key value pair as the target FHIR resource model field value.
If the keyword is not found from the target mapping relationship set, as an optional implementation manner, an error-reporting reminder may be output through a visual interface, so that the mapping relationship is manually configured by a user, and further, based on the mapping relationship manually configured by the user, a key in the medical data key value pair is converted into a resource model field value meeting the FHIR standard.
In addition, the mapping component 103 can also invoke a Validator class to verify the validity of the JSON model for FHIR resources after mapping the keys in the plurality of pairs of medical data key values to the resource model field values that conform to FHIR standards to convert the JSON formatted data described above to the JSON model for FHIR resources. Here, validity means that the JSON model of FHIR resources conforms to FHIR standards.
Based on this, the mapping component 103 calls a Validator class to verify the validity of the JSON model for FHIR resources including: the mapping component 103 validates the mapped plurality of medical data key-value pairs to verify that the mapped medical data key-value pairs comply with FHIR standards.
Here, as can be seen from the above description, the mapping component 103 has mapped the keys in the medical data key value pairs to resource model field values that comply with FHIR standards, and has not processed the values in the medical data key value pairs. In practice, different data types may occur in different formats, for example, in HL 7V 2 format, the standard data type is int type, and in FFIR format, the standard data type is string type. Thus, the validation of the mapped plurality of medical data key-value pairs by the mapping component 102 to verify whether the mapped medical data key-value pairs comply with the FHIR standard comprises: the mapping component 102 determines, for each mapped medical data key-value pair, whether the data type of the median of the mapped medical data key-value pair is consistent with the target data type defined by the FHIR standard, and if not, determines that the verification result indicates that the mapped medical data key-value pair does not meet the FHIR standard; and if so, determining that the verification result indicates that the mapped medical data key-value pair meets the FHIR standard.
Further, as an optional implementation manner, the mapped medical data key-value pair may be converted to obtain the medical data key-value pair meeting the FHIR standard, in case that the verification result indicates that the mapped medical data key-value pair does not meet the FHIR standard. For example, the values in the mapped medical data key value pair may be converted from int type to string type.
As another optional implementation manner, an error notification may be output through the visual interface, so that the user manually inputs a value meeting the FHIR standard, and thus, the mapped medical data key-value pair may be converted according to the content input by the user, so as to obtain the medical data key-value pair meeting the FHIR standard.
And the loading component 104 is used for converting the JSON model of the FHIR resource into an FHIR model (POJO object), namely obtaining the FHIR resource model according to the mapped plurality of medical data key value pairs.
And the filtering component 105 is used for deleting the medical data key-value pairs which are failed to be mapped by the mapping component.
To this end, the structural description of the data model editor illustrated in fig. 1 is completed.
The following describes the medical data processing method provided by the present invention with specific embodiments based on the data model editor illustrated in fig. 1, and the embodiments do not limit the present invention.
Referring to fig. 2, a flowchart of an embodiment of a medical data processing method according to an embodiment of the present invention is provided. As shown in fig. 2, the process may include the following steps:
In one embodiment, the electronic device may receive an externally input, target medical data model to be processed.
In another embodiment, the electronic device may retrieve the target medical data model to be processed from the corresponding storage location according to a user-defined data storage path.
It should be noted that the message format of the target medical data model in the embodiment of the present invention may be a non-FHIR format, such as HL 7V 2 format, HL 7V 3 format, HL7 CDA format, and the like, which is not limited by the embodiment of the present invention.
Taking the medical data processing method provided by the embodiment of the invention applied to the electronic device as an example, the electronic device may be preloaded with the data model editor illustrated in fig. 1.
Based on the data model editor illustrated in fig. 1, in this step 202, the electronic device inputs the target medical data model into the data model editor to obtain a specific implementation process of the FHIR resource model corresponding to the target medical data model, which is output by the data model editor, including: the electronic equipment firstly inputs a target medical data model into a data extraction component in a data model editor, so that data extraction is carried out on the target medical data model through the data extraction component to obtain a plurality of medical data key value pairs; then, the electronic equipment inputs a plurality of medical data key value pairs obtained by the data extraction component into a mapping component in a data model editor, and maps keys in the medical data key value pairs into resource model field values meeting the FHIR standard based on data information of the FHIR resource model through the mapping component; and finally, the electronic equipment inputs the plurality of medical data key value pairs mapped by the mapping component into a loading component in the data model editor, so that the FHIR resource model is obtained by the loading component according to the plurality of mapped medical data key value pairs.
Further, field values corresponding to the same meaning are likely to be different in different message formats, for example, for a patient name, the field value in the format of HL 7V 2 is name, and the field value in the format of HL 7V 3 is patient _ name, which means that corresponding mapping relationship sets are different for different message formats.
Based on this, in the embodiment of the present invention, a message format (hereinafter referred to as a target message format for convenience of description) corresponding to the target medical data model may be further specified in advance, so that when the mapping component maps a key in the plurality of medical data key value pairs to a resource model field value conforming to the FHIR standard, the mapping component may implement the mapping based on the target mapping relationship set corresponding to the target message format.
Specifically, the mapping component may search, for each medical data key value pair, a target mapping relationship set using a key in the medical data key value pair as a key, where the target mapping relationship set includes a mapping relationship between a field value conforming to a target message format and an FHIR resource model field value, and if the key is found from the target mapping relationship set, determine, as the target FHIR resource model field value, the FHIR resource model field value corresponding to the key.
In addition, the mapping component can also verify the plurality of mapped medical data key-value pairs, and if the verification result shows that the mapped medical data key-value pairs do not accord with the FHIR standard, the mapped medical data key-value pairs are converted to obtain the medical data key-value pairs which accord with the FHIR standard. By such processing, the accuracy of the mapped key-value pair of medical data meeting the FHIR standard can be improved.
Wherein the verifying the mapped medical data key-value pair by the mapping component comprises: the mapping component determines whether the data type of the median of the mapped medical data key-value pairs is consistent with a target data type defined by an FHIR standard, if not, the verification result indicates that the mapped medical data key-value pairs are not consistent with the FHIR standard, and if so, the verification result indicates that the mapped medical data key-value pairs are consistent with the FHIR standard.
Further, in a case that it is determined that the verification result indicates that the mapped key-value pair of the medical data does not meet the FHIR standard, the converting the mapped key-value pair of the medical data includes: and converting the data type of the mapped medical data key value pair median value into a target data type.
In one example, assume that the target medical data model is in HL 7V 2 message format, and assume that the standard data type is int type under HL 7V 2 message format, and the standard data type is string type under FHIR format. According to the above description, the mapping component 102 verifies the mapped medical data key value pair, so as to obtain a verification result that the data type of the median of the medical data key value pair is inconsistent with the target data type, and further convert the value in the mapped medical data key value pair from int type to string type.
In addition, if the mapping component does not find a keyword from the set of target mapping relationships, the filtering component in the data model editor deletes the key-value pair of the medical data.
The technical proposal provided by the embodiment of the invention obtains the target medical data model to be processed, inputs the target medical data model into the pre-loaded data model editor to obtain the data output by the data model editor, the FHIR resource model, corresponding to the target medical data model, enables conversion of the medical data model in non-FHIR format to an FHIR resource model that conforms to the FHIR standard, and, because the data conversion is realized by the data model editor, the data model editor supports instant installation and use, namely, any software manufacturer can load the data model editor, thereby realizing the data conversion without software manufacturers developing data standard interfaces based on FHIR, saving development cost and further, the method provides possibility for the operations of converging, intercommunicating and sharing the medical data with different formats provided by different medical systems.
Referring to fig. 3, a flowchart of another embodiment of a medical data processing method according to an embodiment of the present invention is provided. As shown in fig. 3, the process may include the following steps:
It should be noted that, in general, the data model editor is loaded when the format conversion of the medical data model is performed for the first time, and in the subsequent application process, if the pre-loaded data model editor is not unloaded, the data model editor does not need to be loaded repeatedly.
The international standard formats include, but are not limited to, HL 7V 2 format, HL 7V 3 format, HL7 CDA format, and the like.
The user-defined format refers to a non-international standard format which is user-defined by a user.
And step 304, adding a mapping relation corresponding to the custom format in the data model editor.
And step 306, obtaining the FHIR resource model which is output by the data model editor and corresponds to the target medical data model.
As can be seen from the process shown in fig. 3, the data model editor provided in the embodiment of the present invention supports user-defined extension mapping relationships, thereby supporting uniform format conversion of various heterogeneous medical data models.
Referring to fig. 4, a block diagram of an embodiment of a medical data processing apparatus according to an embodiment of the present invention is provided. As shown in fig. 4, the apparatus includes: target acquisition module 41, conversion module 42.
The target obtaining module 41 is configured to obtain a target medical data model to be processed;
a conversion module 42, configured to input the target medical data model into a pre-loaded data model editor to obtain an FHIR resource model corresponding to the target medical data model and output by the data model editor, where the data model editor includes data information of multiple FHIR resource models, and converts a non-FHIR format medical data model into an FHIR resource model based on the data information of the FHIR resource model.
In a possible embodiment, said conversion module 42 comprises (not shown in the figures):
the extraction submodule is used for inputting the target medical data model into a data extraction component in the data model editor so as to extract data of the target medical data model through the data extraction component to obtain a plurality of medical data key value pairs;
a mapping sub-module, configured to input, to a mapping component in the data model editor, the plurality of key value pairs of medical data obtained by the data extraction component, so as to map, by the mapping component, keys in the plurality of key value pairs of medical data to resource model field values that meet FHIR standards based on data information of the FHIR resource model;
and the loading sub-module is used for inputting the plurality of medical data key-value pairs mapped by the mapping component into a loading component in the data model editor so as to obtain the FHIR resource model according to the plurality of mapped medical data key-value pairs by the loading component.
In a possible embodiment, the mapping sub-module is specifically configured to:
searching a target mapping relation set by using keys in the medical data key value pairs as keywords through the mapping component aiming at each medical data key value pair, wherein the target mapping relation set comprises a mapping relation between a field value conforming to the target message format and an FHIR resource model field value, and the target message format is a message format corresponding to the target medical data model;
if the keywords are found from the target mapping relation set, determining the FHIR resource model field value corresponding to the keywords as a target FHIR resource model field value;
mapping a key in the medical data key value pair to the target FHIR resource model field value.
In one possible embodiment, the mapping submodule comprises (not shown in the figures):
a verification sub-module for verifying the mapped plurality of key-value pairs of medical data by the mapping component before the mapped plurality of key-value pairs of medical data are input to the loading component in the data model editor;
the conversion sub-module is used for converting the mapped medical data key value pair to obtain the medical data key value pair meeting the FHIR standard if the verification result shows that the mapped medical data key value pair does not meet the FHIR standard;
the loading submodule is specifically configured to:
and obtaining an FHIR resource model according to the plurality of key value pairs of the medical data which conform to the FHIR standard by the loading assembly.
In one possible embodiment, the verification sub-module is specifically configured to:
determining whether the data type of the median of each mapped medical data key-value pair is consistent with the target data type defined by the FHIR standard or not according to each mapped medical data key-value pair;
and if not, determining that the verification result indicates that the mapped medical data key-value pair does not meet the FHIR standard.
In a possible implementation, the conversion submodule is specifically configured to:
and if the data type of the median of the mapped medical data key-value pairs is determined to be inconsistent with the target data type defined by the FHIR standard, converting the data type of the median of the mapped medical data key-value pairs into the target data type.
In a possible embodiment, the mapping submodule further comprises (not shown in the figures):
and the deleting submodule is used for deleting the medical data key value pair by a filtering component in the data model editor if the key word is not found from the target mapping relation set through the mapping component.
Fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present invention, where the electronic device 500 shown in fig. 5 includes: at least one processor 501, memory 502, at least one network interface 504, and other user interfaces 503. The various components in the electronic device 500 are coupled together by a bus system 505. It is understood that the bus system 505 is used to enable connection communications between these components. The bus system 505 includes a power bus, a control bus, and a status signal bus in addition to a data bus. For clarity of illustration, however, the various buses are labeled as bus system 505 in FIG. 5.
The user interface 503 may include, among other things, a display, a keyboard, or a pointing device (e.g., a mouse, trackball, touch pad, or touch screen, among others.
It is to be understood that the memory 502 in embodiments of the present invention may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The non-volatile memory may be a Read-only memory (ROM), a programmable Read-only memory (PROM), an erasable programmable Read-only memory (erasabprom, EPROM), an electrically erasable programmable Read-only memory (EEPROM), or a flash memory. The volatile memory may be a Random Access Memory (RAM) which functions as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (staticiram, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (syncronous DRAM, SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), enhanced synchronous dynamic random access memory (EnhancedSDRAM, ESDRAM), synchronous link dynamic random access memory (synchlink DRAM, SLDRAM), and direct memory bus random access memory (DRRAM). The memory 502 described herein is intended to comprise, without being limited to, these and any other suitable types of memory.
In some embodiments, memory 502 stores elements, executable units or data structures, or a subset thereof, or an expanded set thereof as follows: an operating system 5021 and application programs 5022.
The operating system 5021 includes various system programs, such as a framework layer, a core library layer, a driver layer, and the like, and is used for implementing various basic services and processing hardware-based tasks. The application 5022 includes various applications, such as a media player (MediaPlayer), a Browser (Browser), and the like, for implementing various application services. The program for implementing the method according to the embodiment of the present invention may be included in the application program 5022.
In the embodiment of the present invention, by calling a program or an instruction stored in the memory 502, specifically, a program or an instruction stored in the application 5022, the processor 501 is configured to execute the method steps provided by the method embodiments, for example, including:
acquiring a target medical data model to be processed;
and inputting the target medical data model into a pre-loaded data model editor to obtain an FHIR resource model which is output by the data model editor and corresponds to the target medical data model, wherein the data model editor comprises data information of a plurality of FHIR resource models, and the medical data model in a non-FHIR format is converted into the FHIR resource model based on the data information of the FHIR resource model.
The method disclosed by the above-mentioned embodiments of the present invention may be applied to the processor 501, or implemented by the processor 501. The processor 501 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 501. The processor 501 may be a general-purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, or discrete hardware components. The various methods, steps and logic blocks disclosed in the embodiments of the present invention may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present invention may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software elements in the decoding processor. The software elements may be located in ram, flash, rom, prom, or eprom, registers, among other storage media that are well known in the art. The storage medium is located in the memory 502, and the processor 501 reads the information in the memory 502 and completes the steps of the method in combination with the hardware.
It is to be understood that the embodiments described herein may be implemented in hardware, software, firmware, middleware, microcode, or any combination thereof. For a hardware implementation, the processing units may be implemented within one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), general purpose processors, controllers, micro-controllers, microprocessors, other electronic units configured to perform the functions described herein, or a combination thereof.
For a software implementation, the techniques described herein may be implemented by means of units performing the functions described herein. The software codes may be stored in a memory and executed by a processor. The memory may be implemented within the processor or external to the processor.
The electronic device provided in this embodiment may be the electronic device shown in fig. 5, and may execute all the steps of the medical data processing method shown in fig. 2 and 3, so as to achieve the technical effects of the medical data processing method shown in fig. 2 and 3, for which, reference is specifically made to the descriptions related to fig. 2 and 3, which are not described herein again for brevity.
The embodiment of the invention also provides a storage medium (computer readable storage medium). The storage medium herein stores one or more programs. Among others, the storage medium may include volatile memory, such as random access memory; the memory may also include non-volatile memory, such as read-only memory, flash memory, a hard disk, or a solid state disk; the memory may also comprise a combination of memories of the kind described above.
When one or more programs in the storage medium are executable by one or more processors, the medical data processing method executed on the electronic device side is realized.
The processor is used for executing the medical data processing program stored in the memory so as to realize the following steps of the medical data processing method executed on the electronic equipment side:
acquiring a target medical data model to be processed;
and inputting the target medical data model into a pre-loaded data model editor to obtain an FHIR resource model which is output by the data model editor and corresponds to the target medical data model, wherein the data model editor comprises data information of a plurality of FHIR resource models, and the medical data model in a non-FHIR format is converted into the FHIR resource model based on the data information of the FHIR resource model.
Those of skill would further appreciate that the various illustrative components and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied in hardware, a software module executed by a processor, or a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
The above-mentioned embodiments are intended to illustrate the objects, technical solutions and advantages of the present invention in further detail, and it should be understood that the above-mentioned embodiments are merely exemplary embodiments of the present invention, and are not intended to limit the scope of the present invention, and any modifications, equivalent substitutions, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.
Claims (12)
1. A method of medical data processing, the method comprising:
acquiring a target medical data model to be processed;
and inputting the target medical data model into a pre-loaded data model editor to obtain an FHIR resource model which is output by the data model editor and corresponds to the target medical data model, wherein the data model editor comprises data information of a plurality of FHIR resource models, and the medical data model in a non-FHIR format is converted into the FHIR resource model based on the data information of the FHIR resource model.
2. The method of claim 1, wherein inputting the target medical data model into a preloaded data model editor to obtain the FHIR resource model corresponding to the target medical data model output by the data model editor comprises:
inputting the target medical data model into a data extraction component in a pre-loaded data model editor, and performing data extraction on the target medical data model through the data extraction component to obtain a plurality of medical data key value pairs;
inputting a plurality of medical data key value pairs obtained by the data extraction component into a mapping component in the data model editor, so that keys in the medical data key value pairs are mapped into resource model field values conforming to the FHIR standard based on data information of the FHIR resource model by the mapping component;
and inputting the plurality of medical data key-value pairs mapped by the mapping component into a loading component in the data model editor, so as to obtain the FHIR resource model according to the plurality of mapped medical data key-value pairs by the loading component.
3. The method of claim 2, wherein the mapping, by the mapping component, a key of a plurality of the medical data key value pairs to a resource model field value conforming to FHIR standards based on data information of the FHIR resource model comprises:
aiming at each medical data key value pair through the mapping component, searching a target mapping relation set by taking a key in the medical data key value pair as a key word, wherein the target mapping relation set comprises a mapping relation between a field value conforming to a target message format and an FHIR resource model field value, and the target message format is a message format corresponding to the target medical data model;
if the keywords are found from the target mapping relation set, determining the FHIR resource model field value corresponding to the keywords as a target FHIR resource model field value;
mapping a key in the medical data key value pair to the target FHIR resource model field value.
4. The method of claim 2, wherein prior to said inputting the mapped plurality of medical data key-value pairs into a loading component in the data model editor, further comprising:
verifying the mapped plurality of key-value pairs of medical data by the mapping component;
if the verification result shows that the mapped medical data key value pair does not accord with the FHIR standard, converting the mapped medical data key value pair to obtain the medical data key value pair which accords with the FHIR standard;
the obtaining, by the loading component, an FHIR resource model according to the mapped plurality of medical data key-value pairs includes:
and obtaining an FHIR resource model according to the plurality of key value pairs of the medical data which conform to the FHIR standard by the loading assembly.
5. The method of claim 4, wherein verifying the mapped plurality of medical data key-value pairs by the mapping component comprises:
determining, by the mapping component, for each mapped medical data key-value pair, whether a data type of a median of the mapped medical data key-value pair is consistent with a target data type defined by an FHIR standard;
and if not, determining that the verification result indicates that the mapped medical data key-value pair does not meet the FHIR standard.
6. The method of claim 5, wherein said converting the mapped medical data key-value pairs comprises:
and if the data type of the median of the mapped medical data key-value pairs is determined to be inconsistent with the target data type defined by the FHIR standard, converting the data type of the median of the mapped medical data key-value pairs into the target data type.
7. The method of claim 3, further comprising:
and if the keywords are not found from the target mapping relation set through the mapping component, deleting the medical data key value pairs through a filtering component in the data model editor.
8. A data model editor, comprising:
the data extraction component is used for extracting data of the input target medical data model to obtain a plurality of medical data key value pairs;
a mapping component for mapping keys in a plurality of medical data key value pairs to resource model field values conforming to FHIR standards based on data information of a plurality of FHIR resource models;
and the loading component is used for obtaining the FHIR resource model according to the mapped plurality of medical data key-value pairs.
9. The data model editor of claim 8, further comprising:
and the filtering component is used for deleting the medical data key-value pairs which are mapped by the mapping component and fail.
10. A medical data processing apparatus, characterized in that the apparatus comprises:
the target acquisition module is used for acquiring a target medical data model to be processed;
and the conversion module is used for inputting the target medical data model into a pre-loaded data model editor to obtain an FHIR resource model which is output by the data model editor and corresponds to the target medical data model, wherein the data model editor comprises data information of a plurality of FHIR resource models, and the medical data model in a non-FHIR format is converted into the FHIR resource model based on the data information of the FHIR resource model.
11. An electronic device, comprising: a processor and a memory, the processor being configured to execute a medical data processing program stored in the memory to implement the medical data processing method of any one of claims 1 to 7.
12. A storage medium storing one or more programs executable by one or more processors to implement the medical data processing method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111436539.8A CN114171205A (en) | 2021-11-26 | 2021-11-26 | Medical data processing method and device and digital model editor |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111436539.8A CN114171205A (en) | 2021-11-26 | 2021-11-26 | Medical data processing method and device and digital model editor |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114171205A true CN114171205A (en) | 2022-03-11 |
Family
ID=80481584
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111436539.8A Pending CN114171205A (en) | 2021-11-26 | 2021-11-26 | Medical data processing method and device and digital model editor |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114171205A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116013487A (en) * | 2023-03-27 | 2023-04-25 | 深圳市浩然盈科通讯科技有限公司 | Data adaptation method and system applied to medical system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180293351A1 (en) * | 2017-04-06 | 2018-10-11 | Surescripts LLC | System and method for generating data resources in a processing system |
| CN110688343A (en) * | 2019-08-26 | 2020-01-14 | 天津开心生活科技有限公司 | Method and device for converting data format |
| CN110968322A (en) * | 2019-11-27 | 2020-04-07 | 北京旷视科技有限公司 | JSON data processing method and device and electronic system |
| KR20210015584A (en) * | 2019-07-31 | 2021-02-10 | 경북대학교 산학협력단 | Methods of providing health care service based on fhir standard and system of performing the same |
-
2021
- 2021-11-26 CN CN202111436539.8A patent/CN114171205A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180293351A1 (en) * | 2017-04-06 | 2018-10-11 | Surescripts LLC | System and method for generating data resources in a processing system |
| KR20210015584A (en) * | 2019-07-31 | 2021-02-10 | 경북대학교 산학협력단 | Methods of providing health care service based on fhir standard and system of performing the same |
| CN110688343A (en) * | 2019-08-26 | 2020-01-14 | 天津开心生活科技有限公司 | Method and device for converting data format |
| CN110968322A (en) * | 2019-11-27 | 2020-04-07 | 北京旷视科技有限公司 | JSON data processing method and device and electronic system |
Non-Patent Citations (1)
| Title |
|---|
| 鄢航程: "基于FHIR数据交换标准的临床决策支持", 《中国优秀硕士学位论文全文数据库 信息科技辑》, no. 1, 15 January 2019 (2019-01-15), pages 15 - 39 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116013487A (en) * | 2023-03-27 | 2023-04-25 | 深圳市浩然盈科通讯科技有限公司 | Data adaptation method and system applied to medical system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20180046606A1 (en) | Form Checking Method and Apparatus | |
| CN112765023B (en) | Test case generation method and device | |
| CN114048701B (en) | Netlist ECO method, device, equipment and readable storage medium | |
| US20080295085A1 (en) | Integrated code review tool | |
| CN112819153A (en) | Model transformation method and device | |
| CN110471690B (en) | Loading method and device for SO file of dynamic link library and storage medium | |
| CN111694572A (en) | Code format conversion method, device, computer equipment and storage medium | |
| CN111459509A (en) | Container mirror image construction method and device and server | |
| CN112306533A (en) | Front-end framework automatic conversion method and device, computer equipment and storage medium | |
| CN114171205A (en) | Medical data processing method and device and digital model editor | |
| CN110955434B (en) | Software development kit processing method and device, computer equipment and storage medium | |
| CN111258905A (en) | Defect positioning method and device, electronic equipment and computer readable storage medium | |
| CN112711405B (en) | Method, equipment and storage medium for generating add-delete-modify-check application program interface | |
| CN109429260B (en) | Method and device for checking northbound data | |
| CN117493309A (en) | Standard model generation method, device, equipment and storage medium | |
| CN117171030A (en) | Method, device, equipment and storage medium for detecting software running environment | |
| CN112181939A (en) | Method, device and system for switching sub-base and sub-table based on proxy mode | |
| CN114942781A (en) | Data format adaptation method and device for data reading | |
| CN115687108A (en) | Verification method, platform, terminal and storage medium based on combination of UVM and FPV | |
| CN113722321A (en) | Data export method and device and electronic equipment | |
| CN114817707A (en) | Method and device for creating node and problem, electronic equipment and storage medium | |
| CN109558181B (en) | Method for enabling non-IE browser to be compatible with OCX control, computer storage medium and equipment | |
| CN116302845B (en) | Method and device for determining transaction operation mode, electronic equipment and storage medium | |
| CN111782183B (en) | Method and device for judging component dependency, electronic device and medium | |
| CN113821474A (en) | Data processing method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |