CN113779128B - Medical data system docking method, device, equipment and storage medium - Google Patents
Medical data system docking method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN113779128B CN113779128B CN202111055971.2A CN202111055971A CN113779128B CN 113779128 B CN113779128 B CN 113779128B CN 202111055971 A CN202111055971 A CN 202111055971A CN 113779128 B CN113779128 B CN 113779128B
- Authority
- CN
- China
- Prior art keywords
- data
- interface
- docked
- universal
- docking
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000003032 molecular docking Methods 0.000 title claims abstract description 182
- 238000000034 method Methods 0.000 title claims abstract description 56
- 238000012360 testing method Methods 0.000 claims description 61
- 230000006870 function Effects 0.000 claims description 17
- 238000006243 chemical reaction Methods 0.000 claims description 14
- 238000000605 extraction Methods 0.000 claims description 5
- 238000012545 processing Methods 0.000 abstract description 6
- 238000013075 data extraction Methods 0.000 description 8
- 238000010586 diagram Methods 0.000 description 8
- 210000001503 joint Anatomy 0.000 description 8
- 230000008569 process Effects 0.000 description 7
- 244000046052 Phaseolus vulgaris Species 0.000 description 6
- 235000010627 Phaseolus vulgaris Nutrition 0.000 description 6
- 239000000284 extract Substances 0.000 description 6
- 230000006978 adaptation Effects 0.000 description 5
- 238000012795 verification Methods 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 4
- 230000008859 change Effects 0.000 description 3
- 238000011161 development Methods 0.000 description 3
- 238000002372 labelling Methods 0.000 description 3
- 238000004458 analytical method Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 230000036541 health Effects 0.000 description 2
- 230000002085 persistent effect Effects 0.000 description 2
- 238000003672 processing method Methods 0.000 description 2
- 241000208340 Araliaceae Species 0.000 description 1
- 235000005035 Panax pseudoginseng ssp. pseudoginseng Nutrition 0.000 description 1
- 235000003140 Panax quinquefolius Nutrition 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000003745 diagnosis Methods 0.000 description 1
- 238000002565 electrocardiography Methods 0.000 description 1
- 235000008434 ginseng Nutrition 0.000 description 1
- 238000011835 investigation Methods 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 230000007721 medicinal effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/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/254—Extract, transform and load [ETL] procedures, e.g. ETL data flows in data warehouses
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Medical Treatment And Welfare Office Work (AREA)
Abstract
The invention relates to the field of data processing, and discloses a medical data system docking method, device, equipment and storage medium, which are used for solving the technical problems that in the prior art, when a medical data system is docked, docking services are required to be independently developed aiming at the medical data system to be docked, so that a docking mode is complex, universality is avoided, and time cost and economic cost are high. The method comprises the following steps: acquiring an original data interface of each data item in a database to be docked, and analyzing an interface type corresponding to the original data interface; judging whether the interface type is a standard interface or not; if not, extracting an interface configuration rule corresponding to the interface type from a preset interface configuration database according to the interface type; performing interface assembly on the original data interface according to the interface configuration rule to obtain a universal data interface corresponding to the original interface; and carrying out data system docking according to the universal data interface, and extracting data to be docked in a database to be docked.
Description
Technical Field
The present invention relates to the field of data processing, and in particular, to a medical data system docking method, apparatus, device, and storage medium.
Background
Along with the development of technology, the medical industry is continuously revolutionized; along with the establishment and reform of the medical care system of the national level, the country also puts higher requirements on various hospitals at all levels, and the management of the hospitals is more hierarchical and on a large scale; to be combined with the development and application of information technology; further, the functions of intelligent diagnosis and treatment, remote consultation and the like are realized. However, in the actual operation of the internet hospital, various different data platforms need to be docked, and different systems and data interfaces used by different hospitals need to be docked, so that in the use of the internet hospital, a plurality of different data systems need to be docked, and data connection is established.
In the prior art, when data of a plurality of different data systems are docked, the data systems are typically docked in a manner of customizing and developing corresponding docking services for each system, and data connection among the data systems is completed, but because the data integrity of each data system is different from the system construction manner, the universality and reusability of the docking services are poor when the corresponding docking services are developed for the data systems of each hospital; and the time cost and the economic cost are high during development, so that the resource waste is caused.
Disclosure of Invention
The invention mainly aims to solve the technical problems that in the prior art, when a data system is in butt joint, a butt joint service is required to be independently developed aiming at the data system to be in butt joint, so that the butt joint mode of the data system is complex, the universality is not realized, and the time cost and the economic cost are high.
The first aspect of the invention provides a medical data system docking method, comprising: acquiring an original data interface of each data item in a database to be docked, and analyzing an interface type corresponding to the original data interface; judging whether the interface type is a standard interface or not; if not, extracting an interface configuration rule corresponding to the interface type from a preset interface configuration database according to the interface type; performing interface assembly on the original data interface according to the interface configuration rule to obtain a universal data interface corresponding to the original interface; and carrying out data system docking according to the universal data interface, and extracting data to be docked in the database to be docked.
Optionally, in a first implementation manner of the first aspect of the present invention, the performing data docking according to the generic data interface, and extracting data to be docked in the database to be docked includes: responding to a received data docking request, and extracting a database to be docked and a data item to be docked, which are contained in the data docking request; determining a universal data interface corresponding to the data item to be docked, and sending a data calling instruction to the universal data interface; and extracting the data to be docked from the database to be docked through reflecting the calling instruction according to the data calling instruction.
Optionally, in a second implementation manner of the first aspect of the present invention, the performing interface assembly on the original data interface according to the interface configuration rule, and obtaining a generic data interface corresponding to the original interface includes: acquiring original interface parameters, an original request head and an original naming space of the original data interface; calling a JavaScript function to replace the original interface parameters, the original request header and the original naming space according to the interface configuration rule to obtain universal interface parameters, a universal request header and a universal naming space; and generating a universal data interface according to the universal interface parameters, the universal request header and the universal naming space.
Optionally, in a third implementation manner of the first aspect of the present invention, after the generating a generic data interface according to the generic interface parameter, the generic request header and the generic namespace, the method further includes: sending a connection test request to the universal data interface; responding to the connection test request, and calling a universal interface to extract the test case data from the database to be docked to obtain a test data acquisition result, wherein the test case data is pre-stored in the database to be docked; judging whether the test data acquisition result is a true value or not; if yes, marking the universal data interface as being connected.
Optionally, in a fourth implementation manner of the first aspect of the present invention, the interface configuration rule further includes an interface decryption rule, and extracting, according to the data call instruction, to-be-docked data in the to-be-docked database through a reflection call instruction includes: acquiring a data decryption rule corresponding to preset data to be docked; responding to the data calling instruction, and extracting the encrypted data to be docked corresponding to the data item to be docked through a universal data interface corresponding to the data item to be docked; and decrypting the encrypted data to be docked according to the data decryption rule to obtain the data to be docked.
Optionally, in a fifth implementation manner of the first aspect of the present invention, after the extracting, according to the data call instruction, data to be docked in the database to be docked by reflecting the call instruction, the method further includes: recording the docking request time of the data docking request; extracting the docking completion time for completing the data docking; and calculating the docking time consumption according to the docking request time and the docking completion time, and generating a docking record according to the docking time consumption.
A second aspect of the present invention provides a medical data system docking device comprising: the acquisition module is used for acquiring the original data interfaces of all data items in the database to be docked, and analyzing the interface types corresponding to the original data interfaces; the judging module is used for judging whether the interface type is a standard interface or not; the extraction module is used for extracting the interface configuration rule corresponding to the interface type from a preset interface configuration database according to the interface type if not; the assembling module is used for carrying out interface assembly on the original data interface according to the interface configuration rule to obtain a universal data interface corresponding to the original interface; and the docking module is used for docking the data system according to the universal data interface and extracting data to be docked from the database to be docked.
Optionally, in a first implementation manner of the second aspect of the present invention, the docking module includes: the request analysis unit is used for responding to the received data docking request and extracting a database to be docked and a data item to be docked, which are contained in the data docking request; the instruction sending unit is used for determining a universal data interface corresponding to the data item to be docked and sending a data calling instruction to the universal data interface; and the data extraction unit is used for extracting the data to be docked from the database to be docked through the reflection calling instruction according to the data calling instruction.
Optionally, in a second implementation manner of the second aspect of the present invention, the assembly module includes: the parameter acquisition unit is used for acquiring the original interface parameters, the original request header and the original naming space of the original data interface; the parameter replacement unit is used for calling a JavaScript function to replace the original interface parameter, the original request head and the original naming space according to the interface configuration rule to obtain a universal interface parameter, a universal request head and a universal naming space; and the generating unit is used for generating a universal data interface according to the universal interface parameter, the universal request head and the universal naming space.
Optionally, in a third implementation manner of the second aspect of the present invention, the medical data system docking device further includes a test module, where the test module includes: a test request unit, configured to send a connection test request to the generic data interface; the test data extraction unit is used for responding to the connection test request and calling a universal interface to extract the test case data from the database to be docked to obtain a test data acquisition result, wherein the test case data is pre-stored in the database to be docked; the test judging unit is used for judging whether the test data acquisition result is a true value or not; and the test result labeling unit is used for labeling the universal data interface as connected if the universal data interface is connected.
Optionally, in a fourth implementation manner of the second aspect of the present invention, the interface configuration rule further includes an interface decryption rule, and the data extraction unit includes: the rule extraction subunit is used for acquiring a data decryption rule corresponding to preset data to be docked; the data extraction subunit is used for responding to the data calling instruction and extracting the encrypted data to be docked corresponding to the data item to be docked through the universal data interface corresponding to the data item to be docked; and the decryption subunit is used for decrypting the encrypted data to be docked according to the data decryption rule to obtain the data to be docked.
Optionally, in a fifth implementation manner of the second aspect of the present invention, the medical data system docking device further includes a recording module, where the recording module is specifically configured to: recording the docking request time of the data docking request; extracting the docking completion time for completing the data docking; and calculating the docking time consumption according to the docking request time and the docking completion time, and generating a docking record according to the docking time consumption.
A third aspect of the invention provides a medical data system docking device comprising: a memory and at least one processor, the memory having instructions stored therein; the at least one processor invokes the instructions in the memory to cause the medical data system docking device to perform the steps of the medical data system docking method described above.
A fourth aspect of the present invention provides a computer readable storage medium having instructions stored therein which, when run on a computer, cause the computer to perform the steps of the medical data system docking method described above.
In the technical scheme provided by the invention, the original data interfaces of all data items in the database to be docked are obtained, and the interface types corresponding to the original data interfaces are analyzed; judging whether the interface type is a standard interface or not; if not, extracting an interface configuration rule corresponding to the interface type from a preset interface configuration database according to the interface type; performing interface assembly on the original data interface according to the interface configuration rule to obtain a universal data interface corresponding to the original interface; and carrying out data system docking according to the universal data interface, and extracting data to be docked in a database to be docked. According to the embodiment of the invention, the universal scheme is configured through the pre-configured interface, the universal interface is assembled according to the original data interface of each data item, and the data is docked according to the universal interface, so that the docking operation of the data system is simplified, the universality and reusability of the docking service of the data system are improved, and the time cost and economic cost of docking the data system are reduced.
Drawings
FIG. 1 is a schematic diagram of a first embodiment of a medical data system docking method in accordance with an embodiment of the present invention;
FIG. 2 is a schematic diagram of a second embodiment of a medical data system docking method in accordance with an embodiment of the present invention;
FIG. 3 is a schematic diagram of a third embodiment of a medical data system docking method according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of a fourth embodiment of a medical data system docking method in accordance with an embodiment of the present invention;
FIG. 5 is a schematic diagram of one embodiment of a medical data system docking device in accordance with an embodiment of the present invention;
FIG. 6 is a schematic diagram of another embodiment of a medical data system docking device in accordance with an embodiment of the present invention;
FIG. 7 is a schematic diagram of one embodiment of a medical data system docking device in accordance with an embodiment of the invention.
Detailed Description
The embodiment of the invention provides a medical data system docking method, a device, equipment and a storage medium, which are used for acquiring an original data interface of each data item in a database to be docked and analyzing an interface type corresponding to the original data interface; judging whether the interface type is a standard interface or not; if not, extracting an interface configuration rule corresponding to the interface type from a preset interface configuration database according to the interface type; performing interface assembly on the original data interface according to the interface configuration rule to obtain a universal data interface corresponding to the original interface; and carrying out data system docking according to the universal data interface, and extracting data to be docked in a database to be docked. According to the embodiment of the invention, the universal scheme is configured through the pre-configured interface, the universal interface is assembled according to the original data interface of each data item, and the data is docked according to the universal interface, so that the docking operation of the data system is simplified, the universality and reusability of the docking service of the data system are improved, and the time cost and economic cost of docking the data system are reduced.
The terms "first," "second," "third," "fourth" and the like in the description and in the claims and in the above drawings, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments described herein may be implemented in other sequences than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed or inherent to such process, method, article, or apparatus.
For ease of understanding, a specific flow of an embodiment of the present invention is described below with reference to fig. 1, and one embodiment of a method for interfacing a medical data system according to an embodiment of the present invention includes:
101. acquiring an original data interface of each data item in a database to be docked, and analyzing an interface type corresponding to the original data interface;
It will be appreciated that the execution subject of the present invention may be a medical data system docking device, and may also be a terminal or a server, and is not limited herein. The embodiment of the invention is described by taking a server as an execution main body as an example.
The embodiment is particularly used for the condition that an internet hospital or other medical data needs to be acquired by interfacing with a hospital database, taking the internet hospital as an example, the internet hospital needs to call data such as medical record information of a patient in the operation process so as to process the medical record information of the patient, and the internet hospital needs to interface with hospital information systems (HIS, hospital Information System) of different hospitals in the actual operation process, wherein the hospital information systems are information systems which comprehensively manage people flow, logistics and financial flow of the hospitals and departments to which the hospitals belong by utilizing modern means such as computer software and hardware technology and network communication technology, acquire, store, process, extract, transmit and summarize the data generated in each stage of medical activities, and process the data to form various information, so that comprehensive automatic management and information systems of various services are provided for the integral operation of the hospitals.
Because of the problems of languages and capabilities of HIS manufacturers in different hospitals and the like, the data interfaces of HIS in each hospital are different, so in the embodiment, when the data system is specifically docked, in order to avoid separately establishing a docking service for the data system of each internet hospital, an interface service platform is preconfigured to perform interface configuration on the databases to be docked. Firstly, obtaining database information to be docked, extracting an original data interface corresponding to each data item in the database information to be docked, and determining the interface type of the original data interface according to the database information to be docked.
Specifically, the original data interfaces according to the embodiment may be classified into multiple types according to the language and the configuration mode of the data interfaces, but according to the configuration mode of the original data interfaces, the original data interfaces are classified into two types, namely standard interfaces and non-standard interfaces, wherein the standard interfaces refer to standard interfaces configured based on internet standard interface documents.
In addition, in the embodiment, the code is realized through thread local, so that multiple transmissions are avoided when object cross-layer transmission is performed, and the constraint among layers is broken. Inter-thread data isolation is performed.
102. Judging whether the interface type is a standard interface or not;
103. if not, extracting an interface configuration rule corresponding to the interface type from a preset interface configuration database according to the interface type;
judging whether the original data interface to be docked is a standard interface or not according to the interface type obtained by analysis in the previous step, and if the original data interface is the standard interface, directly taking the original data interface as a data system interface to obtain a universal data interface; or performing simple interface conversion operation according to the interface configuration of the original data interface to obtain the universal data interface. And if the interface type is not the standard interface, extracting an interface configuration rule corresponding to the interface type from a preset interface configuration database according to the interface type of the original data interface.
Specifically, the interface configuration rule is a configuration conversion rule which is constructed in advance according to a specific interface configuration mode of each data system to be docked; in this embodiment, the configuration of the interface may be completed by replacing information such as different request header, namespace, parameter entering mode, and adaptation parameter by a JavaScript function, where JavaScript (abbreviated as "JS") is a lightweight, interpreted or just-in-time compiled programming language with function priority.
In this step, a specific example is described, and when a Web Service program constructed by SOAP (Simple Object Access Protocol) is called to perform data docking, because namespaces, parameter entering modes and the like implemented by different vendors of each data system are different, at this time, different namespaces, adaptation parameters and the like are replaced by JS functions, and specifically, parameter entering required by an interface can be constructed by paramMap, mapItemList, mapItem and mapltem 2 instructions in JavaScript functions.
The SOAP (Simple Object Access Protocol) reference above refers to a simple object access protocol, a protocol specification for exchanging data, which is a lightweight, simple, XML (extensible markup language) based protocol designed to exchange structured and solidified information over WEB, wherein the extensible markup language is a subset of the standard generic markup language, a markup language for marking electronic files to be structured; web Service is a platform independent, low-coupling, self-contained, programmable Web-based application that can be described, published, discovered, coordinated, and configured using open XML standards for developing distributed interoperable applications.
104. Performing interface assembly on the original data interface according to the interface configuration rule to obtain a universal data interface corresponding to the original interface;
extracting original interface configuration information of an original data interface, wherein the original interface configuration information of the original data interface comprises a request head, a naming space, adaptation parameters and the like; the method comprises the steps of obtaining a configuration content table configured according to specific information of data system interface configuration of a data system to be docked, calling a pre-configured JS function code segment to change original interface configuration information and assemble interface information according to a configuration mode in the pre-configured configuration content table, and therefore a general data interface is obtained.
105. And carrying out data system docking according to the universal data interface, and extracting data to be docked in a database to be docked.
And after the universal data interface corresponding to the original data interface is obtained, the data system is docked according to the original data interface and the universal data interface. Specifically, when the data system is in butt joint, the data request terminal needing data butt joint sends a data call request to the universal data interface, and the universal data interface original data interface acquires the data in the corresponding database to be in butt joint, so that the butt joint of the data system and the extraction of the data are completed.
According to the embodiment of the invention, the universal scheme is configured through the pre-configured interface, the universal interface is assembled according to the original data interface of each data item, and the data is docked according to the universal interface, so that the docking operation of the data system is simplified, the universality and reusability of the docking service of the data system are improved, and the time cost and economic cost of docking the data system are reduced.
Referring to fig. 2, a second embodiment of a medical data system docking method according to an embodiment of the present invention includes:
201. acquiring an original data interface of each data item in a database to be docked, and analyzing an interface type corresponding to the original data interface;
202. judging whether the interface type is a standard interface or not;
acquiring database information to be docked, extracting original data interfaces corresponding to data items in the database information to be docked, determining the interface types of the original data interfaces according to the database information to be docked, and judging whether the interface types are standard interfaces or not.
203. If not, extracting an interface configuration rule corresponding to the interface type from a preset interface configuration database according to the interface type;
if the interface is a standard interface, the original data interface is directly used as a data system interface to obtain a universal data interface; or performing simple interface conversion operation according to the interface configuration of the original data interface to obtain the universal data interface. And if the interface type is not the standard interface, extracting an interface configuration rule corresponding to the interface type from a preset interface configuration database according to the interface type of the original data interface.
204. Performing interface assembly on the original data interface according to the interface configuration rule to obtain a universal data interface corresponding to the original interface;
extracting original interface configuration information of an original data interface, wherein the original interface configuration information of the original data interface comprises a request head, a naming space, adaptation parameters and the like; the method comprises the steps of obtaining a configuration content table configured according to specific information of data system interface configuration of a data system to be docked, calling a pre-configured JS function code segment to change original interface configuration information and assemble interface information according to a configuration mode in the pre-configured configuration content table, and therefore a general data interface is obtained.
By way of specific example, a specific configuration table of contents in this embodiment may include the following:
hospital id: designating a hospital code;
hospital name: designating a hospital name;
the method comprises the following steps: the appointed method codes, so that the searching and positioning problems are facilitated;
JS text content: parameter conversion, result conversion and the like can be performed;
parameter conversion: specifying a parameter method of the parameter in the JS text content;
interface parameter entering conversion parameter mark: specifying the assembly type of the parameters;
The interface goes into the conversion return sign: the return type of the parameter;
returning a result conversion: specifying a processing method of a result returned by an interface in JS text content;
parameter mark of interface output: the type of the result set returned by the external interface;
interface parameter output return flag: the result set returned after the processing of the < return result conversion >;
encryption bean: specifying an encryption mode of entering the ginseng;
encryption key: designating an encrypted key;
decryption bean: returning a decryption processing method of the result set;
decryption key: decrypting the key;
network remote call bean: processing the sending request, and assembling different request modes for different external interfaces;
remote method address: URL (Uniform Resource Locator ) address of external interface;
remote namespaces: the external interface is needed to be used when Web Service is adopted;
remote service name: an external interface method;
whether to turn on: whether to use the present configuration content for interface assembly.
205. Sending a connection test request to a universal data interface;
206. responding to a connection test request, and calling a universal interface to extract test case data from a database to be docked to obtain a test data acquisition result;
after the universal data interface is obtained after the assembly of the universal data interface in the previous step, the universal interface needs to be tested to verify whether the universal data interface is already connected. The test case can be pre-configured in the database to be docked, and the corresponding test case data can be obtained through the general data interface obtained through configuration to verify whether the test case is connected or not.
Specifically, the docking terminal firstly sends a connection test request to the universal data interface, and after receiving the connection test request, the docking terminal extracts test case data from the database to be docked to obtain a corresponding test data acquisition result; the test case data are stored in the database to be docked in advance.
207. Judging whether the test data acquisition result is a true value or not;
208. if yes, marking the universal data interface as connected;
after obtaining a data acquisition result, judging whether the data acquisition result is a true value; if yes, marking the universal data interface as being connected. Then, outputting the obtained data acquisition result to a control console, checking the correctness of the data, and marking the universal data interface as a normal working interface if the checking is correct; specifically, when the correctness verification is performed, the method can be used for performing the specific verification in a mode of entering a docking hospital to add a doctor, performing inquiry, prescription and the like to verify the correctness of the interface data checked by the whole-flow link.
209. Responding to the received data docking request, extracting a database to be docked and a data item to be docked, which are contained in the data docking request;
210. determining a universal data interface corresponding to a data item to be docked, and sending a data calling instruction to the universal data interface;
211. And extracting the data to be docked from the database to be docked by reflecting the calling instruction according to the data calling instruction.
After the universal data interface is obtained specifically, specific data docking operation can be performed through the obtained universal data interface, when the data docking operation is performed in this embodiment, data acquisition is performed based on the built universal data interface, specifically, a data docking request from a data request terminal is received, a database to be docked and data items to be docked contained in the data docking request are extracted, the universal data interface corresponding to the data items to be docked is extracted from a preset configuration database, and the data docking is completed by extracting the data items to be docked from the database to be docked through the corresponding universal data interface.
According to the embodiment of the invention, the universal scheme is configured through the pre-configured interface, the universal interface is assembled according to the original data interface of each data item, and the data is docked according to the universal interface, so that the docking operation of the data system is simplified, the universality and reusability of the docking service of the data system are improved, and the time cost and economic cost of docking the data system are reduced.
Referring to fig. 3, a third embodiment of a medical data system docking method according to an embodiment of the present invention includes:
301. acquiring an original data interface of each data item in a database to be docked, and analyzing an interface type corresponding to the original data interface;
302. judging whether the interface type is a standard interface or not;
303. if not, extracting an interface configuration rule corresponding to the interface type from a preset interface configuration database according to the interface type;
in this embodiment, the contents of steps 301-303 are substantially the same as those of step 101-103 in the previous embodiment, so that the description thereof is omitted here.
304. Acquiring original interface parameters, an original request head and an original naming space of an original data interface;
305. the JavaScript function is called to replace the original interface parameters, the original request header and the original naming space according to the interface configuration rule, so that the universal interface parameters, the universal request header and the universal naming space are obtained;
306. generating a universal data interface according to the universal interface parameters, the universal request header and the universal naming space;
extracting original interface configuration information of an original data interface, wherein the original interface configuration information of the original data interface comprises a request head, a naming space, adaptation parameters and the like;
The method comprises the steps of obtaining a preconfigured interface configuration rule, and converting original interface configuration information according to the preconfigured interface configuration rule, wherein in the embodiment, a preconfigured JS function code section is called to change the original interface configuration information and assemble the interface information according to a specific configuration mode in a preset configuration content table, so that a universal data interface is obtained, and specifically, parameters needed by the interface can be built through paramMap, mapItemList, mapItem and mapltem 2 instructions in a JavaScript function.
307. Responding to the received data docking request, extracting a database to be docked and a data item to be docked, which are contained in the data docking request;
308. determining a universal data interface corresponding to a data item to be docked, and sending a data calling instruction to the universal data interface;
after the universal data interface is obtained specifically, specific data docking operation can be performed through the obtained universal data interface, when the data docking operation is performed in this embodiment, data acquisition is performed based on the built universal data interface, specifically, a data docking request from a data request terminal is received, a database to be docked and a data item to be docked contained in the data docking request are extracted, the universal data interface corresponding to the data item to be docked is extracted from a preset configuration database, and a data calling instruction is sent to the universal data interface.
After the universal data interface acquires a data calling instruction, calling a remote interface through a java preset reflection function, namely calling the corresponding original data interface; and after the original data interface receives the data calling instruction, extracting specific data requested in the data calling instruction from a corresponding database. In addition, it is also necessary to determine whether the preset encryption bean (encryption method) and encryption key (encryption key) are included in the preset configuration table of contents, if yes, the data are encrypted according to the encryption bean (encryption method) and the encryption key (encryption key), and the encrypted data are sent to the universal data interface.
309. Acquiring a data decryption rule corresponding to preset data to be docked;
310. responding to a data calling instruction, and extracting encrypted data to be docked corresponding to the data item to be docked through a universal data interface corresponding to the data item to be docked;
311. and decrypting the encrypted data to be docked according to the data decryption rule to obtain the data to be docked.
After the universal data interface is obtained specifically, specific data docking operation can be performed through the obtained universal data interface, when the data docking operation is performed in this embodiment, data acquisition is performed based on the built universal data interface, specifically, a data docking request with short data request is received, a database to be docked and data items to be docked contained in the data docking request are extracted, the universal data interface corresponding to the data items to be docked is extracted from a preset configuration database, and the data docking is completed by extracting the data items to be docked from the database to be docked through the corresponding universal data interface.
According to the embodiment of the invention, the universal scheme is configured through the pre-configured interface, the universal interface is assembled according to the original data interface of each data item, and the data is docked according to the universal interface, so that the docking operation of the data system is simplified, the universality and reusability of the docking service of the data system are improved, and the time cost and economic cost of docking the data system are reduced.
Referring to fig. 4, a fourth embodiment of a method for interfacing a medical data system according to an embodiment of the present invention includes:
401. acquiring an original data interface of each data item in a database to be docked, and analyzing an interface type corresponding to the original data interface;
402. judging whether the interface type is a standard interface or not;
403. if not, extracting an interface configuration rule corresponding to the interface type from a preset interface configuration database according to the interface type;
acquiring database information to be docked, extracting original data interfaces corresponding to data items in the database information to be docked, determining the interface types of the original data interfaces according to the database information to be docked, and judging whether the interface types are standard interfaces or not. And if the interface type is not the standard interface, extracting an interface configuration rule corresponding to the interface type from a preset interface configuration database according to the interface type of the original data interface.
404. Acquiring original interface parameters, an original request head and an original naming space of an original data interface;
405. the JavaScript function is called to replace the original interface parameters, the original request header and the original naming space according to the interface configuration rule, so that the universal interface parameters, the universal request header and the universal naming space are obtained;
406. generating a universal data interface according to the universal interface parameters, the universal request header and the universal naming space;
the details of steps 404 to 406 in this embodiment are substantially the same as those of steps 304 to 306 in the previous embodiment, and thus are not described herein.
407. Sending a connection test request to a universal data interface;
408. responding to a connection test request, and calling a universal interface to extract test case data from a database to be docked to obtain a test data acquisition result;
409. judging whether the test data acquisition result is a true value or not;
410. if yes, marking the universal data interface as connected;
after the universal data interface is obtained after the assembly of the universal data interface in the previous step, the universal interface needs to be tested to verify whether the universal data interface is already connected. The test case can be pre-configured in the database to be docked, and the corresponding test case data can be obtained through the general data interface obtained through configuration to verify whether the test case is connected or not.
Specifically, the docking terminal firstly sends a connection test request to the universal data interface, and after receiving the connection test request, the docking terminal extracts test case data from the database to be docked to obtain a corresponding test data acquisition result.
After obtaining a data acquisition result, judging whether the data acquisition result is a true value; if yes, marking the universal data interface as being connected. Then, outputting the obtained data acquisition result to a control console, checking the correctness of the data, and marking the universal data interface as a normal working interface if the checking is correct; specifically, when the correctness verification is performed, the method can be used for performing the specific verification in a mode of entering a docking hospital to add a doctor, performing inquiry, prescription and the like to verify the correctness of the interface data checked by the whole-flow link.
In a specific implementation operation, in this embodiment, the data value corresponding to the field assettrue may be verified by verifying the data value of the field assettrue (res. Issuccess ()), and if true, the interface is considered to be turned on; after verification as on, outputting the result to a console through a specific data output command field, such as system.out.println (json.tojsonstring (res)); and checking the correctness of the data, and if the result obtained by the checking is correct, considering that the current universal data interface is already connected.
411. Responding to the received data docking request, extracting a database to be docked and a data item to be docked, which are contained in the data docking request;
412. determining a universal data interface corresponding to a data item to be docked, and sending a data calling instruction to the universal data interface;
after the universal data interface is obtained specifically, specific data docking operation can be performed through the obtained universal data interface, in this embodiment, when the data docking operation is performed, data acquisition is performed based on the constructed universal data interface, specifically, a data docking request from a data request terminal is received, a database to be docked and a data item to be docked contained in the data docking request are extracted, the universal data interface corresponding to the data item to be docked is extracted from a preset configuration database, and a data calling instruction is sent to the universal data interface.
413. Acquiring a data decryption rule corresponding to preset data to be docked;
414. responding to a data calling instruction, and extracting encrypted data to be docked corresponding to the data item to be docked through a universal data interface corresponding to the data item to be docked;
415. and decrypting the encrypted data to be docked according to the data decryption rule to obtain the data to be docked.
After the universal data interface is obtained specifically, specific data docking operation can be performed through the obtained universal data interface, in this embodiment, data acquisition is performed based on the built universal data interface when the data docking operation is performed, specifically, a data docking request with short data request is received, a database to be docked and data items to be docked contained in the data docking request are extracted, the universal data interface corresponding to the data items to be docked is extracted from a preset configuration database, and the data item to be docked is extracted from the database to be docked through the corresponding universal data interface, so that data docking is completed.
In this embodiment, the interface configuration rule further includes a decryption rule, where the decryption rule is accessed by configuration, as described in the foregoing embodiment, an encryption bean (encryption method) and an encryption key (encryption key); if not in the common encryption and decryption scheme, the customized extension encryption and decryption is supported; for example, the interface configuration rule includes a decryption interface (DecryptSuperUtil) and an encryption interface (encryptedsuperutil), and provides a general implementation. In addition, general encryption and decryption AES algorithm can be configured to realize the access of the encryption and decryption which is not customized.
In addition, when data is docked, docking request time of the data docking request is recorded; extracting the docking completion time for completing the data docking; calculating the docking time consumption according to the docking request time and the docking completion time, and generating a docking record according to the docking time consumption; and the obtained docking records are subjected to persistent reservation, and the time consumption, performance, frequency and the like of the docking requests can be analyzed, monitored and counted.
According to the embodiment of the invention, the universal scheme is configured through the pre-configured interface, the universal interface is assembled according to the original data interface of each data item, and the data is docked according to the universal interface, so that the docking operation of the data system is simplified, the universality and reusability of the docking service of the data system are improved, and the time cost and economic cost of docking the data system are reduced.
The method for interfacing a medical data system according to the embodiment of the present invention is described above, and the apparatus for interfacing a medical data system according to the embodiment of the present invention is described below, referring to fig. 5, an embodiment of the apparatus for interfacing a medical data system according to the embodiment of the present invention includes:
the acquisition module 501 is configured to acquire an original data interface of each data item in the database to be docked, and analyze an interface type corresponding to the original data interface;
A judging module 502, configured to judge whether the interface type is a standard interface;
an extracting module 503, configured to extract, if not, an interface configuration rule corresponding to the interface type from a preset interface configuration database according to the interface type;
an assembling module 504, configured to perform interface assembly on the original data interface according to the interface configuration rule, so as to obtain a general data interface corresponding to the original interface;
the docking module 505 is configured to dock the data system according to the universal data interface, and extract data to be docked in the database to be docked.
The embodiment of the invention simplifies the docking operation of the data system, improves the universality and reusability of docking service of the data system, and reduces the time cost and economic cost of docking the data system.
Referring to fig. 6, another embodiment of the medical data system docking apparatus according to the present invention includes:
the acquisition module 501 is configured to acquire an original data interface of each data item in the database to be docked, and analyze an interface type corresponding to the original data interface;
a judging module 502, configured to judge whether the interface type is a standard interface;
an extracting module 503, configured to extract, if not, an interface configuration rule corresponding to the interface type from a preset interface configuration database according to the interface type;
An assembling module 504, configured to perform interface assembly on the original data interface according to the interface configuration rule, so as to obtain a general data interface corresponding to the original interface;
the docking module 505 is configured to dock the data system according to the universal data interface, and extract data to be docked in the database to be docked.
In another embodiment of the present embodiment, the docking module 505 includes:
a request parsing unit 5051, configured to respond to a received data docking request, and extract a database to be docked and a data item to be docked that are included in the data docking request;
an instruction sending unit 5052, configured to determine a generic data interface corresponding to the data item to be docked, and send a data call instruction to the generic data interface;
and the data extraction unit 5053 is configured to extract data to be docked in the database to be docked by reflecting the call instruction according to the data call instruction.
In another embodiment of the present embodiment, the assembling module 504 includes:
a parameter obtaining unit 5041, configured to obtain an original interface parameter, an original request header, and an original namespace of the original data interface;
a parameter replacing unit 5042, configured to invoke a JavaScript function to replace the original interface parameter, the original request header, and the original namespace according to the interface configuration rule, so as to obtain a universal interface parameter, a universal request header, and a universal namespace;
A generating unit 5043, configured to generate a generic data interface according to the generic interface parameter, the generic request header and the generic namespace.
In another embodiment of the present embodiment, the medical data system docking device further includes a test module 506, the test module 506 including:
a test request unit 5061 for sending a turn-on test request to the generic data interface;
the test data extraction unit 5062 is configured to call a universal interface to extract the test case data from the database to be docked in response to the connection test request, so as to obtain a test data acquisition result, where the test case data is pre-stored in the database to be docked;
a test judgment unit 5063 for judging whether the test data acquisition result is a true value;
and a test result labeling unit 5064, configured to label the generic data interface as turned on if yes.
In another embodiment of the present embodiment, the interface configuration rule further includes an interface decryption rule, and the data extraction unit 5053 includes:
the rule extraction subunit is used for acquiring a data decryption rule corresponding to preset data to be docked;
the data extraction subunit is used for responding to the data calling instruction and extracting the encrypted data to be docked corresponding to the data item to be docked through the universal data interface corresponding to the data item to be docked;
And the decryption subunit is used for decrypting the encrypted data to be docked according to the data decryption rule to obtain the data to be docked.
In another embodiment of the present embodiment, the medical data system docking device further includes a recording module, where the recording module is specifically configured to:
recording the docking request time of the data docking request;
extracting the docking completion time for completing the data docking;
and calculating the docking time consumption according to the docking request time and the docking completion time, and generating a docking record according to the docking time consumption.
According to the embodiment of the invention, the universal scheme is configured through the pre-configured interface, the universal interface is assembled according to the original data interface of each data item, and the data is docked according to the universal interface, so that the docking operation of the data system is simplified, the universality and reusability of the docking service of the data system are improved, and the time cost and economic cost of docking the data system are reduced.
The medical data system docking apparatus according to the embodiment of the present invention is described in detail above in terms of the modularized functional entity in fig. 5 and 6, and the medical data system docking device according to the embodiment of the present invention is described in detail below in terms of hardware processing.
Fig. 7 is a schematic structural diagram of a medical data system docking device according to an embodiment of the present invention, where the medical data system docking device 700 may have a relatively large difference due to different configurations or performances, and may include one or more processors (central processing units, CPU) 710 (e.g., one or more processors) and a memory 720, and one or more storage media 730 (e.g., one or more mass storage devices) storing application programs 733 or data 732. Wherein memory 720 and storage medium 730 may be transitory or persistent. The program stored on the storage medium 730 may include one or more modules (not shown), each of which may include a series of instruction operations on the medical data system docking device 700. Still further, the processor 710 may be configured to communicate with the storage medium 730 to execute a series of instruction operations in the storage medium 730 on the medical data system docking device 700.
The medical data system docking device 700 may also include one or more power supplies 740, one or more wired or wireless network interfaces 750, one or more input/output interfaces 760, and/or one or more operating systems 731, such as Windows Serve, mac OS X, unix, linux, freeBSD, and the like. It will be appreciated by those skilled in the art that the medical data system docking device structure shown in fig. 7 is not limiting of the medical data system docking device and may include more or fewer components than shown, or may combine certain components, or a different arrangement of components.
The present invention also provides a computer device, which may be any device capable of performing the medical data system interfacing method described in the above embodiments, the computer device including a memory and a processor, the memory having stored therein computer readable instructions which, when executed by the processor, cause the processor to perform the steps of the medical data system interfacing method described in the above embodiments.
In one possible implementation, the data is medical data, such as personal health records, prescriptions, exam reports, and the like.
In one possible implementation, the natural language text is medical text, and the medical text may be a medical electronic record (Electronic Healthcare Record), an electronic personal health record, including a series of electronic records with saved values for investigation, such as medical records, electrocardiography, and medical images.
Information inquiry is a channel for users to quickly acquire required information in many scenes. For example, in the medical field, medical record information required by a user can be queried from a large amount of electronic medical records based on an artificial intelligence model, so that medical record reference can be provided for the user.
The present invention also provides a computer readable storage medium, which may be a non-volatile computer readable storage medium, and which may also be a volatile computer readable storage medium, the computer readable storage medium having instructions stored therein which, when executed on a computer, cause the computer to perform the steps of the medical data system docking method.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, which are not repeated herein.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied essentially or in part or all of the technical solution or in part in the form of a software product stored in a storage medium, including instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a read-only memory (ROM), a random access memory (random access memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The above embodiments are only for illustrating the technical solution of the present invention, and not for limiting the same; although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention.
Claims (7)
1. A medical data system docking method, the medical data system docking method comprising:
acquiring an original data interface of each data item in a database to be docked, and analyzing an interface type corresponding to the original data interface;
judging whether the interface type is a standard interface or not, wherein the standard interface refers to a standard interface configured based on an Internet standard interface document;
if yes, the original data interface is used as a data system interface, and a universal data interface is obtained; or performing interface conversion operation according to the interface configuration corresponding to the original data interface to obtain a universal data interface;
if not, extracting an interface configuration rule corresponding to the interface type from a preset interface configuration database according to the interface type, wherein the interface configuration rule is a configuration conversion rule which is constructed in advance according to a specific interface configuration mode of each data system to be docked, and the specific interface configuration mode is used for indicating a configuration mode in a preset configuration content table;
Acquiring original interface parameters, an original request head and an original naming space of the original data interface;
calling a JavaScript function to replace the original interface parameters, the original request header and the original naming space according to the interface configuration rule to obtain universal interface parameters, a universal request header and a universal naming space;
generating a universal data interface according to the universal interface parameters, the universal request header and the universal naming space;
responding to a received data docking request, and extracting a database to be docked and a data item to be docked, which are contained in the data docking request;
determining a universal data interface corresponding to the data item to be docked, and sending a data calling instruction to the universal data interface;
and extracting the data to be docked from the database to be docked through reflecting the calling instruction according to the data calling instruction.
2. The medical data system docking method of claim 1, further comprising, after said generating a generic data interface from said generic interface parameters, generic request header and generic namespace:
sending a connection test request to the universal data interface;
Responding to the connection test request, and calling a universal interface to extract test case data from the database to be docked to obtain a test data acquisition result, wherein the test case data is pre-stored in the database to be docked;
judging whether the test data acquisition result is a true value or not;
if yes, marking the universal data interface as being connected.
3. The medical data system interfacing method according to claim 1, wherein the interface configuration rule further includes a data decryption rule, and the extracting the data to be interfaced in the database by reflecting the call instruction according to the data call instruction includes:
acquiring a data decryption rule corresponding to preset data to be docked;
responding to the data calling instruction, and extracting the encrypted data to be docked corresponding to the data item to be docked through a universal data interface corresponding to the data item to be docked;
and decrypting the encrypted data to be docked according to the data decryption rule to obtain the data to be docked.
4. The medical data system interfacing method according to claim 1 or 2, further comprising, after the extracting the data to be interfaced in the database to be interfaced by reflecting the call instruction according to the data call instruction:
Recording the docking request time of the data docking request;
extracting the docking completion time for completing data docking;
and calculating the docking time consumption according to the docking request time and the docking completion time, and generating a docking record according to the docking time consumption.
5. A medical data system docking device, the medical data system docking device comprising:
the acquisition module is used for acquiring the original data interfaces of all data items in the database to be docked, and analyzing the interface types corresponding to the original data interfaces;
the judging module is used for judging whether the interface type is a standard interface or not, wherein the standard interface refers to a standard interface configured based on an Internet standard interface document;
if yes, the original data interface is used as a data system interface, and a universal data interface is obtained; or performing interface conversion operation according to the interface configuration corresponding to the original data interface to obtain a universal data interface;
the extraction module is used for extracting interface configuration rules corresponding to the interface types from a preset interface configuration database according to the interface types if not, wherein the interface configuration rules are configuration conversion rules which are built in advance according to specific interface configuration modes of the data systems to be docked, and the specific interface configuration modes are used for indicating configuration modes in a preset configuration content table;
The assembly module is used for acquiring the original interface parameters, the original request header and the original naming space of the original data interface; calling a JavaScript function to replace the original interface parameters, the original request header and the original naming space according to the interface configuration rule to obtain universal interface parameters, a universal request header and a universal naming space; generating a universal data interface according to the universal interface parameters, the universal request header and the universal naming space;
the docking module is used for responding to the received data docking request and extracting a database to be docked and a data item to be docked, which are contained in the data docking request; determining a universal data interface corresponding to the data item to be docked, and sending a data calling instruction to the universal data interface; and extracting the data to be docked from the database to be docked through reflecting the calling instruction according to the data calling instruction.
6. A medical data system docking device, the medical data system docking device comprising: a memory and at least one processor, the memory having instructions stored therein;
the at least one processor invoking the instructions in the memory to cause the medical data system docking device to perform the steps of the medical data system docking method of any of claims 1-4.
7. A computer readable storage medium having instructions stored thereon, which when executed by a processor, implement the steps of the medical data system docking method of any of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111055971.2A CN113779128B (en) | 2021-09-09 | 2021-09-09 | Medical data system docking method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111055971.2A CN113779128B (en) | 2021-09-09 | 2021-09-09 | Medical data system docking method, device, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113779128A CN113779128A (en) | 2021-12-10 |
| CN113779128B true CN113779128B (en) | 2024-04-05 |
Family
ID=78841961
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111055971.2A Active CN113779128B (en) | 2021-09-09 | 2021-09-09 | Medical data system docking method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113779128B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109951538A (en) * | 2019-03-06 | 2019-06-28 | 深圳市飞比电子科技有限公司 | Data processing method, device, system, electronic equipment and storage medium |
| WO2020119430A1 (en) * | 2018-12-14 | 2020-06-18 | 深圳壹账通智能科技有限公司 | Protocol interface test method, device, computer device and storage medium |
| CN112527630A (en) * | 2020-11-18 | 2021-03-19 | 平安消费金融有限公司 | Test case generation method and device, computer equipment and storage medium |
| CN113223687A (en) * | 2021-05-31 | 2021-08-06 | 康键信息技术（深圳）有限公司 | Service access method, device, equipment and storage medium based on login platform |
-
2021
- 2021-09-09 CN CN202111055971.2A patent/CN113779128B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2020119430A1 (en) * | 2018-12-14 | 2020-06-18 | 深圳壹账通智能科技有限公司 | Protocol interface test method, device, computer device and storage medium |
| CN109951538A (en) * | 2019-03-06 | 2019-06-28 | 深圳市飞比电子科技有限公司 | Data processing method, device, system, electronic equipment and storage medium |
| CN112527630A (en) * | 2020-11-18 | 2021-03-19 | 平安消费金融有限公司 | Test case generation method and device, computer equipment and storage medium |
| CN113223687A (en) * | 2021-05-31 | 2021-08-06 | 康键信息技术（深圳）有限公司 | Service access method, device, equipment and storage medium based on login platform |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113779128A (en) | 2021-12-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11538571B1 (en) | Virtual worklist for analyzing medical images | |
| US20200118232A1 (en) | Pre-fetching Patient Data for Virtual Worklists | |
| US8311855B2 (en) | Gathering, storing, and retrieving summary electronic healthcare record information from healthcare providers | |
| US7814169B2 (en) | System and method for establishing and retrieving data based on global indices | |
| KR101066246B1 (en) | Clinical Decision Support System and method thereby | |
| EP1763812A2 (en) | Generalized approach to structured medical reporting | |
| JP2010505205A (en) | Personal health record system and equipment | |
| US20090150439A1 (en) | Common extensible data exchange format | |
| KR101609716B1 (en) | Method and system for collecting clinical data service based on integrated data hub | |
| CN110784509B (en) | Medical information processing method and system and related components | |
| US20050268165A1 (en) | Method and system for automated testing of web services | |
| KR101440926B1 (en) | Apparatus and method for acquiring clinical trial data from electronic healthcare records, initiated by edc system | |
| Lebold et al. | OSA-CBM architecture development with emphasis on XML implementations | |
| Martíez et al. | Seamless integration of ISO/IEEE11073 personal health devices and ISO/EN13606 electronic health records into an end-to-end interoperable solution | |
| CN113658591B (en) | Voice interaction adaptation system for intelligent home | |
| US20130091416A1 (en) | Method for establishing a relationship between semantic data and the running of a widget | |
| US20100185696A1 (en) | Data tranformations for applications supporting different data formats | |
| US20210090717A1 (en) | Cloud-based patient data exchange | |
| CN113779128B (en) | Medical data system docking method, device, equipment and storage medium | |
| Herbold et al. | Combining usage-based and model-based testing for service-oriented architectures in the industrial practice | |
| CN106529153B (en) | The character set matching process and device of Digital imaging in medicine and communication file | |
| Lebold et al. | A framework for next generation machinery monitoring and diagnostics | |
| US9619443B2 (en) | Enhanced messaging transaction performance with auto-selected dual-tag fields | |
| Pavlopoulos et al. | Vital signs monitoring from home with open systems | |
| EP2541872B1 (en) | A rest capable web server |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |