HTTPS/443 onlyBuild 2026.5.15.23Last updated May 2026No PHI by design

Network and System Requirements for Meridyon

This page gives hospital IT teams the domains, browser requirements, email delivery guidance, and support escalation paths needed to prepare for Meridyon scheduling workflows.

Allow List URIs

Critical

Meridyon will not function reliably without these.

*.meridyon.comHTTPS/443
schedule.meridyon.comHTTPS/443
staging.meridyon.comHTTPS/443
*.meridianadmit.comHTTPS/443

Important

The app can run without these, but monitoring, analytics, or email may degrade.

*.sentry.ioHTTPS/443
analytics.meridianadmit.comHTTPS/443
api.resend.comHTTPS/443

Meridyon is designed to sit behind CDN and reverse-proxy infrastructure. Do not pin access to a single static IP address unless Meridyon has provided a site-specific deployment note. Domain allowlisting is the supported default.

Supported Browsers

Windows

Chrome, Edge, Firefox

macOS

Chrome, Edge, Firefox, Safari

iOS/iPadOS

Safari, Chrome

Android

Chrome

Meridyon supports current stable browser versions and does not support Internet Explorer or legacy embedded webviews.

Email Allow List

Meridyon sends transactional scheduling mail from configured Meridyon sender addresses, typically [email protected]. Allow these domains for notifications, request replies, invitations, and password reset messages.

meridyon.comresend.com

Support

For production support, contact [email protected].

Include your organization, affected workflow, browser/device, approximate time, screenshots when safe, and whether the issue blocks patient-care scheduling operations.

Response Targets

Critical outage

Scheduling unavailable, login broadly broken, or production data at risk.

Acknowledge within 1 business hour.

High impact

A core scheduling workflow is degraded for one or more teams.

Acknowledge within 1 business day.

Standard

Configuration help, how-to questions, non-urgent workflow issues.

Acknowledge within 2 business days.

Security and Reliability

Role-based access controls for scheduler, provider, and admin workflows.
Audit logs for administrative and scheduling mutations.
Public health endpoint at /api/health.
Error telemetry through Sentry when configured.
Backup and restore runbooks documented for production operations.
Meridyon is staff-scheduling infrastructure and should not receive PHI.

View health endpoint

Go-Live Readiness

Production and testing health endpoints are monitored.
Release checklist covers migration validation, tests, build, health check, and smoke test.
Daily backups are verified and restore drills are documented.
Incident runbooks cover outage, deploy, migration, email, and rollback scenarios.