CN115691773A

CN115691773A - Hospital data access method, system, storage medium and electronic equipment

Info

Publication number: CN115691773A
Application number: CN202211091694.5A
Authority: CN
Inventors: 张智锋; 张洪亮; 陈攀; 张竹渝; 李彬; 曾敏航; 毕小宇
Original assignee: Beijing Digital Yixin Technology Co ltd
Current assignee: Beijing Digital Yixin Technology Co ltd
Priority date: 2022-09-07
Filing date: 2022-09-07
Publication date: 2023-02-03

Abstract

Some embodiments of the present application provide a method, system, storage medium and electronic device for hospital data access, the system comprising: the data management terminal is used for creating a data dictionary base; sending the database dictionary library to an integration engine end; the integrated engine end is used for receiving the data dictionary library sent by the data management end; acquiring a subscription requirement table selected by an integration administrator; sending a data dictionary database and a subscription requirement table to an object processing end; receiving a target subscription table sent by an object processing end and storing the target subscription table in an integration engine database for a third party platform to call; the object processing end is used for receiving the data dictionary database and the subscription requirement table sent by the integration engine end; responding to the input operation of a user in a subscription requirement table according to a data dictionary library, and acquiring basic information; and acquiring a target subscription table corresponding to the basic information, and sending the target subscription table to the integration engine terminal. Some embodiments of the application can manage hospital data in a unified manner, and quick access to the hospital data is achieved.

Description

Hospital data access method, system, storage medium and electronic equipment

Technical Field

The present application relates to the field of information processing technologies, and in particular, to a method, a system, a storage medium, and an electronic device for hospital data access.

Background

With the development of internet technology, many hospitals have achieved the comprehensive application of various different information systems, and have been able to support the daily clinical, teaching, scientific research and management, etc. work of hospitals basically.

At present, most of service systems established in hospitals are composed of independent information systems provided by different suppliers, and different information systems are integrated in a point-to-point interface mode, namely, data interaction is realized in a point-to-point mode. However, because the different interfaces adopted by the suppliers of the information systems are inconsistent, a point-to-point interface mode is adopted between the information systems, the coupling degree is high, and the maintenance cost is high. Moreover, data is scattered, and a uniform data management standard does not exist, so that the complexity is high and the data access efficiency is low when medical care personnel or other third-party platforms access data.

Therefore, how to provide a technical scheme of a method for efficiently accessing hospital data becomes a technical problem which needs to be solved urgently.

Disclosure of Invention

The technical scheme of the embodiment of the application can be used for uniformly and standardizing management of data in information systems inside and outside a hospital, so that various medical applications can provide uniform data access services, the efficiency of data access is improved, the function of direct coupling of various medical application systems and a medical data center is eliminated, and the maintenance cost and the safety risk of data are reduced.

In a first aspect, some embodiments of the present application provide a method for hospital data access, which is applied to a data management end in a hospital data access system, where the hospital data access system further includes an integration engine end and an object processing end, and includes: creating a database dictionary library, wherein the database dictionary library comprises: the method comprises the steps of obtaining data information and a data identifier corresponding to the data information; and sending the database dictionary library to the integration engine terminal so as to obtain a target subscription table according to the database dictionary for a third-party platform to call.

According to some embodiments of the application, unified and standardized management of data can be realized by creating and sending the database dictionary, the problem of data isomerism is avoided, and support is provided for subsequently improving the efficiency of data access.

In some embodiments, the creating a database dictionary base comprises: creating a data table structure; and responding to the operation of a user, and adding the data information and the data identification in the data table structure.

Some embodiments of the present application may obtain a unified data management standard by adding corresponding information in the data table structure.

In some embodiments, before the sending the database dictionary database to the integration engine, the method further comprises: auditing the data information and the data identification in the data dictionary library; and confirming that the data information and the data identifier are approved.

According to some embodiments of the application, the database dictionary database with high precision can be obtained by auditing the database dictionary database, and the accuracy and consistency of the unified management standard of data are ensured.

In a second aspect, some embodiments of the present application provide a method for hospital data access, which is applied to an integration engine side in a hospital data access system, where the hospital data access system further includes a data management side and an object processing side, and includes: receiving a data dictionary database sent by the data management terminal; obtaining a subscription requirement table selected by an integration administrator, wherein the subscription requirement table comprises: target objects and subscription information to be filled in; sending the data dictionary base and the subscription requirement table to the object processing terminal so that the target object inputs the subscription information to be filled according to the data dictionary base to obtain a target subscription table; and receiving the target subscription table sent by the object processing terminal and storing the target subscription table in an integration engine database for being called by a third party platform.

The integration engine side of some embodiments of the application sends the database dictionary database and the subscription requirement table to the object processing side, and then receives the target subscription table containing all data information of the target object returned by the object processing side, so that a third-party platform can call the target subscription table. By the embodiment, the data can be integrated and stored in a standardized manner, so that a third-party platform can call once to obtain all data information of the target object, the data access efficiency is improved, and the complexity of data access is reduced.

In some embodiments, the method further comprises: monitoring target data related to the target object and confirming whether the target data is changed; acquiring changed data under the condition that the target data is changed; and matching the changed data with the target object, acquiring matched data and storing the matched data in the integration engine database for the third-party platform to call.

Some embodiments of the application can acquire the change data of the target object in time by monitoring the target data related to the target object, and further can acquire all hospital data of the target object, thereby realizing centralized management of the data, solving the problem of clinical data dispersion, and enabling a third-party platform to perform data access service uniformly.

