registered hospitals on Medlinx
raised in seed
"We are delighted to have such a great UX and UI thought process in our team. Overall, the app looks fantastic! Please keep up the great work."
Dr. Ali Esmail from Koronis Health, Canada was concerned that EMR solutions were not making patient care any better in hospitals. In fact, these were largely built for legal documentation & billing. He wanted to better equip physicians with patient data and unchain care teams from the burden of documentation and vague communication channels so to achieve better patient care.
How can we replace the old pen-and-paper methods of clinical management and sync teams on a smart app?
In order to find solid answers to this problem, we had to think from the point of view of Canadian users. We had to build a collaboration platform that would combine various user demographics of hospital staff, physicians, care teams and patients yet would NOT interfere into each other’s space. We did surveys, market research, competitor analysis along with speaking with Dr Esmail who had a clear product strategy. This process helped us drafting user stories important for MVP development. These profiles furthered our design strategy, profiles & personas, scenarios, task flows and information architecture.
Most developers understand boxy EMR apps, we don’t want those.
This will be a complete solution not just an application.
It’s hard to make people understand that collaborative platforms can be fun.
A social networking bent to the whole application can make it easy and fun to use.
Developers may end up creating a complicated software that only doctors understand.
Let’s create a clinical collaboration through web and mobile applications that sync.
We need an easily customizable solution as per hospital requirements and legal compliances.
The application will be compliant of HIPAA and HL-7.
Patient feeds with easy sharing of information, comments, photos, handover notes, and tagging facility. This information is sharable only within specific care teams with restriction filters.
Create discharge plans
Care teams can create discharge plans and a list of active issues. When patients leave the hospital, they can collaborate with care team members in implementing the discharge plan. This results in less number of readmissions in hospitals.
HL7 integration with EMRs
Medlinx app is integrated with All Scripts EMR. Lab results and vital feeds from EMR are available in the application and can be securely shared with physicians.
Dynamic team management
Users can create and manage teams dynamically. They can create, assign, track and manage tasks in real time. In addition, the secure one-to-one and group chats with other clinicians allow them to talk off the record.
I want my chain of hospitals/clinics to sync effortlessly, comply with legal norms and ensure excellent patient care.
I want to have an easy coordination with my doctors and care team even after I am discharged from the hospital.
I want to know exactly what’s happening where in the hospital for better administration and management.
I want to care for my patients personally remotely and focus less on tracking of dates, appointment, coordination etc.
I want to have easy access to most relevant developments in the departments in the entire chain of hospitals or within the care teams.
I want to really make my patients feel comfortable and informed for their speedy recovery and post recovery care.
Team Vinfotech soon figured out that we were building not only a collaborative platform but a collaborative community that would be founded on trust and mutual sharing of information. We ensured that we adhered to security & privacy healthcare policies in U.S and Canada including HIPAA & PIPEDA while building the web, Android and iPhone applications.
During our market research we validated Dr Esmail’s concern that EMR solutions were only addressing legal documentation & billing and failing to improve patient care. Outdated communications cost hospitals $5.1 billion per year while more than 70,000 deaths per year were due to poor communications. It was time for a major disruption through a revolutionary software.
Engaging with Users
Since our user demographic was in Canada, we conducted various surveys collecting views of users in text and videos. We interacted with Canadian doctors, surgeons, resident doctors, medical students, support team, patients, relatives, coordinators and the likes. We sampled the profiles and shortlisted the ones that would help make the app robust.
Business Assessment Document
We prepared a comprehensive document detailing the various needs of the parties involved that need to be collaborated through the application.
Team Vinfotech conducted a workshop with Dr Esmail who shared with us the challenges of a physician in managing several patients and their data. We proposed to build various scenarios that helped him to see the design angle in building the application. We made sure that the app was HIPAA & PIPEDA compliant apart from having EMR integration and HL7 feeds.
Our ultimate users were care givers and care receivers in the medical domain. We presented eight wireframes and left Dr Esmail alone to ponder, mix and match and choose functionality that he felt he needed most as a physician.
User Interface Design
Our user demographic spanned across critical care staff, doctors and surgeons, care team staff like nurses, ward boys, physiotherapists; hospital admin staff, patients and their family. We planned a design that would show relevant information to the people concerned. This means that only login authorized member could view and interact with the data.
Our working prototype accommodated dealing with real life situations from emergency to day-to-day appointment management, general admin duties, flow of relevant information, patient’s treatment within the hospital, discharge plans and post recovery care and so on.
Once the client approved the design, our developers got busy with building a secure web and mobile collaboration platform that would allow care teams and physicians to access the information they needed quickly and easily. Medlinx was built to achieve interoperability with different HIT systems and would use state-of-the-art testing strategies and collaboration with third parties.
We involved users once again for validating our design, UX as well as the efficiency of the application. We accommodated their feedback points first in the beta and then in the final version.