Before developing this application for OVSZ (Hungarian National Blood Transfusion Service), donation centers had to submit lab results to the central database on paper.
OVSZ stored all these results, but never provided a standard protocol for it to be accessed.
Because two-way data synchronization didn't exist, donation centers had no knowledge if a donor has already been marked as ineligible to give blood by another donation center.
Donation centers had no way to check if a donor has been previously marked as ineligible to give blood at another donation center.Solution
Working together with the database architects at OVSZ, we defined a contract which describes the way information from the donation centers is transmitted and processed.
After this, we implemented a data transport method which automatically submits donor information to the central database, whenever a donation center uploads lab result to the application.
Donation centers previously had to submit lab results by paper, which was then manually uploaded to the central database.
This process was tiresome for both the donation centers and OVSZ, and also error-prone because of the human factor.Solution
Defining the standard protocol of how a submission should look like, allowed us to automatically update donor information whenever a donation center finished the lab results.
The first thing we had to learn during this project, is how to handle sensitive healthcare data.
Though Hungarian laws regarding this issue are not as exact, studying the US HIPAA standards and their different implementations helped us build a robust and secure solution which protects donor information.
On most projects we work on, we're used to having complete control of the database, or at the very least have a standard way of accessing it through an API.
In this case we had neither, so we had to work together with the database team at OVSZ to design a system which would allow us to access and update sensitive data through multiple firewalls and intermediary security gates.