Healthcare · Managed platform (TigerConnect)

Secure Messaging

TigerConnect set up and run so urgent clinical messages reach the right person

Book a demonstrationRequest a technical briefingFactsheet

Overview

What you are buying

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.

The problem it solves

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

Requirements it supports

HIPAA Privacy Rule (45 CFR Part 160 and Part 164, Subpart E)HIPAA Security Rule (45 CFR Part 164, Subpart C)HIPAA Breach Notification Rule (45 CFR 164.400-414)Medicare Conditions of Participation: medical record services (42 CFR 482.24)CMS memorandum on texting of patient information among healthcare providers (S&C 18-10-ALL, as revised)

The product supports these requirements; meeting them remains your organization’s responsibility.

Responsibilities

Who is responsible for what

TigerConnect provides and operates the messaging platform, Moraph configures and runs your use of it, and your organization makes the clinical and privacy decisions.

AreaMoraphTigerConnectYour organization
LicensingResells TigerConnect licenses and keeps counts aligned with your usersSets license terms and product availabilityAgrees the users and modules to license and pays under the order
Business associate termsSigns a business associate agreement with you for Moraph's servicesProvides its own BAA under its termsDecides what information may be sent through the service
Platform availabilityMonitors service health, raises incidents with TigerConnect and keeps you informedOperates the platform under its own service commitmentsKeeps a downtime fallback, such as overhead paging or phone, and uses it when needed
ConfigurationDesigns, applies and documents roles, routing, escalation and retentionProvides the platform's configuration optionsApproves the design and every change
Identity and accessConfigures directory sync and single sign-on and manages accountsProvides account and access controls in the platformOwns the directory, joiner and leaver processes
InterfacesBuilds, tests and monitors interfaces to your source systemsProvides supported integration methodsProvides access to source systems and their owners
MonitoringWatches interface errors, directory sync and role coverageMonitors its platform and publishes service statusReports problems through the agreed route
Incident responseLeads incident handling for the service and reports cause and fixResolves platform incidentsDecides on breach assessment and any notification
Platform updatesReviews TigerConnect release notes for effects on your configuration and tells you of changesReleases platform and app updatesCommunicates app changes to clinicians and updates managed devices
DevicesAdvises on device readiness and app configurationProvides the apps for supported devicesSupplies devices or sets policy for personal devices

See how it works

A short walkthrough

Illustrative screens of how Moraph runs the service, with fictional sample data. They are not screens of TigerConnect itself, which belongs to its vendor.

  1. Step 1

    Onboarding tracker

    Each unit moves from assessment to live messaging, and pagers are retired only when coverage and fallback are confirmed.

    UnitRoles configuredSchedule importDevices readyFallback agreedStatus
    4 East MedicalYesConfirmedYesYesLive, pagers retired
    Emergency DepartmentYesConfirmedYesYesLive, pagers in parallel
    Hospitalist serviceYesErrorsYesYesWaiting on scheduler
    Cardiology consultsYesConfirmedPartialYesWaiting on client IT
    Surgical ICUIn designNot startedNoNoDesign review
    Each unit moves from assessment to live messaging, and pagers are retired only when coverage and fallback are confirmed.

  2. Step 2

    Configuration baseline review

    Live configuration is compared with the approved design, and every difference is corrected or explained.

    Configuration baseline · Example Medical Center (fictional)

    Roles in design
    142
    Roles configured
    142
    Escalation rules
    38
    Retention groups
    4
    Differences
    2

    Differences

    • Lifespan for pharmacy group differs from approved setting
    • One escalation rule added without a change record, under review
    Live configuration is compared with the approved design, and every difference is corrected or explained.

  3. Step 3

    Alert triage

    Interface errors and coverage gaps are triaged by Moraph's service desk and worked to an owner.

    AlertSourceDescriptionSeverityOwnerStatus
    AL-3307Lab interfaceNo result messages received in the last hourHighMoraph integration engineerInvestigating with lab IT
    AL-3305Role coverageNight rapid response role has no holderHighUnit schedulerCalled, resolved
    AL-3299Directory sync12 accounts failed: missing departmentMediumClient ITFix requested
    AL-3291Schedule importHospitalist schedule rows rejectedMediumDepartment schedulerCorrecting
    Interface errors and coverage gaps are triaged by Moraph's service desk and worked to an owner.

  4. Step 4

    Working an interface incident

    An interface failure is worked to cause and fix, and clinical owners are told what to do in the meantime.

    Incident INC-4410 · Lab result notifications stopped

    1. No result messages detected by interface monitorMoraph service desk
    2. Clinical communication owner told; units reminded to check results in the EHRMoraph service desk
    3. Cause traced to certificate change on the lab interface serverClient IT with Moraph
    4. Certificate updated and test results confirmed on phonesClient IT
    5. Queued notifications reviewed for deliveryMoraph integration engineer
    6. Incident report reviewed and closedClinical communication owner
    An interface failure is worked to cause and fix, and clinical owners are told what to do in the meantime.

  5. Step 5

    A change request

    Routing and escalation changes are applied only after the clinical owner approves them.

    Change CHG-2208 · Escalate unacknowledged stroke alerts

    Requested by
    Neurology service lead
    Current setting
    No escalation
    Requested setting
    Escalate to backup neurologist if not acknowledged
    Applies to
    Stroke alert role
    Status
    Approved, scheduled

    Approvals

    • Clinical communication owner: approved
    • Client IT: approved
    • Moraph change review: tested in pilot group
    Routing and escalation changes are applied only after the clinical owner approves them.

  6. Step 6

    Monthly service review

    Each service review brings coverage, interfaces, changes, incidents and pager retirement together for clinical and IT leads.

    Service review · Example Medical Center (fictional)

    Units live
    9 of 14
    Pagers retired
    6 units
    Coverage gaps found
    5, all resolved
    Interface incidents
    1, closed
    Changes applied
    8

    Decisions needed

    • Approve rollout order for remaining surgical units
    • Agree fallback for areas with weak wireless coverage
    • Confirm retention for pharmacy conversations
    Each service review brings coverage, interfaces, changes, incidents and pager retirement together for clinical and IT leads.

