BOOKER TECH CONSULTING · CHICAGO
Healthcare interoperability. Cloud foundations. Enterprise data platforms.
Founder of Booker Tech Consulting, bringing architecture leadership and hands-on engineering to integration, cloud, and data modernization.
Open to principal and lead roles, contracts, and focused consulting. C2C/1099 preferred; suitable W2 opportunities welcome.
CONCEPTUAL ARCHITECTURE
Interfaces · APIs · Events
Governed information. Reliable access.
Identity, access & reliability
SELECTED DELIVERY EXPERIENCE
Epic & HL7 integrationCamel · Kafka · SnowflakeAzure · Terraform01 / SELECTED PROFESSIONAL EXPERIENCE
Experience from Ian’s prior healthcare, data, and cloud roles. This is the work he brings to a new team or engagement.
Designed and supported bidirectional HL7 interfaces across clinical, laboratory, pharmacy, radiology, and financial systems. Work included Epic integration, interface engines, and messaging-platform recovery.
Designed and operated Apache Camel and Kafka pipelines carrying clinical data into Snowflake. Responsibilities included the enterprise warehouse’s Gold and Platinum layers and data-governance work.
Deployed an Azure foundation spanning multiple landing zones with Terraform, bringing infrastructure provisioning into a repeatable, code-based process.
02 / THE PRACTICE
An integration problem can become a data problem. An AI pilot can expose both. The architecture needs to account for how the pieces work together.
Understand the interfaces, events, dependencies, and failure paths that connect operational systems to the people who need their data.
Healthcare interoperability · APIs & events · Data pipelines
Bring cloud environments, data platforms, delivery practices, and recovery requirements into an architecture your team can operate.
Azure & hybrid cloud · Snowflake · Infrastructure as code
Define what search and AI can access, how answers will be evaluated, and who owns the decisions and operating controls.
Private AI & search · Permissions · Evaluation & governance
Private AI is a question of control: data access, retention, deployment, evaluation, and ownership. The appropriate model may be managed, customer-cloud, hybrid, or local.
03 / WAYS TO WORK TOGETHER
Bring Ian into a senior role or delivery team, or engage Booker Tech Consulting for a defined integration, cloud, or data challenge.
PRINCIPAL & LEAD ARCHITECTURE
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.
INTEGRATION & INTEROPERABILITY
Review clinical interfaces, APIs, event flows, and data pipelines. Make dependencies, recovery needs, and modernization priorities clear.
Typical work: interface and data-flow mapping, integration design review, migration planning, and scoped engineering.
Discuss integration workCLOUD & DATA PLATFORMS
Bring Azure environments, Snowflake platforms, and delivery practices into a coherent architecture with clear operating ownership.
Typical work: platform assessment, architecture decisions, infrastructure as code, and a sequenced delivery plan.
Discuss platform workPINPOINT THE EXPOSURE
Start with a small number of content connections. Understand where source permissions, service identities, or answer delivery could lose the intended access boundary.
You leave with an access and data-flow map, prioritized gaps, and a remediation sequence.
Best fit: A platform owner, security architect, or AI lead connecting business content to a pilot.
Proposed starting scope: Up to two content connectors, stakeholder discussions, and sanitized architecture and permission evidence.
The decision: What needs attention before expanding access or use?
Discuss a triageEVALUATE THE USE CASE
Look beyond whether a demonstration answers a question. Examine access, source provenance, freshness, retrieval quality, evaluation, and operating ownership.
You leave with a trust-boundary review, evaluation criteria, a risk register, and a proceed, prepare, or stop recommendation.
Best fit: An enterprise-knowledge or AI sponsor with a defined use case, a pilot, or a search experience people do not trust.
Proposed starting scope: One use case and a bounded set of content sources, with a documented review of permissions, citations, freshness, and answer evaluation.
RAG, in plain language: Retrieval-augmented generation combines retrieved source material with a model-generated answer. Both the retrieval and the answer need scrutiny.
Discuss an assessmentDESIGN THE WAY FORWARD
Turn a selected workload into a concrete architecture: identity, data flows, deployment boundaries, evaluation, resilience, and responsibility for operating it.
You leave with a target architecture, decision records, a control and evaluation plan, and a sequenced delivery backlog.
Best fit: A funded initiative with a selected use case and an owner who needs an implementation plan.
Proposed starting scope: One workload and agreed environments, with architecture decisions and operating responsibilities made explicit.
The decision: What should be built, configured, deferred, or changed—and in what order?
Discuss a sprintEvery 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.
04 / ABOUT IAN
Ian Booker
Founder & Principal ArchitectThe connecting thread is the work between systems: data, identity, infrastructure, and the people responsible for them.
Ian’s background spans healthcare integration, enterprise data architecture, cloud foundations, and operational resilience. His experience includes healthcare roles between 2010 and 2024, including integration engineering at Rush and data architecture at Lurie Children’s Hospital.
That delivery experience now informs Booker Tech Consulting’s work on architecture decisions, enterprise search, and governed AI. The practice pairs senior technical judgment with hands-on investigation and clear documentation.
INDEPENDENT LAB WORK
Current lab work explores local and offline model operation, resource constraints, and reproducible engineering environments. It informs questions about quality, latency, deployment choices, and the evidence needed before a system is used in practice.
Applied experimentation and reusable methods. Lab findings are distinct from client production outcomes.
05 / HOW THE WORK HOLDS TOGETHER
The deliverable is a decision your team can explain: what the evidence supports, where uncertainty remains, and who owns the next step.
Agree the business problem and the boundary of the work.
Trace data, identity, connectors, and the relevant trust boundaries.
Define evaluation criteria and document what has been tested.
Make ongoing responsibilities, recovery, and change decisions visible.
START A CONVERSATION
Share the work, the team, and the timing. Ian welcomes relevant senior architecture opportunities and focused consulting inquiries.
C2C/1099 preferred. Suitable W2 roles considered.
Please leave out patient data, credentials, and confidential documents. Supporting material can be arranged afterward.
Send the role, organization, location, engagement type, and expected rate or salary range.
Email Ian about an opportunityOpens your email app with an opportunity outline.
Describe the integration, platform, or architecture challenge and the support you need.
Consulting inquiry
Email Ian about a projectOpens your email app with a project outline.
For consulting, scope, fee, inputs, and timing are agreed before work starts.