Creating a new EHR for improving medical therapies!
In this blog we will give you a short overview about our new EHR (electronic health record) “TBase” on which we have been working for almost a year.
Here are the reasons, why we decided to use SAPUI5
The goal of this project
We have developed a prototype app that is able to meet the medical documentation requirements of our various in-house ambulances (e.g., cardiology, nephrology, and neurology). Our electronic health record “TBase” simplifies therapy documentation in these departments, for example, by replacing paper forms and by providing a modern user interface. The new EHR will also benefit the quality of care at our hospital, because therapies can be systematically reviewed and then adapted for individual patients.
We designed the app with current data protection standards in mind. For example, we need to ensure that viewing patient data is restricted to the specific doctors treating the patient – and that data access is based on patient consent.
Here are some impressions of our app and potential use cases:
In the example below, we automatically generate a diagnosis-report based on a template that can be freely configured. We use a combination of both structured and unstructured data entry, leaving the choice open to the user.
In the example below, we register digital reconstructions of deep brain stimulation electrodes as used in the treatment of Parkinson’s disease.
In the example below, we are automatically generating medical reports for our patients, which requires significantly less time for our medical staff.
Furthermore, when the time is right, we hopefully can support our medical staff by finding and giving the best therapy everywhere.
- Frontend: SAPUI5
- Backend: Hana XSA, Runtime Node.js
- Design: Keep in mind that our requirement was more functional and less fancy. 🙂
- Tabs: Depending on the authorization, the user will only see corresponding tabs and ui elements and not all the tabs and ui-elements that you can see in this video clip.
Now enjoy the beauty of our app. In this video, you can take a look at some of the pages of the app. Note that all entries are demo data without relation to real persons.
Finally, we are very glad to have found a new web development platform (SAP HANA XSA) which suits perfectly in our system landscape and we’ll be able to solve the more complex requirements of our users in the future.
Thank you all for this great community!
A really special thank you is due to my colleagues Dipl.-Inf. Danilo Schmidt (Charité – Universitätsmedizin Berlin), Prof. Dr. Klemens Budde (Charité – Universitätsmedizin Berlin, Med. Klinik m. Schw. Nephrologie und Intensivmedizin) and our fantastic team which were helping us all the time.
I have tried this trick for doing the therapy but the downloading of the software just failed. I have also checked for the solution on the Google Support and really got my solution. Anyone can check for the solution over there.
this is a really nice blog explaining in detail. I really like the blog because you built the story, gave the problem and came with a very nice solution. I am glad the landscape worked great for you and you were able to showcase this. I wonder if this solution is only applicable in germany, because i can see this solution working great in the USA - i dont know all the restrictions/laws of the medical field but i can see this as a use case.
thank you for sharing.
Your post makes for very interesting reading for a SAP HANA XSA use case. Thanks for sharing your experiences as there are not many blogs on this topic. I look forward to seeing more.
I have the following questions:
1. You've mentioned that "we are very glad to have found a new web development platform (SAP HANA XSA) which suits perfectly in our system landscape". Can you elaborate on how SAP HANA XSA was well suited to your system landscape?
2. As you are probably aware through your experience developing the EHR app, SAP HANA XSA is based on a microservice architecture. I'd be interested to know how you applied this paradigm in the development of your application?
3. You've mentioned "Depending on the authorization, the user will only see corresponding tabs and ui elements and not all the tabs and ui-elements". Did you use the Scopes concept to achieve this and if so what are your recommendations/takeaways from using scopes to control access to functional features of an XSA application?