Spok Care Connect is marketed as a unified clinical communication platform for hospitals and health systems. Spok describes the suite as spanning contact center operations, on-call scheduling, secure messaging, enterprise directory, clinical care, and paging. The vendor states that the platform integrates with existing systems to help organizations access, prioritize, and act on information, with the goal of improving workflows and reducing patient safety risks. Spok also describes a hosted deployment option that removes server footprint and uses a recurring subscription model. [1][2]

Documented Platform Components

Spok's product pages identify several components within the Care Connect suite. These include contact center solutions, on-call scheduling, secure messaging, enterprise web directory, clinical care tools, and paging services. The vendor positions the enterprise directory as a centralized source of contact data for roles, departments, locations, and affiliated physicians, while on-call scheduling is described as a source of real-time schedule updates. [1][2]

The hosted solution page lists enterprise web directory, on-call scheduling, and Spok Mobile as base components. Spok states that adding Spok Console can support contact center functions, with Spok Voice Connect available as an additional feature. The vendor also describes paging as part of its platform, referencing what it calls the nation's largest paging network. [2][1]

Secure Messaging and Directory Workflows

Spok's secure messaging materials describe integration with provider directory information, clinical systems, the EHR, and on-call schedules. The vendor states that users can send secure messages, images, data, and videos from smart devices or desktop apps, and that communications are logged for auditability. Spok says the messaging is designed to help support HIPAA requirements and also meets PIPEDA compliance for Canadian partners. [4]

Spok Care Connect Web is documented in Spok's knowledge base as a browser-based tool for sending and receiving secure, encrypted, HIPAA-compliant messages. The documentation states that it connects users with their site's contact directory and allows communication with other Care Connect Web and Spok Mobile users. The intended use section specifies that the tool should not be used in the diagnosis, cure, mitigation, treatment, or prevention of illness or disease. [6]

Hosted Deployment Considerations

Spok's hosted solution page describes a deployment model with easy installation upon sign-up, a recurring subscription plan, no server footprint, and no upfront capital or start-up fees. The vendor states that the base solution includes enterprise web directory, on-call scheduling, and Spok Mobile, all managed by the same team that Spok says is trusted by over 2,200 hospitals. Spok presents this as a way to reduce hospital IT burden. [2]

EHR Integration and Event-Driven Communication

A Spok datasheet describes integration with Epic EHR systems. According to the vendor, Epic can generate HL7 ADT messages with patient demographics, room and bed assignments, nursing station extensions, visit type, and privacy flags. Spok Care Connect receives these messages and updates its patient repository, linking patients to the correct room and nursing station extensions and flagging confidentiality status. [5]

The datasheet also describes WCTP messaging integration with Epic Secure Chat across Haiku, Canto, Rover, or desktop. Spok states that operators can send predefined templates, such as a Code STEMI alert, to recipient groups, with messages including event type, patient location, identifier, and callback instructions. The vendor also describes discharge events triggering alerts to Environmental Services staff for room turnover workflows. [5]

Operator Console and Cisco Webex Integration

Spok publishes technical documentation for operator console users running Cisco Unified Communications Manager with Cisco Webex Contact Center integration. The documentation covers Spok Care Connect Suite 2.6 and later, describing integration through Cisco TSP for non-ACD call control and through public REST and WebSocket APIs for agent state, ACD line call control, and screen pop data. [3]

The technical requirements include SQL Server 2019 or 2022 in standalone or AlwaysOn configuration, a load balancer in front of Care Connect Servers, and CA-signed SSL certificates. Cisco licensing requirements include an Enhanced license for each Operator Console and a minimum of one Standard license for each agent in a Webex Contact Center environment. Spok notes that determining licensing requirements is the responsibility of the client and Cisco representative. [3]

Implementation Context and Customer Example

Spok's case study describes VHC Health, a 537-bed health system in the Washington D.C. metropolitan area, which partnered with Spok in 2018. The case study states that VHC Health transitioned to Spok Care Connect in January 2019 to accompany its Epic EHR integration. The deployment included MediCall console, WebXchange for directory and on-call scheduling, Spok Mobile, paging options, and Spok Voice Connect implemented in 2024. [7]

The case study reports monthly communication metrics attributed to the deployment: 483,727 calls, 397,707 messages via Spok Mobile and SMS pages, and 11,830 average monthly web hits. It also lists emergency code page volumes, including 315 code blue, 207 code red, 665 code STEMI, 3,023 trauma alerts, and 2,538 NICU team or STAT pages. These figures are presented by Spok as results from the VHC Health implementation. [7]