We are pleased to announce the release of TI-Messenger_25_3, the latest update to the TI-Messenger specifications. This release represents a significant step in advancing digital communication within the German healthcare system and provides the foundation for industry partners to develop innovative products for the telematics infrastructure (TI).

Key Updates in TI-Messenger_25_3

The new release introduces several important enhancements to the specifications, supporting the development of interoperable, secure, and efficient products:

1. Launch of Deletion Concept v2
   The updated deletion concept improves clarity and efficiency in managing data lifecycles. This update ensures compliance with regulatory requirements and simplifies implementation for industry partners.

2. Introduction of Provider Type Specification Sheet: TI-Messenger Pro
   A new and uniquely identifiable Provider Type Specification Sheet for TI-Messenger Pro has been introduced. This specification sheet outlines the normative requirements for providers of TI-Messenger services, ensuring secure, functional, and interoperable operation of service units and products.

3. Refinements Based on External Feedback
   We have incorporated valuable feedback from external stakeholders into the specifications. These smaller adjustments reflect our commitment to continuous improvement and collaboration with the industry.

Validity and Certification Pathway

The new specifications have been published with the status ‘valid’, while existing specification sheets will remain in the status ‘certifiable’. This ensures a smooth transition for industry partners while maintaining continuity for current services.

To facilitate approvals under the new release, we are actively working on updating the test system, which is scheduled for deployment in March 2026. Once the updated test system is available, the new specifications will become the standard for product approvals.

Importantly, existing products based on previous specifications will remain fully operational. The old product specifications will retain their ‘valid’ status, meaning that products already deployed can continue to function seamlessly. Additionally, industry partners can still request follow-up client approvals for services based on specification sheets with the ‘valid’ status.

The gematik specialist portal (Fachportal) has just published the new KIB concept for TI-Messenger Pro, titled "gemKPT_Inbetriebnahme_TI-Messenger_Pro" (Version 1.0.0). This updated concept aims to simplify the organisational aspects of the KIB (Commissioning and Initial Operation) process for TI-Messenger Pro, enabling quicker and more efficient implementation. The adjustments follow a thorough analysis of previous KIB processes and incorporate valuable feedback from approval holders. With these changes, the quality of the approval process will be maintained while making its execution more straightforward and effective.

https://fachportal.gematik.de/fileadmin/user_upload/gemKPT_Inbetriebnahme_TI-Messenger_Pro_V1.0.0.pdf

At the same time, the previous KIB concept for TI-Messenger 1.1 and TI-Messenger Pro ("gemKPT_Inbetriebnahme_TI-Messenger") has been updated to Version 1.2.1. This version will now only apply to the KIB process for TI-Messenger 1.1 and will no longer be valid for TI-Messenger Pro.

https://fachportal.gematik.de/fileadmin/user_upload/gemKPT_Inbetriebnahme_TI-Messenger_V1.2.1.pdf

Key Updates in the New KIB Concept for TI-Messenger Pro

The new KIB concept introduces several significant improvements designed to streamline the process for TI-Messenger Pro. These include:

• Consolidated Process: The KIB for service provider institutions (LEI) will now take place in a single phase, replacing the previous three-stage process.
• Simplified Requirements:
  • A reduced number of participants (LEI users) is now required.
  • Fewer documents are necessary, as interim reports have been eliminated.
  • Fewer TI-ITSM changes need to be processed, as the staged approach has been removed.
• Simplified Follow-up Approvals: A clear definition has been introduced outlining the conditions for conducting streamlined KIB processes for follow-up approvals. These will also require:
  • Fewer participants (LEI users).
  • Fewer use cases to be addressed.

These changes represent a significant step forward in simplifying and optimising the KIB process for TI-Messenger Pro, ensuring both efficiency and quality in implementation.

The TI-Messenger program has taken an important step forward with a newly structured roadmap for the Pro 1.1 and Pro 1.2 releases. The decision to redesign and reschedule these releases reflects both the technical maturity of the project and a clear focus on reducing integration risks while delivering value to users earlier and more reliably.

Why the Roadmap Was Restructured

The initial scope of TI-Messenger Pro 1.1 proved to be highly complex during detailed specification. Several components were strongly interlinked, increasing implementation risks and dependencies.
To address this, the original release was decomposed into two consecutive versions — Pro 1.1 and Pro 1.2.

This modular restructuring serves three main goals:

• Risk reduction in integration and testing,

• Early delivery of usable, high-value functions,

• Independence from uncertain external release schedules.

By separating the releases, the TI-Messenger team ensures stable progress and avoids technical bottlenecks, all while keeping the long-term roadmap intact.

What Each Release Delivers

TI-Messenger Pro 1.1

Pro 1.1 focuses on integration, data consistency, and interoperability.
Key components include:

• Integration of Headless and Embedded Clients,

• Provision of structured data and consent management,

• Implementation of Matrix updates 1.15 / 1.16.

Together, these enable seamless embedding into primary systems and specialist applications.
Healthcare providers benefit from fewer media disruptions, reduced manual transitions, and more stable communication processes — all of which support scalability without additional staffing effort.

TI-Messenger Pro 1.2

Pro 1.2 is centered on secure identities, automation, and efficiency.
It introduces:

• Strengthened secure profiles and identity management,

• A standardized bot operating environment,

• Refactoring of power levels to streamline system governance.

These improvements accelerate information flow across care pathways, reduce waiting and idle times, and help relieve clinical and administrative workloads.

Roadmap Timeline

The TI-Messenger roadmap defines a structured sequence for concept development, specification, and release activities across the Pro 1.1 and 1.2 versions.
The concept phase for TI-Messenger Pro 1.1 is already underway and will be followed by specification work starting at the end of February 2026. The release is planned for the end of May 2026, with test readiness expected in the fourth quarter of 2026.
The concept phase for Pro 1.2 is scheduled to start at the end of May 2026, with subsequent specification work extending into early 2027. Test readiness for Pro 1.2 is planned for the third quarter of 2027.

Backlog Items and External Dependencies

Two important functionalities remain on hold due to external dependencies:

• Voice and Video Communication:
  Implementation depends on the completion and approval of the MatrixRTC MSC 4143 specification.
  Since the Matrix Foundation has not yet set a final timeline, this feature has been deferred.
  Current expectations point to a MatrixRTC release in 2026, after which TI-Messenger can integrate federated voice and video calls.

• Multi-Tenant Capability:
  This functionality has also been moved to the backlog, as compliant, multi-tenant market solutions already exist.
  A regulatory assessment is ongoing to determine whether a separate TI-Messenger-specific implementation is required or if existing industry solutions suffice.

A More Sustainable Roadmap

The refined roadmap reflects a pragmatic approach: modular releases, reduced complexity, and coordinated alignment with the broader digital health ecosystem.
By structuring development into manageable, independent phases, the TI-Messenger initiative maintains its momentum while ensuring stability, interoperability, and measurable value for the healthcare sector.

Today, we have released a patch for the test suite.

This update includes several fixes for creating and updating HealthcareServices, where a more lenient comparison is now applied.

Additionally, we now provide a certificate revocation list (CRL) as a precautionary measure in case we ever need to revoke a compromised certificate. To clarify, no certificates have been compromised. However, you will find some revoked certificates in the list, which were deactivated for administrative reasons (e.g., a domain change or similar). We strongly recommend configuring the CRL in your infrastructure so that, in the event of a more critical revocation in the future, you are already familiar with its setup and usage.

We have also published an example Serenity report. This report serves as a reference to assist with test driver implementation. While we will make an effort to keep it up-to-date, please note that the reference system follows agile development practices. As a result, the tests and responses in the report may not always be complete or reflect the latest changes in the test suite.

For a detailed overview of all changes, please refer to our ReleaseNotes.md.

If you encounter any issues with the test suite or have questions about the changes mentioned, please don’t hesitate to raise an issue on GitHub to let us know.

Resources:

Test suite repository: https://github.com/gematik/TI-Messenger-Testsuite

Full release notes: https://github.com/gematik/TI-Messenger-Testsuite/blob/main/ReleaseNotes.md

Test driver API: https://github.com/gematik/TI-Messenger-Testsuite/blob/main/src/main/resources/api/TiMessengerTestTreiber.yaml

Since November 2024 TI-M is based on Matrix v1.11. Since then, four subsequent versions of the protocol have been released including fixes and new features. In order to make these improvements accessible in TI-M we're planning to rebase our specification on Matrix v1.15.

The necessary changes have already been published in https://github.com/gematik/api-ti-messenger/pull/327. The most notable difference is the mandatory switch to the new OAuth 2.0 APIs which will require deploying matrix-authentication-service (or a suitable replacement). If you have any feedback on these planned changes, you're welcome to leave comments and engage with us on GitHub.