In some embodiments, prior to the monitoring target data associated with the target object, the method further comprises: responding to the input operation of the integration administrator, and acquiring the target data to be monitored and a monitoring period in a target database; the monitoring target data related to the target object comprises: and monitoring the target data according to the monitoring period.

According to some embodiments of the application, effective data information can be obtained in time by periodically monitoring the target data to be monitored, which is specified by the integration administrator, so that the resource utilization rate of the integration engine end is improved.

In some embodiments, the method further comprises: and storing the message of the change of the target data to a message log.

Some embodiments of the application can timely acquire the dynamic state of the data and facilitate the calling of a third-party platform by storing the change data and generating the message log.

In a third aspect, some embodiments of the present application provide a method for hospital data access, which is applied to an object processing end in a hospital data access system, where the hospital data access system further includes an integration engine end and a data management end, and includes: receiving a data dictionary database and a subscription requirement table sent by the integration engine end; responding to the input operation of a user in the subscription requirement table according to the database dictionary library, and acquiring basic information; and acquiring a target subscription table corresponding to the basic information, and sending the target subscription table to the integration engine terminal for a third-party platform to call at the integration engine terminal.

The object processing end of some embodiments of the application can fill the subscription requirement table through the data dictionary library to obtain the target subscription table, and send the target subscription table to the integration engine end, and the target subscription table obtained under the unified data management standard is high in standardization, so that the problem of data isomerism is avoided.

In some embodiments, the obtaining the target subscription table corresponding to the basic information includes: if the index record table matched with the basic information exists in the filing index base, taking the index record table as the target subscription table; and if the documenting index database does not have the index record table matched with the basic information, generating the target subscription table corresponding to the basic information.

According to some embodiments of the application, after the basic information is searched in the archive index database, the target subscription table is determined, so that the situation that the basic information of the same target object is stored repeatedly can be avoided, and the utilization rate of memory resources is improved.

In a fourth aspect, some embodiments of the present application provide a system for hospital data access, comprising: the data management terminal is used for creating a data dictionary library, wherein the data dictionary library comprises: the data information and the data identification corresponding to the data information; sending the database dictionary library to an integration engine end; the integration engine end is used for receiving the data dictionary database sent by the data management end; acquiring a subscription requirement table selected by an integration administrator; sending the data dictionary database and the subscription requirement table to an object processing end; receiving the target subscription table sent by the object processing terminal and storing the target subscription table in an integration engine database for a third party platform to call; the object processing end is used for receiving the data dictionary database and the subscription requirement table sent by the integration engine end; responding to the input operation of a user in the subscription requirement table according to the database dictionary library, and acquiring basic information; and acquiring a target subscription table corresponding to the basic information, and sending the target subscription table to the integration engine terminal.

According to some embodiments of the application, the data management end, the integration engine end and the object processing end are integrated in the same system, so that various medical applications can provide unified data access service, the efficiency of data access is improved, the function of direct coupling of various medical application systems and a medical data center is eliminated, and the maintenance cost and the safety risk of data are reduced.

In a fifth aspect, some embodiments of the present application provide a data management terminal, including: a creation module configured to create a database dictionary base, wherein the database dictionary base includes: the data information and the data identification corresponding to the data information; and the data sending module is used for sending the data dictionary library to the integration engine terminal so as to obtain a target subscription table according to the data dictionary for a third party platform to call.

In a sixth aspect, some embodiments of the present application provide an integration engine side, including: the first receiving module is used for receiving the data dictionary database sent by the data management terminal; a selection module, configured to obtain a subscription requirement table selected by an integration administrator, where the subscription requirement table includes: target objects and subscription information to be filled in; the sending module is used for sending the data dictionary base and the subscription requirement table to the object processing terminal so that the target object can input the subscription information to be filled according to the data dictionary base to obtain a target subscription table; and the second receiving module is used for receiving the target subscription table sent by the object processing terminal and storing the target subscription table in an integrated engine database for being called by a third-party platform.

In a seventh aspect, some embodiments of the present application provide an object processing end, including: the receiving module is used for receiving the data dictionary database and the subscription requirement table sent by the integration engine terminal; the input module is used for responding to the input operation of a user in the subscription requirement table according to the database dictionary library and acquiring basic information; and the acquisition module is used for acquiring a target subscription table corresponding to the basic information and sending the target subscription table to the integration engine terminal so as to be called by a third party platform at the integration engine terminal.

In an eighth aspect, some embodiments of the present application provide a computer-readable storage medium on which a computer program is stored, which when executed by a processor, is operable to implement the method according to any one of the embodiments of the first aspect.

In a ninth aspect, some embodiments of the present application provide an electronic device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor when executing the program may implement the method according to any of the embodiments of the first aspect.

In a tenth aspect, some embodiments of the present application provide a computer program product comprising a computer program, wherein the computer program, when executed by a processor, implements the method according to any of the embodiments of the first aspect.

Drawings

In order to more clearly illustrate the technical solutions of some embodiments of the present application, the drawings that are required to be used in some 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 for a person skilled in the art, other relevant drawings can be obtained from these drawings without inventive effort.

FIG. 1 is a system diagram of hospital data access provided by some embodiments of the present application;

FIG. 2 is one of a flow chart of a method of hospital data access provided by some embodiments of the present application;

FIG. 3 is a second flowchart of a method of hospital data access provided by some embodiments of the present application;

