CareHubble

Continuously Updated

It would take years to achieve CareHubble’s vision of providing certification verifiability, payment protection and client to provider matching. CareHubble required a team that could break down the roadmap and build features over time that were valuable to its end users.

Connect Seamlessly

CareHubble needed both clients’ and providers’ data to be connected seamlessly in the system.
All data needed to be searchable and extractable for future use.

Maximum Security

All client information (health and otherwise) must be stored & accessed in accordance with current government guidelines, PIPEDA, PHIPA, HIPAA. The client profile must be kept very secure as it may contain Personal Health Information (PHI).

1. CareHubble provider profiles must integrate with other health services databases so that providers can be found more easily.
2. A Canadian health services database that lets clinicians instantly navigate location-specific health care services for their patients.
   Clients should be able to search by timeslot, e.g. if a client needs a provider from 0800-1100 hrs. then they may search for this timeslot and retrieve a list of providers with the specified availability.
3. RAI Check-Ups (a standardized questionnaire on the client’s health) will be used to capture key health indicators about the client. It should be completed at the following intervals:
   1. First care interaction with CareHubble.
   2. Every 3 months afterward (meaning this could be completed by different providers over extended periods of time).

Through discussions and workshops we were able to highlight pain points with existing systems and map out user flows that focused on utility, performance and user experience. We worked with the CareHubble team to understand their objectives and conduct rapid prototyping that would ensure continuous feedback and on time delivery.

Whenever there was a complex problem to solve, we mapped out the logic to ensure we were extensively ideating and looking for missed opportunities. This ensured that the solution was feasible and that there was continuous alignment between our team and CareHubble’s team.

Building a design system in Figma was an important part of the process to hand over the project to the CareHubble team and work efficiently in different time zones. The components helped engineers to correctly implement the interface requirements and minimize development efforts.