CN114388117A - Data transmission method and device of medical platform - Google Patents
Data transmission method and device of medical platform Download PDFInfo
- Publication number
- CN114388117A CN114388117A CN202210043932.9A CN202210043932A CN114388117A CN 114388117 A CN114388117 A CN 114388117A CN 202210043932 A CN202210043932 A CN 202210043932A CN 114388117 A CN114388117 A CN 114388117A
- Authority
- CN
- China
- Prior art keywords
- interface
- data
- platform
- party
- interfaces
- 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
Images
Classifications
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
- G16H40/40—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the management of medical equipment or devices, e.g. scheduling maintenance or upgrades
-
- 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
- G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
- G16H40/60—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices
- G16H40/67—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices for remote operation
Landscapes
- Health & Medical Sciences (AREA)
- Engineering & Computer Science (AREA)
- Biomedical Technology (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Epidemiology (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Primary Health Care (AREA)
- Public Health (AREA)
- Medical Treatment And Welfare Office Work (AREA)
Abstract
The invention provides a data transmission method and a data transmission device for a medical platform, wherein the method comprises the following steps: receiving a data transmission request initiated by a medical platform through a first interface in a plurality of standard interfaces, wherein the data transmission request is used for requesting data transmission with a target platform in a plurality of third party platforms, and the third party platforms are platforms for providing data storage service; querying a second interface matched with the first interface in a plurality of third-party interfaces of the target platform; the first interface and the second interface are utilized to complete data transmission between the medical platform and the target platform, and the problem of low data processing efficiency in the prior art is solved.
Description
Technical Field
The invention relates to the field of medical data processing, in particular to a data transmission method and device of a medical platform.
Background
In the information management of the medical institution, the medical data of the medical institution is present in the HIS system of the medical institution or other medical systems, when the three-party platform is docked, data exchange must exist between the HIS system and the HIS system, the data are usually acquired through a storage interface, a wbservice interface and an http interface which are provided by the HIS system, the operation is simple in nature, and the problem of data connection must be solved if the work flow is smooth.
1) If one party has data format change in the midway, both parties need to modify codes, which wastes time and labor and has great influence on the system which is already put into use;
2) there are currently multiple his manufacturers on the market, and due to the differences between his systems, there are two solutions for docking each hospital: one is that a set of system is redeveloped to carry out data interaction every time a his of a hospital is docked, and the scheme has long time period and large time and economic cost; because the open interface is not easy or the cost is not accepted in budget, the simplest and most direct mode is that data is input manually, but medical staff do the work of re-entry, although the cost is saved, the cost of labor and time is high due to the large data volume, and the accuracy cannot be ensured.
Disclosure of Invention
The invention mainly aims to provide a data transmission method and a data transmission device of a medical platform, and aims to solve the problem that the data processing efficiency is low in the prior art.
In order to achieve the above object, according to an aspect of the present invention, there is provided a data transmission method of a medical platform, including: receiving a data transmission request initiated by a medical platform through a first interface of a plurality of standard interfaces, wherein the data transmission request is used for requesting data transmission with a target platform of a plurality of third party platforms, and the third party platforms are platforms for providing data storage service; querying a second interface matched with the first interface in a plurality of third-party interfaces of the target platform; and the data transmission between the medical platform and the target platform is completed by utilizing the first interface and the second interface.
Optionally, the data transmission between the medical platform and the target platform is completed by using the first interface and the second interface, including: receiving first data which is sent by a medical platform and meets the requirements of a first interface at the first interface; converting the first data into second data meeting the requirements of a second interface according to a field mapping relation between the first interface and the second interface; and sending the second data to the target platform through the second interface.
Optionally, the data transmission between the medical platform and the target platform is completed by using the first interface and the second interface, including: receiving third data which is sent by the target platform and meets the requirements of the second interface at the second interface; converting the third data into fourth data meeting the requirements of the first interface according to the field mapping relation between the second interface and the first interface; and transmitting the fourth data to the medical platform through the first interface.
Optionally, querying a second interface, which is matched with the first interface, in the plurality of third-party interfaces of the target platform includes: and querying a second interface matched with the first interface in the plurality of third-party interfaces of the target platform in the interface mapping table.
Optionally, before querying a second interface matching the first interface in the plurality of third-party interfaces of the target platform, the method further includes: creating a plurality of standard interfaces, wherein the plurality of standard interfaces are interfaces used by a medical platform, and each standard interface is used for processing one type of data; acquiring all third party interfaces of each third party platform, wherein each third party interface is used for processing one type of data; and creating an association relationship between the plurality of standard interfaces and all third-party interfaces of each third-party platform to obtain an interface mapping table, wherein the standard interfaces processing the same type of data have the association relationship with the third-party interfaces in the interface mapping table.
Optionally, a plurality of standard interfaces is created, including: standard interfaces are created that support fetching lists, fetching multi-values, fetching single values, performing actions, and enumerating transformations.
Optionally, a plurality of standard interfaces is created, including: a standard interface with extension fields is created.
In order to achieve the above object, according to one aspect of the present invention, there is provided a data transmission device of a medical platform, comprising: the medical platform comprises a receiving unit, a data transmission unit and a data storage unit, wherein the receiving unit is used for receiving a data transmission request initiated by the medical platform through a first interface in a plurality of standard interfaces, the data transmission request is used for requesting data transmission with a target platform in a plurality of third party platforms, and the third party platforms are platforms for providing data storage service; the query unit is used for querying a second interface matched with the first interface in a plurality of third-party interfaces of the target platform; and the transmission unit is used for completing data transmission between the medical platform and the target platform by utilizing the first interface and the second interface.
Optionally, when the data transmission between the medical platform and the target platform is completed by using the first interface and the second interface, the transmission unit is further configured to: receiving first data which is sent by a medical platform and meets the requirements of a first interface at the first interface; converting the first data into second data meeting the requirements of a second interface according to a field mapping relation between the first interface and the second interface; and sending the second data to the target platform through the second interface.
Optionally, when the data transmission between the medical platform and the target platform is completed by using the first interface and the second interface, the transmission unit is further configured to: receiving third data which is sent by the target platform and meets the requirements of the second interface at the second interface; converting the third data into fourth data meeting the requirements of the first interface according to the field mapping relation between the second interface and the first interface; and transmitting the fourth data to the medical platform through the first interface.
Optionally, when querying a second interface matching the first interface in the plurality of third-party interfaces of the target platform, the querying unit is further configured to: and querying a second interface matched with the first interface in the plurality of third-party interfaces of the target platform in the interface mapping table.
Optionally, before querying a second interface matching the first interface in the plurality of third-party interfaces of the target platform, the querying unit is further configured to: creating a plurality of standard interfaces, wherein the plurality of standard interfaces are interfaces used by a medical platform, and each standard interface is used for processing one type of data; acquiring all third party interfaces of each third party platform, wherein each third party interface is used for processing one type of data; and creating an association relationship between the plurality of standard interfaces and all third-party interfaces of each third-party platform to obtain an interface mapping table, wherein the standard interfaces processing the same type of data have the association relationship with the third-party interfaces in the interface mapping table.
Optionally, the creating unit, when creating the plurality of standard interfaces, is further configured to: standard interfaces are created that support fetching lists, fetching multi-values, fetching single values, performing actions, and enumerating transformations.
Optionally, the creating unit, when creating the plurality of standard interfaces, is further configured to: a standard interface with extension fields is created.
According to another aspect of the embodiments of the present application, there is also provided a storage medium including a stored program which, when executed, performs the above-described method.
According to another aspect of the embodiments of the present application, there is also provided an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor executes the above method through the computer program.
According to an aspect of the application, a computer program product or computer program is provided, comprising computer instructions, the computer instructions being stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to cause the computer device to perform the steps of any of the embodiments of the method described above.
By applying the technical scheme of the invention, a data transmission request initiated by a medical platform is received through a first interface in a plurality of standard interfaces, wherein the data transmission request is used for requesting data transmission with a target platform in a plurality of third party platforms, and the third party platforms are platforms for providing data storage service; querying a second interface matched with the first interface in a plurality of third-party interfaces of the target platform; the data transmission between the medical platform and the target platform is completed by utilizing the first interface and the second interface, a standard interface of the medical platform (a service product needing to be in butt joint with a third party) can be defined, the supply service of a common third party service manufacturer is built in, and mapping configuration is established, so that a mapping configuration function of supplying service standardization conversion is provided, an interface service can be quickly established without writing codes, and the problem of low data processing efficiency in the prior art can be solved.
In addition to the objects, features and advantages described above, other objects, features and advantages of the present invention are also provided. The present invention will be described in further detail below with reference to the drawings.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, are included to provide a further understanding of the invention, and are incorporated in and constitute a part of this specification, illustrate exemplary embodiments of the invention and together with the description serve to explain the invention and not to limit the invention. In the drawings:
FIG. 1 is a flow chart of an alternative medical platform data transfer method according to an embodiment of the present application;
FIG. 2 is a schematic illustration of an alternative medical platform configuration according to an embodiment of the present application;
FIG. 3 is a schematic illustration of an alternative medical platform mapping service according to an embodiment of the present application;
FIG. 4 is a schematic illustration of an alternative medical platform mapping service according to an embodiment of the present application; and
fig. 5 is a schematic diagram of an alternative medical platform data transfer device according to an embodiment of the present application.
Detailed Description
In order to make the technical solutions better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only partial embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
It should be noted that the terms "first," "second," and the like in the description and claims of this application and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations 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, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
According to an aspect of embodiments of the present application, there is provided method embodiments of a data transmission method of a medical platform.
Fig. 1 is a flowchart of a data transmission method of an alternative medical platform according to an embodiment of the present application, and as shown in fig. 1, the method may include the following steps:
step S102, receiving a data transmission request initiated by a medical platform through a first interface of a plurality of standard interfaces, wherein the data transmission request is used for requesting data transmission with a target platform of a plurality of third party platforms, and the third party platforms are platforms for providing data storage service. The standard interface is commonly used for acquiring examination items, patient information, department lists, hospitalization information and the like, and is created according to the service interface definition provided by the his manufacturer.
And step S104, inquiring a second interface matched with the first interface in a plurality of third-party interfaces of the target platform.
A plurality of standard interfaces can be created firstly, wherein the plurality of standard interfaces are interfaces used by a medical platform, each standard interface is used for processing one type of data, the standard interfaces support list taking, multi-value taking, single value taking, action execution and enumeration conversion, and the standard interfaces are provided with extension fields; acquiring all third party interfaces of each third party platform, wherein each third party interface is used for processing one type of data; and establishing an association relationship between a plurality of standard interfaces and all third-party interfaces of each third-party platform to obtain an interface mapping table, wherein the standard interfaces for processing the same type of data and the third-party interfaces have the association relationship in the interface mapping table. According to the mapping configuration, after the configuration is finished, the standard interface is directly called, and the standard interface is called through the http standard.
After the creation is completed, a second interface matched with the first interface in the plurality of third-party interfaces of the target platform can be queried in the interface mapping table.
And S106, completing data transmission between the medical platform and the target platform by utilizing the first interface and the second interface.
The scheme mainly comprises a sending scheme and an interface, wherein the sending scheme is as follows: receiving first data which is sent by a medical platform and meets the requirements of a first interface at the first interface; converting the first data into second data meeting the requirements of a second interface according to a field mapping relation between the first interface and the second interface; and sending the second data to the target platform through the second interface.
The scheme of reception is as follows: receiving third data which is sent by the target platform and meets the requirements of the second interface at the second interface; converting the third data into fourth data meeting the requirements of the first interface according to the field mapping relation between the second interface and the first interface; and transmitting the fourth data to the medical platform through the first interface.
Through the steps, a data transmission request initiated by the medical platform is received through a first interface in a plurality of standard interfaces, wherein the data transmission request is used for requesting data transmission with a target platform in a plurality of third party platforms, and the third party platforms are platforms for providing data storage service; querying a second interface matched with the first interface in a plurality of third-party interfaces of the target platform; the data transmission between the medical platform and the target platform is completed by utilizing the first interface and the second interface, a standard interface of the medical platform (a service product needing to be in butt joint with a third party) can be defined, the supply service of a common third party service manufacturer is built in, and mapping configuration is established, so that a mapping configuration function of supplying service standardization conversion is provided, an interface service can be quickly established without writing codes, and the problem of low data processing efficiency in the prior art can be solved. The technical solution of the present application is further detailed below with reference to specific steps, as shown in fig. 2 to 4 (the characters in the figures are only used for schematic illustration):
step 1, providing a standard interface, wherein the standard interface is a standard interface customized by a platform product according to service requirements.
A corresponding standard interface is created in the platform according to the access of messages provided by his manufacturers, the access of lists, multiple values, single values, execution actions, enumeration conversion and the like are supported, an extension field is provided for the change field of the used system his, and zero codes are achieved only by page configuration.
Step 2, providing a provisioning service: interface services provided by three-party systems such as HIS, LIS, PACS and the like are called as 'supply services', and the supply services support four types of sql, sp, http and wbservice in the market.
Step 2.1, the manufacturer is created.
Step 2.2, the provisioning service connection address is configured.
And 2.3, establishing a supply service interface, configuring access parameters and supporting message posting.
And 3, interface mapping, namely realizing the standardized conversion of the supply interface by configuring the mapping relation between the supply interface field and the standard interface field.
And configuring a mapping relation between fields of a standard interface and fields of a supply interface, setting the mapping relation to support automatic matching, and enabling the standard interface to access a plurality of supply services.
And 4, accessing services, and mapping the control standard interface to different supply services in different hospitals or different courtyards. And the courtyard area is accessed and switched according to the self condition.
And 5, constructing a service, namely publishing the Sql or Sp into a standard service interface, or publishing the interface service of a third party into the standard interface, and endowing the interface with safety control capability.
It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present application is not limited by the order of acts described, as some steps may occur in other orders or concurrently depending on the application. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required in this application.
Through the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but the former is a better implementation mode in many cases. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present application.
According to another aspect of the embodiment of the application, an apparatus for implementing the method is also provided. Fig. 5 is a schematic diagram of an alternative medical platform data transmission device according to an embodiment of the present application, and as shown in fig. 5, the device may include:
the receiving unit 21 is configured to receive a data transmission request initiated by the medical platform through a first interface of a plurality of standard interfaces, where the data transmission request is used to request data transmission with a target platform of a plurality of third party platforms, and the third party platform is a platform providing data storage service; the query unit 23 is configured to query a second interface, which is matched with the first interface, in the plurality of third-party interfaces of the target platform; and the transmission unit 25 is used for completing data transmission between the medical platform and the target platform by using the first interface and the second interface.
Optionally, when the data transmission between the medical platform and the target platform is completed by using the first interface and the second interface, the transmission unit is further configured to: receiving first data which is sent by the medical platform and meets the requirements of the first interface at the first interface; converting the first data into second data meeting the requirements of the second interface according to a field mapping relation between the first interface and the second interface; and sending the second data to the target platform through the second interface.
Optionally, when the data transmission between the medical platform and the target platform is completed by using the first interface and the second interface, the transmission unit is further configured to: receiving third data which is sent by the target platform and meets the requirements of the second interface at the second interface; converting the third data into fourth data meeting the requirements of the first interface according to a field mapping relation between the second interface and the first interface; sending the fourth data to the medical platform through the first interface.
Optionally, when querying a second interface matching the first interface in the plurality of third-party interfaces of the target platform, the querying unit is further configured to: and querying a second interface matched with the first interface in a plurality of third-party interfaces of the target platform in an interface mapping table.
Optionally, before querying a second interface matching the first interface in the plurality of third-party interfaces of the target platform, the querying unit is further configured to: creating the plurality of standard interfaces, wherein the plurality of standard interfaces are interfaces used by a medical platform, and each standard interface is used for processing one type of data; acquiring all third party interfaces of each third party platform, wherein each third party interface is used for processing data of one type; and creating an association relationship between the plurality of standard interfaces and all third-party interfaces of each third-party platform to obtain the interface mapping table, wherein the standard interfaces processing the same type of data and the third-party interfaces have the association relationship in the interface mapping table.
Optionally, the creating unit, when creating the plurality of standard interfaces, is further configured to: standard interfaces are created that support fetching lists, fetching multi-values, fetching single values, performing actions, and enumerating transformations.
Optionally, the creating unit, when creating the plurality of standard interfaces, is further configured to: creating the standard interface with an extension field.
It should be noted here that the modules described above are the same as the examples and application scenarios implemented by the corresponding steps, but are not limited to the disclosure of the above embodiments. The modules may be implemented by software as part of the apparatus, or may be implemented by hardware.
Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments, and this embodiment is not described herein again.
Optionally, in this embodiment, the storage medium may include, but is not limited to: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.
The above-mentioned serial numbers of the embodiments of the present application are merely for description and do not represent the merits of the embodiments.
The integrated unit in the above embodiments, if implemented in the form of a software functional unit and sold or used as a separate product, may be stored in the above computer-readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or a part of or all or part of the technical solution contributing to the prior art may be embodied in the form of a software product stored in a storage medium, and including instructions for causing one or more computer devices (which may be personal computers, servers, network devices, or the like) to execute all or part of the steps of the method described in the embodiments of the present application.
In the above embodiments of the present application, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
In the several embodiments provided in the present application, it should be understood that the disclosed client may be implemented in other manners. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one type of division of logical functions, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, units or modules, and may be in an electrical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The foregoing is only a preferred embodiment of the present application and it should be noted that those skilled in the art can make several improvements and modifications without departing from the principle of the present application, and these improvements and modifications should also be considered as the protection scope of the present application.
Claims (10)
1. A data transmission method of a medical platform is characterized by comprising the following steps:
receiving a data transmission request initiated by the medical platform through a first interface of a plurality of standard interfaces, wherein the data transmission request is used for requesting data transmission with a target platform of a plurality of third party platforms, and the third party platforms are platforms for providing data storage service;
querying a second interface matched with the first interface in a plurality of third-party interfaces of the target platform;
and completing data transmission between the medical platform and the target platform by utilizing the first interface and the second interface.
2. The method of claim 1, wherein using the first interface and the second interface to complete the data transfer between the medical platform and the target platform comprises:
receiving first data which is sent by the medical platform and meets the requirements of the first interface at the first interface;
converting the first data into second data meeting the requirements of the second interface according to a field mapping relation between the first interface and the second interface;
and sending the second data to the target platform through the second interface.
3. The method of claim 1, wherein using the first interface and the second interface to complete the data transfer between the medical platform and the target platform comprises:
receiving third data which is sent by the target platform and meets the requirements of the second interface at the second interface;
converting the third data into fourth data meeting the requirements of the first interface according to a field mapping relation between the second interface and the first interface;
sending the fourth data to the medical platform through the first interface.
4. The method of claim 1, wherein querying a second interface of the plurality of third party interfaces of the target platform that matches the first interface comprises:
and querying a second interface matched with the first interface in a plurality of third-party interfaces of the target platform in an interface mapping table.
5. The method of claim 4, wherein prior to querying a second interface of the plurality of third party interfaces of the target platform that matches the first interface, the method further comprises:
creating the plurality of standard interfaces, wherein the plurality of standard interfaces are interfaces used by a medical platform, and each standard interface is used for processing one type of data;
acquiring all third party interfaces of each third party platform, wherein each third party interface is used for processing data of one type;
and creating an association relationship between the plurality of standard interfaces and all third-party interfaces of each third-party platform to obtain the interface mapping table, wherein the standard interfaces processing the same type of data and the third-party interfaces have the association relationship in the interface mapping table.
6. The method of claim 5, wherein creating the plurality of standard interfaces comprises:
standard interfaces are created that support fetching lists, fetching multi-values, fetching single values, performing actions, and enumerating transformations.
7. The method of claim 5, wherein creating the plurality of standard interfaces comprises:
creating the standard interface with an extension field.
8. A data transfer device for a medical platform, comprising:
the medical platform comprises a receiving unit, a data transmission unit and a data storage unit, wherein the receiving unit is used for receiving a data transmission request initiated by the medical platform through a first interface in a plurality of standard interfaces, the data transmission request is used for requesting data transmission with a target platform in a plurality of third party platforms, and the third party platforms are platforms for providing data storage service;
the query unit is used for querying a second interface matched with the first interface in a plurality of third-party interfaces of the target platform;
and the transmission unit is used for completing data transmission between the medical platform and the target platform by utilizing the first interface and the second interface.
9. A storage medium, characterized in that the storage medium comprises a stored program, wherein the program when executed performs the method of any of the preceding claims 1 to 7.
10. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor executes the method of any of the preceding claims 1 to 7 by means of the computer program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210043932.9A CN114388117A (en) | 2022-01-14 | 2022-01-14 | Data transmission method and device of medical platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210043932.9A CN114388117A (en) | 2022-01-14 | 2022-01-14 | Data transmission method and device of medical platform |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114388117A true CN114388117A (en) | 2022-04-22 |
Family
ID=81202642
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210043932.9A Pending CN114388117A (en) | 2022-01-14 | 2022-01-14 | Data transmission method and device of medical platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114388117A (en) |
-
2022
- 2022-01-14 CN CN202210043932.9A patent/CN114388117A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108021710B (en) | Dynamic interface conversion method, device, terminal equipment and storage medium | |
| US11288725B2 (en) | Managing service provider service options | |
| CN101159730B (en) | Information processing method, system and device of multimedia affiliation center | |
| US9491125B2 (en) | System and method for multi-channel delivery of transformed and augmented messages in real-time | |
| CN106792653A (en) | A kind of communicating number information processing method, apparatus and system | |
| CN110969001A (en) | Feedback information generation method and device, storage medium, processor and terminal | |
| CN110825807A (en) | Data interaction conversion method, device, equipment and medium based on artificial intelligence | |
| CN112052267B (en) | Data query method, equipment, server and storage medium | |
| CN106998314B (en) | Account interaction method and device | |
| CN115526160A (en) | Rich text processing method, device and equipment and storage medium | |
| CN114388117A (en) | Data transmission method and device of medical platform | |
| US8856204B2 (en) | Managing service provider messaging | |
| CN105338202A (en) | Communication processing method and device | |
| CN110858201A (en) | Data processing method and system, processor and storage medium | |
| CN113312190A (en) | Cooperative processing method and device for government affair service business | |
| CN104427380B (en) | A kind of information processing method, electronic equipment and system | |
| CN111506646A (en) | Data synchronization method, device, system, storage medium and processor | |
| US8386452B2 (en) | Data combination system and data combination method | |
| CN110969410A (en) | Contract sharing method and device and storage medium | |
| CN117472477A (en) | Micro-service calling method, platform, device, terminal equipment and readable storage medium | |
| CN111090530A (en) | Distributed cross-interprocess communication bus system | |
| CN111417109B (en) | eSIM card and operator file management method and management system thereof | |
| CN114006939A (en) | Message pushing method and device | |
| WO2016202030A1 (en) | Resource configuration loading method and apparatus | |
| CN105207980A (en) | Information processing method and electronic equipment |
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 |