FIG. 4 is a third flowchart of a method of hospital data access provided by some embodiments of the present application;

FIG. 5 is an interactive flow diagram of hospital data access provided by some embodiments of the present application;

fig. 6 is a block diagram of a data management end according to some embodiments of the present application;

fig. 7 is a block diagram of an integration engine according to some embodiments of the present application;

fig. 8 is a block diagram of an object processing side according to some embodiments of the present application;

fig. 9 is a schematic diagram of an electronic device according to some embodiments of the present application.

Detailed Description

Technical solutions in some embodiments of the present application will be described below with reference to the accompanying drawings in some embodiments of the present application.

It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures. Meanwhile, in the description of the present application, the terms "first", "second", and the like are used only for distinguishing the description, and are not construed as indicating or implying relative importance.

In the related technology, most of the service systems established in most hospitals at present are composed of independent information systems provided by different suppliers, the information systems are integrated by adopting a point-to-point interface mode, the system coupling degree is high, and the multiplexing of data and the cooperative needs of services are difficult to meet. The types of databases relied on by the service system include SQL Server, oracle, sybase, mySQL and the like, which causes a significant problem of data heterogeneity. And each information system has an independent login account and a login interface, so that unified user management and portal management are lacked, and the system management difficulty is high. In the information construction process, a large number of information islands are generated, so that the problems of low system integration level, low information sharing and utilization rate and the like are caused.

The conventional service system is deployed under a conventional architecture provided by an information platform manufacturer, that is, virtual machines are deployed on one server, a centralized array such as a storage area network SAN or a network attached storage NAS is generally used for storing virtualized data, so that a shared cloud service is provided for all the virtual machines, and the problem of idle CPU and memory resources is solved through virtualization. However, with large-scale application of virtualization, more and more virtual machines are provided, and the virtual machines run on the traditional storage more and more slowly, which becomes the biggest bottleneck limiting the virtualization application.

At present, many hospitals implement comprehensive applications such as Hospital Information Systems (HIS), laboratory Information Systems (LIS), radiology Information Systems (RIS), medical image storage and transmission systems (PACS), electronic Medical Records (EMR), financial management and material management, etc., and the business systems can basically support daily clinical, teaching, scientific research and management of hospitals. In the process of information interaction inside and outside a hospital, two main information interaction modes are available: one is direct data exchange between systems by adopting point-to-point; another method is to adopt a Service Oriented Architecture (SOA) based Architecture, utilize an Enterprise Service Bus (ESB) as a connection hub, and implement a preliminary information management and data access function in compliance with HL 7V 2.X or V3 protocol.

It can be known from the related technologies that the different suppliers of the existing service systems cause inconsistent interfaces, and the service systems are integrated in a point-to-point interface manner, so that the system coupling degree is high, the maintenance cost is high, and the risk is high. And in terms of data management: lack of unified data management, the updating and adjusting of data are cumbersome. Clinical data are scattered, so that medical staff can obtain one-sided information, and scattered medical health data need to be integrated. The object main index management is incomplete, so that the problem of inconsistent object main index information of each system is caused. Lack of uniform yard-level data standards will create data heterogeneity problems. The business system and the management scientific research system are not reasonably separated, the mutual influence is serious, and the phenomena of heavy business and light management scientific research are prominent. And multi-system account management is adopted, so that unified user management, portal management and system management are not available. In addition, the prior art does not support containerized deployment of k8s, docker and the like, is difficult to integrate various commercialized or open source cloud Platform as a Service (Platform as a Service), and does not have good dynamic telescopic on-demand expansion capability.

The Kubernetes English abbreviation k8s is a container cluster management system for automatic deployment, scaling and container management of Google open source, and can provide functions of application deployment, maintenance, expansion mechanism and the like. The use of kubernets facilitates the management of cross-machine running containerized applications.

In view of this, some embodiments of the present application provide a hospital data access system, where the system deploys a data management end, an integration engine end, and an object processing end on a container cloud management to obtain a container cloud-based hospital data access system, and the system can perform unified and standardized management on data in internal and external information systems of a hospital, so that various medical applications can provide unified data access services, the efficiency of data access is improved, the function of direct coupling between various medical application systems and a medical data center is eliminated, and the maintenance cost and the security risk of data are reduced.

Referring to fig. 1, fig. 1 is an overall block diagram of a system for hospital data access provided by some embodiments of the present application.

The system of hospital data access of figure 1 comprises: a data management side 100, an integration engine side 200, and an object processing side 300. Wherein, the data management end 100 can send the database dictionary to the integration engine end 200. The integration engine side 200 and the object processing side 300 can implement bidirectional communication. The integration engine 200 may send the data dictionary database and the subscription requirement table to the object processing terminal 300, and may also monitor the change condition of the target data in other target databases, and obtain the matching data in the case of change. The object processing terminal 300 may fill the subscription requirement table according to the database dictionary to obtain a target subscription table, and then send the target subscription table to the integration engine terminal. As can be seen in FIG. 1, FIG. 1 also includes a third party platform 400, wherein the third party platform 400 can interact with the system for hospital data access. The third party platform 400 may send a request for obtaining data to the integration engine 200, and the integration engine 200 may send data (i.e. target subscription table or matching data) corresponding to the request to the third party platform 400. It should be noted that the third party platform 400 may be a doctor side, a nurse side, a medical procedure side, or the like. The present application is not limited thereto.