Workflows

The principal workflows

  1. Set up

    Moraph configures TigerConnect around how your organization communicates: who is reachable, by name and by role, and what happens when they do not respond.

    • Communication patterns reviewed with nursing, physician and unit leaders
    • Directory connected so users join and leave with your HR and identity records
    • Roles defined for on-call, charge nurse, rapid response and other positions
    • Escalation and message priority rules agreed and configured
    • Retention and message lifespan set to your policy

  2. Route

    Messages and alerts are routed to whoever holds a role at that moment, using on-call schedules and shift assignments, so senders do not need to know who is on call.

    • On-call schedules imported from your scheduling system
    • Clinicians opt into roles at the start of a shift where your process allows
    • Sender messages the role; TigerConnect delivers to the current holder
    • Unanswered priority messages escalate as configured
    • Schedule and role gaps flagged to the unit or department owner

  3. Integrate

    Moraph builds and runs the interfaces that send lab results, nurse call and other system alerts to clinicians' phones, within what TigerConnect and your source systems support.

    • Alert sources and message types agreed with clinical owners
    • Interfaces built through TigerConnect's supported integration methods
    • Each alert type tested end to end with the source system team
    • Interface volumes and errors monitored
    • Failures raised as incidents and worked to resolution

  4. Run

    Moraph operates the service: managing users and roles, monitoring interfaces and adoption, handling changes and keeping the configuration documented.

    • Joiners, movers and leavers kept in step with your directory
    • Interface and delivery issues triaged by Moraph's service desk
    • Change requests assessed, approved by you and applied
    • Role coverage and pager retirement tracked with clinical leaders
    • Service review held with IT, nursing, medical staff and privacy

Roles and permissions

Who does what in the product

Each role below is a starting point. During implementation we set them up to match your teams, and every action anyone takes is recorded in the audit trail.

Clinical communication owner

CNO or CMO delegate, director of nursing informatics, clinical communications manager

Owns how clinical messages flow: which roles exist, how routing and escalation work, and when pagers are retired.

Sees

  • Role, routing and escalation configuration
  • Role coverage and schedule gaps by unit
  • Adoption and pager retirement progress
  • Interface health for clinical alerts

Does

  • Approves roles, routing rules and escalation paths
  • Approves alert types sent to phones from lab and other systems
  • Decides the pager retirement plan for each unit
  • Brings clinician feedback to service reviews
  • Requests changes through the service

Cannot

  • Change retention or message lifespan without the privacy officer
  • Grant administrative access to TigerConnect
Approvals
Approves roles, routing, escalation and alert types; retention settings also need the privacy officer.
Notified about
Role coverage gaps, interface incidents that affect clinical alerts, changes waiting for approval, and service review reports.

