CE Data Architect

At Lilly, the work is demanding because patients are waiting. We unite caring with discovery to help make life better for people around the world, knowing that every decision, every detail, and every day matters. Headquartered in Indianapolis, Indiana, our over 50,000 employees around the globe take on complex challenges to discover and deliver life-changing medicines, strengthen how health is understood and managed, and support the communities we serve. This is hard, urgent, selfless work—but it’s work worth doing. If you’re driven by purpose and ready to bring your best to work that truly matters for patients, we invite you to join us.  Organization Overview Lilly CIA powers the enterprise with governed, AI-ready data products, a converged semantic layer, and the identity and policy infrastructure behind Lilly’s digital experiences. Within CIA, the LillyDirect Covered Entity (CE) Pharmacy pod builds and operates the data platform that sits inside the pharmacy’s covered-entity trust boundary — handling identified PHI under HIPAA with strict isolation from parent-side systems. This role anchors the architecture of that platform.

Summary The CE Data Architect owns the end-to-end data architecture for the CE Pharmacy platform within the covered-entity boundary: the canonical data models, the medallion/lakehouse structure, the identity crosswalk, PHI classification, data contracts, and the isolation controls that keep identified PHI from crossing to parent-side systems without tokenization. This is a governance-first, evidence-based role that translates regulatory and privacy constraints into durable, load-bearing architecture — partnering closely with stewardship, policy-as-code, and engineering to ensure the platform is compliant, auditable, and built to scale.

Own the canonical CE data architecture   — conceptual, logical, and physical models across the Databricks / Unity Catalog medallion (bronze → silver → gold), scoped entirely within the CE trust boundary. Model the CE identity and crosswalk layer   spanning Reltio MDM, Auth0/Passport, Datavant tokens, Scriptly, Genesys, Prescryptive, and Transcend — defining authoritative-anchor logic and safeguarding merge/split integrity. Author and steward data contracts   (ODCS) for CE data products, defining schema, quality, freshness/SLA, and lineage expectations between producers and consumers. Codify PHI data classification   across the ~300-field registry and ensure row/column-level security, masking, and tokenization boundaries are enforced architecturally — not merely documented. Design the CE isolation model   that prevents identified PHI from crossing to parent-side systems without Datavant tokenization; partner with the Policy-as-Code Engineer to render architectural intent as OPA/Rego. Establish reference architecture and patterns   so Analytics Engineers and Data Engineers build CE data products consistently and to standard. Define lineage, cataloging, and metadata strategy   for CE, ensuring end-to-end traceability that supports audit readiness and incident response. Provide architectural review and gatekeeping   for new CE data flows, integrations, and AI/agent consumption paths. Partner across governance and platform   — HIPAA governance, Privacy, Legal/DLO, and platform owners (PPH) — to keep the architecture compliant and defensible. Enable Skill and agent development   — architect the data contracts, reference patterns, and guardrails that let Applied-AI / Agent Engineers build CE Skills and agents against governed data, so PHI classification and consent travel with the data into agentic consumption. Supply CI/CD patterns for data, policy, and agent artifacts   — define and standardize the pipelines (Azure DevOps, Git-based promotion across dev → test → prod) that version and ship models, ODCS contracts, OPA/Rego policies, Skills, and agents within the CE boundary. Basic Requirements