A field issue has been identified that affects the intended permissions model for chat initiation in TI-M ePA. To address this, a mandatory update will be released tomorrow.

The intended system design specifies that healthcare institutions (LEIs) should only be discoverable in the directory (VZD) if they have explicitly configured their visibility for insured persons. At present, LEIs are being found in the VZD and are therefore reachable—and can be invited to chats—by insured persons, even if this was not intended.

Unintended visibility currently allows the Matrix address of LEIs to become known, enabling chat invitations that should not be possible without explicit consent. Such behavior deviates from the intended permissions model..

We will address this issue promptly by implementing the necessary technical adjustments. Moving forward, LEIs will only be visible by insured persons if they have actively set their visibility accordingly.

Solution Approach:
As part of the fix, we will adopt the use case from TI-M Pro into TI-M 1.1.2 as a hotfix:
AF_10377 – Organization – Set FHIR-VZD Visibility for Insured Persons

In addition, we will centrally correct the affected entries in the VZD so that they are no longer visible to insured persons, thereby preventing unwanted chat invitations.

By controlling visibility in the VZD, we prevent the Matrix address from being exposed, thereby stopping unwanted chat invitations from insured persons.

We appreciate your feedback and will continue to monitor and optimize the system as required during this rollout phase.

As part of our product development, we would like to start a public discussion on the TI-Messenger Connect.

Our hypothesis: There is a growing need for 1:1 communication between service providers and patients in the healthcare system. Especially in primary care. As things stand today, patients need to be identified at a high level of trust for the health ID before any communication via the TI Messenger.

The TI-Messenger Connect outlines a target image for simplified access to enable 1:1 communication between insured persons and service providers. The TI-Messenger Connect is intended to enable context-related and low-threshold 1:1 communication (“care context”). TI-M Connect therefore starts where patients are already (digitally) located: In doctors' surgeries, hospitals, pharmacies and telemedical contexts.

• Service providers will be able to provide their patients with their own TI messenger - integrated into a patient portal, a pharmacy app or an appointment booking platform, for example (design goal 1 - TI-M address for all).
• For insured persons, communication via connection requests will be much easier to access because service providers will open a bidirectional chat room with their patients directly on site - from within the care context (design goal 2 - simple onboarding).

Our long-term goal: TI-M shall be used in telemedicine in the future.

To discuss TI-M Connect with us, please comment via Github Discussions: 

https://github.com/gematik/api-ti-messenger/discussions/316

Today, a minor version of the test suite has been released. This update includes some non-breaking refactoring and streamlining of our API, as well as a change in test cases 10X0109 and 10X0508 which now allow status code 200 additionally to code 404. For full details and all changes and features in this release, please refer to our ReleaseNotes.md.

If you encounter any issues with the test suite, please raise an issue on GitHub to inform us.

Resources:

Test suite repository: https://github.com/gematik/TI-Messenger-Testsuite

Full release notes: https://github.com/gematik/TI-Messenger-Testsuite/blob/main/ReleaseNotes.md

Test driver API: https://github.com/gematik/TI-Messenger-Testsuite/blob/main/src/main/resources/api/TiMessengerTestTreiber.yaml

gematik is introducing a new, more flexible approach to scheduling approval test slots for TI-M Pro. Effective immediately, the process outlined in the updated procedure description for product approval (gemZul_Prod_TI-M_Pro) has been revised to enhance efficiency and reduce delays. This approach addresses three primary issues:

1. Manufacturers no longer need to endure lengthy waiting periods if they have a later testing slot.
2. Missed reserved test slots will not result in manufacturers being placed at the end of the queue.
3. Test slots will be shorter and smoother, enhancing predictability for your release dates.

Instead of assigning fixed time slots for approval tests, gematik will now provide short-term testing dates once manufacturers have fully met the required entry criteria. These criteria will be carefully verified and approved by gematik before a test date is issued. To ensure readiness for the approval test, manufacturers must fulfill the following entry criteria:

• Internal Testing (EvT): A test report from the manufacturer’s internal testing must be submitted, demonstrating a 100% pass rate. Exceptions are allowed only for defects that can be clearly and verifiably attributed to external factors beyond the manufacturer’s responsibility.
• Reference Implementation Testing: A test report from testing with gematik’s reference implementation must also show a 100% pass rate, with the same exception for external defects.
• Comprehensive Test Documentation:
  • Test Concept
  • Test-Requirement-Matrix
  • Test Case Specifications
