chrispeng [ad_1]
Aiming at the development trend of hospital informatization, a kind ofSmart HospitalThe Internet of Things solution adopts WLAN network to realize data transmission, and introduces Internet of Things application middleware platform to realize the standardization and standardization of Internet of Things application deployment, avoiding repeated construction of infrastructure and information islands in the process of hospital informatization. The article first introduces the overall architecture of the Internet of Things application in smart hospitals, expounds the associated objects of RFID tags and WiFi tags, the implementation process and the security system; secondly, the implementation block diagram of the Internet of Things middleware platform is described, and the implementation of key modules and data processes are discussed; The typical hospital application system based on the Internet of Things middleware platform is given again, and the realization and functions of each subsystem are explained; finally, the deployment method of the system is given. The system has been successfully applied on a pilot basis, and after further optimization and improvement, it can be promoted and used on a large scale.
1 Introduction
Internet of ThingsThrough sensing technology, people and people, people and things, things and things in the real world are correlated, and signals are transmitted through the network. These correlated signals are processed, controlled, mined, and analyzed through platform software, and finally we can get the results. Information needed. Applying the Internet of Things technology to the hospital industry can easily solve the visual management of hospital assets, such as where the assets are, what is the current status, what is the current situation, and how the process is used. Through the visualized management system of hospital assets, the hospital’s work process is optimized, daily operating costs are reduced, the hospital’s work efficiency is improved, and the safety of medical care is improved.
Hospital assets include patients, doctors, nurses, nurses, medical equipment, medical drugs, medical equipment, medical places, medical waste, etc. By wearing corresponding label products to hospital assets, the status of back-end visualized management of assets is realized, and the use efficiency and work efficiency of assets are analyzed. Tags are divided into RFID tags, WiFi tags, RFID+WiFi tags, WiFi+ sensors, and RFID+WiFi+ sensors. Scan RFID tags, view basic information related to assets, and interface with the HIS system to improve business efficiency. The sensor detects the environmental temperature and humidity, the vital characteristics of the patient, and the emergency call button, and transmits the data back to the background management system through the WiFi network to realize remote monitoring. Reverse control can be realized as required.
As the Internet of Things technology continues to advance and deepen in hospitals, asset management and simple applications based on RFID, WiFi, barcode and other sensor technologies have begun to be implemented. The independent construction of each subsystem gradually constitutes an application information island. In the future, in order to achieve data fusion, it is necessary to integrate the data, processes, and reports of these IoT subsystems. Due to different IoT subsystem development platforms, different software versions, different interface specifications, and different manufacturers, integration will be a very complex and troublesome task. The construction of various subsystems will also cause repeated construction of infrastructure, resulting in waste of resources. This is the result that the leaders of the hospital information department do not want to see. In order to solve this problem, it is necessary for the hospital informatization supervisor to take a long-term consideration and build an informatization platform for the application of the Internet of Things in the hospital to achieve unified planning and phased implementation.
This paper proposes a solution for the implementation of a hospital IoT application information platform, and introduces a hospital IoT application middleware platform to realize the unified deployment and management of IoT data. The platform provides external standard interfaces to facilitate data integration with upper-level application software and facilitate data integration with the hospital’s existing information system. Based on this platform architecture, when new IoT applications need to be extended, only the upper-level application software needs to be developed according to the business process of the new application. The assignment, association, event setting, warning setting, map setting, permission setting, etc. work in Just click and operate on the IoT application middleware platform. This implementation architecture realizes the data integration and sharing of the Internet of Things applications in the hospital, eliminates the problem of information islands between various subsystems, and facilitates the maintenance and management of the platform of the information office colleagues.
2. System implementation architecture
Figure 1 shows the architecture diagram of the hospital IoT application system, which is divided into four parts: object, data collection, network transmission and software application. The application software includes two parts: IoT middleware software and functional application software.
Figure 1 Hospital IoT application system architecture
Application objects: including doctors, nurses, nurses, focusing on patients, infants, medical equipment, medical equipment, medical waste, vehicles, drug storage rooms, vaccine storage places, blood storage places and other assets that have management needs.
Data collection layer: reflects the technical characteristics of the Internet of Things application. Different from Internet applications, IoT applications need to associate tags with application objects, and obtain information and data of application objects through data collection terminals, such as personnel positions, behavior trajectories, equipment maintenance records, medical waste treatment processes, environmental temperature and humidity, and patient vital characteristics data Wait. For passive tags, it is necessary to scan through a fixed reader/handheld terminal to read the data; for active tags, the tag periodically actively emits a signal, and the signal contains sensor detection data.
Network transmission layer: realize data transmission.Adopted in the hospital industryWLANThe internet. Deploy WiFi wireless routers in areas that need to be managed. The wireless router receives the data sent by the tag reader, handheld terminal, and active tag, and forwards the data to the IoT application middleware platform according to the protocol requirements. The wireless router is required to be configured to support multiple services such as data, voice, video, positioning, etc. concurrently. At least two SSIDs are configured, and the WAPI authentication mechanism is introduced. Only tags, readers, handheld terminals and other products with legal digital certificates of this system are allowed to access the network and transmit data to ensure the safety and reliability of WiFi coverage in the hospital.
Application layer: Including hospital IoT application middleware software and functional application software developed according to business processes. Middleware software is responsible for the basic management of hospital IoT applications, including label management, personnel management, department management, authority management, map management, event management, security management, location management, report management, etc. Functional application software includes special patient positioning management, baby safety management, key patient emergency call management, critical patient fall prevention management, emergency call management of medical staff, environmental temperature and humidity monitoring, vital body characteristics monitoring of key patients, and full life cycle of medical supplies/equipment Management, medical waste management, etc.
Public technology: runs through the entire system architecture, including system identification, management, and data security. Different security measures are adopted at different layers. For application objects, each label, task, action, and event has its own identity. Identifiers are managed hierarchically by objects.
The system workflow is:
(1) The tag actively sends data packets to the wireless router through the reader. The data packet contains sensor monitoring data. The format and frequency of tag data transmission are configured in advance through the IoT application middleware platform.
(2) The wireless router works in the thin AP mode and forwards the label data with authority according to the authentication mechanism. According to the agreed agreement, the wireless router forwards the data to the hospital IoT application middleware platform.
(3) The hospital IoT application middleware platform unpacks and analyzes the data, and stores it in the database according to the pre-configured permissions. The location management module in the middleware platform needs to receive tag data packets forwarded by more than 3 wireless router base stations, and calculate the location of the tag by calling the positioning algorithm according to the signal strength in the data packet, and display it on the map. In order to improve the positioning accuracy, the system adopts the positioning algorithm of RSSI + map matching, and the positioning accuracy can reach 1-3 meters.
(4) The application software calls the business process to communicate and interact with the middleware platform, and displays the monitoring data on the software interface in real time. Support two-dimensional map display and three-dimensional map display. When an event warning occurs, the application software interface prompts, supports interface red markings and voice prompts. Application software supports viewing and management according to permissions.
3. Middleware platform structure of hospital IoT application
The hospital Internet of Things application middleware platform is the core of the system, which realizes data collection, transmission, display, early warning, and management in one, and realizes data conversion and standardization. Downward and hardware sensors, upward and application layer software, parallel to the hospital’s existing information system interface. The hospital IoT application middleware plays an intermediary role in the hospital IoT application, shielding the complexity of the front-end hardware, and standardizing the collected data and sending it to the back-end IT system. In the next step, big data mining and analysis for IoT applications in the hospital industry will export data from this platform.
The IoT application middleware system runs on the Windows Server server. In order to facilitate centralized management and remote control, the system is developed based on the BS architecture and supports remote web access. Figure 2 shows a block diagram of the system implementation structure, which is divided into 6 modules: database, positioning gateway, basic service, data management, data application system, and integrated interface.
(1) Database
Using Windows SQL 2008 Standard Edition, save system data parameters, including tag upload data, positioning gateway solution data, and data management module setting data.
(2) Positioning gateway
Receive the positioning signal forwarded by the WiFi tag and call the positioning algorithm. Calculate the label position according to the reference coordinates of the map.
(3) Basic services
Realize the call processing of maps, reports, and workflow engines.
(4) Data management
Contains module functions such as label management, personnel management, event management, map management, location management, security management, and statistical report management.
Tag management is the main tag entry and deletion. The system only monitors the tags that are in the enabled state in the database.
Personnel management completes the entry and deletion of personnel lists, associates personnel with tags, and restricts personnel activity partitions and activity time ranges.
Event management sets up alarm events. The setting requirements for each alarm event are specific to personnel name, area name, time range and priority.
Map management: Import and delete maps, partition and label the maps.
Security management settings system administrator login account.
The statistical report forms a report for asset-related data according to keywords such as time period, day, week, department, and asset name.
Figure 2 The structure diagram of the hospital IoT application middleware platform
(5) Data application
Contains modules such as asset retrieval, alarm event query, statistical reporting, and system management. It belongs to the web application interface, which is convenient for the administrator to carry out daily maintenance and management of the middleware platform.
Query the database according to the asset name and time range, obtain the asset’s course of action within the specified time range, display it to the user in a visual way, and draw the course of the course on the map.
Record tag alarm events in a list. An alarm event requires data such as asset information, tag information, trigger time, trigger location, and current processing status. Supports query by asset name, by tag ID, by location, by time period and other fields.
(6) Integrated interface
Two interface modes, API and EVENT, are designed, and EVENT is a high-priority event interface.
The API is provided as a lib library and integrated into the third-party software. You can access the resources in the IoT application middleware system by calling the API. The Lib library package contains all the object API functions in the data management module.
EVENT actively sends message packages to third-party software platforms to achieve linkage, and supports standard-based HTTP Post, Web Service and Mail three modes.
Considering the future large-capacity operation, distributed deployment. Divide the system shown in Figure 2 into 3 subsystems. These three subsystems are independently designed and developed, and each subsystem uses standard interfaces for communication. Database selection, no need to develop, just install directly; positioning gateway is designed and developed according to the subsystem mode; basic service module, data management module, data application module and integrated interface module are designed and developed according to one subsystem mode. The biggest advantage of this architecture is to facilitate the flexible deployment of the system in the future. Three subsystems can be installed on three servers to run, or three systems can be installed on one server to run. This mainly depends on the number of tags that the system needs to manage.
4. System function
The visualized management solution of hospital assets is built on the middleware platform of the hospital’s Internet of Things application, and provides the following functional applications around WiFi positioning technology:
(1) Special patient safety management
Wear tag products for special patients (VIP patients, mental patients, infectious disease patients, the elderly, infants and young children), locate personnel locations in real time through RFID tags, and record personnel activity tracks. When patients with infectious diseases, infants, psychiatric patients and other key monitoring patients leave this ward/enter an unauthorized ward, the system will automatically alarm and prompt. When the monitored vital feature data is over alert, the system will automatically alarm and prompt. When the old man falls, the tag with acceleration monitoring capability triggers the fall event, and the system automatically alarms. After an alarm event is triggered, the system displays the asset name, alarm category, alarm time, and current location, and at the same time, it links with the video surveillance system to call the current screen.
VIP patients wear RFID tags with calling function. When patients encounter an emergency at any location in the hospital, they can press the button on the tag to make a mobile call instead of calling at the bedside as before. After the system receives the call alarm, it locks the patient’s call area, links the video image, and checks the scene.
The nurse scans the patient’s RFID wristband to identify the patient’s identity and inquire about the patient’s basic information.
(2) Safety management of medical staff
Wear label products with calling function for medical staff and nurses. When an emergency occurs anywhere in the hospital, the medical staff can touch the button on the label to call for help. The system will automatically alarm, lock the call area of the medical staff, and link the video Images, check the scene. When an emergency event occurs, the nurse can also look up the current location of the doctor through the platform to quickly find the doctor.
(3) Medical equipment management system
Through the Internet of Things technology, the existing asset management system of the hospital is upgraded and improved to realize the full life cycle management of medical assets. The content includes asset purchase, asset allocation, asset maintenance, asset inventory, asset tracking, statistical reports, etc., to achieve visual asset management and avoid the problem of symmetry between physical assets and financial book information. Managers use the software platform to view basic asset information, current location, quantity, maintenance plan, etc. in real time; use handheld terminals to scan asset tags for asset inventory and query asset maintenance records. When the asset is not in the predetermined location, the administrator can check the current location of the asset and the moving track by entering the asset name. When the asset needs maintenance, the system automatically alarms.
Track the movement status of assets and equipment, and count the efficiency of asset use.
(4) Refrigeration and freezing environment monitoring system
Install RFID tags with environmental parameter monitoring in refrigerated and frozen environments such as medicines, blood banks, vaccine storage places, and sterile equipment storage places, and set environmental parameter thresholds through the system. The tag actively transmits the monitoring data, and the system interface displays the data of the monitoring environment in real time. When the storage environment parameter changes exceeding the threshold value, the system immediately alarms, eliminating manual timing on-site recording and improving work efficiency.
The application of real-time online environmental monitoring ensures that the medical storage environment meets the requirements and avoids frequent problems caused by changes in environmental parameters.
(5) Tracking management of medical drugs, equipment, and garbage
Install RFID tags for medicines, equipment, garbage and other medical equipment. The tags are associated with the medical equipment. The system records the path, operation and running time of the medical equipment in real time to ensure that the medical equipment is sent and received, disinfected, transferred, and transported in accordance with regulations. Process execution. When the execution process does not follow the standard process operation, the system automatically alarms. When the medical equipment exceeds the authorized working range, the system alarms. Managers can track the entire management process according to the alarm records and find out where the problem lies.
5. System deployment and implementation
5.1 Infrastructure deployment
The system transmits data through the WLAN network. Compared with active RFID and Zigbee technologies, WLAN has the characteristics of high bandwidth and high real-time performance. It also supports the transmission of voice, data, and video, which can effectively meet the needs of mobile medical care, remote visits, voice calls, As business needs such as telemedicine, WLAN technology has gradually entered hospitals and will develop rapidly. So this scheme is based on WLAN network design. For hospitals that have deployed WLAN networks, the system can be directly reused to avoid infrastructure reconstruction. The hospital IoT application management platform supports WLAN AP to work in FAT mode and FIT mode. In addition to deploying WLAN equipment, the system needs to deploy triggers based on positioning accuracy requirements. The trigger satisfies the precise positioning of 0.5 meters and is mainly used to distinguish hospital beds, wards and wards. Figure 3 shows the system infrastructure deployment network architecture diagram.
Figure 3 Infrastructure deployment diagram of the hospital IoT application management system
Network security includes several aspects such as user authentication, authority control management, data encryption, and physical isolation. In order to ensure the security of the hospital’s WLAN network, the constructed WLAN network needs to open the WAPI authentication mechanism. It can further integrate H3C’s EAD terminal admission control system to realize tag user identity authentication, network security authentication and efficient terminal management.
5.2 How to wear the label
Hospital IoT application tags include two categories: passive RFID tags, which collect asset data to the hospital IoT application middleware platform through an RFID reader. Active WiFi tags, which actively collect sensor data to the hospital IoT application middleware platform. Different label related assets have different ways of wearing:
² The mobile emergency call label for doctors and nurses adopts a badge hanging type, which is convenient for medical staff to operate. Normally, the medical staff can put the label in the pocket of the work clothes.
² The patient’s label adopts wristband type and badge type. The label that needs to monitor the vital signs of the patient depends on the specific situation. The patient tag must be integrated with RFID+WiFi to facilitate short-distance and long-distance identification.
² The label of medical equipment is pasted or bound. For small equipment, it is recommended to use the paste method; for the medium and large equipment, it is recommended to use the binding method. The device is larger, and the optional label is also larger, so it is easy to find when fixed on the device.
² Labels for medical devices are either pasted or embedded.
² The label of medical waste is printed or pasted. Each medical waste bag is printed with an RFID label or pasted with a label in advance.
² Environmental monitoring tags are placed in the monitoring environment. Some tags also need to use probes to ensure the accuracy of the monitoring data.
Regardless of passive tags or active tags, tags need to be associated with assets before they are distributed. The associated operation is executed on the IoT application middleware system. Each label needs to be associated with assets, setting the department, preset events, activity scope and other operations. The hospital IoT application middleware platform supports intercommunication with hospital HIS. The nurse can scan the patient’s tag with a handheld terminal to immediately call up the patient’s basic information and treatment process records. By entering the asset name, you can immediately query the asset’s current location, activity trajectory, and monitoring data.
5.3 Application platform deployment
The hospital IoT application solution supports centralized deployment and distributed deployment, and realizes a three-tier deployment management method for wards, departments, and hospitals. The main difference between centralized deployment and distributed deployment is the deployment of the positioning engine server. Centralized deployment uses one positioning engine, and the positioning engine data is forwarded to the IoT application middleware platform through the agreed interface; distributed deployment uses multiple positioning engines, and the positioning engine server data is forwarded to the IoT application middle through the agreed interface Software platform. Distributed deployment is mainly used to disperse the concurrent load of system work and improve the real-time performance of work.
Figure 4 The deployment topology diagram of the hospital IoT application management system platform
The first floor is ward-level management (floor): authorized personnel manage subordinate patients, medical staff, important equipment, environmental humidity monitoring, etc., and complete the functional operations provided within the authority. Mainly authorized to ward nurses.
The second layer is department-level management: authorized personnel manage subordinate patients, medical staff, important equipment, environmental temperature and humidity monitoring, etc., and complete the functional operations provided within the authority. Mainly authorized to the director of the department.
The third layer is the overall management of the hospital: authorized personnel manage the patients, medical staff, equipment, monitoring temperature and humidity in the area, and complete the functional operations provided within the authority. The administrator on this level can manage the public areas of the hospital, such as the garbage transfer station, the hospital gate, the entrance and exit of the outpatient building, and the inspection and laboratory area. It is mainly authorized to the person in charge of the information department and the head of the hospital.
Based on the system deployment architecture, medical staff are equipped with mobile terminals, and advanced secure link encryption technology is adopted to realize mobile visual management on any occasion and at any time in the hospital to meet the needs of dynamic portable applications.
6 Conclusion
As a new and cutting-edge technology, the Internet of Things has no precedent for large-scale application at home and abroad. The main reason is that there are some problems in the business development process such as inconsistent standards and high application costs. However, as technology continues to mature and standardization work continues to improve, these problems will gradually and effectively be resolved.
This article presents an overall solution for the application of the Internet of Things in hospitals, and introduces the system architecture and implementation deployment of the solution. The construction of the Internet of Things in hospitals is a long-term continuous improvement process that requires long-term planning, unified standards, unified command, and phased implementation. The hospital IoT application middleware platform proposed in this paper is responsible for basic functions such as label management, asset management, map management, process management, and system management to facilitate application expansion in the next step. When you need to increase the personnel location management application, you only need to develop the top-level application. The distribution, association, permissions and other settings of the relevant labels can be operated on the middleware platform; when you need to add the drug circulation management application, you only need to develop the top-level application. Yes, the distribution, association, and permissions of the relevant tags can be set on the middleware platform. The hospital Internet of Things application middleware platform greatly improves the progress of the hospital’s development and deployment of Internet of Things application systems, shortens the project cycle, and at the same time standardizes standardized interfaces to facilitate intercommunication with hospital information systems such as HIS, PACS, CIS, and EMR.
[ad_2]
