Principal Architect, Payer Data Platform

Veradigm•Raleigh, NC

About The Position

Veradigm is building Health Network Architecture (HNA), a platform that brings its clinical, payer, and Life Sciences businesses onto shared foundations. The Principal Architect, Payer Data Platform defines and delivers the clinical and payer data foundation used by Veradigm’s payer products on HNA, including how data is ingested, modeled through shared definitions and contracts, and accessed by products, analytics, AI features, and partners. The role supports outcomes across risk adjustment, quality, care coordination, prior authorization, and CMS interoperability. This hands-on individual contributor defines shared clinical and payer data definitions, contracts, and API and big-data access patterns. Product teams build on these foundations, while HNA platform architecture owns the overall platform design. The architect works alongside Product and engineering teams in the US and India, carrying complex data problems through to production. Approximately 25% of the role involves building reference implementations and shared primitives; the remainder focuses on design, design review, and collaboration with delivery teams. The role also designs data foundations that AI features can use accurately and safely, and uses AI in engineering work. It helps payer products give health plans a complete, current view of members and providers faster answers by addressing gaps between payer and provider data.

Requirements

Bachelor’s degree or equivalent technical/business experience (required).
At least 5 years of experience designing data platforms for healthcare clinical and/or payer data, such as claims, eligibility, or clinical records (required).
Expertise in relational, dimensional, and FHIR resource modeling, as well as canonical models and data contracts.
Hands-on experience with healthcare data standards: X12 EDI, NCPDP, HL7 v2, C-CDA, FHIR R4, and major implementation guides; and code sets including ICD-10, CPT/HCPCS, LOINC, SNOMED CT, RxNorm, and NDC.
API and service design experience, including REST and FHIR APIs, event-driven design, and caching.
Ability to write and review production code in a major language such as Python, Java, or C#.
Working knowledge of payer business areas including risk adjustment, quality, care management, utilization management, prior authorization, and CMS interoperability rules.
Uses AI tools as part of daily design and engineering work.
Experience designing healthcare-data foundations for AI features, including grounding, structured extraction, evaluation, and PHI guardrails.
Understanding of how clinical data from provider systems flows into payer use cases such as risk adjustment and quality.
Ability to design internal platforms that other teams adopt, with clear contracts, sensible defaults, documentation, and migration paths.
Strength with cloud data platforms and ingestion, including AWS, cloud data warehouses or lakehouses such as Snowflake, relational databases, batch and streaming pipelines, and orchestration.
Knowledge of master data management and identity resolution for members and providers.
Knowledge of PHI security and compliance, including HIPAA, audit, and controls behind HITRUST and SOC 2.
Experience or knowledge of data quality, observability, and lineage practices.
Ability to explain data architecture clearly to engineers, product managers, and executives, in writing and in person.
Legally authorized to work in the United States or Canada; employment eligibility verification is required as a condition of hire.
Visa sponsorship is not offered.

Nice To Haves

Master’s degree (preferred).
10+ years of relevant work experience, with 2–3 years at the Expert level or equivalent experience (preferred).
5+ years of practical experience designing and building enterprise or distributed software systems (preferred).
AWS Certified Solutions Architect – Professional or equivalent cloud architecture certification (preferred).

Responsibilities

Design ingestion frameworks for claims, remittance, enrollment, eligibility, pharmacy, lab, ADT, and clinical documents across X12, HL7, FHIR, and file feeds.
Establish standards for data validation, reconciliation, provenance, observability, and safe reprocessing, enabling end-to-end measurement of data quality and delivery.
Define the architecture and sequence for migrating existing payer feeds onto HNA without disrupting customers.
Design shared clinical and payer data definitions and contracts for payer products on HNA.
Enable payer products to reuse shared definitions, contracts, and services while supporting their distinct workflows.
Govern data models, including versioning, schema evolution, extension approvals, and data contracts with producer and consumer teams.
Define when products and partners should use synchronous APIs, events, bulk exchange, or analytical access, including FHIR-based interfaces where appropriate.
Design data access with Security and Privacy to meet HIPAA minimum-necessary, consent, and audit requirements within performance and cost targets.
Design data foundations for AI features, including definitions, provenance, and access controls that support accurate and safe use of clinical and payer data.
Build reference implementations and shared primitives, and publish standards and examples that enable teams to adopt them independently.
Use AI in engineering work, including mapping feeds to shared definitions, generating and testing transformations, and detecting data quality issues; establish patterns for teams to follow.
Review data designs across payer product teams against shared standards and collaborate with HNA platform architecture, which owns the overall platform design.
Work with Product from problem definition, translate product direction into data architecture, and support teams through delivery until product and platform outcomes are achieved.
Grow data-modeling skills across engineering teams.
Travel up to 20% may be required.