TI 2.0

What does TI 2.0 mean for embedded digital-health integrations?

The TI 2.0 architecture changes how access, identities and trust are provided around healthcare applications. MEMM places its Headless, identity/policy and versioned integration boundaries on the application side of that change; it is not positioned as a TI-Gateway, a ZETA implementation or a general identity provider.

Topics:TI 2.0TI-GatewayZero TrustHealth IDEUDI Wallet

Three architecture shifts integrators should keep separate

  • Software-based TI access belongs to the external access and operator architecture; MEMM does not replace that access layer.
  • Digital identity evidence can be mapped into versioned identity and attribute contexts without merging verification with application authorization.
  • Zero Trust is used as an architectural separation principle for identity, attributes, policy and execution; it is not a ZETA conformance claim.

Why the product boundary matters

Infrastructure may evolve independently from the host application. A stable product-facing contract gives the application a clearer integration surface while external operator, identity and trust responsibilities remain explicit.

What this page explicitly does not claim: This page is an architecture classification. It does not claim TI 2.0 conformance, TI-Gateway functionality, ZETA integration, general federation support or approval by gematik.