Microservice architecture for ePA connection<\/h2><\/h2><\/div>The integration of digital health applications (DiGA) into the electronic patient record (ePA) places high demands on interoperability, data protection and security.
\nSince January 1, 2024, Section 6a of the Digital Health Applications Ordinance (DiGAV) also stipulates a mandatory connection to the ePA.
\nThe associated adjustments and enhancements to the DiGA front and back ends and the connection of the DiGA to the telematics infrastructure (TI) are far-reaching:<\/p>\n<\/div>
- <\/i><\/span>\n\n
\nINTEROPERABILITY<\/strong><\/p>\n<\/header>\n Implementation of the ePA interface in accordance with Annex 2 Requirement 5 DiGAV <\/div>\n<\/div>\n<\/div><\/li>- <\/i><\/span>\n\n
\n\nDATA PROTECTION<\/strong><\/p>\n<\/header>\n Integration of the health ID in accordance with Annex 1 Requirement 15a DiGAV <\/div>\n<\/header>\n<\/div>\n<\/div><\/li>- <\/i><\/span>\n\n\n
\n\nMIO<\/b><\/p>\n<\/header>\n Creation and validation of medical information objects (MIO) for export to the ePA <\/div>\n<\/header>\n<\/div>\n<\/div>\n<\/div><\/li><\/ul>When implementing these points, all the requirements of Gematik as the leading player must also be taken into account.
\nWith the MedicalOne Connect platform solution, the aim was to create an all-in-one solution by splitting the core functionalities due to the various requirements.<\/p>\n<\/div><\/div><\/div>
The integration of digital health applications (DiGA) into the electronic patient record (ePA) places high demands on interoperability, data protection and security.
\nSince January 1, 2024, Section 6a of the Digital Health Applications Ordinance (DiGAV) also stipulates a mandatory connection to the ePA.
\nThe associated adjustments and enhancements to the DiGA front and back ends and the connection of the DiGA to the telematics infrastructure (TI) are far-reaching:<\/p>\n<\/div>
- <\/i><\/span>\n\n
\n INTEROPERABILITY<\/strong><\/p>\n<\/header>\n
Implementation of the ePA interface in accordance with Annex 2 Requirement 5 DiGAV <\/div>\n<\/div>\n<\/div><\/li>- <\/i><\/span>
\n\n\n \n DATA PROTECTION<\/strong><\/p>\n<\/header>\n
Integration of the health ID in accordance with Annex 1 Requirement 15a DiGAV <\/div>\n<\/header>\n<\/div>\n<\/div><\/li>- <\/i><\/span>
\n\n\n\n \n MIO<\/b><\/p>\n<\/header>\n
Creation and validation of medical information objects (MIO) for export to the ePA <\/div>\n<\/header>\n<\/div>\n<\/div>\n<\/div><\/li><\/ul>When implementing these points, all the requirements of Gematik as the leading player must also be taken into account.
\nWith the MedicalOne Connect platform solution, the aim was to create an all-in-one solution by splitting the core functionalities due to the various requirements.<\/p>\n<\/div><\/div><\/div> - <\/i><\/span>
![\"BAYOOMED](\"https:\/\/www.bayoomed.com\/wp-content\/uploads\/sites\/4\/2024\/07\/BAYOOMED-MedicalOne-Connect-Microservices-DiGA-and-ePA-1.png\" "\\"BAYOOMED")
<\/span><\/div><\/div><\/div>