Privacy officer

Privacy officer, HIPAA privacy officer, chief compliance officer

Decides how long messages are kept, who can see them and what may be sent, and approves settings that affect PHI.

Sees

  • Retention, lifespan and recall settings
  • Change requests that affect PHI handling
  • Records of message retrievals made for investigations or legal requests

Does

  • Approves retention and lifespan settings
  • Approves policies on attachments, images and forwarding
  • Requests message retrieval for investigations through the service
  • Reviews privacy-relevant incidents

Cannot

  • Change routing or roles
  • Read messages without a logged request under your process
Approvals
Approves retention, lifespan, attachment and export settings and any message retrieval request.
Notified about
Changes waiting for approval, privacy-relevant incidents, and completed retrieval requests.

Client IT administrator

Clinical systems manager, identity administrator, mobile device manager

Owns the directory, devices, network and source systems that TigerConnect depends on.

Sees

  • Directory synchronization status and errors
  • Interface configuration and health
  • Moraph's administrative access and its activity
  • Change and incident records

Does

  • Maintains directory attributes used for accounts and roles
  • Provides access to source systems for interfaces
  • Approves technical changes and schedules them
  • Manages devices and app deployment where you use mobile device management
  • Works incidents with Moraph where your systems are involved

Cannot

  • Approve clinical routing or retention changes on behalf of clinical or privacy owners
  • Remove records of Moraph's administrative actions
Approvals
Approves technical changes, interfaces and Moraph's administrative access.
Notified about
Directory sync errors, interface incidents, scheduled changes and access reviews for Moraph's roles.

Unit or department scheduler

Unit secretary, department scheduler, medical staff office coordinator

Keeps the schedules and role assignments that routing depends on accurate.

Sees

  • On-call schedules and role assignments for their unit or department
  • Coverage gaps flagged for their area

Does

  • Maintains schedules in your scheduling system
  • Corrects role assignments when coverage changes
  • Resolves coverage gaps flagged by the service

Cannot

  • Create new roles or change routing rules
  • See other departments' schedules unless granted
Approvals
Changes to routing or roles go to the clinical communication owner.
Notified about
Coverage gaps for their area and schedule import errors.

Clinician

Physicians, nurses, advanced practice providers, pharmacists, respiratory therapists

Uses the app to reach colleagues and to receive urgent messages and alerts.

Sees

  • Messages and conversations they are part of
  • The directory and roles they are allowed to message
  • Alerts routed to them or their role

Does

  • Sends and replies to messages and group conversations
  • Takes and hands off roles at shift change where configured
  • Acknowledges priority messages and alerts
  • Reports problems through your service desk

Cannot

  • Change retention, routing or escalation
  • Keep access after leaving the organization
Approvals
None.
Notified about
Messages and alerts routed to them or their role, as configured.

Moraph service team

Moraph service engineer, integration engineer, Moraph service desk

Configures, monitors and maintains TigerConnect and its interfaces to your approved design.

Sees

  • TigerConnect administrative configuration
  • Interface volumes, errors and logs
  • Directory sync status
  • Change, access and incident records

Does

  • Applies approved roles, routing, escalation and retention settings
  • Builds, tests and monitors interfaces
  • Handles user, role and access requests
  • Leads incident handling and escalates to TigerConnect
  • Prepares service reviews and maintains documentation

Cannot

  • Read message content as part of routine operations
  • Apply changes without the approvals your process requires
  • Decide clinical routing or retention policy
Approvals
Every change Moraph applies is approved by your named owners; emergency changes are reviewed with you afterwards.
Notified about
Interface errors, directory sync failures, new requests and approvals, and TigerConnect notices that affect your configuration.

Auditor (read-only)

Internal auditor, compliance reviewer

Reviews evidence that the service is configured and run as approved.

Sees

  • Configuration documentation and its history
  • Change, access review and incident records
  • Service review reports

Does

  • Reads and exports evidence within the scope granted
  • Leaves review notes where enabled

Cannot

  • Change, approve or delete anything
  • Read message content
Approvals
Their access is approved by the privacy officer or IT administrator, with a scope and an end date.
Notified about
Nothing by default.

Permissions at a glance

