CN112582036A - Medical data exchange platform - Google Patents
Medical data exchange platform Download PDFInfo
- Publication number
- CN112582036A CN112582036A CN201910942328.8A CN201910942328A CN112582036A CN 112582036 A CN112582036 A CN 112582036A CN 201910942328 A CN201910942328 A CN 201910942328A CN 112582036 A CN112582036 A CN 112582036A
- Authority
- CN
- China
- Prior art keywords
- data
- message
- uploaded
- medical
- verification
- 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
- 238000012545 processing Methods 0.000 claims abstract description 30
- 238000012546 transfer Methods 0.000 claims abstract description 23
- 238000012795 verification Methods 0.000 claims description 34
- 230000006978 adaptation Effects 0.000 claims description 28
- 238000000034 method Methods 0.000 claims description 20
- 238000013524 data verification Methods 0.000 claims description 14
- 238000005538 encapsulation Methods 0.000 claims description 11
- 238000004140 cleaning Methods 0.000 claims description 6
- 238000013075 data extraction Methods 0.000 claims description 5
- 238000013500 data storage Methods 0.000 claims description 5
- 238000004806 packaging method and process Methods 0.000 claims description 3
- 230000036541 health Effects 0.000 description 6
- 238000010586 diagram Methods 0.000 description 4
- 230000000694 effects Effects 0.000 description 4
- 230000002452 interceptive effect Effects 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 3
- 238000011161 development Methods 0.000 description 3
- 238000010276 construction Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 238000012550 audit Methods 0.000 description 1
- 230000002457 bidirectional effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 238000007418 data mining Methods 0.000 description 1
- 238000012938 design process Methods 0.000 description 1
- 238000003745 diagnosis Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 230000005180 public health Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H10/00—ICT specially adapted for the handling or processing of patient-related medical or healthcare data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/324—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the data link layer [OSI layer 2], e.g. HDLC
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Health & Medical Sciences (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 relates to the technical field of data, in particular to a medical data exchange platform, which comprises: registering and auditing the identity information, and if the identity information passes the auditing, uploading the data or lifting the query request; performing data processing on the uploaded data to form a release message; performing first data transfer on the release message; and routing the message according to the query request, extracting the release message after the first data transfer, performing second data transfer, and sending the transferred release message to the query requester. According to the medical data exchange platform, the uploaded data are subjected to data processing and first data transfer, so that formats of the data uploaded by different systems are uniformly converted and stored in the medical data exchange platform, and the data stored in the medical data exchange platform are analyzed through second data transfer, so that a query requester can read the data information conveniently, data exchange and sharing among different systems are realized, and the efficiency and stability of data exchange are improved.
Description
Technical Field
The invention relates to the technical field of data, in particular to a medical data exchange platform.
Background
With the advancement of the national medical reform, the construction of medical and health informatization is more and more concerned by people inside and outside the industry, and the sharing demand of medical data resources is very urgent.
At present, a large number of new and old technologies and new and old manufacturers are staggered in the information-based construction process, and due to the situation of multi-head competition, information systems of different versions are charged by different companies. Therefore, the functional effects of the information systems are different, the data structures of the information systems owned by the medical institutions in the medical combination are difficult to unify, and the sharing and the exchange of heterogeneous data generated after the medical institutions are communicated cannot be realized.
Disclosure of Invention
In view of the problem that the heterogeneous data among the medical institutions cannot be exchanged and shared, the invention provides a medical data exchange platform which can convert the heterogeneous data formats of different systems into the same format and analyze the same format when the medical data exchange platform is required to be used, so that the data exchange and the data sharing are realized.
In order to achieve the above purpose, the embodiment of the invention adopts the following technical scheme:
in a first aspect, the present invention provides a medical data exchange method, including: verifying the registered identity information, and if the verification is passed, uploading data or lifting a query request; performing data processing on the uploaded data to form a release message; performing first data transfer on the release message; and routing the message according to the query request, extracting the release message after the first data transfer, performing second data transfer, and sending the transferred release message to the query requester.
According to one aspect of the invention, the specific step of performing data processing on the uploaded data to form the publishing message comprises: verifying the standardization of a service system with data uploading requirements; if the verification is a standardized system, the uploaded data is verified through the front-end adaptation system, and the uploaded data passing the verification is used as a release message; and if the verification is a non-standardized system, performing first data processing on the data through the pre-adaptation system to form a release message.
According to one aspect of the invention, the specific steps of checking the uploaded data through the pre-adaptation system and using the checked uploaded data as the release message include: extracting the uploaded data through a front-end adaptation system and verifying the uploaded data; if the verification is successful, outputting the uploaded data and taking the uploaded data as a release message; and if the verification fails, returning the uploaded data to the pre-adaptation system.
According to one aspect of the invention, the specific step of performing the first data processing on the data by the pre-adaptation system to form the publishing message comprises: extracting the uploaded data through a front adaptation system and carrying out data verification on the uploaded data; carrying out data cleaning on the uploaded data which is qualified in verification; storing the cleaned uploaded data; and performing message encapsulation on the stored uploaded data to form a release message.
According to one aspect of the present invention, the step of performing the first data forwarding on the release message includes: receiving the release message and judging whether to forward the release message; if the message needs to be forwarded, sending the message to a lift query requester; if the message does not need to be forwarded, the issued message is analyzed, and the analyzed data is stored in the database.
According to one aspect of the present invention, the specific steps of routing a message according to an inquiry request, extracting a post-transfer publication message from first data, and sending the post-transfer publication message to an inquiry requester include: receiving a query request; matching the query request with the service ID in the routing relation table to determine a routing path; extracting the published message after the first data transfer through a routing path and assembling; and sending the assembled message to a query requester.
According to one aspect of the invention, the medical data exchange method further comprises: whether the issuing message sent to the inquiry requester is successfully sent is verified, and if the issuing message is successfully sent, data exchange is ended; and if the failure occurs, the forwarding is carried out again.
In a second aspect, the present invention provides a medical data exchange architecture comprising: the data layer is configured to collect data and perform data processing on the data; the exchange layer is configured to exchange the data after the data processing is carried out on the data layer or analyze and store the data after the data processing is carried out on the data layer; and the application layer is configured to call and store the data stored in the exchange layer according to the requirement.
In accordance with one aspect of the invention, a data layer is configured to include a pre-adaptation system and a heterogeneous information system, wherein: the heterogeneous information system performs data extraction, data verification, data cleaning, data storage and message encapsulation on the data, or analyzes the data and stores the analyzed data; and the heterogeneous information system performs data exchange on the data processed by the pre-adaptation system.
In a third aspect, the present invention provides a medical data exchange system, which includes an authentication module, a data acquisition module, a data verification module, a message encapsulation module, a pre-data center module, and an exchange center, wherein: the identity authentication module is used for authenticating the identity information of the user; the data acquisition module is used for acquiring data uploaded by a user with qualified identity information verification; the data checking module is used for carrying out format checking on the data acquired by the data acquisition module so as to remove the data with unqualified format; the message packaging module is used for converting the data successfully verified by the data verification module into messages and storing the messages in a database; the prepositive data center module is used for backing up standardized data and providing a data source when a message is constructed; the switching center is used for providing a plurality of service interfaces for the inquiry requester to call and store the messages stored in the database.
The implementation of the invention has the advantages that: through auditing the registered identity, the safety of personal information is enhanced, and information leakage is avoided; the data processing and the first data transfer are carried out on the uploaded data, so that formats of the data uploaded by different systems are converted uniformly and stored in the medical data exchange platform, and then the data stored in the medical data exchange platform are analyzed through the second data transfer, so that an inquiry requester can read the data information conveniently, the data exchange and sharing among different systems are realized, the data exchange efficiency is improved, the stable operation is ensured on the basis of not influencing the field working environment, and early warning can be timely given and correct processing can be given when a network connection error or the platform stops working normally and data errors or loss occurs in the data transmission process.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without creative efforts.
Fig. 1 is a flowchart of a medical data exchange method according to an embodiment of the present invention;
fig. 2 is a diagram of a medical data exchange architecture according to an embodiment of the present invention;
fig. 3 is a structural diagram of a medical data exchange system according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the 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 invention.
A medical data exchange platform is illustrated below in conjunction with fig. 1-3.
Embodiment 1, as shown in fig. 1, fig. 1 is a flowchart of a medical data exchange method according to an embodiment of the present invention, where the medical data exchange method includes the following steps:
and S1, verifying the registered identity information, and if the verification is passed, uploading data or lifting the query request.
Generally, business requirements in a hospital need to be analyzed, diagnosis and treatment business processes need to be combed, a medical process-oriented service directory and a service library are established, and the services and metadata of the services are defined and stored so as to perform operations such as searching, publishing, registering, managing and the like on the services. In this embodiment, the medical data exchange platform includes a data uploader, an exchange center and a query requester, the data uploader issues data and uploads the data to the exchange center for storage or transfer, the query requester calls the data in the exchange center according to actual requirements, in order to facilitate management and avoid privacy disclosure, the data uploader and the query requester firstly perform identity and/or service registration, the exchange center performs verification on the identity and/or service registration, the data uploader can upload the data only after the verification is passed, and the query requester can extract the query request to query the data; and returning a feedback message of the failure of the audit to the query requester or the data uploader.
And S2, performing data processing on the uploaded data to form a publishing message.
In this embodiment, the specific step of performing data processing on the uploaded data to form the release message includes: verifying the standardization of a service system with data uploading requirements; if the verification is a standardized system, the uploaded data is verified through the front-end adaptation system, and the uploaded data passing the verification is used as a release message; and if the verification is a non-standardized system, performing first data processing on the data through the pre-adaptation system to form a release message.
Generally, in the medical field, the importance is paid to standardized heterogeneity, and a part of standardized business systems and a part of non-standardized business systems exist in the region. The standardization means that all data formats, data types and interaction modes meet national standards, and non-standardized systems which do not meet the requirements. Due to the difference of standardization, an adapter is configured in front of a system which does not meet the national health information standard, and is mainly used for the standardization of data and the assembly and sending of messages. The standardized service system adapter mainly plays a role in checksum message sending.
Specifically, when the verification is a standardized system, the uploaded data is verified through the pre-adaptation system, and the specific step of taking the verified uploaded data as the release message comprises the steps of extracting the uploaded data through the pre-adaptation system and verifying the uploaded data; if the verification is successful, outputting the uploaded data and taking the uploaded data as a release message; and if the verification fails, returning the uploaded data to the pre-adaptation system. When the system is verified to be a non-standardized system, the specific step of performing first data processing on the data through the pre-adaptation system to form the release message comprises the following steps: extracting the uploaded data through a front adaptation system and carrying out data verification on the uploaded data; carrying out data cleaning on the uploaded data which is qualified in verification; storing the cleaned uploaded data; and performing message encapsulation on the stored uploaded data to form a release message. In the application, different medical information manufacturers often develop different medical information systems on different platforms by using different development tools, and different information systems store and transmit data by using different data formats such as JAVA, XML, CSV, HL7 and the like, so that the medical information systems are accessed to a data exchange platform, and bidirectional conversion between different data formats of the systems and an XML format unified by the platform is completed through message encapsulation.
More specifically, the specific flow of data extraction includes receiving the form of the data military XML file uploaded by the data uploader and storing the data military XML file into a corresponding folder, if the data military XML file is successfully received, returning a confirmation message to the message sender, and if the data military XML file is failed, requesting retransmission; judging whether a folder for storing the received message is empty, if not, reading the XML files in batches, and if so, waiting for receiving the message; the received message is analyzed, cleaned, mapped and the like; storing the processed message fields into a platform central database; and transferring the processed files to corresponding transit folders, and regularly clearing the processed message files in the transit folders.
In this embodiment, the data verification is mainly a verification of a data format, a data structure, and a data type, and is a necessary process of standardization work. Data verification is mainly divided into two types, namely a non-standardized system which does not meet service specifications, and a standardized system which meets platform service specifications. The data extraction of the non-standardized system adopts a direct database capture mode, the acquired data needs to be firstly subjected to data format verification and then assembled into a standard message, and then the message structure is verified. The standardized system firstly checks the message structure and then checks the data format and data type. The step of verifying the standardized system data comprises the following steps: checking the message structure, directly returning a checking result if the checking is unsuccessful, stopping checking, and circularly reading each data element if the structure is successfully checked; judging whether the data element is the last data element of the message, if so, finishing the circulation, returning a verification result, finishing the verification, if not, sequentially verifying the data type and the data format, and recording the verification result; judging whether the data is of a code type, if not, continuing to circularly execute the steps, if so, checking the value domain code of the data, and continuously circularly reading the data element to execute the steps after checking is finished; and returning to a corresponding verification result after verification is completed.
Optionally, the message encapsulation specifically includes: determining the type of the message, namely determining whether the business scene is clinical service or interactive service; determining a business activity domain according to specific business requirements, and finding out data sets related to business activities, wherein generally, one activity related to clinical services corresponds to one data set, and one interactive service possibly corresponds to a plurality of data sets; constructing an HL7V3 message or a shared document Schema; and generating a V3 message according to the Schema. In this embodiment, an XMLSpy tool is adopted, and a blank XML document can be generated only by importing a Schema file; all Xpath nodes of the XML are extracted through coding, a mapping relation is established between the Xpath nodes and a specific data set table in the service database, and relevant data in the service database are extracted and filled in corresponding nodes of the XML file to obtain standard V3 information.
After the data is cleaned, verified, stored and encapsulated into HL7V3 information, the data is sent to the platform by calling WebService service or MessageQueue service provided by the medical data exchange platform. In this embodiment, the specific steps of message publishing include: the client carries out initialization configuration on a corresponding server address, a Zookeeper address, a message response mode, a serialization mode and the like of a producer; creating a product according to the configuration information: the instantiation of the instance object creates a transaction object (DefaultEventHandler) and a product: the thread pool is used for connecting different service agents; serializing J messages and operation users, wherein the internal realization is to perform the serializing operation on all the messages and the operation users through a transaction object; the messages are grouped. Acquiring addresses of all service agents according to the configuration information, and grouping the messages according to the theme, namely matching different service agents; the Send method of the Producer is called to Send the message to the corresponding service agent according to the grouping situation of the message and the configured sending mode (synchronous or asynchronous) of the message.
And S3, performing first data relay on the issuing message.
In a specific implementation manner, the specific step of performing the first data forwarding on the release message includes: receiving the release message and judging whether to forward the release message; if the message needs to be forwarded, sending the message to a lift query requester; if the message does not need to be forwarded, the issued message is analyzed, and the analyzed data is stored in the database. In this embodiment, the platform receives the release message, and if the reception fails, the data uploader needs to upload the data again, and if the reception succeeds, the platform forwards the message to the query requester according to the routing rule, and the database uses an HBase central database.
And S4, routing the message according to the query request, extracting the release message after the first data transfer, performing the second data transfer, and sending the transferred release message to the query requester.
In this embodiment, the specific steps include: receiving a query request; matching the query request with the service ID in the routing relation table to determine a routing path; extracting the published message after the first data transfer through a routing path and assembling; and sending the assembled message to a query requester.
Specifically, the message routing is a core function of the data exchange platform, and the specific step of matching the query requester with the service ID in the routing relation table to determine the routing path includes: after receiving a query request initiated by a query requester, the medical data exchange platform matches the query request with a service ID in a routing relation table so as to determine which services the query request is routed to, and prepare for calling the services. And when the routing relation table information is changed, manually sending a routing relation modification notice to a message queue of the modification cache. And after obtaining the route change message, re-reading the route relation table and refreshing the route cache.
In the present application, the medical data exchange method further includes: whether the issuing message sent to the inquiry requester is successfully sent is verified, and if the issuing message is successfully sent, data exchange is ended; and if the failure occurs, the forwarding is carried out again.
In the actual design process, the medical data exchange method further comprises an exception handling process, namely when the service call fails, the medical data exchange platform carries out exception feedback on the inquiry requester on one hand so that the inquiry requester can know the service call failure conveniently and further carry out the next processing; on the other hand, the medical data exchange platform performs exception logging on the exception condition so as to facilitate the system administrator to track and eliminate the exception. In the present application, the exception types mainly include an authority check exception, a route retrieval exception, a service registration exception, a message routing transmission exception, and the like.
Specifically, the data layer refers to application systems or platforms with different development languages, development platforms, data structures, data storage forms and standardization degrees, and the major systems in the area are classified into three major categories according to research: hospital platform class, regional system class, and scattered business class. The exchange layer is mainly responsible for receiving, forwarding and integrating data, and mainly comprises a message queue for message transceiving, a platform Service for providing an interactive interface and a central Service database for data integration, wherein the data transceiving adopts a Web Service mode, and data exchange is performed by using a standard HL7V3 message and a shared document, so that the complexity of completing data exchange by operating the database in the past is reduced, and meanwhile, the international medical information exchange standard is also followed. The platform provides service interfaces for registration, updating, merging, inquiring, logout and calling according to actual services, and the database provides service data storage of electronic medical records and health files. The application layer can provide corresponding applications such as medical management, public health, data mining, business report forms and the like for the portal platform by utilizing the characteristics of platform information intercommunication and integrated data.
In this embodiment, the data layer is configured to include a pre-adaptation system and a heterogeneous information system, where: the heterogeneous information system performs data extraction, data verification, data cleaning, data storage and message encapsulation on the data, or analyzes the data and stores the analyzed data; and the heterogeneous information system performs data exchange on the data processed by the pre-adaptation system.
In a specific implementation manner, the exchange layer is used as a core of the medical data exchange platform, and the exchanging layer is configured to exchange data after data processing is performed on the data layer or analyze and store data after data processing is performed on the data layer specifically includes: the exchange layer strips and integrates the public service in the region to form basic public service, and provides a plurality of interfaces to adapt to different entrance protocols and exit protocols so as to be called by different medical institutions. Furthermore, the exchange layer receives the data message output by the pre-adaptation system through the ingress protocol, analyzes and stores the data message, and after receiving the query request, sends the data message after corresponding analysis to the query requester through the egress protocol according to the query request.
In a specific implementation manner, the switching center 6 includes a message queue module, an interface service module, and a service data center module, where the message queue module is responsible for receiving and sending data, the interface service module provides an interactive interface for platform registration, update, merging, and query services, and the service data center module is responsible for integrating service data of each system and platform, and generally includes two types of service data, i.e., electronic medical records and health records.
In this embodiment, the area switching integrated platform interface service includes two aspects, one is a basic service of the platform, and the other is an area platform service interface service. The basic services include four major types of services, registration, update, inquiry and logout. The business interface service covers 18 services required in the service interaction specification of the regional health information platform. This interface is actively invoked by the applicant. The business data center module is used for registering services of patients, medical personnel and medical institutions and retrieving, accessing and integrating services of health files according to the interoperation command and the specific message flow, and returning operation results in the form of the message flow.
In summary, the embodiments of the present invention have the following advantages: through auditing the registered identity, the safety of personal information is enhanced, and information leakage is avoided; the data processing and the first data transfer are carried out on the uploaded data, so that formats of the data uploaded by different systems are converted uniformly and stored in the medical data exchange platform, and then the data stored in the medical data exchange platform are analyzed through the second data transfer, so that an inquiry requester can read the data information conveniently, the data exchange and sharing among different systems are realized, the data exchange efficiency is improved, the stable operation is ensured on the basis of not influencing the field working environment, and early warning can be timely given and correct processing can be given when a network connection error or the platform stops working normally and data errors or loss occurs in the data transmission process.
The above description is only an embodiment of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present invention disclosed herein are intended to be covered by the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the appended claims.
Claims (10)
1. A medical data exchange method, characterized in that the medical data exchange method comprises:
verifying the registered identity information, and if the verification is passed, uploading data or lifting a query request;
performing data processing on the uploaded data to form a release message;
performing first data transfer on the release message;
and carrying out message routing according to the query request, extracting the release message after the first data transfer, carrying out second data transfer, and sending the transferred release message to a query requester.
2. The medical data exchange method according to claim 1, wherein the specific step of performing data processing on the uploaded data to form the release message comprises:
verifying the standardization of a service system with data uploading requirements;
if the verification is a standardized system, the uploaded data is verified through the front-end adaptation system, and the uploaded data passing the verification is used as a release message;
and if the verification is a non-standardized system, performing first data processing on the data through a pre-adaptation system to form a release message.
3. The medical data exchange method according to claim 2, wherein the specific steps of verifying the uploaded data through the pre-adaptation system and using the verified uploaded data as the release message include:
extracting the uploaded data through the pre-adaptation system and verifying the uploaded data;
if the verification is successful, outputting the uploaded data and taking the uploaded data as a release message;
and if the verification fails, returning the uploaded data to the front adaptation system.
4. The medical data exchange method according to claim 2, wherein the step of performing the first data processing on the data by the pre-adaptation system to form the release message comprises:
extracting the uploaded data through the pre-adaptation system and carrying out data verification on the uploaded data;
carrying out data cleaning on the uploaded data which is qualified in verification;
storing the cleaned uploaded data;
and performing message encapsulation on the stored uploaded data to form a release message.
5. The medical data exchange method according to any one of claims 1 to 4, wherein the step of performing the first data forwarding on the release message comprises:
receiving the release message and judging whether to forward the release message;
if the message needs to be forwarded, sending the message to a lift query requester;
and if the forwarding is not needed, analyzing the issued message, and storing the analyzed data in a database.
6. The medical data exchange method according to claim 1, wherein the specific steps of performing message routing according to the query request, extracting the posted message relayed by the first data, and sending the relayed posted message to the query requester include:
receiving the query request;
matching the query request with the service ID in the routing relation table to determine a routing path;
extracting the published message after the first data transfer through the routing path and assembling;
and sending the assembled message to the inquiry requester.
7. The medical data exchange method according to claim 1, further comprising: whether the issuing message sent to the inquiry requester is successfully sent is verified, and if the issuing message is successfully sent, data exchange is ended; and if the failure occurs, the forwarding is carried out again.
8. A medical data exchange architecture, wherein the medical data exchange architecture comprises:
the data layer is configured to collect data and perform data processing on the data;
the exchange layer is configured to exchange the data after the data processing is performed on the data layer or analyze and store the data after the data processing is performed on the data layer;
and the application layer is configured to call and store the data stored in the exchange layer according to the requirement.
9. The medical data exchange architecture of claim 8, wherein the data layer is configured to include a pre-adaptation system and a heterogeneous information system, wherein:
the heterogeneous information system performs data extraction, data verification, data cleaning, data storage and message encapsulation on data, or analyzes the data and stores the analyzed data;
and the heterogeneous information system performs data exchange on the data processed by the pre-adaptation system.
10. The medical data exchange system according to claim 1, wherein the medical data exchange system comprises an authentication module, a data acquisition module, a data verification module, a message encapsulation module, a preposed data center module and a switching center, wherein:
the identity authentication module is used for authenticating the identity information of the user;
the data acquisition module is used for acquiring data uploaded by a user with qualified identity information verification;
the data checking module is used for carrying out format checking on the data acquired by the data acquisition module so as to remove the data with unqualified format;
the message packaging module is used for converting the data successfully verified by the data verification module into messages and storing the messages in a database;
the prepositive data center module is used for backing up standardized data and providing a data source when a message is constructed;
the switching center is used for providing a plurality of service interfaces for the inquiry requester to call and store the messages stored in the database.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910942328.8A CN112582036A (en) | 2019-09-30 | 2019-09-30 | Medical data exchange platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910942328.8A CN112582036A (en) | 2019-09-30 | 2019-09-30 | Medical data exchange platform |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112582036A true CN112582036A (en) | 2021-03-30 |
Family
ID=75116796
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910942328.8A Pending CN112582036A (en) | 2019-09-30 | 2019-09-30 | Medical data exchange platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112582036A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115408460A (en) * | 2022-08-24 | 2022-11-29 | 中逸安科生物技术股份有限公司 | Information integration system for vaccine production process |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101477596A (en) * | 2009-02-02 | 2009-07-08 | 中国网络通信集团公司 | Medical data center system |
| CN108520770A (en) * | 2018-03-28 | 2018-09-11 | 深圳中兴网信科技有限公司 | Medical test data sharing method, medical test data-sharing systems |
| CN110111862A (en) * | 2019-03-29 | 2019-08-09 | 北京汉博信息技术有限公司 | Information platform |
| CN110188132A (en) * | 2019-04-29 | 2019-08-30 | 安徽晶奇网络科技股份有限公司 | A kind of method for interchanging data and system |
-
2019
- 2019-09-30 CN CN201910942328.8A patent/CN112582036A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101477596A (en) * | 2009-02-02 | 2009-07-08 | 中国网络通信集团公司 | Medical data center system |
| CN108520770A (en) * | 2018-03-28 | 2018-09-11 | 深圳中兴网信科技有限公司 | Medical test data sharing method, medical test data-sharing systems |
| CN110111862A (en) * | 2019-03-29 | 2019-08-09 | 北京汉博信息技术有限公司 | Information platform |
| CN110188132A (en) * | 2019-04-29 | 2019-08-30 | 安徽晶奇网络科技股份有限公司 | A kind of method for interchanging data and system |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115408460A (en) * | 2022-08-24 | 2022-11-29 | 中逸安科生物技术股份有限公司 | Information integration system for vaccine production process |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7685143B2 (en) | Unified logging service for distributed applications | |
| US8443374B2 (en) | Business application integration adapters management system | |
| US9020826B2 (en) | Direct connectivity system for healthcare administrative transactions | |
| JP5377494B2 (en) | Healthcare semantic interoperability platform | |
| US20060085361A1 (en) | Anomaly detector in a health care system using adapter | |
| CN101083582A (en) | Heterogeneous medical information integrated system based on HL7 agent server | |
| US20060253860A1 (en) | Systems and methods for interfacing an application of a first type with multiple applications of a second type | |
| CN103530524A (en) | Medical information intelligent data platform, use method and application thereof | |
| CN109460912B (en) | Data processing method, data processing device, storage medium and electronic equipment | |
| KR20140063512A (en) | Method and system for centralized reservation context management on multi-server reservation system | |
| CN108536433A (en) | A kind of J2EE Development Frameworks and the development approach based on the J2EE Development Frameworks | |
| WO2006044721A2 (en) | Interfacing disparate software applications | |
| CN115516574B (en) | Cloud-based API specification management method for linking multiple hospital servers and federated servers in a concurrent manner | |
| CN101854348A (en) | Realization method of SOA (Service Oriented Architecture) accessing core supporting system in peripheral system | |
| CN112256530A (en) | Log service method capable of tracking link and system thereof | |
| CN108964971A (en) | A kind of data interchange platform | |
| US20070156737A1 (en) | Application integration systems and methods | |
| KR100932711B1 (en) | Medical Information Integrated Management System and Method | |
| CN105407163B (en) | Data processing system and method applied to anti money washing processing | |
| CN107302583A (en) | A kind of automation operation management method that data integration is realized based on Kylo | |
| CN112582036A (en) | Medical data exchange platform | |
| CN116032946A (en) | Cross-region synchronization method, device and medium for detection report | |
| CN112215705A (en) | International credit card clearing platform | |
| CN107330089B (en) | Cross-network structured data collection system | |
| CN115086191B (en) | Automatic test method, device and equipment for bank card |
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 |