Two vendors are involved in this program — one being onboarded (active contract, ongoing SLA management) and one being offboarded (the platform this program replaces). Both need different artifacts, which is why they're handled as separate documents rather than one generic vendor page.
Vendors on This Program
PulseConnect
HIPAA-compliant video visit SDK, licensed for the life of MedConnect Mobile and beyond.
- Contract type: Annual SaaS license + support SLA
- BAA executed during vendor selection (pre-program)
- Managed via: SOW Summary & Performance Scorecard
Vantix Health Systems
Vendor of CareLink Classic, the legacy telehealth platform this program replaces.
- Contract type: Legacy per-seat license, expiring on the announced end-of-life timeline
- Managed via: Legacy Vendor Offboarding Plan
Vendor Governance Roles
| Role | Responsibility |
|---|---|
| C. Tyrrell (PO & Delivery Lead) | Owns the vendor relationship at the program level — escalation point, SLA review cadence, contract renewal decisions |
| A. Singh (Engineering Lead, Anchor) | Technical point of contact for PulseConnect's SDK integration and support tickets |
| T. Brannigan (Compliance) | Owns BAA compliance for PulseConnect and data-handling/deletion certification for Vantix offboarding |
| M. Delacroix (Sponsor) | Approves any vendor contract changes with budget impact (see Change Control Log, CR-01) |
Why Two Different Vendor Artifacts
An incoming vendor needs ongoing performance management — SLA tracking, support responsiveness, renewal planning. An outgoing vendor needs a one-time, checklist-driven offboarding — data export, license termination, deletion certification. Treating both the same way would either under-manage the active relationship or over-engineer a one-time wind-down. Keeping them as separate documents matches how they're actually managed.