CN112148783A - Data exchange method, device and equipment - Google Patents
Data exchange method, device and equipment Download PDFInfo
- Publication number
- CN112148783A CN112148783A CN202011041145.8A CN202011041145A CN112148783A CN 112148783 A CN112148783 A CN 112148783A CN 202011041145 A CN202011041145 A CN 202011041145A CN 112148783 A CN112148783 A CN 112148783A
- Authority
- CN
- China
- Prior art keywords
- service request
- request information
- client
- target interface
- sending
- 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
- 238000000034 method Methods 0.000 title claims abstract description 31
- 238000012545 processing Methods 0.000 claims abstract description 14
- 238000012795 verification Methods 0.000 claims description 25
- 230000015654 memory Effects 0.000 claims description 9
- 238000006243 chemical reaction Methods 0.000 claims description 6
- 238000012216 screening Methods 0.000 claims description 6
- 238000004590 computer program Methods 0.000 claims description 2
- 238000010586 diagram Methods 0.000 description 4
- 230000000750 progressive effect Effects 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 2
- 238000010276 construction Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
Images
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/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
-
- 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/24—Querying
- G06F16/245—Query processing
-
- 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
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H10/00—ICT specially adapted for the handling or processing of patient-related medical or healthcare data
Abstract
The embodiment of the application provides a data exchange method, a device and equipment, wherein the data exchange method comprises the following steps: receiving service request information sent by a client; acquiring interface information of a server corresponding to the service request information according to the service request information; determining a target interface and input parameters of the target interface according to the interface information and the service request information; calling the target interface according to the input parameters; acquiring output parameters of the target interface; and sending a service processing result to the client according to the output parameter. The data exchange between different information systems is realized.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a data exchange method, apparatus, and device.
Background
With the continuous development of information technology, more and more enterprise information systems need to exchange data frequently with other information systems outside. For example, the intelligent medical system needs to frequently visit the information systems of various hospitals and health service centers to complete inquiry, registration and other businesses. Because each information system has its own operating environment and data storage mode, the data formats are different, the data interfaces are diversified, and different information systems cannot directly exchange heterogeneous data.
In the prior art, in order to implement data exchange with external heterogeneous systems, a corresponding interface program needs to be separately developed for each external heterogeneous system according to data requirements, the flexibility and the universality of data exchange are low, the data requirements can change along with services, the workload of program development is large, and the operation cost is high.
Disclosure of Invention
An object of the embodiments of the present application is to provide a data exchange method, apparatus and device, which are used to implement data exchange between different information systems.
A first aspect of an embodiment of the present application provides a data exchange method, including: receiving service request information sent by a client; acquiring interface information of a server corresponding to the service request information according to the service request information; determining a target interface and input parameters of the target interface according to the interface information and the service request information; calling the target interface according to the input parameters; acquiring output parameters of the target interface; and sending a service processing result to the client according to the output parameter.
In an embodiment, after the determining a target interface and input parameters of the target interface according to the interface information and the service request information, the method further includes: judging whether the input parameters need to be checked or not according to the service request information; when the input parameters need to be checked, checking the input parameters according to a preset checking rule, and judging whether the checking is passed; and when the input parameter is not checked, sending a checking result to the client.
In an embodiment, when the input parameter needs to be verified, verifying the input parameter according to a preset verification rule includes: judging whether the field of the input parameter is in a preset range or not; if the field of the input parameter is in a preset range, the input parameter passes the verification; and if the field of the input parameter is not in the preset range, the input parameter is not checked to be passed.
In an embodiment, after the invoking the target interface according to the input parameter, the method further includes: judging whether the target interface is successfully called; and when the target interface is not successfully called, sending error information to the client.
In an embodiment, the sending the service processing result to the client according to the output parameter includes: carrying out format conversion on the output parameters to obtain standard data; screening the standard data according to the service request information to obtain target data; and sending the target data to the client.
A second aspect of the embodiments of the present application provides a data exchange device, including: the receiving module is used for receiving service request information sent by a client; the first acquisition module is used for acquiring interface information of a server corresponding to the service request information according to the service request information; the determining module is used for determining a target interface and input parameters of the target interface according to the interface information and the service request information; the calling module is used for calling the target interface according to the input parameters; the second acquisition module is used for acquiring the output parameters of the target interface; and the first sending module is used for sending the service processing result to the client according to the output parameter.
In one embodiment, the method further comprises: the first judgment module is used for judging whether the input parameters need to be checked according to the service request information; the verification module is used for verifying the input parameters according to a preset verification rule when the input parameters need to be verified, and judging whether the verification is passed; and the second sending module is used for sending the verification result to the client when the input parameter is not verified.
In one embodiment, the method further comprises: the second judgment module is used for judging whether the target interface is successfully called; and the third sending module is used for sending error information to the client when the target interface is not successfully called.
In one embodiment, the verification module is configured to: judging whether the field of the input parameter is in a preset range or not; if the field of the input parameter is in a preset range, the input parameter passes the verification; and if the field of the input parameter is not in the preset range, the input parameter is not checked to be passed.
In one embodiment, the first sending module is configured to: carrying out format conversion on the output parameters to obtain standard data; screening the standard data according to the service request information to obtain target data; and sending the target data to the client.
A third aspect of embodiments of the present application provides an electronic device, including: a memory to store a computer program; a processor configured to perform the method of the first aspect of the embodiments of the present application and any of the embodiments of the present application.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments of the present application will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and that those skilled in the art can also obtain other related drawings based on the drawings without inventive efforts.
Fig. 1 is a schematic view of an application scenario of a data exchange method according to an embodiment of the present application;
fig. 2 is a schematic structural diagram of an electronic device according to an embodiment of the present application;
FIG. 3 is a flow chart illustrating a data exchange method according to an embodiment of the present application;
FIG. 4 is a schematic flow chart illustrating a data exchange method according to another embodiment of the present application;
fig. 5 is a schematic structural diagram of a data exchange device according to an embodiment of the present application.
Reference numerals:
110-client, 120-data exchange middleware, 130-server, 200-electronic equipment, 210-bus, 220-processor, 230-memory, 500-data exchange device, 501-receiving module, 502-first obtaining module, 503-determining module, 504-calling module, 505-second obtaining module, 506-first sending module, 507-first judging module, 508-checking module, 509-second sending module, 510-second judging module and 511-third sending module.
Detailed Description
The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.
In the description of the present application, the terms "first," "second," and the like are used for distinguishing between descriptions and do not denote an order of magnitude, nor are they to be construed as indicating or implying relative importance.
In the description of the present application, the terms "comprises," "comprising," and/or the like, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, elements, components, and/or groups thereof.
In the description of the present application, the terms "mounted," "disposed," "provided," "connected," and "configured" are to be construed broadly unless expressly stated or limited otherwise. For example, it may be a fixed connection, a removable connection, or a unitary construction; can be mechanically or electrically connected; either directly or indirectly through intervening media, or may be internal to two devices, elements or components. The specific meaning of the above terms in the present application can be understood by those of ordinary skill in the art as appropriate.
Please refer to fig. 1, which is a schematic view of an application scenario of a data exchange method according to an embodiment of the present application. In the application scenario, the client 110, the data exchange middleware 120, and the multiple servers 130 are included, where the client 110 includes, but is not limited to, a smartphone client, a tablet computer client, a notebook computer client, a desktop computer client, and the like, the multiple servers 130 may be HIS systems (Hospital Information systems) of medical institutions such as different hospitals and health service centers, respectively, and the service interfaces provided by the servers 130 may be implemented based on different interface protocols, including, but not limited to, webservice, http, DLL, and databases.
The user can inquire information such as personal historical attendance record, health record, hospital doctor scheduling condition and the like through the client 110, and can also make appointment registration through the client 110. The client 110 communicates with the plurality of servers 130 through the data exchange middleware 120, and the data exchange middleware 120 may perform the data exchange method in the following embodiments to realize data exchange between the client 110 and the plurality of servers 130.
Fig. 2 is a schematic structural diagram of an electronic device 200 according to an embodiment of the present application, and the electronic device includes at least one processor 220 and a memory 230, where fig. 2 illustrates one processor as an example. The processors 220 and the memory 230 are connected by a bus 210, and the memory 230 stores instructions executable by the at least one processor 220, the instructions being executed by the at least one processor 220 to cause the at least one processor 220 to perform a data exchange method as in the embodiments described below.
Fig. 3 is a flowchart illustrating a data exchange method according to an embodiment of the present application, which can be executed by the electronic device 200 shown in fig. 2 to implement data exchange between different information systems. The method comprises the following steps:
step 301: and receiving service request information sent by the client.
In the above step, the service request information includes a service type and input information related to the service type.
In an embodiment, a user may send service request information for querying a scheduling condition of a doctor through a client, where a service type included in the service request is a scheduling query, and other input information related to the service type includes, but is not limited to, hospital information, department information, query time period, and the like to which the doctor belongs.
In an embodiment, the user may send the service request information for appointment registration through the client, the service type included in the service request is registration, and other input information related to the service type includes, but is not limited to, hospital information, department information, doctor information, appointment time, and the age, sex, identification number, contact number, etc. of the patient who wants to make an appointment registration.
Step 302: and acquiring interface information of the server corresponding to the service request information according to the service request information.
In the above steps, according to the service request information, a service end which needs to perform data exchange with the client in the service request information is determined, and interface information of the service end is obtained, where the interface information includes, but is not limited to, a name, a type, a calling mode, and the like of a service end interface, and the interface type includes, but is not limited to, webservice, http, and the like.
In an embodiment, the service request information includes hospital information of a shift scheduling condition inquired by a user, and then according to the service request information, it is determined that the HIS system of the hospital is a server that needs to exchange data with the client, and interface information corresponding to the server that is prestored is obtained.
In an embodiment, the service request information includes hospital information that the user wants to register, and then, according to the service request information, it is determined that the HIS system of the hospital is a server that needs to exchange data with the client, and interface information corresponding to the server that is pre-stored is obtained.
Step 303: and determining the target interface and the input parameters of the target interface according to the interface information and the service request information.
In one embodiment, the target interface is determined to be a shift interface according to the interface information and the service request information, and the input parameters of the target interface include, but are not limited to, a doctor id, a start time, an end time, and the like.
In one embodiment, the target interface is determined to be an ordering interface according to the interface information and the service request information, and the input parameters of the target interface include, but are not limited to, doctor id, appointment time, patient name, patient age, patient sex, and the like.
Step 304: and calling the target interface according to the input parameters.
Step 305: and acquiring the output parameters of the target interface.
In an embodiment, the target interface is a shift register interface, and the obtained output parameter of the target interface is shift register list data.
In an embodiment, the target interface is a placing interface, and the obtained output parameter of the target interface is an order number.
Step 306: and sending the service processing result to the client according to the output parameter.
In the above step, sending the service processing result to the client according to the output parameter may include: carrying out format conversion on the output parameters to obtain standard data; screening the standard data according to the service request information to obtain target data; and sending the target data to the client.
In an embodiment, the obtained output parameter of the target interface is shift schedule data, the shift schedule data can be cleaned and screened according to the query time period in the service request information, data with a timing field value inconsistent with the query time period in the shift schedule data are filtered, and data with a remaining timing field value consistent with the query time period are sent to the client as a service processing result.
In an embodiment, the obtained output parameter of the target interface is an order number, and the order number can be sent to the client as a service processing result to indicate that the subscription registration is successful.
Fig. 4 is a flowchart illustrating a data exchange method according to an embodiment of the present application, which can be executed by the electronic device 200 shown in fig. 2 to implement data exchange between different information systems. The method comprises the following steps:
step 401: and receiving service request information sent by the client. See the description of step 301 in the above embodiment for details.
Step 402: and acquiring interface information of the server corresponding to the service request information according to the service request information. See the description of step 302 in the above embodiment for details.
Step 403: and determining the target interface and the input parameters of the target interface according to the interface information and the service request information. See the description of step 303 in the above embodiment for details.
Step 404: and judging whether the input parameters need to be checked or not according to the service request information.
In the above steps, it is determined whether the input parameter needs to be checked according to the service request information, if the input parameter needs to be checked, step 405 is executed, and if the input parameter does not need to be checked, step 407 is executed.
Step 405: and checking the input parameters according to a preset checking rule, and judging whether the checking is passed or not.
In the above steps, the input parameter is verified according to a preset verification rule, if the input parameter verification fails, step 406 is executed, and if the input parameter verification passes, step 407 is executed. In an embodiment, the plurality of preset check rules may be in a parallel relationship or a progressive relationship, if the plurality of preset check rules are in a parallel relationship, the check may be performed simultaneously or sequentially according to each preset check rule, and if the plurality of preset check rules are in a progressive relationship, the check may be performed sequentially according to a progressive logic between the preset check rules.
In one embodiment, it can be determined whether the field of the input parameter is within a predetermined range; if the field of the input parameter is in the preset range, the input parameter passes the verification; and if the field of the input parameter is not in the preset range, the input parameter is not checked. For example, for pediatric registered service request information, it may be determined whether the input parameter age field is less than or equal to 14; for the gynecological registration service request information, whether the input parameter gender field is 0 or not can be judged, wherein 0 represents a female and 1 represents a male.
In one embodiment, it may be determined whether the field of the input parameter is null; if the field of the input parameter is not null, the input parameter passes the verification; and if the field of the input parameter is null, the input parameter is not checked. For example, for the service request information of the subscription registration, it can be determined whether the input parameter identification number field is null value.
In an embodiment, whether the field value type of the input parameter is correct or not can be judged; if the field value type of the input parameter is correct, the input parameter passes the verification; and if the field value type of the input parameter is incorrect, the input parameter is not checked. For example, it may be determined whether the value type of the age field of the input parameter is correct, and if the value type of the age field is a number, the value type of the field of the input parameter is correct, and the input parameter passes verification.
Step 406: and sending the verification result to the client.
In the above steps, a check result is sent to the client to prompt the reason of the failure of the service processing.
Step 407: and calling the target interface according to the input parameters. See the description of step 304 in the above embodiment for details.
Step 408: and judging whether the target interface is successfully called.
In the above step, if the target interface is not successfully called, execute step 409; if the target interface is successfully invoked, step 410 is performed.
In an embodiment, whether the target interface is successfully called may be determined through a code field returned by the target interface, and if the code field is equal to 1, it indicates that the target interface is not successfully called, and step 409 is executed; if the code field is equal to 0, indicating that the target interface was successfully invoked, step 410 is performed.
Step 409: and sending error information to the client.
Step 410: and acquiring the output parameters of the target interface. For details, refer to the description of step 305 in the above embodiment.
Step 411: and sending the service processing result to the client according to the output parameter. See the description of step 306 in the above embodiment for details.
As shown in fig. 5, which is a schematic structural diagram of a data exchange device 500 according to an embodiment of the present application, the device can be applied to the electronic device 200 shown in fig. 2, and includes: the system comprises a receiving module 501, a first obtaining module 502, a determining module 503, a calling module 504, a second obtaining module 505, a first sending module 506, a first judging module 507, a checking module 508, a second sending module 509, a second judging module 510 and a third sending module 511. The principle relationship of the modules is as follows:
the receiving module 501 is configured to receive service request information sent by a client.
The first obtaining module 502 is configured to obtain, according to the service request information, interface information of a server corresponding to the service request information.
The determining module 503 is configured to determine the target interface and the input parameter of the target interface according to the interface information and the service request information.
And the calling module 504 is used for calling the target interface according to the input parameters.
And a second obtaining module 505, configured to obtain an output parameter of the target interface.
A first sending module 506, configured to send the service processing result to the client according to the output parameter.
The first determining module 507 is configured to determine whether the input parameter needs to be checked according to the service request information.
The checking module 508 is configured to check the input parameter according to a preset checking rule when the input parameter needs to be checked.
A second sending module 509, configured to send the verification result to the client when the input parameter is not verified.
And a second judging module 510, configured to judge whether the target interface is successfully called.
A third sending module 511, configured to send an error message to the client when the target interface is not successfully called.
In one embodiment, the verification module 508 is configured to: judging whether the field of the input parameter is in a preset range or not; if the field of the input parameter is in the preset range, the input parameter passes the verification; and if the field of the input parameter is not in the preset range, the input parameter is not checked.
In one embodiment, the first sending module 506 is configured to: carrying out format conversion on the output parameters to obtain standard data; screening the standard data according to the service request information to obtain target data; and sending the target data to the client.
For a detailed description of the data exchange device 500, please refer to the description of the related method steps in the above embodiments.
An embodiment of the present invention further provides a storage medium readable by an electronic device, including: a program that, when run on an electronic device, causes the electronic device to perform all or part of the procedures of the methods in the above-described embodiments. The storage medium may be a magnetic Disk, an optical Disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a Flash Memory (Flash Memory), a Hard Disk (Hard Disk Drive, abbreviated as HDD), a Solid State Drive (SSD), or the like. The storage medium may also comprise a combination of memories of the kind described above.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. The above description is only a preferred embodiment of the present application, and is only for the purpose of illustrating the technical solutions of the present application, and not for the purpose of limiting the present application. Any modification, equivalent replacement, improvement or the like, which would be obvious to one of ordinary skill in the art and would be within the spirit and principle of the present application, should be included within the scope of the present application.
Claims (10)
1. A method of data exchange, comprising:
receiving service request information sent by a client;
acquiring interface information of a server corresponding to the service request information according to the service request information;
determining a target interface and input parameters of the target interface according to the interface information and the service request information;
calling the target interface according to the input parameters;
acquiring output parameters of the target interface;
and sending a service processing result to the client according to the output parameter.
2. The method of claim 1, further comprising, after determining a target interface and input parameters of the target interface according to the interface information and the service request information:
judging whether the input parameters need to be checked or not according to the service request information;
when the input parameters need to be checked, checking the input parameters according to a preset checking rule, and judging whether the checking is passed;
and when the input parameter is not checked, sending a checking result to the client.
3. The method according to claim 2, wherein when the input parameter needs to be verified, verifying the input parameter according to a preset verification rule comprises:
judging whether the field of the input parameter is in a preset range or not;
if the field of the input parameter is in a preset range, the input parameter passes the verification;
and if the field of the input parameter is not in the preset range, the input parameter is not checked to be passed.
4. The method of claim 1, further comprising, after said invoking said target interface according to said input parameters:
judging whether the target interface is successfully called;
and when the target interface is not successfully called, sending error information to the client.
5. The method of claim 1, wherein sending the service processing result to the client according to the output parameter comprises:
carrying out format conversion on the output parameters to obtain standard data;
screening the standard data according to the service request information to obtain target data;
and sending the target data to the client.
6. A data exchange device, comprising:
the receiving module is used for receiving service request information sent by a client;
the first acquisition module is used for acquiring interface information of a server corresponding to the service request information according to the service request information;
the determining module is used for determining a target interface and input parameters of the target interface according to the interface information and the service request information;
the calling module is used for calling the target interface according to the input parameters;
the second acquisition module is used for acquiring the output parameters of the target interface;
and the first sending module is used for sending the service processing result to the client according to the output parameter.
7. The apparatus of claim 6, further comprising:
the first judgment module is used for judging whether the input parameters need to be checked according to the service request information;
the verification module is used for verifying the input parameters according to a preset verification rule when the input parameters need to be verified, and judging whether the verification is passed;
and the second sending module is used for sending the verification result to the client when the input parameter is not verified.
8. The apparatus of claim 6, further comprising:
the second judgment module is used for judging whether the target interface is successfully called;
and the third sending module is used for sending error information to the client when the target interface is not successfully called.
9. The apparatus of claim 6, wherein the first sending module is configured to:
carrying out format conversion on the output parameters to obtain standard data;
screening the standard data according to the service request information to obtain target data;
and sending the target data to the client.
10. An electronic device, comprising:
a memory to store a computer program;
a processor to perform the method of any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011041145.8A CN112148783A (en) | 2020-09-28 | 2020-09-28 | Data exchange method, device and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011041145.8A CN112148783A (en) | 2020-09-28 | 2020-09-28 | Data exchange method, device and equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112148783A true CN112148783A (en) | 2020-12-29 |
Family
ID=73894859
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011041145.8A Pending CN112148783A (en) | 2020-09-28 | 2020-09-28 | Data exchange method, device and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112148783A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114885026A (en) * | 2022-07-07 | 2022-08-09 | 飞狐信息技术（天津）有限公司 | Data interface request processing system, method, equipment and storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103297381A (en) * | 2012-02-22 | 2013-09-11 | 阿里巴巴集团控股有限公司 | Service access method based on plugin and system thereof |
| CN107888656A (en) * | 2017-10-09 | 2018-04-06 | 北京京东尚科信息技术有限公司 | Service the call method and calling device of end interface |
| CN109815013A (en) * | 2019-01-02 | 2019-05-28 | 深圳壹账通智能科技有限公司 | Business data processing method, device, computer equipment and storage medium |
| CN111092877A (en) * | 2019-12-12 | 2020-05-01 | 北京金山云网络技术有限公司 | Data processing method and device, electronic equipment and storage medium |
| CN111143404A (en) * | 2019-12-04 | 2020-05-12 | 北京城市网邻信息技术有限公司 | Service processing method and device |
| CN111221727A (en) * | 2019-12-30 | 2020-06-02 | 瑞庭网络技术（上海）有限公司 | Test method, test device, electronic equipment and computer readable medium |
| CN111625580A (en) * | 2020-04-22 | 2020-09-04 | 口碑(上海)信息技术有限公司 | Data processing method, device and equipment |
-
2020
- 2020-09-28 CN CN202011041145.8A patent/CN112148783A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103297381A (en) * | 2012-02-22 | 2013-09-11 | 阿里巴巴集团控股有限公司 | Service access method based on plugin and system thereof |
| CN107888656A (en) * | 2017-10-09 | 2018-04-06 | 北京京东尚科信息技术有限公司 | Service the call method and calling device of end interface |
| CN109815013A (en) * | 2019-01-02 | 2019-05-28 | 深圳壹账通智能科技有限公司 | Business data processing method, device, computer equipment and storage medium |
| CN111143404A (en) * | 2019-12-04 | 2020-05-12 | 北京城市网邻信息技术有限公司 | Service processing method and device |
| CN111092877A (en) * | 2019-12-12 | 2020-05-01 | 北京金山云网络技术有限公司 | Data processing method and device, electronic equipment and storage medium |
| CN111221727A (en) * | 2019-12-30 | 2020-06-02 | 瑞庭网络技术（上海）有限公司 | Test method, test device, electronic equipment and computer readable medium |
| CN111625580A (en) * | 2020-04-22 | 2020-09-04 | 口碑(上海)信息技术有限公司 | Data processing method, device and equipment |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114885026A (en) * | 2022-07-07 | 2022-08-09 | 飞狐信息技术（天津）有限公司 | Data interface request processing system, method, equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7860897B2 (en) | Optimized method of locating complete aggregation of patient health records in a global domain | |
| US20030074248A1 (en) | Method and system for assimilating data from disparate, ancillary systems onto an enterprise system | |
| US11126627B2 (en) | System and method for dynamic transactional data streaming | |
| WO2002048831A2 (en) | Method, apparatus, and system for aggregating, targeting, and synchronizing health information delivery | |
| US11533387B2 (en) | Interface engine architecture | |
| CN114172829B (en) | Server health monitoring method and system and computing equipment | |
| EP2232775A1 (en) | Dynamic communication stack | |
| CN112054915B (en) | Processing method, device and system for client exception pre-warning and computing equipment | |
| US20100198948A1 (en) | Dynamic web service deployment and integration | |
| CN110969417B (en) | Government affair item synchronization method, device, system, computer equipment and storage medium | |
| CN112148783A (en) | Data exchange method, device and equipment | |
| US11269856B2 (en) | Methods, apparatuses, and systems for ingesting and consuming data utilizing a trading partner manager | |
| CN114880194B (en) | Service abnormity monitoring method and device, electronic equipment and computer storage medium | |
| Cruz et al. | Using OPC and HL7 standards to incorporate an industrial Big Data historian in a health IT environment | |
| CN116627758A (en) | Method, device, equipment and medium for reporting abnormality of front-end system of Internet hospital | |
| US20160063077A1 (en) | Data brokering system for fulfilling data requests to multiple data providers | |
| US20160267230A1 (en) | Touchless processing | |
| US9313272B2 (en) | Information processor and information processing method | |
| US20110099436A1 (en) | Expedited transaction failure handling by leveraging a reliable message transport protocol to assist detection of discarded processing | |
| CA2861754A1 (en) | Data brokering system for fulfilling data requests to multiple data providers | |
| CN111741118B (en) | Interface calling method, device, computer equipment and computer readable storage medium | |
| US9519754B2 (en) | Apparatuses and methods for parallel analytics | |
| CN113779128B (en) | Medical data system docking method, device, equipment and storage medium | |
| CN109543948B (en) | Follow-up examination method, device, server and medium based on data analysis | |
| US20220100750A1 (en) | Data shape confidence |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20201229 |