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/

We are pleased to announce the beta release of the TI-M Test Suite Version 2. This release marks an important milestone towards making TI-M Pro and TI-M ePA available to end users.

What's included?

• New test cases specifically designed for TI-M Pro and TI-M ePA. Please read this Documentation Testsuite V2.

• Comprehensive release notes detailing the updates.

Resources:

• Test Suite Repository: GitHub Repository

• Full Release Notes: Release Notes

• Test Driver API: API Documentation

Feedback and Support:

If you encounter any issues or have suggestions, please create an issue directly in our GitHub repository.

Your feedback helps us continuously improve the test suite, supporting our goal of delivering secure and reliable healthcare communication solutions.

Reference Implementation:

The update for the reference implementation is scheduled for next Tuesday (11.03).

We wish you all successful testing!

Please find attached an example test run with the new release of the reference implementation. The tests can be started with the following command:

mvn clean verify -Pdont-break-preparation -DpoolGroupString="poolGroupString" \

-Dcucumber.filter.tags="@Ctl:BP or @Ctl:SchnittstellenDaten \

or @File:FeatureFile_00_01_V2_Basis \

or @File:FeatureFile_04_01_V2_Basis \

or @File:FeatureFile_04_04_V2_Basis \

or @File:FeatureFile_06_01_V2_Basis \

or @File:FeatureFile_06_03_V2_Basis \

or @File:FeatureFile_06_04_V2_Basis" | tee logfilename.txt

Before you start, you have to mark the following test cases with @WIP because these tests are still not implemented:

@TCID:TIMV2BASISAF040114

@TCID:TIMV2BASISAF050120

@TCID:TIMV2BASISAF060112

After that, you will execute the first 79 scenarios (158 test cases). Please feel free to execute the tests with your own test reference implementation, which you can order via the Gematik ITSM Portal.

NOTE: Our experience shows that early testing against the reference implementation is the single most important factor for a successful product approval. So, as the saying goes: the best time to plant a tree was 20 years ago; the best time to start your TI-M testing is today.

Example test run:

2025-02-25_07_28_25.zip

We’re excited to announce the latest update to the TI-M Pro Light reference implementation, which brings several enhancements designed to improve your testing experience.

Key Updates

Matrix 1.11 Integration

This release includes an update to Matrix 1.11, allowing new test cases for both TI-M Pro and TI-M ePA. This is a significant step forward in ensuring the quality of your upcoming releases.

New Test Driver

We’re also introducing a new test driver that comes with its own clients. This means you can use the reference implementation without needing your own clients, making it easier to get TI-M ePA modules approved within the ePA FdV approval process. Plus- no additional TI-M Pro client required. In addition this will cut your test runtime to just a little over 20% of what it currently is!

HBA Card Upload

To take full advantage of these new features, you’ll need to upload HBA (Health Professional Card) cards. You can find detailed instructions in the user documentation here: User Documentation.

Ordering HBA Test Cards

You can order HBA test cards through the Fachportal. For more details, check out this link: Order HBA Test Cards.

Additional Resources

If you’re interested, the current version of the test suite is available here: Current Test Suite, along with the latest test cases: Current Test Cases.
We’re looking forward to the official first full (beta) release on GitHub by March 10th, which will include the test suite and test cases. We’ll keep you posted as the release date approaches.
Thank you for your continued support! We can’t wait to see how TI-M Pro and TI-M ePA will enhance communication in German healthcare!

Germany's healthcare system is on the brink of a significant digital upgrade with the introduction of the TI-Messenger, a key feature in the upcoming electronic patient record (ePA) releases. This innovation aims to streamline communication between healthcare providers and patients, enhancing the overall efficiency and accessibility of healthcare services.
The ePA Release 3.0.5, scheduled for July 2025, will introduce the TI-M ePA, specifically designed to facilitate communication between healthcare providers and insured patients. This development promises to improve interaction and information exchange, making healthcare services more responsive and patient-centered.
Looking ahead to early 2026, the ePA will expand the use of TI-M Pro, enabling insurance providers to integrate this tool for direct communication with insured patients. This feature will empower patients by providing them with a direct line to manage their healthcare coverage and related inquiries efficiently.
These advancements in the ePA system mark a significant step forward in digital healthcare, fostering better connectivity and engagement between all stakeholders involved.

We are happy to Relase the next version of out Tescases für TI-M Pro and we hope they will help you on your jurny to a scusessfull lunche. Plese be remainded that this is a pre release and will be an updatet version in a few weeks. In addion some of the Test cases can only be used for your internal testing, beouse our referenzimplementation needs to be updated bevor it supports all use casese.

In addion as a preparion for you TI-M ePA releases we provide you with the test cases for our Look & Feel workshon and the manuel test.

We wish you all a good weekend.

Test Cases without HBA functionality (Only for TI-M Pro for Health Insurance Providers)

Testsuite Testfälle (Basis&Pro) - Arbeitsstand - ProKrankenkasse (ohne HBA Funktionalität).zip

Test Cases with HBA functionality

Testsuite Testfälle (Basis&Pro) - Arbeitsstand - Pro.zip

We are excited to announce that we plan to refactor the Deletion Strategy for TI Messenger. The current concept for deleting rooms and content in the TI Messenger has been regularly questioned and criticized in feedback workshops and support requests. To address these concerns, we have developed a proposal for a clear, meaningful, and well-reasoned deletion strategy based on user stories.

This proposal is now available on GitHub.

We kindly ask for your feedback on this proposal to help us provide a robust solution in the specification. Your insights and suggestions will be invaluable in ensuring the effectiveness and efficiency of the new implementation.

Please take a moment to review the concept and share your thoughts. 

Thank you for your collaboration!

Link:
https://github.com/gematik/api-ti-messenger/pull/291

To assist you in obtaining approval for the TI-M Pro, we are publishing today the lists of manual tests and the tests for the Look and Feel Workshop. We hope these resources will help you prepare effectively for the approval process.

Please note that these lists are only for the TI-M Pro approvals and are not final. We may adjust them if necessary, and any changes will also be published here. You may wish to check back when you are nearing the start of your approval process to stay updated on any modifications.

We are committed to supporting you throughout this process and wish you success in your preparations.

Welcome to the new year! We're kicking things off with a fresh patch for our test suite. This update tidies up a few areas, including correcting a typo in the profile name 'dont-break-preparation.' We've also streamlined the build configuration and updated our dependencies to keep everything running smoothly.
As always, if you run into any issues, we’d love to hear from you. Please let us know by creating an issue on GitHub. Your feedback helps us make continuous improvements. Here's to a fantastic year ahead!

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