Four boundaries that stay separate
- Canonical TI-Flow domain: stable process, task, actor and transition semantics independent of wire representation.
- Flowtype/profile generation: explicit version controls allowed features, actors and transitions.
- FHIR® adapter: deterministic mapping and local profile validation outside the workflow transaction.
- Delivery boundary: durable intent/payload is delivered and reconciled only after successful commit.
Why FHIR® should not become authoritative process state
If internal process semantics are stored directly as an external profile representation, every profile revision can leak back into workflow logic. A separate domain boundary supports versioned adapters and controlled profile changes without silently reinterpreting running processes.
What this page explicitly does not claim: This page describes a version-bound development architecture. It does not claim complete Draft_TI-Flow_26_2 implementation, HCC/ZETA conformance, FHIR® profile completeness, approval or provider readiness.