ActionComms ownerPrivacyClient ITSchedulerClinicianMoraph teamAuditor
Define roles and routingApprovesView onlyView onlyNo accessNo accessFullView only
Change escalation rulesApprovesNo accessView onlyNo accessNo accessFullView only
Set retention and message lifespanView onlyApprovesView onlyNo accessNo accessFullView only
Approve alert types sent to phonesApprovesView onlyApprovesNo accessNo accessFullView only
Maintain on-call schedulesView onlyNo accessNo accessOwn work onlyNo accessView onlyNo access
Send and receive messagesFullFullFullFullFullNo accessNo access
Build and change interfacesApprovesNo accessApprovesNo accessNo accessFullView only
Retrieve messages for an investigationNo accessApprovesNo accessNo accessNo accessFullNo access
Manage users and accountsNo accessNo accessApprovesNo accessNo accessFullView only
View change and incident recordsView onlyView onlyView onlyNo accessNo accessFullView only
Manage Moraph's administrative accessNo accessView onlyFullNo accessNo accessNo accessView only
  • Full
  • Own work only
  • Approves
  • View only
  • No access

How access is controlled

  • Roles here describe who decides what in the service. Inside TigerConnect, clinicians hold ordinary user accounts and Moraph's engineers hold only the administrative rights your IT team grants.
  • Clinical routing is a clinical decision. Moraph configures roles, routing and escalation, but your clinical communication owner approves them.
  • Message content is retrieved only on a request approved by your privacy officer, and each retrieval is recorded with who asked, who approved and who carried it out.
  • Moraph's administrative access is reviewed with your IT administrator, used only for approved, time-bound work, and recorded.

Features

What it does

Role-based messaging

TigerConnect delivers messages to whoever holds a role, such as the on-call cardiologist or the 4 East charge nurse, configured by Moraph to match your units and services.

On-call schedule routing

On-call schedules from your scheduling system are used to route messages, so the sender reaches the clinician covering at that time.

Priority and escalation

Urgent messages are marked and escalate as configured if they are not acknowledged, following rules your clinical leaders approve.

Delivery and read status

Senders see when a message has been delivered and read, rather than waiting on a call-back.

Message lifespan and retention

Message lifespan, recall and retention set in TigerConnect to your policy, with the settings documented and approved by privacy.

Directory-driven accounts

Users are created, changed and removed from your directory, so people who leave lose access and new staff appear in the directory.

Lab and result notifications

Where your lab or EHR can send them, critical and other agreed results are delivered to the responsible clinician's phone through a monitored interface.

Alert and nurse call interfaces

Alerts from nurse call and other clinical systems routed to phones, where TigerConnect and the source system support it, configured with each system's owner.

Pager retirement planning

A unit-by-unit plan for moving from pagers to the app, with role coverage, device readiness and fallback agreed before pagers are withdrawn.

Device and app readiness

Guidance and configuration for organization-owned and personal devices, working with your mobile device management where you use it.

Interface monitoring

Volumes and errors on each interface are watched by Moraph's service desk, and failures are raised as incidents.

Service reviews

Regular reviews of adoption, role coverage, interface health, changes, incidents and open risks with your clinical and IT leads.

Integrations

How it connects to your systems

Connects toHowWhat flows
DirectoryAccounts, departments and titles synchronized from your directory, such as Active Directory or Microsoft Entra ID.In: users, departments, titles and status.
Single sign-onClinicians sign in to the app through your identity provider where TigerConnect and your provider support it.In: user identity and authentication.
On-call schedulingSchedules from your scheduling system feed role routing, through the integration methods TigerConnect supports.In: on-call schedules and role assignments.
Laboratory and EHR resultsCritical and other agreed results sent to the responsible clinician, where your lab or EHR can produce them as HL7 or other supported messages.In: result notifications for the agreed result types.
Nurse call and clinical alertsAlerts from nurse call and other alerting systems routed to phones, where the source system and TigerConnect support it.In: alert events with location and priority.
Mobile device managementApp deployment and device policy for organization-owned phones through your mobile device management tool.Within your MDM: app configuration and device policy.
Your service deskRequests and incidents raised by your staff routed to Moraph's service desk, or linked to your own tool.In and out: tickets, status and resolution notes.

Each integration is confirmed in discovery and specified in the design. See how an engagement progresses.

Security and privacy

How your data is protected

Encrypted messaging

TigerConnect encrypts messages in transit and at rest on its platform and in the app, and Moraph configures lifespan and recall to your policy.

Single sign-on

Clinicians sign in through your identity provider where supported, and Moraph's staff sign in to Moraph systems with multi-factor authentication.

Role-based access

