Lean in Complex Healthcare Systems

 

Hey,
Our team received several requests to work on caregiver apps since last quarter of 2016. We reviewed a list of doctor, health, medical apps, and business requirements. So it was easy to sort out a list of tasks that should be included in any ultimate caregiver systems.

Here is how it works:

Aim
Create a system for Administrator, Staff, Patients, and Family members of the patient.

Requirements
Requirements for Admin:
Possibility to:

  • create profiles for caregivers;
  • create profiles for patients;
  • create a plan for the staff;
  • sort the best staff members for Patient based on geolocation;
  • check the status of the work;
  • get feedbacks from patients about work done;
  • get feedbacks from family members of the patients.

- Requirements for the Staff:
Possibility to:

  • check daily plan and weekly plans;
  • check feedbacks from the patient;
  • mark tasks as “done”, “not done”.

- Requirements for the Patients:
Possibility to:

  • check daily plans;
  • leave references about the every ToDo;
  • mark ToDo’s with “like”, “do not like”;
  • review details about caregiver.

- Requirements for the Family members:
Possibility to:

  • receive daily notifications about Patient status;
  • heck info about every ToDo status.

Technical requirements:

  • custom Server side to store all data;
  • web Admin Panel would be more than enough;
  • 3 Native iOS and Android apps;
  • design for these 3 apps based on UX of each platform.

The development of such system can take around 6 months even with simultaneous development.

What to do?
There is still 2 sides of the coin. For the one side, there is a list of competitive tools with slightly different functionality on which you can just close your eyes. And branding from the other side. Sure, such huge managing system requires a lot of funds. But what if you would go step-by-step? What if I say that such healthcare system can be integrated twice faster and with more reasonable price?

Our solution is Lean methodology:

1) Sorting out the audience and their devices. Let’s imagine that:
 — your staff have iPhones;
 — your patients have Android devices;
 — families mainly have iPhones.
This point cuts funds and time for mobile development greatly. Let’s go further.

2) We can cut the feature list and keep just the main to integrate:

The development of such system requires not half a year to integrate. We need just several months and just half of required funds.

Do you think your audience will use your healthcare consulting?
Is it affordable?
Do you think such approach is worth of using?

The main point here is that the quality of the system stays outstanding and it is easy to scale it. You do understand what your users would say about the cross-platformed buggy system, so you don’t need to use it.

If you do agree with such methodology, please share this article. If you are not sure how to use it in your particular situation — drop us a line.

 

Subscribe to our news. And stay tuned!