If you are going to askus anyway, we shouldanswer here first.

CCP (Care Control Pathway) is a digital healthcare infrastructure built specifically for insurance companies to govern cross-border and complex care — turning international healthcare from a transaction into a controlled, auditable process.

Insurers, TPAs, and corporate health plan administrators who fund cross-border or high-cost care and need real-time visibility, clinical governance, and cost control over that spend.

Traditional medical travel focuses on access — getting the patient to care. CCP focuses on control — governing treatment pathways, cost, and outcomes on a single platform with a full audit trail, rather than coordinating through emails and broker chains.

No. CCP sits alongside your existing systems as the governance layer for cross-border and complex care cases — it doesn't replace your core policy administration or claims systems.

CCP scales from a single pilot cohort (as small as 500 lives) to a full corporate book, using the same 6-factor clinical risk framework at every level.

No. CCP is designed to work alongside brokers, not around them. Brokers remain the client relationship owner; CCP gives their placements a governed international healthcare benefit they can offer with confidence.

Yes. CCP is white-label-ready and deployable under a broker's or insurer's own brand within 7 days.

Multinational and large corporate clients increasingly expect an international healthcare benefit as standard. CCP lets brokers offer a governed, audit-grade version of that benefit rather than losing accounts to a competitor who already has one.

Commercial structures are agreed case by case, depending on the placement and the scale of the book. Reach out to discuss a specific partnership or channel arrangement.

No. CCP governs what a TPA was never designed to govern — cross-border treatment pathways, clinical risk, and provider quality — while your TPA continues to manage core claims administration.

Yes. CCP is built to sit alongside existing TPA and claims workflows, feeding structured case and risk data back into your existing reporting rather than requiring a rip-and-replace.

CCP surfaces the clinical risk data — six quantified risk factors per case — at the point of decision. The insurer's or TPA's underwriting team retains full approval authority; CCP does not make clinical or commercial decisions on your behalf.

Most existing international healthcare programmes are transactional — they fund the care but don't govern it. CCP adds the missing governance layer on top of what you already offer: real-time case visibility, a 6-factor clinical risk score on every case, and audit-grade reporting — without disrupting your existing hospital network or benefit structure.

No. CCP can operate with your existing network and provider relationships, or with MediGence's own network of 500+ hospitals across 20+ countries — whichever your existing programme already uses.

The same 7-day timeline applies — configure, onboard, pilot, go live — regardless of whether you're launching a new programme or adding governance to an existing one.

You can launch a fully governed programme from zero in 7 days, under your own brand, using MediGence's existing network of 500+ hospitals across 20+ countries — no need to build a provider network yourself.

Yes. We recommend a 90-day pilot on a single corridor and cohort (for example, 500 lives), with an audit-grade outcome pack delivered on day 91 and a scale term sheet ready if the numbers hold.

MVT, our operational medical value travel service, lets you refer your first cases immediately — no platform build, no contract lock-in — proving the model before you decide whether to invest in owning the CCP infrastructure.

7 days: Day 1-2 Configure (brand, geography, benefit structure, KYC rules), Day 3-4 Onboard (operator, sales, and corporate accounts), Day 5-6 Pilot (first cohort and test cases), Day 7 Go Live.

Your benefit structure and policy rules, your branding assets (if white-labelling), a list of corporate accounts or cohorts to onboard, and a nominated internal point of contact for configuration sign-off.

Minimal involvement is needed. CCP is deployed and configured by MediGence's team; your IT team's role is typically limited to any data integration you choose to enable, and isn't required for go-live.

Yes. CCP is white-label-ready — your name, your branding, your dashboard — with MediGence's infrastructure running behind it.

A dedicated account manager, a 24/7 support helpdesk, and a case manager assigned to every patient case from referral through to full recovery.

Every case request runs against a 48-hour clock. Second opinions carry a 72-hour turnaround with fellowship-certified doctors. Post-operative follow-ups are scheduled and tracked against defined recovery milestones.

Cases flagged red or amber in the risk assessment trigger priority escalation, with alerts to your underwriting or case management team so you can approve, reject, or request clarification before treatment proceeds.

Your dedicated account manager is the first point of contact, backed by the 24/7 helpdesk for any patient- or case-level issue outside business hours.

All data is encrypted at rest and in transit. Access is role-based, so each user — insurer, hospital, case manager, or patient — sees only what their role permits.

Yes. MediGence's platform follows HIPAA-aligned and GDPR-aligned data handling practices, and clinical data governance operates under NABH-aligned standards.

Every request, approval, rejection, and escalation is logged automatically. No request leaves the platform unlogged — audit-grade by design, and exportable for your compliance and actuarial teams.

Data is hosted on secure cloud infrastructure with encryption at rest. Access is restricted by role, so insurers and hospitals only see case data relevant to their own patients and policies.

Yes — a full data security and compliance documentation pack is available on request as part of onboarding.