Clinicians see their own conversations, and Moraph's service team works on configuration and interfaces rather than message content.

Controlled privileged access

Moraph's administrative rights are granted by your IT team, used only for approved work, and keys and credentials cannot be used without explicit, time-bound authorization.

Independent audits

Moraph's operations are audited under SOC 2 Type II and ISO/IEC 27001, and Moraph signs a business associate agreement with you. TigerConnect's own assurance reports are available from TigerConnect under its terms.

Data residency

Messages are held where TigerConnect hosts your organization's service, and Moraph's service records are held in the United States, United Kingdom or Australia region you choose.

Company-wide controls, independent audits (SOC 2 Type II and ISO/IEC 27001) and data residency are described in our Trust Center, where you can request the evidence pack.

Reporting

What you can report on

11 standard reports, grouped by who uses them. Each shows who it is for, how it can be broken down, how it is delivered and what it is used for. The data behind them is also available to your own reporting tools.

Adoption and coverage

Role coverage

For clinical communication owner, unit leaders

Roles with and without a current holder, by unit and time of day, and gaps found against the on-call schedule.

Break down by
Unit, Role, Shift, Gap type
Delivered as
Live view; scheduled email
Used for
Making sure every role that receives urgent messages is covered.

Pager retirement progress

For clinical communication owner, nursing and medical leadership

Each unit's progress through readiness steps, pagers still in use, and decisions outstanding.

Break down by
Unit, Readiness step, Pagers remaining
Delivered as
Service review pack; PDF
Used for
Planning and evidencing the move away from pagers.

Active users

For clinical informatics, client IT

Users signed in over the period by department and role, drawn from TigerConnect's reporting.

Break down by
Department, Role, Period
Delivered as
Service review pack; CSV export
Used for
Seeing where adoption is low and training is needed.

Interfaces

Interface health

For client IT, clinical communication owner

Message volumes, errors and outages on each interface over the period, with the incidents raised.

Break down by
Interface, Error type, Period
Delivered as
Live view; service review pack
Used for
Confirming lab and alert messages are reaching clinicians.

Directory sync results

For client IT

Accounts created, changed and disabled by each sync, and records that failed with the reason.

Break down by
Sync run, Result, Department
Delivered as
Live view; CSV export
Used for
Keeping the directory accurate so messages reach the right people.

Schedule import results

For schedulers, client IT

Schedule imports, records rejected and roles left without a holder after import.

Break down by
Department, Import run, Error type
Delivered as
Live view; scheduled email
Used for
Fixing schedule errors before they leave a role uncovered.

Governance

Change log

For client IT, privacy officer, auditors

Every change applied, with its request, approvers, date and outcome.

Break down by
Change type, Approver, Period
Delivered as
Live view; CSV and PDF export
Used for
Evidencing that changes followed the approval route.

Retention and lifespan settings

For privacy officer, auditors

Current retention, lifespan and recall settings by user group, with the approval behind each.

Break down by
User group, Setting, Approver
Delivered as
Live view; PDF export
Used for
Showing that message handling matches privacy policy.

Message retrieval log

For privacy officer, auditors

Each request to retrieve message content, who requested and approved it, and when it was fulfilled.

Break down by
Requester, Reason, Date
Delivered as
Live view; PDF export
Used for
Accounting for every access to message content.

Service

Incidents and requests

For client IT, service review attendees

Incidents and requests by type, age and status, with cause and resolution for incidents.

Break down by
Type, Severity, Age, Status
Delivered as
Live view; service review pack
Used for
Seeing what went wrong and what is waiting.

Service review summary

For iT, nursing, medical staff and privacy leadership

A summary of adoption, coverage, interfaces, changes, incidents and open risks for the period.

Break down by
Period, Area
Delivered as
PDF; scheduled email
Used for
Giving leadership one view of how clinical messaging is running.

Exports, access and evidence

  • Service reports come from Moraph's change, access, incident and interface monitoring records, and can be exported to CSV and PDF.
  • Adoption and use figures come from TigerConnect's own reporting, so they reflect what TigerConnect records and keeps.
  • Reports contain configuration, activity and interface data, not message content.
  • Reports respect each viewer's role: schedulers see their own areas, and auditors see evidence reports within their scope.
  • Service review packs are kept with the service records so earlier periods can be revisited.

Deployment

Where and how it runs

TigerConnect cloud, managed by Moraph

TigerConnect hosts the service; Moraph configures and operates it for you under a managed service agreement.

Moraph-managed with your existing licenses

