As is good practice in service design, Marco spent several days with doctors in their hospitals and clinics. He was surprised by how little had changed in the workflow of doctors since his time in practicing medicine. Pens were exchanged for monitors, but the workflow had largely remained the same. Many of the doctors Marco interviewed were (slightly) frustrated by the ratio of helping patients to time spent on administrative tasks. Many felt like robots filling the fields of their Electronic Health Records (EHR).
These talks were also a great opportunity for Martijn to experience the systems and processes that left many medical professionals feeling obstructed to provide care to patients as efficiently as they would like to. Martijn started observing and measuring the duration of the out clinic consultations to see how much time was effectively spent on providing care to the patient. He noted that from the 8 minutes a doctor and patient sat across each other during a short consult, 6 minutes were spent on exchanging information that could just as well have been exchanged in preparation for the consultation.
Several physicians and nurses laid bare the problem best; many intake consults have the same structure and outcome: the doctor asks mostly general questions that could just as well have been filled out by a patient on a (digital) form before the consultation, and patients often feel disappointed by the lack of time spent discussing their most prudent health-related issues. This is how the first Open HealthHub app came to be. The Improve Mobile app, soon-to-be part of the Open HealthHub, was launched in April 2016. The Improve Mobile App was the first end-to-end encrypted mobile app for PROMs (patient reported outcome measures) in Europe, with RadboudUMC as launching customer.
The first application the Improve Mobile App was built on the Open HealthHub in 2016; The second application was launched a year after the app was launched and offered a suite for medical professionals to create their own PROMs and information material, a library with at the time 100 validated PROMs, and a smart scheduling module.
Feedback from a hospital that had helped us develop and test the Open HealthHub provided input for the next point of focus: interoperability. ‘’The app and hub are saving us time, but would be truly great if the data could automatically be added to the patients’ electronic healthcare record (EHR) file’’ the doctor said. We agreed this was what the hub needed to become truly interoperable. Martijn’s expertise in API’s and interoperability would prove to be invaluable to realize this. It was also the start of the first real world test that would give us insight into how interoperable the new hub would be in the infrastructure of a large hospital.
Making highly secured and largely unstructured patient data flow from one system (and data format) to another was never going to be an easy task. Luckily, the foundation was already there. When trying to break vendor lock-in, two ingredients are key: working with international standards for medical data such as FHIR instead of creating a unique data standard for your own application, and open APIs. This combination is the basis for true interoperability that allows the user to integrate the solution much more easily than traditional systems, allows switching to alternative solutions, and benefits from a far larger community of technical experts.
Based on feedback from the successful launch at the hospital that helped us launch the Open HealthHub and from the customers that have come since, we are currently creating documentation so we can publicly publish an open API-hub for FHIR APIs that allow any developer to integrate our Open HealthHub in their digital infrastructure.