Top to bottom: who sees it, what orchestrates the next touch (Customer.io: segments → journeys → actions), what computes the things a segment cannot, what the data means, and where it lands. Systems of record sit beside the stack; identity and the PHI gate cut across it. The thick arrows are the buses every patient's data rides. Click any box for its inputs, outputs, status and its own connections; switch on a detail flow to see one loop's individual arrows; use the story buttons to walk a Green patient through the layers. Double-click the canvas to reset.
Every box names what it is, what it reads, what it writes, and where it stands (live, in flight, build, planned, open). Arrows light up for the box you pick.
Customer.io already uses Actions for the leaves of a journey — a message, a webhook, an attribute update — and Segments for the rules that drive them. So the orchestration layer is drawn in that vocabulary and is Customer.io alone. The layer beneath it is Processing: engines and pipelines that compute what a segment cannot (a PRISM decision, an audiogram read, a form's completeness, a fax match) and hand the result back as an attribute or event the segment can test. Azure rules and event jobs live there too, Action-based: each runs when a webhook action fires or when someone presses the button. The TNT pipeline and the Medical Clearance App's chase cadence became segments and journeys; only the mFax piece stays in Processing, because Customer.io has no fax action.