If you already license TigerConnect, Moraph can take over configuration, interfaces and operations, subject to TigerConnect's terms.

Alongside other Moraph services

Run with Moraph's Clinical Collaboration, Enterprise Mobility or Physician On-Call Scheduling so communication, devices and schedules are managed together.

Security controls, independent audits and data residency are set out in our Trust Center. Engagement models and what drives a quotation are on Working with Moraph.

Implementation

What a rollout involves

The general phases are on Working with Moraph. For this product, they involve the following.

Communication assessment

We map how messages and pages flow today, unit by unit, with nursing, physician and IT leads. We need time with unit leaders and a list of paging groups and alert sources.

Design

Roles, routing, escalation, retention and alert types are designed with your clinical communication owner and approved, with privacy approving retention and PHI settings.

Directory and schedules

Directory sync and on-call schedule imports are configured and checked so accounts and roles are accurate before anyone relies on them.

Interfaces

Lab, nurse call and other alert interfaces are built and tested end to end with each source system team, one alert type at a time.

Pilot and rollout

A pilot unit goes live first, then units follow in an order you choose. Pagers are retired only when a unit's coverage and fallback are confirmed.

Handover to run

Service desk routes, approvers, review cycles and reporting are agreed, and the service moves into managed operation.

Limitations

What it does not do

Worth knowing before you evaluate it.

  • Moraph is not TigerConnect. The platform belongs to TigerConnect, and TigerConnect's own service commitments, roadmap, maintenance and outages apply to it.
  • Licenses are subject to TigerConnect's terms, and features such as scheduling, alarm and nurse call integrations depend on the modules you license.
  • Messages reach clinicians only when their phones are on, connected and running the app. Your organization needs a downtime fallback, and pagers may still be needed in areas with poor coverage.
  • Routing is only as accurate as your schedules and directory. Errors in either can send messages to the wrong person, so ownership of both matters.
  • Interfaces depend on what your lab, EHR, nurse call and other systems can send. Some alerts may not be available to route.
  • Secure messaging does not replace your medical record. Orders and documentation follow your policies and belong in the EHR.
  • Moraph does not make clinical routing, escalation or retention decisions. Your organization approves them and remains responsible for HIPAA compliance.
  • Clinical alarm management decisions, including which alarms are sent to phones, remain with your clinical and biomedical engineering teams.

Evaluation checklist

What to test in a demonstration or pilot

Questions worth putting to us, and to any other vendor you are considering.

  1. Choose one unit and map who is paged for what today, then review the proposed roles and routing
  2. Check how on-call schedules will be imported and who will own their accuracy
  3. List the lab and alert sources you want on phones and confirm what each system can send
  4. Review the downtime fallback with nursing and medical leadership
  5. Walk through a message retrieval request and confirm who approves it
  6. Review a sample service review pack with your clinical communication owner

Questions

Frequently asked questions

Will this replace all our pagers?

It can replace many of them, unit by unit, but that is your decision. Pagers are retired only where role coverage, devices and a downtime fallback are in place, and some areas may keep them.

Can clinicians use their own phones?

Yes, if your policy allows it. TigerConnect provides apps for common smartphones, and Moraph helps you set device and app policy, including through your mobile device management tool where you use one.

Who signs the business associate agreement?

Moraph signs one with you for Moraph's services, and TigerConnect provides its own under its terms.

Does Moraph read our messages?

No, not as part of routine operations. Message content is retrieved only on a request your privacy officer approves, and each retrieval is recorded.

Can orders be sent by secure message?

That is a policy decision for your organization, guided by CMS and accreditation expectations. Moraph configures the service to your policy; documentation and order entry belong in your EHR.

How is it priced?

As a managed service, usually based on the number of users and the interfaces in scope, with licenses and onboarding quoted separately. See Working with Moraph for what drives a quotation.

Next steps

Evaluate Secure Messaging

Book a demonstration

See the product working with sample data, focused on your workflows.

Request a demonstration

Request a technical briefing

Architecture, integrations, security and hosting, with our engineers and your technical team.

Request a briefing

Factsheet

This page on two sides, to share with colleagues or add to your evaluation file.

Open the factsheet

Buying through a formal procurement? See How to buy for purchasing routes, accessibility conformance reports and company information. Documentation: Secure Messaging guides on docs.moraph.com (getting started and security guides are public; setup, administration and integration guides are for client accounts). Support: Secure Messaging support guide.

Related products