Currently, China's large and medium-sized medical institutions have built HIS systems with basic functions and basic CIS systems such as PACS, RIS, LIS, etc., and the construction of clinical medical management information systems has begun to be extended to departments with more intensive diagnostic and therapeutic behaviors such as operating rooms and ICUs.
However, the realization of all these architectural patterns is inseparable from the connection between data and data.
As we all know, the hospital's information management network is divided into an intranet and an extranet, internally it is the business process management of each department and position; externally it is the connection between the HIS system and the external medical and healthcare public **** platform. With the full penetration of medical informatization into the operation and management of hospitals, interconnection ratings, electronic medical record ratings, etc. bring new downstream demands. The construction of various data interfaces has become more and more urgent, almost to the point where it is difficult to carry out many of the hospital's operations without doing data interfaces.
Including the National Health Commission has launched relevant mandatory policy requirements: for example, in 2020, all second-level hospitals to achieve the Health Commission electronic medical record grading evaluation of more than 3; three hospitals to achieve the hospital information interconnection of various diagnostic and treatment links to achieve the standardized maturity of the hospital information interconnection assessment of level 4.
Traditional interface methods have a way around the hurdle
Because of this, as a former head of the information section of a number of grassroots hospitals, currently working in a professional medical IT company for many years of medical IT practitioners. All along, in the hospital information department, the most exhausting for me is not a variety of hardware and software frequent installation and maintenance, but the superiors and issued a variety of information technology docking requirements; in the IT company, I did the most is not the product development, and to solve a variety of data collection, software data interfaces, the coordination of the relationship between the parties.
Traditional realization of multi-system data **** enjoy a variety of methods, these methods have their own advantages and disadvantages, to cite a common data docking methods:
Database **** enjoy the data mode. System A and System B exchange data by connecting to the same table on the same database server. This way of interaction is much simpler. Through the transaction mechanism of the database, it can be made into a reliable data exchange. However, the number of systems that can be connected at the same time is limited in this way, and it is unlikely that systems from two different companies will open up their own databases.
Other ways to realize the ftp/file **** enjoy the server way, message way. These traditional data interface methods although the principle of realization is different. But there is a *** the same thing, all need to be the original software vendors with open interfaces to realize the case.
With other industry IT systems are different, the medical industry IT system is more complex, and the core data is extremely important. In fact, many vendors are not willing to see the hospitals to put forward this data interface requirements, because for any medical software vendors, this also means that they find trouble. More because, too many stakeholders, the various medical IT vendors independent of each other, each occupying a mountain, or out of data security considerations, or out of business competition, and is not willing to cooperate. These factors also contribute to the fact that the cost of interface development for the healthcare industry is probably the highest of any industry. It often costs anywhere from tens to hundreds of thousands of dollars.
No interface under the open Hospital multi-system data docking and public health automatic reporting design and implementation
So, there is no way to bypass the original software vendors can realize the data interface? Today I want to share with you is no interface open under the hospital multi-system data docking and public health automatic reporting of a design and implementation.
Below we analyze a specific scenario, the hospital needs to HIS system data uploaded to the regional public health platform, these data need to be uploaded, including basic patient information, consultation, charging records, discharge instructions, cost data, and even medical imaging images. Currently, these data are in various modules of the HIS system, including various form data, detail page fields, images, etc.
But for various reasons, we could not get data interface support from HIS manufacturers. So the only way we can get this data is to grab it from the HIS interface and then enter it into the interface of the public health platform. This process can be achieved by generating an interface using the 101 Software Universal Data Interface Generator.
First of all, we need to use 101 Software Interface Generator to configure a tool to collect data from the HIS system. 101 Software Universal Data Interface Generator refreshes and collects data at a fixed frequency from the target software interface and writes it to the collection database, and then provides a data interface to the public health platform based on the collection database (including database view and data dictionary), which can be provided in the form of a database view interface, or in the form of a database view interface, or in the form of a database view interface. Provide data interface (including: database view, data dictionary) to the public health platform based on the collection database, which can be provided in the way of database view interface or web service;
Scope of application of Software Common Data Interface Generator
Relative to the traditional data interface, 101 Software Common Data Interface Generator has the following characteristics:
1.Supporting the compatibility of almost all kinds of CS/BS software based on the Windows platform;
2.Supporting the compatibility of almost all kinds of data collection software based on the Windows platform. Software;
2. Do not need to cooperate with software manufacturers to generate data interfaces;
3. Tools are simple and practical, users can generate data interfaces in accordance with their own needs for DIY configuration;
4. Typically, the configuration of the generation of data interfaces for a target software can be completed within an hour.
5. The cost is much lower than the software manufacturers with the data interface to do.
Just like all current data interface implementation, 101 Software Universal Data Interface Generator is universal, but not everything. In the following three cases, 101 interface generator temporarily can not fully meet user needs.
1, data real-time requirements are very high, requiring data refresh in real time within seconds, such as the hospital's call system, temporarily unable to meet (subject to software robots click to operate the target software's response time is generally required to several seconds to tens of seconds);
2, the data required to obtain the target software interface can not be displayed on the visible. (Because the tool can only realize data acquisition on the target software WYSIWYG data)
3, the server side of the target software can not support continuous data query request pressure. (This way of data collection requires repeated data queries on the target software to obtain the latest real-time updated data, this repeated query request process may give the target software server-side pressure)
But it is worth pointing out that it has been realized that the data interface is truly zero-code operation. Even if you don't have an IT background and don't know how to code, it's easy to DIY a software data interface for your own work scenario. I once found an ordinary resident, he completely rely on their own hands on the generation of a physical examination car reported to the hospital health management system data interface.
In the healthcare IT industry, where data silos abound, automating data reporting on public health platforms as an alternative to traditional data interfaces is not a bad solution. How far and how many areas can it solve the many pain points of data interfaces, we can try it.