ITL SoftwareHCSA TI 2.0 MEMM
Mobile Health · HCSA TI 2.0 UI concept

Mobile application for insured users.

DiPag, TI-Messenger, ePA and e-prescriptions in one coherent mobile product vision. Clear interface boundaries enable technical evaluation with existing healthcare platforms.

View mobile screens Discuss integration scope

UI concept with synthetic sample data. Integration and approval status are assessed separately.

UI concept with synthetic data · click either screen to enlarge · video consultation is illustrative
04
Mobile areasDiPag · TIM-M · ePA · e-Rezept
UI
Concept screensSynthetic sample data
TI
IntegrationAssessed per project
Mobile application 01—04

Four insured-user application areas.

A consistent view of key mobile journeys — from patient invoices and messaging to health documents and prescriptions.

01 / 04UI concept

DiPag

Digital patient invoices

Patient invoices, reimbursement states and related documents.

02 / 04UI concept

TIM-M

Secure communication

Structured messaging and document exchange with healthcare contacts.

03 / 04UI concept

ePA

Electronic patient record

Document-oriented views and health-record navigation.

04 / 04UI concept

e-Rezept

Digital prescriptions

Mobile views for prescriptions and their states.

The images illustrate user flows with synthetic data. They are not evidence of live TI connectivity, production readiness, certification or gematik approval.

Evidence status

Concept and technical integration, clearly separated.

The mobile experience is presented as a UI concept using synthetic sample data. The current implementation, integration and approval status must be assessed for each specific project.

Public evidence status HCSA TI 2.0
AreaUI presentationProduction TI connection
DiPagConcept viewNot publicly evidenced
TIM-MConcept viewNot publicly evidenced
ePAConcept viewNot publicly evidenced
e-RezeptConcept viewNot publicly evidenced

No blanket claim of production readiness, gematik approval, conformance or interoperability. Technical verification and scope are determined with each partner.

Technical context

ZETA remains a background security context.

Zero Trust and access architecture belong behind the user-facing services. ZETA is not a fifth app module and the concept does not assert implementation or regulatory conformity.

User-facing modulesDiPagTIM-MePAe-prescriptionsZETA · Access/security context
Partnerships

Architecture & technology partnerships

Integration review · Technical evaluation · Joint development. HCSA complements existing landscapes at explicitly defined module and interface boundaries.

Discuss integration scope

MEMM remains a separate technology area. Explore MEMM platform