Member-Data Stewardship GCC Operating-Model Director

The mandate

Claims, provider and care-management data products are scheduled for India ownership, but current stewards approve definitions without controlling remediation and engineers fix quality without understanding permissible use. Regional functions maintain competing member and episode concepts. Leadership needs an operating model that gives the GCC actionable stewardship while privacy, clinical and actuarial accountabilities remain in their proper lines.

The five-month deliverable combines a stewardship charter, four member-data product envelopes and an exercised issue-resolution kit. Milestone one closes source, definition and use mapping in week four; milestone two fixes decision boundaries in month two; milestone three runs quality, consent and incident scenarios in month four; milestone four delivers transfer waves, role profiles, economics and accepted artefacts.

The client will provide approved data samples, dictionaries, lineage records, quality incidents, use approvals, supplier agreements and access to claims, care, privacy and actuarial owners. Acceptance requires India stewards to resolve two unseen quality disputes, route one proposed use correctly and lead an incident replay with traceable decisions. The data and privacy officers jointly sign each product envelope.

The engagement does not include issuing privacy or clinical opinions, processing live member cases, redesigning source claims systems, selecting data tools or implementing the target platform. Consultants may define stewardship evidence and escalation but cannot approve a use purpose, change a clinical code or accept residual risk. All records stay inside client-governed analytical environments.

Definitions, use maps, quality thresholds, decision matrices, incident protocols, role profiles and transfer gates will be delivered in editable form and applied during workshops. Before close, client stewards must classify a fifth data product and defend its GCC boundary unaided. Implementation beyond that proof is separately commissioned and cannot condition acceptance of the operating model.

Why this is external work

Regional data owners defend familiar definitions, privacy teams focus on use and engineers focus on repair, leaving stewardship without an integrated outcome. The future India owners lack organisational standing to arbitrate the design before transfer. Independent health-data operating expertise can establish useful authority without appropriating legal, clinical or actuarial decisions.

What you will own

• Map claims, provider, eligibility and care data from source meaning through transformation, use, quality and retirement.
• Define product-level steward authority over definitions, quality thresholds, issue priority, lineage evidence and change proposals.
• Separate permissible-use approval, clinical coding, actuarial interpretation, engineering execution and data-product accountability.
• Design Hyderabad and Chennai stewardship leadership with domain access, escalation standing and two-deep specialist coverage.
• Exercise conflicting definitions, consent restrictions, supplier errors, delayed eligibility and downstream model-impact scenarios.
• Establish acceptance gates for documentation, access, decision history, incident readiness and source-steward withdrawal.
• Deliver four product envelopes, resolution playbook, talent design, migration economics and unresolved policy questions.

Candidate qualifications

• Designed data stewardship for health-insurance claims, provider, eligibility or care-management products spanning several regional operating models.
• Established India stewards with executable quality, definition and remediation-priority authority rather than committee-only accountability.
• Distinguished privacy purpose approval, clinical semantics, actuarial judgment, engineering repair and member-data product stewardship.
• Resolved definition disputes where competing episode, provider or eligibility rules created material operational and analytical consequences.
• Exercised sensitive-data incidents with traceable business decisions while keeping identifiable member records inside controlled environments.
• Delivered stewardship artefacts that client teams reused on additional regulated data products without consulting support.

Non-negotiables

• Can complete two India residencies and all four Zurich data-product milestones inside five months.
• Will disclose insurer, provider, data-broker, privacy-technology, analytics and systems-integration relationships.
• Brings health-data product stewardship and India operating-model design; generic data governance is insufficient.
• Accepts client-controlled records, no legal or clinical opinion and dual data-privacy acceptance.

1. 49 words maximum. Describe a member-data quality dispute that could not be solved by an engineering fix alone.
2. 49 words maximum. Which stewardship decision belongs in India, and which permissible-use decision must remain elsewhere?
3. 49 words maximum. What controlled client evidence must exist before you map the first data product?