FAQs
Answers for healthcare teams evaluating Med Pulse.
Use these answers to understand setup, notification workflows, user access, delivery evidence, archive support, and compliance-related operations.
Platform and setup
Who is Med Pulse designed for?
Med Pulse supports clinics, specialty practices, administrative teams, and regional healthcare organizations that need stronger service visibility, notification workflows, archive retrieval, and support around fax-dependent operations.
Does Med Pulse replace the underlying fax system?
Med Pulse is positioned as an ancillary service layer. It supports the operational work around fax-dependent communications, including notifications, delivery evidence, routing support, archive requests, and compliance documentation.
Can a practice use multiple numbers or users?
Yes. Service planning can include multiple users, departments, locations, and numbers based on the organization’s workflow and tier.
Security and compliance
How does Med Pulse support healthcare workflows?
The service is structured around delivery evidence, documented support requests, archive retrieval, and operational records that help teams prepare for internal reviews.
Is a Business Associate Agreement available?
BAA requests can be routed through the sales or support process so the appropriate account contact can review requirements and next steps.
Can access be restricted?
Access planning may include user controls, account scoping, endpoint context, and operational procedures appropriate to the customer’s deployment.
Delivery and operations
How are service issues handled?
Customers submit online tickets with service area, priority, organization details, and technical context. Requests are triaged by support teams in California, Texas, and New York.
What happens during urgent events?
Production-impacting issues can be routed through the 24/7/365 on-call escalation path, with ticket context used to help the technical team understand impact quickly.
Can Med Pulse support integrations?
Yes. Service discussions can include API access, workflow integration, delivery status, and archive-related requirements.
Next step
Still have questions?
Open a support ticket or contact sales and the right team will route your request online.
