Woman coding MergeComm for inbound and outbound actions.

How Does MergeComm Work? Part 1

(Part 1 of 2)

MergeComm is our integration engine and innovative SQL-based Intelligent Series (IS) platform application that streamlines inbound and outbound communications, ensuring the correct resources are being notified in a secure, HIPAA-compliant environment. 

MergeComm is scalable and works seamlessly with our suite of call center applications, as well as with the product offerings of other vendors. It adds automated dispatching scenarios to our Intelligent Series (IS) platform and these dispatch scenarios can run automatically based on inbound triggers such as an e-mail message, a miSecureMessages (MSM) message, a Short Message Service (SMS) message, or a Telocator Alphanumeric Protocol (TAP) message. Jobs can be scheduled to run on a recurring basis or can be initiated by an operator in a call center, a web user running a web script, and a third-party application interacting with the available Application Program Interfaces (APIs).

Inbound Triggers 

Customers can configure inbound triggers for use with MergeComm.

Schedule – MergeComm Scenarios can be scheduled to run automatically by adding a scheduled task to the IS System Schedule. 

miSecureMessages (MSM) – miSecureMessages is our secure messaging and paging application. MSM users can send secure messages to IS to be processed.

POP3 E-mail – POP3 involves settings that specify the mail server to poll and the e-mail address to monitor for retrieval of e-mail messages. 

SMTP E-mail – IS has a built-in SMTP server with which the SMTP client applications communicate, enabling the SMTP clients to send e-mail messages directly to IS.

SMS Modem – SMS Modem enables receiving inbound SMS text messages from users.

SMS Aggregator – SMS aggregator services integrate bulk messaging services with IS for sending and receiving SMS text messages using a secure internet connection.

EMR (HL7) – MergeComm allows inbound HL7 messages to be received from a hospital electronic medical record (EMR) system to be filtered and mapped to trigger a MergeComm scenario.

Phone – Our Genesis soft switch enables users to place a phone call to a number that is directed into IS to initiate a MergeComm scenario.

TAP – Telocator Alphanumeric Protocol (TAP) can be used to accept a message from a direct connect device.

Rauland-Borg – Devices that use Rauland-Borg Responder IV protocol can send the extension, room, bed, call type, and message into fields that can be accessed from a MergeComm script.

WCTP – Wireless Communications Transfer Protocol (WCTP) can be used to accept a message from a wireless device. IS uses the device’s phone number to match the message to a trigger.

Web Service (SOAP and REST) – Web Service provides an API to enable external applications to initiate a MergeComm scenario. 

Outbound Interfaces

MergeComm outbound dispatching utilizes the IS directory and associated contact methods, and also interfaces with external Web services and EMR systems using the HL7 communication protocol. MergeComm can initiate outbound actions for use with:

  • Phone calls using our soft switching platform.
  • SMTP e-mail messages.
  • TAP paging messages.
  • SNPP paging messages.
  • WCTP paging messages.
  • Fax messages via the CopiaFacts or RightFax application.
  • SMS text messaging modems.
  • SMS aggregator services.
  • miSecureMessages secure mobile text messaging application.
  • Text messages to Vocera users via the Vocera VMI and VMP interfaces.
  • External Web services to facilitate communications with third-party systems.
  • Outbound EMR Integration (Outbound HL7). Can send HL7-based messages for tasks such as updating a patient’s medical record and managing appointment schedules.
  • Group Dispatching

(Read Part 2 of 2)