With one of our customers from Germany, our team was challenged with designing, developing, and providing an application called VOS<\/strong> (Verordnungssoftware<\/strong><\/em>) whose primary goal is to deal with e-prescriptions as well as with the treatment plan for patients. Once you get to know how e-prescription works in Germany<\/a>, you instantly see how many things have to be tested:<\/p>\n\n\n\n When it comes to the e-prescription system in Germany, Gematik enables three separated environments: TITUS<\/strong> (test environment), RU<\/strong> (Referenzumgebung<\/strong><\/em>, reference environment), and PU<\/strong> (Produktionsumgebung<\/strong><\/em>, production environment). From the testing perspective, TITUS<\/strong> and RU<\/strong> look very interesting.<\/p>\n\n\n\n In order to access the test environment, you can buy a license from Gematik<\/strong> for a Titus<\/a><\/strong> service, which brings you accessibility to all of the needed components including:<\/p>\n\n\n\n On the other hand, access to the reference environment<\/a> connection is established through third-party RU<\/strong> access providers. The architecture of the RU<\/strong> environment is similar to TITUS<\/strong>:<\/p>\n\n\n\n Despite PVS<\/strong> – VOS<\/strong> communication flow, seems like all of the mentioned points can be tested via TITUS<\/strong> service. So why do we have to even bother to use the RU environment? The devil is in the details and the fact that in TITUS<\/strong> service, some of the operations with connector (PIN prompts, signing documents using HBA cards, and so on) are performed in a simulated manner, meaning you can’t test your application behavior in some cases (e.g. wrong PIN entered, timeout occurred during signature). Also, some of the connector capabilities are entirely disabled (comfort signature management, changing a PIN). Finally, connectors and card terminals used on RU<\/strong> (Referenzumgebung<\/strong>) are the same which are used in the PU<\/strong> (Produktionsumgebung<\/strong>) environment by practitioners in their workplaces. Therefore, using the RU<\/strong> (Referenzumgebung<\/strong>) environment is the only way to ensure, that your application is likely to work in the production environment as well.<\/p>\n\n\n\n Utilizing reference environment capabilities in the testing process improves your application stability in terms of being consistent with the production environment. However, it also brings some problems, that have to be solved:<\/p>\n\n\n\n Our RU<\/strong> (Referenzumgebung<\/strong>) enabler is not supporting multiple simultaneous VPN connections so we have to share the same VPN connection across all of the devices, CI\/CD runners, and deployment nodes. <\/p>\n\n\n\n We solved the first problem by establishing a Multi-Hop VPN connection. Therefore, every machine connected to our Intranet network (e.g. developer’s computer, CI\/CD runner<\/a>, card terminal) is also connected to the RU<\/strong> (Referenzumgebung<\/strong>) environment out of the box. That’s really cool but the second problem remains. How team developers can perform PIN verification when they are not actually having physical access to the terminal? Furthermore, what about PIN verification in the terminal in the automated CI\/CD test pipeline<\/a>? Fortunately, the card terminal device gives the opportunity to verify the PIN using the terminal\u2019s Remote API interface. Thus, we decided to develop an extra Intranet component responsible for hooking to the terminal API, listening for PIN requests, and performing PIN verification whenever it is needed. Obviously, this component is fully configurable and can be temporarily disabled if you want to perform PIN verification and test your application manually.<\/p>\n\n\n\n Built infrastructure is used by many developers at NubiSoft on a daily basis, helping them and our customers to build fast-growing and rapidly-changing software with desired reliability and stability.<\/p>\n\n\n\n In conclusion, integrating Gematik TI-RU Environment in a CI\/CD pipeline fits to our innovative approach to healthcare application development. It empowers developers and healthcare organizations we work with to streamline their software development processes, adhere to regulatory requirements, and deliver patient-centric software solutions more efficiently.<\/p>\n","protected":false},"excerpt":{"rendered":" In this blog post, we explore integration of Gematik TI-RU Environment in a CI\/CD pipeline and its profound implications for healthcare application development. We delve into the key concepts behind CI\/CD pipelines, the significance of Gematik TI-RU Environment in the healthcare domain, and the steps involved in seamlessly automating the entire development and deployment process. […]<\/p>\n","protected":false},"author":7,"featured_media":1251,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_case_study_excerpt":"","footnotes":""},"categories":[55,221],"tags":[48,47,334,254],"class_list":["post-1196","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops","category-healthcare","tag-cd","tag-ci","tag-e-prescription","tag-gematik"],"_links":{"self":[{"href":"https:\/\/nubisoft.io\/blog\/wp-json\/wp\/v2\/posts\/1196","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nubisoft.io\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nubisoft.io\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nubisoft.io\/blog\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/nubisoft.io\/blog\/wp-json\/wp\/v2\/comments?post=1196"}],"version-history":[{"count":24,"href":"https:\/\/nubisoft.io\/blog\/wp-json\/wp\/v2\/posts\/1196\/revisions"}],"predecessor-version":[{"id":4710,"href":"https:\/\/nubisoft.io\/blog\/wp-json\/wp\/v2\/posts\/1196\/revisions\/4710"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nubisoft.io\/blog\/wp-json\/wp\/v2\/media\/1251"}],"wp:attachment":[{"href":"https:\/\/nubisoft.io\/blog\/wp-json\/wp\/v2\/media?parent=1196"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nubisoft.io\/blog\/wp-json\/wp\/v2\/categories?post=1196"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nubisoft.io\/blog\/wp-json\/wp\/v2\/tags?post=1196"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
Gematik TITUS vs RU environment<\/h2>\n\n\n\n
\n
\n
How to use the Gematik TI Referenzumgebung<\/strong> environment in CI\/CD pipeline?<\/h2>\n\n\n\n
\n
![\"CI\/CD](\"https:\/\/nubisoft.io\/blog\/wp-content\/uploads\/2023\/05\/Frame-2-1-1024x625.png\")
<\/figure>\n<\/figure>\n\n\n\n![\"Automated](\"https:\/\/nubisoft.io\/blog\/wp-content\/uploads\/2023\/05\/Frame-1-1024x625.png\")
<\/figure>\n\n\n\nSummary<\/h2>\n\n\n\n