Capabilities

Enterprise architecture across AI, automation, and integration

A practitioner's depth in the systems that matter — from applied AI to healthcare interoperability — applied to advisory and architecture engagements.

AIAutomationAPIsEpicHL7FHIRMirth ConnectOperational IntelligenceContact Center IntelligenceHealthcare Integration
01

AI Architecture

Designing practical AI systems that improve operations, decision-making, and efficiency — built to deliver, not to demo.

  • Applied AI systems
  • Decision support
  • Operational intelligence
02

Automation Architecture

End-to-end business automation using modern cloud orchestration, with observability and auditability built in.

  • n8n orchestration
  • Workflow automation
  • Event pipelines
03

API & Integration

Architecting integrations and interoperability frameworks that scale across enterprise systems.

  • API strategy
  • Interoperability frameworks
  • Scalable ecosystems
04

Healthcare Integration

Deep experience across Epic, HL7, FHIR, OAuth, and healthcare workflows and interoperability.

  • Epic Bridges
  • HL7 v2.x
  • FHIR · OAuth / SMART on FHIR
  • Mirth Connect
05

Operational Intelligence

Turning operational data into executive-level decision support with no hidden state — everything persisted and queryable.

  • Metrics & telemetry
  • Executive dashboards
  • Data modeling
06

Contact Center Intelligence

Instrumenting contact center operations to surface signals that improve service and efficiency.

  • Conversation analytics
  • Workflow automation
  • Quality signals

Contact center intelligence

One operation, seen whole

A call center is an organism: calls enter, branch, pool, transfer, escalate, loop back, or quietly die in a queue. Instrument every vessel and the organism becomes governable — bottlenecks visible, vendor claims testable, spend accountable. Hover the telemetry to inspect the anatomy.

INBOUND≈3.3K/DAYIVRTRIAGEQUEUECONGESTION = DENSITYAGENT POOLHANDOFFDEPT TRANSFERESCALATETIER 2 / SUPCONTAINEDSELF-SERVICERESOLVEDFIRST CALLCALLBACKRE-ENTERS TRUNKABANDONEDDEAD END · MEASURED

Telemetry surface

Anatomy mirrors a real, governed 1.2M-call/yr operation — values shown are representative, not live. Case study

Integration connector depth

Every channel, inbound and outbound — hands-on across all three

Epic Bridges, Epic Interconnect, and Mirth Connect cover most of what healthcare integration demands. The following connection types aren't theoretical — each was built, debugged, and maintained in production across 200+ integrations.

Epic Bridges

Epic's HL7 v2.x interface engine — the backbone of inbound and outbound message exchange across scheduling, labs, clinical documents, billing, and provider directories. Worked across ADT, ORM, ORU, SIU, MDM, DFT, BAR, and RDE message types.

Certified · Dec 2025

Receive (inbound)

  • MLLP/TCP — inbound HL7 v2.x stream
  • Batch file via FTP / SFTP
  • Print-to-file (lab reports, documents)
  • Web Blob (binary document ingest)
  • Data Courier (batch extract load)
  • Epic-to-Epic Care Everywhere / Cross-Org

Send (outbound)

  • MLLP/TCP — outbound HL7 v2.x stream
  • Batch file via FTP / SFTP
  • Web Blob (document push to downstream)
  • Data Courier (batch export)
  • Print dispatch (report delivery)
  • Scheduled outbound feeds (lab, pharmacy, billing)

Epic Interconnect

Epic's web services and FHIR layer — the API surface that exposes Epic data to third-party systems, apps, and payer/provider networks. Worked in TST on FHIR R4 builds, SMART on FHIR OAuth flows, and EWS integrations for scheduling and document exchange.

TST environment

Receive (inbound)

  • FHIR R4 REST API (read, search, create)
  • SMART on FHIR / OAuth 2.0 authorization
  • Epic Web Services — SOAP/WSDL
  • HL7 v2 over HTTP(S)

Send (outbound)

  • FHIR R4 REST API (write, patch)
  • Epic Web Services — SOAP/WSDL
  • App Orchard / third-party API push
  • Subscription notifications (FHIR topic-based)

Mirth Connect

Open-source integration engine used to route, transform, and monitor HL7, FHIR, and custom messages across clinical and operational systems. Built and maintained channels across the full connector library — inbound source listeners and outbound destination senders.

200+ channels built

Receive (inbound)

  • TCP Listener — MLLP (HL7 v2.x)
  • HTTP / HTTPS Listener
  • File Reader — local, FTP, SFTP
  • Database Reader — JDBC/SQL polling
  • Web Service Listener — SOAP/WSDL
  • JMS Listener — queue/topic
  • DICOM Listener
  • Email Reader — POP3 / IMAP
  • JavaScript Reader (custom polling logic)
  • AS2 Connector

Send (outbound)

  • TCP Sender — MLLP (HL7 v2.x)
  • HTTP / HTTPS Sender
  • File Writer — local, FTP, SFTP
  • Database Writer — JDBC/SQL insert/update
  • Web Service Sender — SOAP/WSDL
  • JMS Sender — queue/topic
  • DICOM Sender
  • SMTP Sender (email delivery)
  • Document Writer (PDF generation)
  • JavaScript Writer (custom dispatch logic)

Technology ecosystem

Fluent across the enterprise healthcare stack

EHR & platforms

  • Epic (Bridges, Data Courier)
  • Cerner
  • Meditech
  • Allscripts
  • NextGen

Integration engines

  • Mirth Connect
  • Corepoint
  • Cloverleaf
  • InterSystems IRIS / HealthShare
  • Rhapsody

Standards

  • HL7 v2.x
  • FHIR R4
  • SMART on FHIR
  • OAuth2
  • CCDA
  • X12 / EDI

Cloud, data & automation

  • AWS (Certified Cloud Practitioner)
  • n8n
  • Baserow
  • Workato
  • SQL / data modeling

Need this depth on your initiative?

Advisory, fractional, or a focused architecture review — start with a conversation.

Book a Consultation →