It should be noted that the data management end 100, the integration engine end 200, and the object processing end 300 are deployed in the same system, and can provide a unified data access service for various medical applications, and eliminate the direct coupling between various medical application systems and the medical data center. For example, based on the technology of managing the Docker container by Kubernetes, the hospital information system resources are pooled, so that unified operation and maintenance can be realized through the container cloud, and unified management of the integration engine side, the data management side and the object processing side is realized. Some embodiments of the present application provide a hospital data access system that is a consistent container cloud technology-based, micro-service architecture, loosely-coupled, and extensible hospital information integration platform.

For example, in some embodiments of the present application, the data management side 100, the integration engine side 200, and the object processing side 300 are deployed in a container cloud. That is to say, the application splits the service system into individual micro-services, each micro-service is programmed by using a Spring Cloud as a framework, and then is installed in different Docker containers after being encapsulated by programs, so that the fast replication and redundancy functions can be realized to meet the continuous increase and fault tolerance of the service. And then, a container distributed by the KubeSphere deployment management cluster is utilized, the service provides deployment management conditions for the container by constructing the Kubernets cluster, the number of nodes of the working cluster is reduced and enlarged, and resources are elastically provided for Docker application, so that the platform has the functions of increasing and decreasing loads along with real-time service volume and independently and dynamically starting and stopping each micro-service module.

The following exemplifies the relevant functions of the units of fig. 1.

In some embodiments of the present application, the data management end 100 is configured to at least: creating a database dictionary base, wherein the database dictionary base comprises: the method comprises the steps of obtaining data information and a data identifier corresponding to the data information; and sending the database dictionary library to an integration engine terminal.

For example, in some embodiments of the present application, the Data Management terminal 100 may also be referred to as a Master Data Management (MDM) for creating and maintaining consistency, integrity, relevance, and accuracy of business Data for the hospital side. The traditional MDM needs to send corresponding data to different third party platforms for multiple times according to requirements, and the data issuing efficiency is low. In some embodiments of the present application, the MDM is improved, so that the MDM only needs to send data to the integration engine end 200 once, and the integration engine end 200 can distribute the data according to the subscription table of the third party platform 400, thereby improving the data publishing efficiency.

In some embodiments of the present application, the integration engine 200 is configured to at least: receiving a data dictionary database sent by the data management terminal; acquiring a subscription requirement table selected by an integration administrator; sending the data dictionary database and the subscription requirement table to an object processing end; and receiving the target subscription table sent by the object processing terminal and storing the target subscription table in an integration engine database for being called by a third party platform.

For example, in some embodiments of the present application, the integration engine end 100 (which may also be referred to as an integration engine) is an operation engine of a hospital Data access system, which supports multiple medical Data standard exchange protocols (e.g., HL 7V 3 based on an interface protocol in XML format of Web Service, and FHIR V4.0 based on JSON format of RESTFUL style), and which adopts a multi-layer architecture design, can Capture Data changes by using CDC (Change Data Capture), and can also receive and send messages through a message queue. The integration engine can provide auxiliary functions such as configuration management function, log monitoring function, data distribution and mapping, facilitates daily supervision, and provides efficient service for patients (as a specific example of target objects).

In some embodiments of the present application, the object processing side 300 is at least configured to: receiving the data dictionary database and the subscription requirement table sent by the integration engine end; responding to the input operation of a user in the subscription requirement table according to the database dictionary library, and acquiring basic information; and acquiring a target subscription table corresponding to the basic information, and sending the target subscription table to the integration engine terminal.

For example, in some embodiments of the present application, the object processing side 300 may also be referred to as a Patient Master Index system (EMPI), which is a system for managing a Patient Master Index (MPI). The system is maintained in multiple domains or across domains to identify patient instances, wherein the patient instances in all the domains are unique, that is, patient identifications from multiple systems can be associated, and the association of the same patient multi-service ID and the unification of patient information are realized. EMPI may enable interaction with an integration engine. For example, the patient gender is recorded in the patient main index in the EMPI, and the corresponding codes of the patient gender in the third-party platform 400 are different, so that the MDM database is required to be provided to the EMPI through the integration engine, and a standard gender dictionary is provided for the EMPI for data standardization. The traditional EMPI system needs to read data in batches at regular time and then can carry out main index merging on patients, and due to the fact that the integration engine is connected into some embodiments of the EMPI system, the patient information received in the EMPI system can be merged in real time.

A method implementation process of hospital data access performed by the data management terminal 100 according to some embodiments of the present application is exemplarily set forth below with reference to fig. 2.

Referring to fig. 2, fig. 2 provides a method for hospital data access according to some embodiments of the present application, which may include: s210, creating a data dictionary library, wherein the data dictionary library comprises: the data identification comprises data information and a data identification corresponding to the data information. S220, the data dictionary database is sent to the integration engine end, so that a target subscription table can be obtained according to the data dictionary conveniently, and the target subscription table can be called by a third-party platform.

For example, in some embodiments of the present application, the data management end 100 may customize and generate a standard data dictionary library, and send the data dictionary library to the integration engine end 200, so that the object processing end 300 may obtain the data dictionary library through the integration engine end 200, and finally obtain a standardized target subscription table.

In some embodiments of the present application, S210 may include: creating a data table structure; and responding to the operation of the user, and adding the data information and the data identification in the data table structure.

