Secure Messaging

Principal workflows

• 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.
• 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.
• 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.
• Run: Moraph operates the service: managing users and roles, monitoring interfaces and adoption, handling changes and keeping the configuration documented.

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

Reporting

• Role coverage and schedule gaps by unit
• Pager retirement progress
• Interface health for lab and alert messages
• Directory and schedule import errors
• Changes, retention settings and message retrievals
• Incidents and requests by type and age

Features

• 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

• Directory: Accounts, departments and titles synchronized from your directory, such as Active Directory or Microsoft Entra ID.
• Single sign-on: Clinicians sign in to the app through your identity provider where TigerConnect and your provider support it.
• On-call scheduling: Schedules from your scheduling system feed role routing, through the integration methods TigerConnect supports.
• Laboratory and EHR results: Critical and other agreed results sent to the responsible clinician, where your lab or EHR can produce them as HL7 or other supported messages.
• Nurse call and clinical alerts: Alerts from nurse call and other alerting systems routed to phones, where the source system and TigerConnect support it.
• Mobile device management: App deployment and device policy for organization-owned phones through your mobile device management tool.
• Your service desk: Requests and incidents raised by your staff routed to Moraph's service desk, or linked to your own tool.

Deployment

• 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 and privacy

• 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.

Limitations

• 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.

Next steps

Book a demonstration or a technical briefing at www.moraph.com/solutions/secure-messaging. Purchasing routes and company information: www.moraph.com/how-to-buy.