System status

MediCare HIS · operational health

Real-time component health, 90-day uptime, active incidents, and planned maintenance. Bookmark this page. When something feels off, this is where to check first.

All systems operational

Last updated just now

Components

We monitor each component on its own. A degraded sub-system won't always affect every customer, so check the incident notes to see who's touched.

Tenant portals
Hospital clinical app — <slug>.medicarehis.com
Operational
API
Tenant + admin API endpoints
Operational
Database
Postgres primary + automated hourly snapshots
Operational
Marketing website
medicarehis.com — apex marketing pages
Operational
Email delivery
Transactional email (alerts, reports, password reset)
Operational
Outbound webhooks
Partner integrations + analyser-result push
Operational

Active incidents

No incidents reported.

Hitting a problem that isn't listed here? Email [email protected] with your hospital name and what you're seeing.

Planned maintenance

No maintenance windows scheduled in the next 14 days.

We announce maintenance at least 7 days ahead on this page and by email to your hospital's nominated technical contact.

Incident history

The last 90 days. Customers can ask us for the full history, with root-cause writeups.

No incidents in the last 90 days.

What we monitor + how

External synthetic monitoring (UptimeRobot) checks the public marketing site and one tenant portal every 60 seconds from three regions. Internal alerting (Prometheus + Sentry) watches error rates, p95 latency, queue depth, and database health. A P1 alert wakes the on-call engineer within 5 minutes.

Want the full operational model? The SLA covers tiers, RPO / RTO commitments, the response-time matrix by severity, and service-credit remedies. For support channels and escalation paths, see how support works.