For example, in some embodiments of the present application, a data administrator may create a data table structure on a page of the data management terminal 100. For example, taking a standard gender dictionary as an example, as shown in table 1, the table structure includes: a code (as one specific example of data identification) and gender (as one specific example of data information). The corresponding codes and the genders represented by the codes are then filled in table 1 to obtain the final standard gender dictionary, as in table 2.

TABLE 1

Code	Sex

TABLE 2

Code	Sex
		0	Unknown sex
1	Male sex
		2	Female with a view to preventing the formation of wrinkles
9	Unspecified sex

It should be noted that, in some embodiments of the present application, the data dictionary library includes a plurality of data sub-dictionaries, for example, in addition to the standard gender dictionary, a payment type dictionary (e.g., self-payment, medical insurance payment), a certificate type dictionary (e.g., identification card, passport), and so on.

To ensure the accuracy of the database dictionary repository, in some embodiments of the present application, before performing S220, the method for hospital data access further comprises: auditing the data information and the data identification in the data dictionary library; and confirming that the data information and the data identifier are approved.

For example, in some embodiments of the present application, manual review needs to be performed on all the data sub-dictionaries in the data dictionary library to ensure accuracy and standardization of the data, and if the data sub-dictionaries are not approved (for example, the data sub-dictionaries are not approved due to editing errors of a data administrator), the data in the data sub-dictionaries needs to be modified and reviewed again until the data sub-dictionaries are published after the approval is passed, that is, the data is sent to the integration engine end 200.

A method implementation process of hospital data access performed by the integration engine end 200 provided by some embodiments of the present application is exemplarily set forth below in conjunction with fig. 3.

Referring to fig. 3, fig. 3 is a flowchart of a method for accessing hospital data according to some embodiments of the present application, where the method for accessing hospital data may include: s310, receiving a data dictionary library sent by the data management terminal; s320, obtaining a subscription requirement table selected by the integration administrator, wherein the subscription requirement table comprises: target objects and subscription information to be filled in; s330, sending the data dictionary base and the subscription requirement table to the object processing terminal so that the target object inputs the subscription information to be filled according to the data dictionary base to obtain a target subscription table; s340, receiving the target subscription table sent by the object processing terminal and storing the target subscription table in an integration engine database for being called by a third party platform.

For example, in some embodiments of the present application, an integration administrator of the integration engine side 200 may send corresponding subscription requirements to corresponding target objects. The integration administrator may perform service registration and service subscription at the integration engine end 200, obtain a corresponding subscription requirement table according to the requirement of the service subscription, and then send the subscription requirement table and the database dictionary to the target object of the object processing end 300. The target object can input the subscription information to be filled according to the data dictionary library to obtain a target subscription table. Finally, the integration engine 200 may receive the target subscription table returned by the object processing end 300, and store the target subscription table in the integration engine database for the third party platform 400 to call. It should be noted that one target object corresponds to one target subscription table.

In order to obtain more complete data information, in some embodiments of the present application, the method for hospital data access may further include: monitoring target data related to the target object and confirming whether the target data is changed; acquiring changed data under the condition that the target data is changed; and matching the changed data with the target object, acquiring matched data and storing the matched data in the integration engine database for the third-party platform to call.

For example, in some embodiments of the present application, the integration administrator may also configure producer events. Where a producer refers to a target database (e.g., a registry database, a payment database, and a check query database, among other different business systems) from which data may be generated. Because the target database has more data, the integration administrator can configure a producer event (e.g., a registration event) related to the target data according to the data requirement, and then configure a corresponding producer task (e.g., a registration task) according to the producer event. And then monitoring the producer task, obtaining the latest changed data when the data in the producer task is changed, matching the changed data with a target subscription table of a corresponding patient (namely, an object, also called a target object), integrating all data of the patient to obtain matched data, and storing the matched data in an integration engine database.

In order to improve the efficiency of acquiring data, in some embodiments of the present application, the method for hospital data access before monitoring the target data related to the target object may further include: responding to the input operation of the integration administrator, and acquiring the target data to be monitored and a monitoring period in a target database; the monitoring target data related to the target object comprises: and monitoring the target data according to the monitoring period.

For example, in some embodiments of the present application, the integration administrator may also set a monitoring period for the producer task, enabling a timed check of the producer task. For example, the monitoring period may be set in units of hours, days, weeks, or months, and the present application is not particularly limited thereto. At the time of the timer check, whether or not the data is changed is checked by the CDC.

In order to obtain dynamic information of data in time, in some embodiments of the present application, the method for hospital data access may further include: and storing the message of the change of the target data to a message log.

A method implementation process of hospital data access performed by the object processing terminal 300 according to some embodiments of the present application is exemplarily set forth below with reference to fig. 4.

Referring to fig. 4, fig. 4 is a flowchart of a method for accessing hospital data according to some embodiments of the present application, where the method for accessing hospital data may include: s410, receiving the data dictionary database and the subscription requirement table sent by the integration engine terminal. And S420, responding to the input operation of the user in the subscription requirement table according to the database dictionary library, and acquiring basic information. S430, acquiring a target subscription table corresponding to the basic information, and sending the target subscription table to the integration engine terminal for a third party platform to call at the integration engine terminal.

For example, in some embodiments of the application, the object processing terminal may enter corresponding basic information, for example, field information such as a name, a birth date, an identification number, a mobile phone number, and the like of the target object, into the subscription information to be filled in the subscription requirement table, so as to obtain the target subscription table, and finally send the target subscription table to the integration engine terminal 200.

