Architecture & Health IT
Thirty years of enterprise architecture experience — including hands-on work inside federal health systems, health information exchanges, and clinical EHR integrations. Available for senior consulting, staff augmentation, and architecture advisory roles.
Health IT & Interoperability
- HIE Architecture & Leadership — Technical lead for the South Sound Health Information Exchange (SSHIE); architecture, ONC onboarding compliance, partner communications, NHIN briefings, and use case specification.
- EHR Integration — Direct integration-layer work with Epic's gateway (via InterSystems HealthShare/MultiCare at Madigan), AHLTA, Essentris, CHCS, and GE Centricity PACS. Hands-on, not adjacent.
- Clinical Interoperability Standards — HL7, C32/CCD/C84/C62, NwHIN/NHIN Direct, CONNECT. Designed ED-specific document exchange use cases: C32 on patient arrival, C84/C62 on discharge.
- SSO & Context Management — Microsoft/Sentillion CCOW-compliant single sign-on across disconnected clinical systems; DoD CAC smart card integration (MiCARE PHR).
- Federal & Regulated Environments — DIACAP, SDL, DOJ SDLC, TATRC-funded projects. Comfortable in VA, DoD, and federal-adjacent health IT contexts.
HIMSS member · MS-HUG (Microsoft Healthcare Users Group) member · CONNECT-a-thon participant
Architecture Modernization
Experienced in the full socio-technical scope of modernization — not just the technology, but the organizational alignment, domain modeling, and change management that make it stick. See how I approach it.
- Domain-Driven Design (DDD) — Bounded contexts, domain events, and strategic design to decompose legacy monoliths into maintainable, independently deployable services.
- EventStorming & Domain Discovery — Collaborative workshops to surface domain models, identify boundaries, and build shared understanding across technical and business teams.
- Team Topologies — Aligning team structures and interaction modes with software architecture for sustainable delivery. Conway's Law applied intentionally.
- Microservices & API Architecture — MEAN/.NET stacks, Docker/Kubernetes, Azure/AWS/GCP. Enterprise integration patterns, BizTalk SOA message brokering, and modern API design.
- Cloud Migration & Modernization — Azure, AWS, and Google Cloud; CI/CD pipelines; Cloudflare Workers for modern edge-deployed architectures.
- AI/LLM Integration — Active, current experience evaluating and integrating Copilot, Claude, GPT, and Gemini into development and operational workflows. Early work on an emergency-management LLM ontology.
Representative Work
- Implemented Federal Health Architecture for Franciscan, MultiCare & Madigan Regional HIO
- Designed the MERIT message broker architecture for WRMC (BizTalk SOA)
- Contributed to the Phuket Provincial Intelligent Operations Center architecture
- Built and maintains EOC.online — open-source microservice platform for emergency operations
How to Engage
- Senior consulting & staff augmentation — architecture advisory, technical lead, hands-on development
- Architecture reviews & second opinions — assess what you have, recommend a path
- Short-term & project-based — discovery sprints, proof-of-concept work, targeted fixes
- Healthcare IT contract roles — HIE, EHR integration, federal health systems
How I approach modernization
A repeatable method built on published, field-tested work, not a framework I made up. Each step names where it comes from.
- 1
Listen before drawing
A listening tour across the organization: engineers, operators, users and leadership. I ask what people dread changing, what takes ten times longer than it should, and what they have given up asking for. Then I draw what is actually there (C4 context and container diagrams), not what the old documents say.
Nick Tune, Architecture Modernization · Simon Brown, C4 model
- 2
Tie the work to business outcomes
Modernization is not a rewrite with feature parity. I start from why: competitors moving faster, growth the system can no longer carry, poor UX, costly internal tooling. Wardley Maps show which parts of the value chain are evolving toward commodity and which are worth custom work.
Simon Wardley, Wardley Mapping · Jonathan Smart, Better Value Sooner Safer Happier
- 3
Find the real domain boundaries
Big Picture EventStorming puts the business timeline on a wall, so the boundaries come from how the work flows, not from the current code. Domain Storytelling replays real workflows. The result is a set of bounded contexts with low change coupling between them.
Alberto Brandolini, EventStorming · Eric Evans, Domain-Driven Design
- 4
Invest where it differentiates
Not every part of the system deserves the same money. Core Domain Charts separate what makes the business distinctive (build it well) from what is supporting or generic (simplify it, or buy it).
Nick Tune, Core Domain Charts
- 5
Align teams with the architecture
Systems end up shaped like the organizations that build them, so I design both on purpose: stream-aligned teams that own a domain end to end, platform teams that remove friction, and clear interaction modes between them.
Matthew Skelton & Manuel Pais, Team Topologies · Conway's Law
- 6
Migrate in slices, and keep it honest
Deliver a first real slice within three to six months, then scale what works. Strangler-fig migration and anti-corruption layers let old and new run side by side. Architectural fitness functions in the build stop the new structure from quietly eroding.
Martin Fowler, Strangler Fig · Ford, Parsons & Kua, Building Evolutionary Architectures
Weighing technical debt
Ask the people in the code
Pain interviews are the fastest signal and need no tooling. Engineers know which modules nobody dares touch.
Mine the git history
Files that change every sprint and are also complex are where debt costs the most. Ugly code nobody has touched in three years can usually wait.
Measure delivery, not just code
DORA metrics (deployment frequency, lead time, change failure rate, time to restore) expose coupling, testing and observability debt before anyone reads a line of code.
Static analysis and coverage
Complexity, duplication, outdated dependencies and test coverage give a baseline, and a way to show the trend improving.
Compare intended to actual
A current-state C4 audit next to the intended design: shared databases, direct calls that should go through an API, undocumented integrations. The gaps are the debt.
Keep a debt register
Each item scored by business impact × change frequency ÷ cost to fix, so the priorities can be defended in business terms rather than engineering taste.
The bookshelf behind the methods
Books I have read closely and apply in practice.
Fundamentals of Software Architecture
Neal Ford & Mark Richards. Architecture characteristics, styles and trade-off analysis. I wrote a 90+ page synthesis of it.
Software Architecture: The Hard Parts
Ford, Richards, Sadalage & Dehghani. Pulling distributed systems apart: data ownership, service granularity, sagas and contracts.
Architecture Modernization
Nick Tune. The socio-technical playbook behind the steps above: listening tours, EventStorming, Core Domain Charts, Team Topologies.
Software Systems Architecture
Nick Rozanski & Eoin Woods. Stakeholder-driven viewpoints and perspectives for describing large systems rigorously.
Collaborative Software Design
van Kelle, Verschatse & Baas-Schwegler. Building architectural agreement across teams you do not control.
Patterns of Enterprise Application Architecture
Martin Fowler. Domain Model, Repository, Data Mapper: the reasons behind the patterns modern frameworks take for granted.
Enterprise Integration Patterns
Gregor Hohpe & Bobby Woolf. Patterns I implemented directly in the MERIT message broker at Madigan.
Talk to John
You'll reach me directly, not a sales team. Describe what you need and I typically reply within one business day.