• Advance Notice: Manufacturers must provide at least 10 working days' notice before submitting all deliverables.

This updated approach benefits both manufacturers and gematik by minimizing delays in scheduling approval tests and optimizing the use of testing resources. Looking ahead, gematik plans to extend this streamlined scheduling process to TI-M ePA approvals and will provide further updates in due course. This change reflects gematik’s commitment to fostering a more efficient and collaborative approval process, ensuring that all stakeholders can move forward with confidence and clarity.

Today, a patch for the test suite has been released. This update includes automated test cases for dehydrated devices. For full details of all changes, please refer to our ReleaseNotes.md.

If you encounter any issues with the test suite, please raise an issue on GitHub to inform us.

Resources:

Test suite repository: https://github.com/gematik/TI-Messenger-Testsuite

Full release notes: https://github.com/gematik/TI-Messenger-Testsuite/blob/main/ReleaseNotes.md

Test driver API: https://github.com/gematik/TI-Messenger-Testsuite/blob/main/src/main/resources/api/TiMessengerTestTreiber.yaml

Today, a patch for the test suite has been released. This update includes some refactoring of our test cases, as well as a fix for a misleading error in the tear-down steps of test cases 10X0103 and 10X0104. For full details of all changes, please refer to our ReleaseNotes.md.

If you encounter any issues with the test suite, please raise an issue on GitHub to inform us.

Resources:

Test suite repository: https://github.com/gematik/TI-Messenger-Testsuite

Full release notes: https://github.com/gematik/TI-Messenger-Testsuite/blob/main/ReleaseNotes.md

Test driver API: https://github.com/gematik/TI-Messenger-Testsuite/blob/main/src/main/resources/api/TiMessengerTestTreiber.yaml

The digital communication landscape in healthcare faces a significant challenge: How can large organizations, such as hospitals or corporate groups, establish a secure, efficient, and unified communication infrastructure without introducing technical complexity or incurring excessive costs? The answer lies in the possibility of operating a corporate TI-Messenger service. This solution not only offers economic advantages but also enhances user experience and builds trust in communication via the TI-Messenger.

The Challenge: Fragmented Infrastructure and Limited Flexibility

Currently, the deployment of the TI-Messenger relies on the use of SMC-B cards, which authenticate the identity of individual facilities. Each facility must operate a separate TI-Messenger service, which creates significant administrative overhead for large organizations with multiple facilities. This fragmented infrastructure complicates the user experience, increases operational costs, and hinders the adoption of modern communication solutions, such as a unified corporate campus chat.

Another drawback of this structure is the lack of transparency: Users often struggle to identify chat partners and associate them with specific organizations, as each facility operates under its own unique Matrix domain. This can lead to uncertainty in communication and negatively impact the acceptance of the TI-Messenger.

The Solution: A Centralized Corporate TI-Messenger Service

The possibility of operating a corporate TI-Messenger service offers an elegant and practical solution. This approach creates a unified trust space that spans all facilities within a corporate group. The registration and management of this service are handled via a central SMC-B card issued to an overarching organizational unit within the corporation. This structure enables the use of a single, unified Matrix domain for the entire corporate group, delivering a range of benefits.

Benefits of a Corporate TI-Messenger Service

1. Increased Efficiency: Consolidating the infrastructure reduces operational costs and administrative burdens significantly. Instead of managing multiple services for each facility, only one centralized service is required.

2. Improved User Experience: A unified Matrix domain simplifies the identification of chat partners and fosters trust in communication. External users can easily recognize whether a chat partner belongs to a renowned organization, such as Charité.

3. Enabling Campus Chats: A centralized corporate service makes it possible to implement a campus chat, optimizing internal communication across the organization. Employees can communicate seamlessly regardless of their specific facility or unit.

4. Simplified Integration: A centralized structure facilitates the integration of the TI-Messenger into existing IT systems and applications within the corporate group, boosting the efficiency of the entire IT infrastructure.

5. Consistency and Trust: A consistent user experience and clear association of users with a corporate group improve both the acceptance and trust in the TI-Messenger.

How to Get a Corporate TI-Messenger Service

Organizations interested in operating a corporate TI-Messenger service can follow a straightforward process to get started. Here’s how it works:

