Technical FAQ
Technical guidance for routing, integrations, and delivery support.
This page gives technical and operations contacts a clearer view of common implementation topics, support intake expectations, and service review paths.
Integrations
Can Med Pulse support API workflows?
Yes. Sales and service planning can cover API access, permissions, endpoint context, webhooks, and operational ownership.
What technical context should be included in a ticket?
Include affected service, endpoint or location, impact, timing, error details, recent changes, and whether the issue is production-impacting.
Delivery support
How are routing issues triaged?
Support reviews the service area, priority, organization context, and technical description, then routes the issue to the right operational path.
What events should be treated as urgent?
Issues that block production document delivery, affect multiple locations, or create patient-care administrative risk should be submitted as urgent or critical.
Archive and review
Can customers request archived records?
Yes. Authorized contacts can submit archive retrieval requests with the date range, facility, record context, and review objective.
Can Med Pulse help with recurring reviews?
Higher-touch service tiers can include root cause review, endpoint audit context, archive operations, and support planning.
Next step
Need technical support?
Submit an online ticket and include the details our team needs to triage the request quickly.
