Client portal
Portal access, support intake, archive requests, and customer workflow views.
System status
Current operating posture for Med Pulse services.
Use this page for a customer-facing snapshot of service availability, maintenance communication, and incident escalation paths. Active customer-specific issues should still be submitted through support so they can be triaged and tracked.
All monitored services operational
Open Support Ticket
No broad customer-impacting incident is currently posted. Customer-specific issues should be submitted as support tickets.
Service indicators
Status categories for customer-facing operations.
Support ticket intake
Online ticket submission, priority capture, service-area routing, and confirmation handling.
Notification workflows
Status notification services around customer communication events and exception handling.
Archive retrieval
Search, request, and evidence-package workflows for retained operational records.
API and webhooks
Customer integration context for notifications, evidence, archive requests, and audit events.
Monitoring services
Infrastructure monitoring, DNS propagation checks, application response, and availability signals.
Incident levels
- Operational: no known broad customer impact.
- Degraded: a service is available but experiencing elevated errors or latency.
- Partial outage: one service area or region is materially affected.
- Major outage: broad production impact across multiple customer workflows.
Communication process
When an incident is identified, Med Pulse prioritizes internal triage, customer-impact assessment, mitigation, and customer communication. Ticketed requests remain the system of record for organization-specific issues.
- Impact review and assignment
- Customer support updates through the ticket path
- Closeout notes after resolution
