HIPPA and HITECH are huge concerns for anyone interacting with Medical Records, and traditionally, this has made it hard for Doctors to efficiently share medical records between clinicians from different offices. Security is paramount when interacting with such records, and MedChart Sync was designed from the ground up to address that concern. We started by separating the PII (Personally Identifiable Information) from the records being sent, and then using internal IDs to point back to records in Clinician Management Systems like Dr. Chrono. Then I designed a system to encrypt files for the reciever, and then keep them encrypted until the user enters their password in our web interface.
When our clients came to us with their needs, we had to step back and make sure that we understood all of the laws regarding Medical Data Transfer. We didn't just want to meet the minimum requirements, we wanted to exceed them.
We had a tight budget and a long list of requirements when the project started. We turned to a third-party system called Express App Framework or XAF to meet our timelines. We designed our Clinician Backend in just a few hours using this tool, and then exposed an API for our frontend. We also relied on Azure functions to handle executing queued tasks in the system.
The MVP of MedChart Sync was launched on the Azure Cloud Platform. It decouple Identifying information from the medical data being transmitted, allowing for anonymous data to be related back to patients on each side. It stored notes in an encrypted format that was only decrypted in the browser using the recipients credentials as the key. It use TLS to ensure that files moving across networks where encrypted end-to-end.
I hope you will consider me when you're looking for a software engineer with the experience to help your team become cloud-native. With my years of practical, real-life experience building...
