Figure 2.

Example data and information systems architecture for effective remote surveillance. A and B indicate data acquisition pathways for 2 different types of medical devices: a traditional patient monitor (“medical device”) and a wearable patient monitor (“wearable medical device”). (1) In pathway A, patient data collected on the medical device are fed into “Medical Device Drivers,” a software application that enables connection between medical devices and downstream software applications. The “device gateway” then receives the data and transforms it into a Healthcare Language-7 message. The “Healthcare Language-7 integration engine” (C) receives the Healthcare Language-7 messages from the device gateway and then splits and distributes them to (D) the “data lake” (composed of the “enterprise data warehouse” that includes clinical and nonclinical high-resolution data) and (F) the electronic medical record. Data from the enterprise data warehouse are sent to the “remote monitoring and predictive analytics servers” on which analytics can be performed and alerts generated. These alerts are fed to (E) downstream systems that alert the clinician, such as pagers or visual display systems. (2) Alternatively, in pathway B, the “wearable medical device” may send its data to a “cloud-based storage” system. Using an “application programming interface (API),” the data can then be delivered to the data lake.