To ensure reasonable utilization of memory resources, in some embodiments of the present application, S430 may include: if the index record table matched with the basic information exists in the filing index base, taking the index record table as the target subscription table; and if the documenting index database does not have the index record table matched with the basic information, generating the target subscription table corresponding to the basic information.

For example, in some embodiments of the present application, when any target object is archived, that is, when a target subscription table is generated, whether an index record table of any target object exists may be retrieved from the archive index database according to the unique identifier of any target object. For example, the information is retrieved in the archive index database by at least one of the name, the year and month of birth, the mobile phone number and the identification number of any target object. If the index record table of any target object exists, a new table does not need to be generated for any target object again, corresponding information can be directly added into the index record table as required, or the index record table is directly used as a target subscription table. If any target object does not retrieve the corresponding record, the record is shown to be the first filing, and the recorded basic information is generated into a target subscription table.

An interactive flow diagram of hospital data access provided by some embodiments of the present application is illustrated below in conjunction with figure 5. Referring to fig. 5, fig. 5 is a specific interactive process for hospital data access provided by some embodiments of the present application. The following illustrates an interactive process for hospital data access.

S510, creating a database dictionary base.

For example, as a specific example of the present application, a data manager may create a data dictionary library at the data management terminal 100 according to data requirements, where the data dictionary library may include a plurality of data sub-dictionaries, and each data sub-dictionary includes codes and meanings corresponding to the codes. See table 2 above for details.

S520, the data dictionary database is sent to the integration engine terminal.

For example, as a specific example of the present application, the data management side 100 sends a database dictionary to the integration engine side 200.

S530, receiving the data dictionary database sent by the data management terminal, and acquiring the subscription requirement table selected by the integration administrator.

For example, as a specific example of the present application, the integration administrator may confirm the needs of the patient (as a specific example of the target object), select a subscription requirement table of the patient, and subsequently implement the profiling of the patient. The subscription requirement table contains the patient and the subscription information to be filled in.

S540, the data dictionary database and the subscription requirement table are sent to the object processing terminal.

For example, as a specific example of the present application, the integration engine side 200 sends a database dictionary and a subscription requirement table to the patient profiling side (as a specific example of the object processing side 300).

And S550, receiving the data dictionary database and the subscription requirement table sent by the integration engine terminal.

For example, as a specific example of the present application, a patient profiling end receives a database dictionary repository and a subscription requirement table.

And S560, responding to the input operation of the user in the subscription requirement table according to the database dictionary library, and acquiring basic information.

For example, as a specific example of the present application, a filing person at the patient filing end (as a specific example of the user) may fill out subscription information (e.g., basic information: name, phone, identification number and gender, etc.) to be filled out in the subscription requirement table according to the database dictionary. Unified standardized management of data can be realized through the data dictionary base, and integration in later period is not needed, so that the data access efficiency is improved.

And S570, acquiring a target subscription table corresponding to the basic information, and sending the target subscription table to the integration engine terminal.

For example, as a specific example of the present application, after completion of filing, or after completion of partial information (e.g., filling in a name and a phone number), the filing index base may be searched for the presence of the patient's index record table. The filled-in basic information may be merged with the index record table, if any, to obtain a patient subscription table (as a specific example of a target subscription table). If not, generating the basic information into a patient subscription table.

S580, receiving the target subscription table sent by the object processing terminal and storing the target subscription table in an integration engine database.

For example, as a specific example of the present application, the patient profiling side sends the patient subscription table to the integration engine side 200 and stores it.

S590, monitoring target data related to the target object, and acquiring changed data under the condition that the target data is changed; and matching the changed data with the target object, acquiring matched data and storing the matched data in the integration engine database.

For example, as a specific example of the present application, the integration engine end 200 may further configure a producer task related to the patient, timely obtain the changed data through timing monitoring, and match the changed data with the patient subscription table of the patient to obtain all data of the patient.

In some embodiments of the present application, all of the patient's data is stored to the integration engine database, where the data in the integration engine database is ready for the healthcare provider (as one specific example of the third party platform 400) to recall.

It should be noted that, although the target subscription table and the acquisition of the matching data are performed in different steps in the foregoing embodiments, in other embodiments of the present application, it may also be monitored whether the target data is changed while the subscription requirement table is sent to the object processing end 300. The present application is not limited thereto.

In addition, in some embodiments of the present application, the step of the data management terminal 100 creating the database dictionary repository may be before performing S560. In other embodiments of the present application, the integration engine side 200 page may be a database dictionary repository of historical versions that have been stored. Or, if the data administrator has updated the historical version of the database dictionary library, the embodiment of the present application may be executed from S510, and the updated database dictionary library is sent to the integration engine 200 again. It should be understood that the specific procedures for implementing the embodiments of the present application may be determined according to actual requirements, and the present application is not limited specifically herein.

According to some embodiments of the application, the data and the portal are integrated and unified through the data management end 100, the integration engine end 200 and the object processing end 300, the infrastructure of the hospital information system is improved, the expansibility and the adaptability of the hospital application system to the change of requirements are improved, and the integrity, the consistency, the timeliness, the standard property and the usability of the data are realized. The integration engine end 200 is always used as an intermediary platform, organically connects different independent ends, and realizes unified access of data. Moreover, the container Cloud technology of the micro-service architecture realized based on the Spring Cloud framework and the Docker can realize a series of functions including application deployment on demand, easy application management, cluster expansion/contraction on demand, storage persistence, easy container transplantation and the like.

