Skip to content

Moraph for clients

Sign in

Getting started

Getting started with Secure Messaging

What Secure Messaging is for, who uses it, what you need before you start, and your first steps.

Applies to Secure Messaging as it works today. Moraph updates the platform continuously, and this page is reviewed when it changes.

Last reviewed 2 min readReport a problem
On this page
  1. What it is for
  2. Who uses it
  3. Before you start
  4. Steps to get started
  5. Where to go next

Moraph resells, implements and runs TigerConnect so clinicians can send and receive urgent messages, alerts and lab results on encrypted smartphone apps instead of pagers and personal texting. We configure roles, on-call routing, message retention and integrations with your directory, scheduling, lab and alerting systems, and then operate the service and its interfaces day to day. Your organization decides who should be reached for what, and keeps every clinical and privacy decision.

What it is for

Many hospitals still rely on pagers for urgent communication, with call-back numbers that leave the sender waiting and no record of whether a message was read. Clinicians fill the gaps with personal text messaging, which puts PHI on unmanaged apps. Where secure messaging has been bought, it often sits half-configured: roles do not match the on-call schedule, lab and alarm interfaces were never finished, and nobody owns the directory, so messages go to the wrong person or to someone who left months ago.

  • Pages give no confirmation that the message was received or read
  • Personal text messaging puts PHI on apps your organization does not control
  • Messages go to a named person rather than whoever holds the role or is on call
  • Interfaces to lab, scheduling and alerting systems are unfinished or unmonitored

Who uses it

  • Hospitals and health systems moving from pagers to smartphone messaging
  • Nursing, hospitalist and physician leaders who depend on reaching the on-call clinician
  • Clinical informatics and IT teams responsible for clinical communication systems
  • Privacy and security officers concerned about PHI in personal text messages
  • Organizations that already license TigerConnect and want it configured and run properly

Before you start

  • Your organization uses Secure Messaging as a managed platform from Moraph, under an agreement that covers it.
  • Licences for TigerConnect, bought through Moraph or under your own agreement with the vendor.
  • A Moraph account in your organization for each person who works with Moraph on the service.
  • Named technical and security contacts, recorded in the Moraph Portal.

Steps to get started

  1. Agree the scope of the managed service for Secure Messaging with Moraph, including which environments and teams it covers.

  2. Name your administrators, technical contact and security contact in the Moraph Portal under People and access.

  3. Review the configuration baseline Moraph proposes for your regulations, and record any changes you need.

  4. Confirm how users will sign in, through your identity provider where the platform supports it.

  5. Agree the pilot group and the cut-over plan with your Moraph delivery lead.

Where to go next

Was this page helpful?

Report a problem with this page
What’s the problem?
Quote the step or heading if you can. Don’t include passwords or personal records.
Only if you’d like a reply. We use it for this report and nothing else.

Need help with your own setup rather than this page? Raise a support ticket.