Most technology problems are coordination problems. The stack is rarely the issue.
BTS Integration is the integration architecture practice of Jordan Johnson. Twenty years designing, building and owning the interfaces that move clinical data, claims and orders between enterprise systems, across healthcare, energy and manufacturing.
The part of the estate nobody owns until it breaks.
Orders that never arrive. Claims that reject for reasons no one can trace. Clinical data that lands in the wrong record. A report that is right on Monday and wrong by Friday.
Underneath each of those is the same thing: systems, teams and vendors that were never asked to agree on anything. The work is designing the layer where they agree, building it so it survives production, and leaving behind an architecture the next person can read.
Systems that should have been talking years ago
Fragmented data, manual reconciliation and siloed tools are operational debt. Map the estate, design the target state, lead the build.
Architecture that survives the handoff
Canonical schemas, message contracts, error handling and the runbook that keeps interfaces alive after go-live. The measure of an integration is whether it still works once the architect has moved on.
Estates that carry the cost of change
Point-to-point connections accumulate quietly. Every new interface costs more than the last one, until something centralizes them and the curve flattens.
Three kinds of problem, all of them versions of the same one.
Integration architecture and delivery
Target-state design for enterprise integration: canonical schemas, message contracts, error handling, and the operational runbook that keeps interfaces alive after go-live. Delivered across Azure and AWS, SAP PI, Boomi and IBM MQ, with C# and .NET services against SQL Server and Oracle.
Energy & industrial work → ArchitectureEDI and healthcare data exchange
X12 and HL7, deep rather than broad. 837, 835, 270 and 271 across providers, payers and clearinghouses under HIPAA. 204, 214 and 210 in transportation and logistics. HL7 across clinical and imaging platforms in a federal health program.
Healthcare & payer work → Data ExchangeIntegration estate assessment
An honest inventory of what an estate actually contains: the interfaces, the systems behind them, where the coupling is load-bearing, what is undocumented, where the single points of failure are, and what the cost of change looks like before a modernization, a platform migration or a transaction.
Assessment for M&A → AssessmentWhat the work actually runs on.
Twenty years produces a specific inventory rather than a general one.
SAP PI, Boomi, IBM MQ, enterprise service bus architectures, and legacy integration stacks carried through migration. Publish and subscribe, request and reply, file and batch, and the failure modes each one hides.
X12: 837, 835, 270, 271 in healthcare; 204, 214, 210 in transportation. HL7 v2 across clinical, imaging and cardiology platforms. Canonical schemas and message contracts as the layer above both.
Azure and AWS. C# and .NET services, SQL Server and Oracle, PowerShell for the operational edges. Interfaces built to be monitored, not just deployed.
SAP, Oracle Transportation Management, manufacturing execution systems, EMR and clinical platforms including GE Centricity, PACS and imaging, and the mainframe estates that still sit behind several of them.
Datadog, Jira, TFS, Bitbucket. Onshore and offshore team coordination, 24/7 production support, release and configuration management discipline carried over from federal work.
HIPAA across providers, payers and clearinghouses. Federal configuration management in a NASA health program. Medical device and insurance environments where an interface change is a controlled change.
The Architect
Jordan Johnson is an integration architect based in Houston, Texas, with twenty years of enterprise integration experience.
The arc runs from a federal health program to heavy industry to regulated healthcare. Nine years at NASA Johnson Space Center on clinical systems integration, progressing from configuration analyst to technical developer to technical integrations architect. Six years at TechnipFMC running integration delivery for an energy manufacturer across onshore and offshore teams. Since 2021, architecture ownership on client estates in specialty metals, medical devices and insurance.
What stayed constant is the problem underneath. Different industries, different platforms, the same failure: systems bought at different times, by different people, to solve different problems, and no one ever made responsible for the space between them.
The lack of a clear architecture, accountable ownership and a roadmap tied to the business is what actually costs money. The rest is the stack getting blamed.
Six estates, five industries.
Representative engagements. Details generalized where client confidentiality applies.
HL7 integration architecture for clinical systems at NASA Johnson Space Center
Designed and implemented the interface layer connecting the Flight Medicine and Occupational Medicine clinical programs, moving HL7 across GE Centricity, PACS and cardiology platforms. Established the integration standards that unified patient data across two previously siloed programs.
Nine years. Configuration analyst to integrations architect.Integration delivery across a dual-platform enterprise estate at TechnipFMC
Owned production interfaces spanning SAP and a legacy integration stack, including Oracle Transportation Management and Foreign Trade Zone operations with X12 204, 214 and 210. Coordinated onshore and offshore delivery teams, cut manual reconciliation and built reporting visibility for operations leadership.
Roughly 35 production interfaces.Canonical integration architecture on a cloud MES migration
Brought connected systems onto canonical schemas through an enterprise service bus and introduced a publish and subscribe pattern that decoupled the estate ahead of a manufacturing execution system migration to cloud, in a specialty metals environment running 24/7.
Roughly 20 connected systems onto canonical schemas.X12 and HL7 exchange across providers, payers and clearinghouses
Architected 837, 835, 270 and 271 transaction sets alongside HL7 clinical messaging under HIPAA, spanning provider systems, payer connections and clearinghouse intermediaries in a regulated medical device environment.
Claims, remittance and eligibility, end to end.Consolidation of a point-to-point estate onto a centralized integration layer
Replaced accumulated direct system-to-system connections with a single governed integration layer, cutting the cost of change for every downstream interface and giving the estate one place to reason about failure.
Nearly two years. Insurance carrier estate.Integration delivery on a downstream refining program
Technical consulting inside a downstream refining and chemicals environment for Motiva Enterprises, delivered through Deloitte, working the enterprise integration layer between plant and corporate systems.
Port Arthur. Downstream refining and chemicals.Where this work applies
Integration problems look different by industry and behave the same way underneath. The constraints that matter are regulatory exposure, transaction volume, and how many systems were bought before anyone asked how they would talk to each other.
Get in touch
Email is the fastest way to reach me.