Referring to fig. 6, fig. 6 is a block diagram illustrating a data management side according to some embodiments of the present application. It should be understood that the data management end corresponds to the above-mentioned method embodiment of fig. 2, and can perform the steps related to the above-mentioned method embodiment, and the specific functions of the data management end can be referred to the above description, and the detailed description is appropriately omitted here to avoid repetition.

The data management terminal of fig. 6 includes at least one software functional module that can be stored in a memory in the form of software or firmware or solidified in the data management terminal, and the data management terminal includes: a creating module 610, configured to create a database dictionary base, where the database dictionary base includes: the data information and the data identification corresponding to the data information; and a data sending module 620, configured to send the database to the integration engine end, so as to obtain a target subscription table according to the database, so as to be called by a third party platform.

In some embodiments of the present application, the creating module 610 is specifically configured to create a data table structure; and responding to the operation of the user, and adding the data information and the data identification in the data table structure.

In some embodiments of the present application, before the data sending module 620, the data management side further includes an auditing module (not shown in the figure) for auditing the data information and the data identifier in the data dictionary repository; and confirming that the data information and the data identifier are approved.

Referring to fig. 7, fig. 7 is a block diagram illustrating components of an integration engine provided in some embodiments of the present application. It should be understood that the integration engine end corresponds to the method embodiment of fig. 3 described above, and is capable of executing various steps related to the method embodiment described above, and specific functions of the integration engine end may be referred to the description above, and detailed descriptions are appropriately omitted here to avoid repetition.

The integration engine side of fig. 7 includes at least one software functional module that can be stored in a memory in the form of software or firmware or solidified in the integration engine side, and the integration engine side includes: a first receiving module 710, configured to receive a database dictionary library sent by the data management end; a selecting module 720, configured to obtain a subscription requirement table selected by the integration administrator, where the subscription requirement table includes: target objects and subscription information to be filled in; a sending module 730, configured to send the data dictionary database and the subscription requirement table to the object processing end, so that the target object enters the subscription information to be filled according to the data dictionary database to obtain a target subscription table; the second receiving module 740 is configured to receive the target subscription table sent by the object processing end and store the target subscription table in the integration engine database, so that the target subscription table can be called by a third party platform.

In some embodiments of the present application, the integration engine further includes a monitoring module (not shown in the figure), which is configured to monitor target data related to the target object, and determine whether the target data is changed; acquiring changed data under the condition that the target data is changed; and matching the changed data with the target object, acquiring matched data and storing the matched data in the integration engine database for the third-party platform to call.

In some embodiments of the present application, the monitoring module is specifically configured to respond to an input operation of the integration administrator, and acquire the target data to be monitored and a monitoring period in a target database; and monitoring the target data according to the monitoring period.

Referring to fig. 8, fig. 8 is a block diagram illustrating components of an object processing side according to some embodiments of the present application. It should be understood that the object processing side corresponds to the embodiment of the method in fig. 4 described above, and is capable of executing the steps related to the embodiment of the method described above, and the specific functions of the object processing side can be referred to the description above, and the detailed description is appropriately omitted here to avoid repetition.

The object processing side of fig. 8 includes at least one software function module that can be stored in a memory in the form of software or firmware or solidified in the object processing side, and the object processing side includes: a receiving module 810, configured to receive the database dictionary database and the subscription requirement table sent by the integration engine; an input module 820, configured to respond to an input operation of a user in the subscription requirement table according to the database dictionary base, and obtain basic information; an obtaining module 830, configured to obtain a target subscription table corresponding to the basic information, and send the target subscription table to the integration engine end, so that a third party platform can call the target subscription table at the integration engine end.

In some embodiments of the present application, the obtaining module 830 is specifically configured to, if it is determined that an index record table matching the basic information exists in the profiling index library, take the index record table as the target subscription table; and if the documenting index database does not have the index record table matched with the basic information, generating the target subscription table corresponding to the basic information.

Some embodiments of the present application further provide a computer-readable storage medium, on which a computer program is stored, which when executed by a processor can implement the operations of the method corresponding to any of the above-mentioned methods provided by the above-mentioned embodiments.

Some embodiments of the present application further provide a computer program product, which includes a computer program, wherein the computer program, when executed by a processor, can implement the operations of the method corresponding to any of the above-mentioned methods provided by the above-mentioned embodiments.

As shown in fig. 9, some embodiments of the present application provide an electronic device 900, the electronic device 900 including: memory 910, processor 920 and a computer program stored on the memory 910 and executable on the processor 920, wherein the method according to any of the embodiments described above is implemented when the processor 920 reads the program from the memory 910 through the bus 930 and executes the program.

Processor 920 may process digital signals and may include various computing structures. Such as a complex instruction set computer architecture, a structurally reduced instruction set computer architecture, or an architecture that implements a combination of instruction sets. In some examples, processor 920 may be a microprocessor.

Memory 910 may be used to store instructions that are executed by processor 920 or data related to the execution of instructions. The instructions and/or data may include code for performing some or all of the functions of one or more of the modules described in embodiments of the application. The processor 920 of the disclosed embodiment may be used to execute the instructions in the memory 910 to implement the methods shown above. Memory 910 includes dynamic random access memory, static random access memory, flash memory, optical memory, or other memory known to those skilled in the art.

