Data Architects

Job Summary

Working in the Health System Insight Center, the Data Architect helps build and maintain the Health System Insight Platform—University of Utah Health’s enterprise environment for curated datasets to inform system decision‑making and action. As a member of the Insight Center, you will partner with clinical analysts to translate ambiguous questions into durable, domain‑focused data assets (e.g., care lines, market intelligence, economic models, and system performance).

This role is distinct from “one‑off” report writing; success is measured by building stable foundations that eventually graduate into standardized production.

• Client‑facing discovery:
  Partnering with frontline stakeholders to understand the “why” before building the “what.”
• Analytical diagnosis:
  Using structured methods to trace data issues to their source.
• Durable iteration:
  Designing first‑iteration assets that are built to outlive their initial request.
• Standardized stewardship:
  Applying institutional naming and documentation standards from day one.
• Production graduation:
  Orchestrating the handoff of stable assets to EDW and platform engineers.

• Design and build new, domain‑focused data assets in direct partnership with clinical analysts and care line teams to answer strategic, clinical, or operational questions.
• Iterate on data structures and definitions as the understanding of a question develops, ensuring assets are built for long‑term durability rather than one‑off use.
• Standardize naming conventions, business definitions, and derivations from the initial build to ensure data integrity and ease of use for downstream partners.
• Collaborate with Enterprise Data Warehouse architects to leverage existing institutional assets and ensure new work complements the broader data infrastructure.
• Orchestrate the handoff of stable, mature assets to the platform’s internally‑focused architects and engineers for graduation into the gold‑standard production layer.
• Work with Solution Analysts to migrate analyst inquiries toward shared, durable assets, reducing the reliance on custom, non‑standardized datasets.
• Integrate data privacy and protection standards into the design of all new datasets, ensuring the secure handling of PHI and adherence to IRB‑governed protocols.
• Pursue continuous professional development and keep pace with emerging technologies to support the ongoing growth of the Health System Insight Platform.
• Undertake additional architectural duties as needed to support the Insight Center and the organization’s evolving data needs.

• 1 year of higher education can be substituted for 1 year of directly related work experience.
• Data Architect, II:
  Requires a bachelor’s (or equivalency) + 4 years or a master’s (or equivalency) + 2 years of directly related work experience.
• Data Architect, III:
  Requires a bachelor’s (or equivalency) + 6 years or a master’s (or equivalency) + 4 years of directly related work experience.
• Data Architect, IV:
  Requires a bachelor’s (or equivalency) + 8 years or a master’s (or equivalency) + 6 years of directly related work experience.
• Demonstrated expertise in navigating ambiguity by translating high‑level clinical, operational and strategic inquiries from stakeholders into robust, well‑structured data assets that move work forward.
• Proficiency with SQL and at least one modern data transformation framework or ETL / ELT toolset.
• A proven track record of data stewardship, including the consistent application of naming standards, business definitions, dependency tracking, and lineage as part of the core deliverable.
• Ability to work cooperatively and effectively within the context of a large, highly complex academic medical center.
• Capability to thrive in settings that require a balance of sustained, iterative client partnership and the agility to respond quickly to emerging issues.

• Hands‑on experience with healthcare data sources and Epic‑derived data models like Clarity and Caboodle, as well as claims and registry data.
• Familiarity with clinical and operational workflows and an understanding of how EHR configuration decisions impact downstream data capture and…