# Synclo > Synclo Complete Care was a suite of hospital products, one for each person in a visit: the patient at the helpdesk, the doctor, the nurse at the station and the lab technician. I designed all of it as the only designer, and helped build it. - Canonical page: https://www.hirahul.xyz/synclo - Company: Detrix, which became Synclo - Period of the work: 2020–2022 - Role: The only designer across the product line, as an individual contributor. I also helped build the system. - Team: I was the only designer, alongside engineers including Vinay Kumar (senior software engineer) and Akhil Ravilla (software engineer), under our CEO, Ajit. - Case study last updated: 2026-10-18 - Author: Yamparala Rahul ## The products Six products, one for each person in a visit. I designed all of them, and a test run in real hospitals removed two. | Product | Platform | Used by | What it was for | What became of it | | --- | --- | --- | --- | --- | | CheckIn | Web | Patients at the hospital helpdesk | Check in by scanning a QR code, in the patient's own language. | | | QMS for Doctors | iPad | OPD doctors | Run the day's patient queue and consultations, with AI diagnostic support and e-prescriptions. | | | MDsync | iOS and Android | Doctors | Oversee consultations, with a full view of each patient's profile. | Removed after the hospital test run | | PatientSync | iOS and Android | Patients | View reports, book and manage appointments, and track maternity care. | | | LabSync | Windows | Lab technicians | Handle lab report requests and billing. | Removed after the hospital test run | | NPmS | Desktop and web | Head nurses at the nursing station | Monitor patients, assign work and keep the station productive. | | ## Why we started with medium-sized hospitals [https://www.hirahul.xyz/synclo#why-medium](https://www.hirahul.xyz/synclo#why-medium) The size of a hospital changed the problem, so we chose a size before we designed a screen. We sorted hospitals into three sizes by who works there and how many patients they see. Turn the knob on the clinic model to compare them. Small clinics had little reason to change. Large hospitals keep patient data inside the hospital; for them we planned the suite on their own servers, managed by us. Medium hospitals were willing to experiment and had a budget, and we needed somewhere to build, test and change the product. We started there. The three sizes in the clinic model: - Small: 1 doctor · 1 nurse; 10–15 patients a day. What they had: A small team with no digital process. Everything is manual. What they asked for: Tools to manage the clinic and bring in revenue, ideally all in one workspace or plan. Why we did not start here: Small clinics had little reason to optimise. Many were evening practices run by doctors who also worked at a larger hospital, sometimes below their own homes, and sent patients who needed more to that hospital. - Medium: 3–5 doctors · 6–12 nurses · 1 head nurse; 25–40 patients. What they had: A medium team with some digital process, not streamlined. What they asked for: A streamlined process, and departments that connect to each other. Why we started here: Often run by a doctor couple, with two different sets of patients' needs. They had enough coordination to need a connected suite, were willing to experiment, and had a budget. A startup needs somewhere to build, test and change a product, and they were that place. - Large: 10–20 doctors · 30 nurses · 4 head nurses; 80–120 patients a day. What they had: A large team with digital infrastructure, on an old interface. What they asked for: A better interface, and AI to help with resource management and analytics. Why we did not start here: They already ran their own ERP, and they are strict about patient data leaving the hospital. That data is not material for a startup to test with. Our plan for large hospitals: This was never a limit of the suite. We planned to supply the servers with the application, so every record stays on the hospital's premises, with us managing the servers on a platform subscription. ### Evidence: research-challenges [https://www.hirahul.xyz/synclo#research-challenges](https://www.hirahul.xyz/synclo#research-challenges) · design Our research deck's brief: clinics of different sizes work differently, and consultation time is the thing to cut. - Synclo challenges slide: clinics of different levels function differently, and Synclo wants to reduce consultation time, over small, medium and large target clinics (https://www.hirahul.xyz/portfolio/Synclo/Research/01-challenges.webp) ## Arriving: the patient checks themselves in [https://www.hirahul.xyz/synclo#arriving](https://www.hirahul.xyz/synclo#arriving) Check-in starts with the patient's own language and ends with the patient confirming what the doctor will read. A patient scans a QR code at the helpdesk and checks in on their own phone. Before sending, they read back exactly what the doctor will see. That is the first of two checks a person makes before anything moves on; the second is the doctor's. ### Evidence: checkin-flow [https://www.hirahul.xyz/synclo#checkin-flow](https://www.hirahul.xyz/synclo#checkin-flow) · design Language first, then their concerns in their own words, then follow-ups. The last screen is the check: the patient confirms what reaches the clinician. - Language first: Synclo Check In asking the patient to choose a preferred language before anything clinical, co-branded with the hospital (https://www.hirahul.xyz/portfolio/Synclo/Check%20In/Screens/01-language.webp) - Their own words: Check In asking what is your concern, with searchable categories and a checklist of common symptoms (https://www.hirahul.xyz/portfolio/Synclo/Check%20In/Screens/02-concerns.webp) - Follow-ups: Check In asking how long the patient has had a fever, with the selected concerns shown as removable chips above (https://www.hirahul.xyz/portfolio/Synclo/Check%20In/Screens/03-questions.webp) - They confirm it: Check In reading back the captured details, concerns and answers for the patient to verify before they are sent on (https://www.hirahul.xyz/portfolio/Synclo/Check%20In/Screens/04-summary.webp) ### Evidence: checkin-wait [https://www.hirahul.xyz/synclo#checkin-wait](https://www.hirahul.xyz/synclo#checkin-wait) · design Then the wait: where they are in the queue, how long, and what the visit will include. - Waiting: Check In waiting area screen counting down the wait with the queue position and a visit overview from check-in through to discharge (https://www.hirahul.xyz/portfolio/Synclo/Check%20In/Screens/05-waiting.webp) - Waiting room allotted: Patient waiting screen showing minutes until a room is allotted, above an hourly chart of how busy the clinic usually is (https://www.hirahul.xyz/portfolio/Synclo/Check%20In/Screens/06-waiting-room-allotment.webp) ## The consultation [https://www.hirahul.xyz/synclo#consultation](https://www.hirahul.xyz/synclo#consultation) The doctor's day is one board, and the AI's suggestions wait for the doctor's choice. In a consultation the AI only suggests, and the doctor decides: treatment stays locked until the doctor picks one of its diagnoses. So a person stands at both ends of the model: the patient confirms the symptoms before it sees them, and the doctor confirms the plan after. We built the AI but never fully tested it, so these screens show how it was designed to reach the doctor, not a proven model. ### Evidence: qms-custom-space [https://www.hirahul.xyz/synclo#qms-custom-space](https://www.hirahul.xyz/synclo#qms-custom-space) · design Every panel is a widget, so each doctor composes the board their day needs. - Synclo QMS custom space, a doctor-composed board mixing an anatomy reference image, notes and a break timer with the standard consultation widgets (https://www.hirahul.xyz/portfolio/Synclo/QMS/Screens/02-custom-space.webp) ### Evidence: ai-review [https://www.hirahul.xyz/synclo#ai-review](https://www.hirahul.xyz/synclo#ai-review) · design Suggestions, then three candidate diagnoses at 80, 50 and 30 percent with treatment locked until the doctor picks, then medicines the doctor curates, with the patient's instructions in plain words. - Suggested, then qualified: Consultation capture, with suggested symptoms and suggested diagnoses the doctor selects from, and a panel to mark each one as to rule out, suspected or follow up (https://www.hirahul.xyz/portfolio/Synclo/In%20Clinic/Screens/05-consultation-symptoms.webp) - Three candidates, the doctor picks: Three candidate diagnoses from Synclo AI with probability scores of 80, 50 and 30 percent, as radio options the doctor must choose between before treatment unlocks (https://www.hirahul.xyz/portfolio/Synclo/In%20Clinic/Screens/06-ai-diagnosis.webp) - Recommended, then curated: Recommended medicines the doctor ticks, unticks or deletes, beside an intake panel whose plain-English preview composes from the dosage, frequency, duration and timing chosen (https://www.hirahul.xyz/portfolio/Synclo/In%20Clinic/Screens/07-ai-treatment.webp) ### Evidence: solution-architecture [https://www.hirahul.xyz/synclo#solution-architecture](https://www.hirahul.xyz/synclo#solution-architecture) · design Where the model sits: between the patient's check and the doctor's. - Synclo solution architecture, showing check-in, profile and management systems over a backend of queue management, an AI model and archival, with two validation gates (https://www.hirahul.xyz/portfolio/Synclo/System/solution-architecture.webp) ## The nurse station [https://www.hirahul.xyz/synclo#nurse-station](https://www.hirahul.xyz/synclo#nurse-station) NPmS was designed for the head nurse: the same queue, with the actions that belong to the station. Several products write to one patient record, so each block names the product that last updated it, and when. A nurse can see where a fact came from before trusting it. ### Evidence: nurse-queue [https://www.hirahul.xyz/synclo#nurse-queue](https://www.hirahul.xyz/synclo#nurse-queue) · design The live queue: its length, the average wait and patients seen per hour, a hold control, and each patient one click from no-show, reschedule or vitals. - NMS live queue showing current queue length, average wait and throughput above a searchable, reorderable patient list with a hold-queue control (https://www.hirahul.xyz/portfolio/Synclo/NMS/Screens/02-live-queue.webp) ### Evidence: record-provenance [https://www.hirahul.xyz/synclo#record-provenance](https://www.hirahul.xyz/synclo#record-provenance) · design One record, several products. Each block names which one last touched it, and when. - NMS patient summary where each block of details names the product that last updated it and when (https://www.hirahul.xyz/portfolio/Synclo/NMS/Screens/03-patient-summary.webp) ## Between visits: maternity care [https://www.hirahul.xyz/synclo#between-visits](https://www.hirahul.xyz/synclo#between-visits) Maternity care runs across many visits, so the patient and the doctor need one history. For the 9M maternity vertical of Ankura Hospitals, one of the hospitals we onboarded, we designed PatientSync: an iOS and Android app, connected to the doctor's QMS, that follows a mother through 16 months or more of visits. Every consultation starts from the whole history. ### Evidence: patientsync [https://www.hirahul.xyz/synclo#patientsync](https://www.hirahul.xyz/synclo#patientsync) · design PatientSync: the next appointment and recent prescriptions at home, visits marked virtual or walk-in, reports to open, and the family's records beside the patient's own. - Home: A patient's home showing the next appointment with its hospital and doctor, recent prescriptions as documents, and a book-an-appointment action (https://www.hirahul.xyz/portfolio/Synclo/NMS/Patient%20Workspace/01-home.webp) - Virtual or walk-in: Upcoming appointments marked virtual or walk-in, with a join-call control that says it enables fifteen minutes before, above past appointments (https://www.hirahul.xyz/portfolio/Synclo/NMS/Patient%20Workspace/02-appointments.webp) - Reports: Patient reports in the Synclo patient app (https://www.hirahul.xyz/portfolio/Synclo/NMS/Patient%20Workspace/07-patient-reports.webp) - The family's records too: A profile sheet switching between the patient's own record and a family member's, with an option to add a new member (https://www.hirahul.xyz/portfolio/Synclo/NMS/Patient%20Workspace/08-members.webp) ## What the hospitals changed [https://www.hirahul.xyz/synclo#what-changed](https://www.hirahul.xyz/synclo#what-changed) Real hospitals removed two of our six products, both because of how those hospitals worked. After the first QMS demo, two to three multi-speciality hospitals agreed to a test run, and we onboarded three, Ankura among them. The average consultation fell from about 30 minutes to about 20. MDsync went first. Doctors declined it: in maternity care, patients' messages are many and often urgent, and they belong in the QMS with the secondary doctor or nurse, not on the consulting doctor's phone. LabSync went too. Most of these hospitals used partner labs, so there was no in-house lab for it to serve. ### Evidence: mdsync [https://www.hirahul.xyz/synclo#mdsync](https://www.hirahul.xyz/synclo#mdsync) · design MDsync, removed after the test run: the doctor's day by stage and ward, a profile from provisional to final diagnosis, examination as a checklist, and referrals. - The day, in numbers: A doctor's dashboard showing patient satisfaction, incoming against outgoing referrals, patients split across examination, investigation, treatment and discharge, and a work-scope of wards and ICUs by room (https://www.hirahul.xyz/portfolio/Synclo/QMS/Doctor%20Workspace/01-home.webp) - Provisional, then final: A patient profile listing provisional and final diagnosis tabs above examination methods and investigations (https://www.hirahul.xyz/portfolio/Synclo/QMS/Doctor%20Workspace/03-patient-profile.webp) - Examination as a checklist: An examination in progress, with tabs for inspection, auscultation, palpation and percussion and findings ticked off as a checklist (https://www.hirahul.xyz/portfolio/Synclo/QMS/Doctor%20Workspace/04-examination.webp) - Referrals: The referrals list in the Synclo doctor phone app (https://www.hirahul.xyz/portfolio/Synclo/QMS/Doctor%20Workspace/06-referrals.webp) ### Evidence: lab-dashboard [https://www.hirahul.xyz/synclo#lab-dashboard](https://www.hirahul.xyz/synclo#lab-dashboard) · design LabSync on Windows, removed after the test run: tests advised against patients who came, walk-ins and referrals, then trending tests, sales and payments. - LabSync dashboard on Windows: counts for advised by doctor, patients visited, advised but not visited, direct walk-ins and referrals to other labs, above trending tests, weekly sales, coupons and payment methods (https://www.hirahul.xyz/portfolio/Synclo/LabSync/Screens/01-dashboard.webp) ## What this case study does not claim - The clinic sizes are the team's planning segments, not a survey of real hospitals. - The AI was built but never fully tested. Its screens show how the review steps were designed, not diagnostic accuracy or clinical validation. - The drop from about 30 to about 20 minutes per consultation comes from the hospital test run, not a controlled study. - The clinic model is drawn for this case study, not a Synclo screen. Its furniture shows what a room is for, not how many it holds. ## The team The Synclo team standing together in an office, with a handwritten 'Me' arrow pointing at Rahul. (https://www.hirahul.xyz/portfolio/Synclo/Team/01-team.webp) The Synclo team. I'm the one marked “Me”. ## Related - [Healthcare collection](https://www.hirahul.xyz/healthcare): Every Synclo screen in one feed, with the other patient apps from the same years and related healthcare work. - [Synclo: Doctor App Demo](https://www.youtube.com/watch?v=1NQ1LtteJfA): A walkthrough of the app for doctors, on YouTube.