The above description is only an example of the present application and is not intended to limit the scope of the present application, and various modifications and changes may be made to the present application by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application. It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising a … …" does not exclude the presence of another identical element in a process, method, article, or apparatus that comprises the element.

Claims

1. A method for hospital data access, which is applied to a data management end in a hospital data access system, wherein the hospital data access system further comprises an integration engine end and an object processing end, and the method comprises the following steps:

creating a database dictionary base, wherein the database dictionary base comprises: the data information and the data identification corresponding to the data information;

and sending the database dictionary database to the integration engine terminal so as to obtain a target subscription table according to the database dictionary for a third-party platform to call.

2. The method of claim 1, wherein the creating a database dictionary repository comprises:

creating a data table structure;

and responding to the operation of a user, and adding the data information and the data identification in the data table structure.

3. The method of claim 1 or 2, wherein prior to said sending said database dictionary repository to the integration engine, the method further comprises:

auditing the data information and the data identification in the data dictionary library;

and confirming that the data information and the data identifier are approved.

4. A method for hospital data access, which is applied to an integration engine side in a hospital data access system, wherein the hospital data access system further comprises a data management side and an object processing side, and the method comprises the following steps:

receiving a data dictionary database sent by the data management terminal;

acquiring a subscription requirement table selected by an integration administrator, wherein the subscription requirement table comprises: target objects and subscription information to be filled in;

sending the data dictionary base and the subscription requirement table to the object processing terminal so that the target object inputs the subscription information to be filled according to the data dictionary base to obtain a target subscription table;

and receiving the target subscription table sent by the object processing terminal and storing the target subscription table in an integration engine database for being called by a third party platform.

5. The method of claim 4, wherein the method further comprises:

monitoring target data related to the target object and confirming whether the target data is changed;

acquiring changed data under the condition that the target data is changed;

and matching the changed data with the target object, acquiring matched data and storing the matched data in the integration engine database for the third-party platform to call.

6. The method of claim 5, wherein prior to the monitoring target data related to the target object, the method further comprises:

responding to the input operation of the integration administrator, and acquiring the target data to be monitored and a monitoring period in a target database;

the monitoring target data related to the target object comprises:

and monitoring the target data according to the monitoring period.

7. The method of claim 5 or 6, further comprising:

and storing the message of the change of the target data to a message log.

8. A method for hospital data access, which is applied to an object processing side in a hospital data access system, wherein the hospital data access system further comprises an integration engine side and a data management side, and the method comprises:

receiving a data dictionary database and a subscription requirement table sent by the integration engine end;

responding to the input operation of a user in the subscription requirement table according to the database dictionary library, and acquiring basic information;

and acquiring a target subscription table corresponding to the basic information, and sending the target subscription table to the integration engine terminal for a third-party platform to call at the integration engine terminal.

9. The method of claim 8, wherein the obtaining the target subscription table corresponding to the basic information comprises:

if the index record table matched with the basic information exists in the filing index base, taking the index record table as the target subscription table;

and if the documenting index database does not have the index record table matched with the basic information, generating the target subscription table corresponding to the basic information.

10. A system for hospital data access, comprising:

the data management terminal is used for creating a data dictionary library, wherein the data dictionary library comprises: the method comprises the steps of obtaining data information and a data identifier corresponding to the data information; sending the database dictionary to an integration engine end;

the integration engine end is used for receiving the data dictionary database sent by the data management end; acquiring a subscription requirement table selected by an integration administrator; sending the data dictionary database and the subscription requirement table to an object processing end; receiving the target subscription table sent by the object processing terminal and storing the target subscription table in an integration engine database for being called by a third-party platform;

the object processing end is used for receiving the data dictionary database and the subscription requirement table sent by the integration engine end; responding to the input operation of a user in the subscription requirement table according to the data dictionary library, and acquiring basic information; and acquiring a target subscription table corresponding to the basic information, and sending the target subscription table to the integration engine terminal.

11. A data management terminal, comprising:

a creation module configured to create a database dictionary base, wherein the database dictionary base includes: the data information and the data identification corresponding to the data information;

and the data sending module is used for sending the data dictionary library to an integration engine end so as to obtain a target subscription table according to the data dictionary for a third-party platform to call.

12. An integrated engine-side, comprising:

the first receiving module is used for receiving a data dictionary library sent by the data management end;

a selection module, configured to obtain a subscription requirement table selected by an integration administrator, where the subscription requirement table includes: target objects and subscription information to be filled in;

the sending module is used for sending the data dictionary base and the subscription requirement table to the object processing terminal so that the target object can input the subscription information to be filled according to the data dictionary base to obtain a target subscription table;

and the second receiving module is used for receiving the target subscription table sent by the object processing terminal and storing the target subscription table in an integrated engine database for being called by a third party platform.

13. An object processing side, comprising:

the receiving module is used for receiving the data dictionary base and the subscription requirement table sent by the integration engine end;

the input module is used for responding to the input operation of a user in the subscription requirement table according to the data dictionary base and acquiring basic information;

and the acquisition module is used for acquiring a target subscription table corresponding to the basic information and sending the target subscription table to the integration engine terminal so as to be called by a third party platform at the integration engine terminal.

14. A computer-readable storage medium, having stored thereon a computer program, wherein the computer program, when executed by a processor, performs the method of any one of claims 1-9.

15. An electronic device comprising a memory, a processor, and a computer program stored on the memory and running on the processor, wherein the computer program, when executed by the processor, performs the method of any one of claims 1-9.