Trinity Health began exploring the Internet of Things as an important technology about ten years ago. Since then, it has invested in implementing pilots centered on a number of IoT-based point solutions. These have included IP-enabled medical devices and patient wearables and, more recently, self-regulating refrigerators and home monitoring tools. The trials are helping Trinity Health learn about IoT execution requirements and understand how more pervasive collection of and access to patient health data can lead to new ways of working. Point solutions serve as strategic experiments whereby Trinity Health identifies and refines sensor placement; creates middleware to connect technologies and data; develops vendor relationships with device providers, data aggregators, and infrastructure suppliers; and builds associations with promising start-up firms. Often, IT initiates a point solution to inspire colleagues to reimagine current work processes. IT partners with key internal areas to increase the likelihood that new ideas will be accepted by and integrated into the organization. Informatics represents a particularly good partner because its staff is clinically and technically savvy, making it good at highlighting where point solutions could be productive.
In 2012, St. Joseph Mercy Oakland Hospital, one of Trinity Health’s member hospitals, planned a facilities upgrade. Trinity Health recognized the initiative as an opportunity and began a pilot—the Intelligent Care System (ICS)[foot]Trinity Health’s Intelligent Care System (ICS) is an integrated suite of healthcare technologies.[/foot]—to deliver an innovative patient health experience from assembled point solutions. Trinity Health furnished thirty hospital rooms with key sensor-embedded equipment. The pilot team described a vision for how integrated technologies would help the health system improve four outcomes: safety, clinical, satisfaction (of patients, doctors, and staff), and efficiency. Then leaders selected eight technologies that they believed would best support this vision.[foot]“St. Joseph Mercy Oakland (SJMO) Intelligent Care,” St. Joseph Mercy Oakland Hospital SJMO, video that describes the eight ICS technologies piloted at the hospital, https://www.youtube.com/ watch?v=n-cQR0iZjwU.[/foot]
The pilot team drew upon lessons from earlier strategic experiments and worked with vendor partners to resolve execution obstacles. Security was a key concern. Rather than pushing for open network architectures, Trinity Health opted for a closed network approach—not just for the component technologies, but for the entire hospital—to significantly reduce cybersecurity concerns (i.e., the risk that devices could be hacked and misused).
The proprietary nature of the ICS networks, devices, and data formats introduced significant integration challenges. The pilot team constructed a semantic integration and reconciliation layer to bridge the eight technologies. By connecting IoT data with electronic medical records and the company’s enterprise data infrastructure, this layer also helped the project team assemble a holistic view of the patient. The data infrastructure included master data management and data quality management for its core structured and unstructured data and brought with it a growing data science team focused on analytics.
Additionally, the pilot team established policies and procedures, both to reinforce security and ease integration and to address data ownership and appropriate data use concerns. The team relied heavily on Trinity Health’s vendor management, legal, and contracting capabilities to coordinate within and across external partners. HIPAA and related practices came in handy. For example, Trinity Health mandated that business associate agreements [foot]A BAA is a contract between a HIPAA-covered entity and a HIPAA business associate that protects personal health information (PHI) in accordance with HIPAA guidelines. The agreement requires partners to share risk of data breach and to respect data use restrictions.[/foot] be secured with its IoT partners, from device providers to data aggregators. HIPAA also helped to establish explicitly that patients owned the data that flowed throughout the ICS.
Pilot leaders began developing specific use cases that leveraged subsets of the eight chosen IoT technologies in order to impact priority levers of patient care. The levers included fall prevention, pressure ulcer reduction, improved alarm management and response, simpler workflows, and better communications. For example, one use case was designed to test the integration of a nurse call system with a real-time location system and smart bed technology; the lever was to reduce fall risk. The pilot team configured the smart bed technology to send an alert to a nurse’s mobile device if a patient starts to get out of bed. When an alert is received, the nurse can respond to the patient, call the patient and ask him or her to remain in bed, or text another caregiver to respond to the patient. There is an electronic display board of on-duty staff real-time locations, and nurse call alerts are automatically cancelled upon the caregiver entering the patient’s room. The resulting 57% reduction in nurse call response time correlated with a 12% improvement in patient satisfaction.
Once the use case infrastructure was in place, additional use cases were tested.