Patient Treatment Application is designed to be used by hospital patients. It is expected that the application will reduce the rate of readmissions by providing assistance during all treatment phases.
Before treatment starts users get all relevant information on the therapy program from app educational resources (stored in Azure Blob Storage). The app helps to keep users’ health records including a record of their general condition, vitals (blood pressure, heart rate, etc.), laboratory test results, and an activity tracker (sleeping, walking, sport, etc.) which can be viewed as charts to track changes over time. These daily data are stored in a Health Journal, each page of which represents a particular day. Daily checklists and appointments help users to monitor timely medication and procedures. Each user’s health records are stored safely in a specific format regulated by a Fast Healthcare Interoperability Resources standard.
Also maybe interesting:
What Was Done
The system consists of an Azure web application and a mobile app client (Android, iOS and UWP supported). Data stored locally on mobile devices are encrypted as per HIPAA requirements. The system uses and supports FHIR - an international standard for storing and exchanging data between medical facilities.
The application features the following high-level modules:
- User management (including federated login, multi-factor authentication, phone passcode; managing user profiles);
- Educational resources (Azure access and sync with local database);
- Daily and medication checklists;
- Secure notifications;
- Calendar and appointments;
- Health History;
- Secure text/video chat (future releases)
A cross-platform solution has been created on top of Xamarin. The database is hosted in Azure and Azure blob storage is used for storing big files. Admin features are implemented in an ASP .NET MVC web interface.
The application is supposed to be used in different health care organizations, so for this reason the team set up separate B2C Azure Active Directory instances for the patients and hospital staff. Azure AD instances are configurable in terms of using Federated login features which would allow user authentication using their social networks (such as Facebook, Twitter, etc.) profiles. Mobile app UI is metadata-driven so the users are able to customize the information which goes through the application.
Before treatment starts it’s essential that the patient gets all relevant information on the treatment program and procedure. For this reason, there is a required education feature. The device pulls up necessary information from Azure blob storage. It is pulled either during app initialization or synchronized manually or by a user-configured schedule. The resources, which may be HTML5 articles, or presentations or videos, are tracked to be viewed in full so that overall progress can be tracked and assessed. The resources can also be marked as optional, so that the user only downloads them, if interested. All resources are flexibly categorized using a tree-based structure. Resources assignment is on the user level, UI for this is organized in a web interface.
Each user’s health records are stored in a specific format regulated by an FHIR (Fast Healthcare Interoperability Resources) standard. All healthcare-related records should be compliant with this standard. The team created another layer of users – FHIR users, which would then be linked to the user data stored in the Azure SQL database.
Health records include:
- Basic questionnaire (overall feeling, general notes);
- Vitals (blood pressure, heart rate, blood sugar);
- Medication list;
- Laboratory test results;
- Activity tracker (walking, running, sleeping, sports, etc.)
These data are stored in a Health journal page, each page representing a particular day. Vitals and lab test results can be viewed in a diagram to assess the changes over time.