1. Express Your Interest During Card Application: When applying for an SMC-B card through gematik, indicate your intent to operate a corporate TI-Messenger service. This ensures your request is processed with the necessary considerations.

2. Submit the Required Documentation: Provide the required documentation that outlines the corporate structure and demonstrates your organization’s eligibility. This includes proof of the organizational hierarchy and the ability to manage user accounts across the corporate group.

3. Choose Between Existing or New Cards: Depending on your organization’s current setup, you can either use an existing SMC-B card for registration or order a new card specifically for this purpose. If you choose to reuse an existing card, ensure it meets the necessary requirements for the corporate service.

4. Registration and Setup: Once the card is issued or approved, it can be used to register the corporate TI-Messenger service. This includes setting up the unified Matrix domain and ensuring compliance with all relevant guidelines.

5. Ongoing Management: As part of the registration process, the organization is required to maintain up-to-date corporate structure information and ensure that user accounts are only issued within the corporate group. This guarantees the integrity of the trust space.

By following these steps, organizations can streamline their communication infrastructure and unlock the full potential of a corporate TI-Messenger service.

Conclusion: A Forward-Thinking Solution for Healthcare

The possibility of operating a corporate TI-Messenger service is more than just a technical adjustment—it is a step toward a modern, efficient, and user-friendly communication infrastructure in healthcare. Large organizations, such as hospitals and healthcare networks, stand to benefit significantly from this approach, as it enhances the economic viability and practical usability of the TI-Messenger. By adopting this solution, the TI-Messenger becomes a compelling alternative to existing platforms, driving digital transformation in the healthcare sector.

A new minor version of the test suite has been released. This version includes numerous automated test cases and some updates to the test driver API. For a detailed list of changes, please refer to the ReleaseNotes in the GitHub repository.
Additionally, the patch version improves the cleanup behavior, which is now mandatory to adhere to. This enhancement will increase stability during interoperability tests.
If you encounter any issues with the test suite, please create an issue on GitHub to inform us.

Resources:

Test Suite Repository: https://github.com/gematik/TI-Messenger-Testsuite

Full Release Notes: https://github.com/gematik/TI-Messenger-Testsuite/blob/main/ReleaseNotes.md

Test Driver API: https://github.com/gematik/TI-Messenger-Testsuite/blob/main/src/main/resources/api/TiMessengerTestTreiber.yaml

With our new TI-Messenger feature concept, we are setting a secure standard for automated communication in healthcare. Our goal is to reduce and simplify communication efforts. For instance, incoming TI-Messenger requests from service providers and health insurance companies can be automatically answered by a bot, while personalized reminders can be sent to patients. All of this is achieved while maintaining the highest level of security.

Discover more in our feature concept released today and share your thoughts with us!

Link: https://gemspec.gematik.de/prereleases/Draft_gemF_TI-M_Automatisierung/

We are pleased to announce the release of two updates:

TI-Messenger251-2 for TI-M Pro 1.0.2 and TI-Messenger251-1 for TI-M ePA 1.1.2.

Both releases focus on essential technical adjustments and clarifications without the need for a commentary procedure.

Common Features in Both Releases:

• Urgent changes in data transmission were necessary for privacy reasons.
• Several profiles have been deprecated due to changes in the Afo budget, affecting all product versions:
  • Provider Type
  • Product Type Client
  • Product Type FD
• Removal of the obligation to deliver operational data and ad hoc reports.
• Adjustment of events for federated and cross-sector communication.
• Modification of the requirements for matrix modules.
• Revision of the test concept examination procedure.

TI-Messenger25_1-1 Specific Adjustments for TI-M ePA 1.1.2:

• Service: Adjustment of the examination procedure for ID_TOKEN deletion.
• Service: Adjustment of matrix events when removing users from orphaned spaces.
• Service: Addition of the "Entity Statement Publish" requirement.

TI-Messenger25_1-2 Specific Adjustments for TI-M Pro 1.0.2:

• Provider: Introduction of a 24/7 contact point.
• Client: Tracking adjustments.
• Service: Adjustment of the TI-Messenger information interface from "MUST" to "SHOULD".

These updates aim to enhance the functionality and privacy of our systems, ensuring compliance with the latest standards and requirements.

You can find the releases here:

https://gemspec.gematik.de/releases/TI-Messenger_25_1-1/

https://gemspec.gematik.de/releases/TI-Messenger_25_1-2/