IAN BOOKER · FOUNDER & PRINCIPAL ARCHITECT

Principal architecture.
From systems to decisions.

Healthcare integration, cloud foundations, and enterprise data platforms.

Start with a bounded architecture review, or bring Ian into your delivery team for principal architecture leadership.

For fragile interfaces, unclear data dependencies, and modernization that needs senior technical direction.

Discuss a project or contract Discuss an architecture role

CONCEPTUAL ARCHITECTURE

Connecting the whole picture.

Clinical
systemsBusiness
applicationsDocuments
& knowledge

Integration

Interfaces · APIs · Events

Cloud & data foundation

Governed information. Reliable access.

AnalyticsSearch &
AI readiness

ACROSS EVERY LAYER

Identity, access & reliability

An illustrative approach to connecting systems and preparing data for analytics and AI.Ian Booker · Booker Tech ConsultingIllustrative example · Not a client system.

PRODUCTION HEALTHCARE EXPERIENCE

Epic & HL7 integrationCamel · Kafka · SnowflakeAzure · Terraform

01 / SELECTED PROFESSIONAL EXPERIENCE

Architecture grounded
in delivery.

Selected examples from Ian’s prior employment, including Rush and Lurie Children’s Hospital. These describe professional experience, not BTC client engagements.

RUSH & LURIE · PRIOR EMPLOYMENT

Clinical integration and recovery

The work: Bidirectional information exchange across clinical, laboratory, pharmacy, radiology, and financial systems.

Ian’s contribution: At Rush, designed, developed, and administered HL7 and EDI interfaces supporting Epic integration. At Lurie, led an Epic upgrade and directed recovery of a critical Corepoint outage.

Operating responsibility: At Rush, built messaging-platform backup, high-availability, and disaster-recovery capabilities, with automated error notifications and operational documentation.

HL7 · Epic · HealthShare · Corepoint

LURIE · DATA ARCHITECT, 2020–2024

Clinical data, warehouse, and cloud

The work: Connecting Epic-related data flows to Snowflake analytics and establishing reusable cloud foundations.

Ian’s contribution: Designed clinical data integration with Camel and Kafka and owned enterprise warehouse data layers in Snowflake.

Architecture responsibility: Led data governance initiatives and metadata roadmaps with stakeholders. Deployed a multi-landing-zone Azure foundation with Terraform to automate provisioning.

Camel · Kafka · Snowflake · Azure · Terraform

02 / WAYS TO WORK TOGETHER

Two ways to engage.

Need a specific decision answered? Start with a review. Need an architect on the team? Bring Ian into delivery.

01 / BOUNDED ARCHITECTURE REVIEWS

A clear decision and a delivery plan.

Choose the review that fits the problem. Explore its scope and sample output before starting a conversation.

Integration & Interoperability

Integration Architecture Review

Review details & sample output

Best fit: Aging healthcare interfaces, unclear dependencies, reliability concerns, or an upcoming modernization.

You leave with: A current-state flow map, dependency and failure analysis, prioritized gaps, a target design, and a sequenced implementation plan.

The decision: What should be stabilized, redesigned, or migrated first?

Starting scope & boundaries

Starting scope: One agreed integration workflow and its connected systems, reviewed through stakeholder discussions and sanitized interface and architecture evidence.

Boundary: Production changes, a complete interface inventory, and migration execution are separately scoped.

Cloud & Data Platforms

Cloud & Data Architecture Review

Review details & sample output

Best fit: An Azure or Snowflake initiative with unclear dependencies, inconsistent provisioning, or unresolved operating responsibilities.

You leave with: A map of platform components and data flows from source to reporting, prioritized architecture gaps, target design and decision records, operating responsibilities, and a sequenced delivery plan.

The decision: Which data and platform changes are necessary, and how should delivery be sequenced?

Starting scope & boundaries

Starting scope: One workload and agreed environments, using architecture documents, data definitions, infrastructure definitions, and stakeholder discussions.

Boundary: Implementation, migration, penetration testing, and ongoing operations are separately scoped.

Every engagement starts with an agreed question and a written scope, fee, inputs, and delivery date. Initial reviews use sanitized evidence. System access and implementation are agreed separately.

02 / EMBEDDED ARCHITECTURE LEADERSHIP

Senior direction within your team.

Architecture direction, design review, delivery recovery, and hands-on technical leadership. Work can support an internal team, a consulting partner, or a scoped modernization initiative.

Discuss an architecture role Discuss a project or contract

03 / HOW THE WORK HOLDS TOGETHER

Make the important
questions explicit.

The deliverable is a decision your team can explain: what the evidence supports, where uncertainty remains, and who owns the next step.

Findings & trade-offsArchitecture decisionsPriorities & ownership

01
What decision are we making?
Agree the business problem and the boundary of the work.
02
What can the system actually access?
Trace data, identity, connectors, and the relevant trust boundaries.
03
What would count as a useful result?
Define evaluation criteria and document what has been tested.
04
Who will operate and own it?
Make ongoing responsibilities, recovery, and change decisions visible.

04 / ABOUT IAN

A principal architect.
A practitioner’s perspective.

Ian Booker

Founder & Principal Architect

View Ian’s professional background

The connecting thread is the work between systems: data, identity, infrastructure, and the people responsible for them.

Ian’s healthcare technology experience spans 2010–2024, including integration engineering at Rush and data architecture at Lurie Children’s Hospital.

Booker Tech Consulting pairs that experience with hands-on investigation and clear documentation, from integration and platform decisions to governed enterprise AI.

INDEPENDENT LAB WORK

Test the assumptions.
Record the limits.

Independent experiments explore local and offline models, resource constraints, and reproducible engineering environments to inform architecture questions and deployment choices.

Applied experimentation and reusable methods. Lab findings are distinct from client production outcomes.

START A CONVERSATION

Bring the architecture
challenge into focus.

Share the work, the team, and the timing. Ian welcomes relevant senior architecture opportunities and focused consulting inquiries.

contact@bookertechconsulting.com

Please leave out patient data, credentials, and confidential documents. Supporting material can be arranged afterward. How we use inquiry information.

Projects & contracts

Describe the integration, platform, or architecture challenge and the support you need.

Consulting inquiry

Discuss a project or contract

Opens your email app with a project outline.

Or use the inquiry form

For consulting, scope, fee, inputs, and timing are agreed before work starts.

Architecture roles

Open to suitable full-time architecture roles and focused consulting engagements.

Send the role, organization, location, engagement type, and expected rate or salary range.

Discuss an architecture role

Opens your email app with an opportunity outline.

Or use the inquiry form

Request résumé View LinkedIn

Principal architecture.From systems to decisions.

Connecting the whole picture.

Integration

Cloud & data foundation

Architecture groundedin delivery.

Clinical integration and recovery

Clinical data, warehouse, and cloud

Two ways to engage.

A clear decision and a delivery plan.

Integration & Interoperability

Integration Architecture Review

Cloud & Data Platforms

Cloud & Data Architecture Review

Senior direction within your team.

Make the importantquestions explicit.

What decision are we making?

What can the system actually access?

What would count as a useful result?

Who will operate and own it?

A principal architect.A practitioner’s perspective.

Test the assumptions.Record the limits.

Bring the architecturechallenge into focus.