Creating the On-Premises Gateway and Spok Go Integrations

Before You Begin

• Ensure e.Notify 7.1.3 is used. 
• Ensure you have the URL of the load balancer for the on-premises gateway in order for e.Notify to communicate with Spok Go.
• Ensure the customer has set up user accounts within Spok Go and e.Notify.

e.Notify Integration

See Integrating e.Notify with Spok Go for instructions on configuring the e.Notify integration.

Before You Begin

• Ensure you have MediCall version 11.12 or higher installed
• Ensure you have the URL of the load balancer for the on-premises gateway in order for MediCall to communicate with Spok Go.

MediCall Integration

See Integrating MediCall with Spok Go for instructions on configuring the MediCall integration.

Before You Begin

• Ensure you have Smart Suite version 7.1.3 installed.
• Ensure you have the URL of the load balancer for the on-premises gateway in order for Smart Suite to communicate with Spok Go.
• If you will configure single sign-on, ensure each user has an email with the correct domain (name@besthospital.org). If the domain is incorrect, the user will not be able to sign in using single sign-on.
• If you will configure single sign-on, ensure the display order for emails is set within Smart Center. Only the first email will be synchronized during the integration.

Smart Suite Integration

See Integrating Smart Suite with Spok Go for instructions on configuring the Smart Suite integration.

Before You Begin

• Ensure you have Spok Console version 7.11 or higher installed
• Ensure you have the URL of the load balancer for the on-premises gateway in order for Spok Console to communicate with Spok Go.

Spok Console Integration

See Integrating Spok Console with Spok Go for instructions on configuring the Spok Console integration.

Before You Begin

• Ensure you have Spok Messenger version 5.17 or higher.
• Ensure you have the URL of the load balancer for the on-premises gateway in order for Spok Messenger to communicate with Spok Go.
• For TAP connections, ensure you followed the TAP specifications outlined in the Telocator Alphanumeric Protocol (Nurse Call) Interface Specifications.

Spok Messenger Integration

See Integrating Spok Messenger with Spok Go for instructions on configuring the Messenger integration.

Before You Begin

• Ensure you have the URL of the load balancer for the on-premises gateway in order for systems that are sending HL7 to communicate with Spok Go.
• Ensure you followed the HL7 specifications outlined in the interface specifications documents below:
  • HL7 Interface Specifications - ORM General Order Message.pdf
  • HL7 Interface Specifications - ORU Observation Results.pdf
  • HL7 Interface Specifications - ORA Observation Report Alert Acknowledgements.pdf

HL7 integration

See Integrating HL7 with Spok Go for instructions on configuring the HL7 integration.

Before You Begin

• Ensure you followed the TAP specifications outlined in the Telocator Alphanumeric Protocol (Nurse Call) Interface Specifications.
• Ensure you have the URL of the load balancer for the on-premises gateway in order for Nurse Call systems to communicate with Spok Go.

Nurse Call Integration

See Integrating Nurse Call with Spok Go for instructions on configuring the Nurse Call integration.

Before You Begin

• Ensure you have the URL of the load balancer for the on-premises gateway in order for non-Spok systems that are sending pages to communicate with Spok Go.

Inbound Paging Integration

See Integrating Inbound Paging with Spok Go for instructions on configuring the Inbound Paging integration.

Before you Begin

Configuring Spok Exchange File Connector

See Configuring the Spok Exchange File Connector for instructions on configuring the Spok Exchange File Connector.