Skip to main content

Pathways

A modern, git-native take on the interface engine.

Pathways is what we are building beyond the parsers — an integration engine where the channel is just code, the state is just files, and the deploy is just a commit. It is not ready, and we won't pretend it is.

This page is a teaser, not a product page. There is no release, no version number, and no demo. We share more here as the engine takes shape.

The landscape today

Healthcare's interface engines today.

Three integration engines carry the majority of US healthcare's message traffic. We have built and maintained channels in all three; this is how they orient.

Mirth Connect

The open-core integration engine most US healthcare teams have touched at least once — channels defined in a GUI, configuration exported as XML.

Rhapsody

A widely-deployed commercial integration engine — channels defined visually, routes and filters configured per environment in the product.

Cloverleaf

A long-running commercial integration engine — channels and translations configured in the product, with environment promotion handled by export and import.

Each of these engines is a real, working tool that real teams ship real traffic on. They share one design assumption from the era they were built in: the channel is configured in a product, not authored in a repository. Pathways is a bet on the other side of that assumption.

The bet

Git-native, end to end.

Pathways is being designed around the workflow engineering teams already use for everything else they care about. Four tenets describe the direction, not a feature list.

The channel is just code

A channel is a typed TypeScript module in your repository. Reviewable, testable, refactorable. No GUI as the source of truth.

The state is just files

Configuration, profiles, and per-environment overrides live in the same repository as the channel — versioned, diffable, and migration-safe.

The deploy is just a commit

Promotion to staging or production is a merge. The deployed version is always the commit on a branch — nothing edited live in a UI.

The history is just git log

Who changed which channel, when, and why — the answer is in your existing version-control history, not in a separate audit pane.

Honest status

What Pathways is not yet.

We would rather surprise a reader with capability than disappoint them with a missing feature. So the floor we set publicly is the floor we are sure about.

  • No release. No version. No demo.

  • No drop-in replacement for Mirth, Rhapsody, or Cloverleaf today.

  • No SaaS offering planned. Pathways is being designed as software you run, not a managed service.

  • We'll say more about timing when there's more to say.

Want to follow along?

Drop us a line. We will write back when Pathways has something a reader can actually try, and not before.

Email us to follow along Read the open-source code