Startup Journey
This page is password protected. Enter the access password to continue.
Incorrect password. Please try again.
This page is password protected. Enter the access password to continue.
A Clinical intelligence layer that converts longitudinal patient records into concise, visit-ready context for General physicians without replacing the EHRs.
General physicians (GPs) in polyclinic settings see up to 8 patients per day. Before each consultation, they must mentally reconstruct a visit-ready picture of the patient from a voluminous, chronologically organised record - one that is not structured around the current reason for visit.
This work is cognitively expensive. Chart review frequently spills beyond the scheduled consultation window or into non-working hours. Even after reviewing, clinicians report residual uncertainty about whether the most important context has been surfaced.
The challenge is not information scarcity. It is relevance prioritisation inside an information-rich environment. Finding the right information takes longer than writing the consultation note itself.
Clinexus sits alongside the existing EHR. It takes the current reason for visit and retrieves, scores, and structures the patient record into a concise pre-consultation overview - highlighting active issues, relevant medications, recent lab changes, and open clinical questions.
Clinicians can ask bounded follow-up questions grounded in the patient context, with responses linked back to the source record. External clinical guidelines (Kaypahhoito, Terveysportti) surface where relevant without blending with patient data.
We do not replace the EHR (eventually if we get a chance we can replace few systems). We make the data in it cognitively usable, in the narrow window before the patient walks in.
We have completed user research with GPs in polyclinic and primary care settings in Finland. The product requirements are defined and the core architecture is in build. The v1.0 scope covers reason-for-visit-anchored retrieval, structured pre-consultation overview, bounded query interface, and audit logging.
We are running with synthetic and de-identified patient data during the pilot phase, in line with healthcare data compliance requirements.
Entered the Startup Journey program with a defined product scope and research-backed problem statement. This week focused on distilling our ask into something concrete and actionable for mentors. Key realisation: our blocker is not product clarity - it is getting a supervised pilot with real clinical data moving fast enough to generate useful signal. That is the specific problem we need help solving.
