Glycoz for clinicians · 13 headaches, answered
Built for the headaches of running a clinic or a hospital.
Patients who forget between visits, records in five places, attendance and payroll by hand, beds on a whiteboard, stock that runs out. Each chapter below names one, says what Glycoz does about it, and lists what is built.
The whole platform, at a glance →Between visits
You see ten minutes. This shows you the months in between.
Your patients keep their own health record on their phone, every day — readings and medicines, blood pressure and weight, pulse, oxygen, meals and activity — even with no signal. When one connects you, what they share appears in your browser exactly as they recorded it.
- You see a few minutes every few weeks
- Your patient measures things every day for months. You get ten minutes in a room, and most of what happened never comes up.
- What you hear is remembered, not recorded
- People round the numbers, forget the bad days, and describe an even pattern that was never even. The days that mattered are the ones least likely to come out right.
- Advice waits until the next visit
- Something you would have said in week one gets said in week six, because there was no way to say it that reached them and stayed on their record.
And three things are true before you start.
Each one takes a worry off the table instead of answering it with a promise. None of them is a setting anybody can change.
- They add you. You cannot add them
- You make a code, they type it into their own app — or they find you and ask, and you accept. There is no screen anywhere that lets you add a patient, and you never see or hold their password.
- They choose what you see
- Area by area, and separately for each doctor. Anything they hold back shows you a “not shared” card and nothing else — its values are never sent to your browser.
- They can close it without asking
- A patient can switch an area off, or end the connection, at any time without telling you, and it takes effect on your very next request — so the panel always shows what they are content for you to see.
What is built
- An offline-first app your patients keep
- Sharing per area and per doctor, enforced on the server
- Connection by a code you give, or a request they send
- Prescriptions that reach the patient's phone
Where to start
It opens on the day, not on a report.
Two dashboards, and one switch between them. The first is the day's work: who is booked, what has been recorded for each of them since you last saw them, what is waiting on you, and who has gone quiet. The second is the whole list over ninety days.
On the day’s dashboard, patients past the thresholds you set are grouped by what dealing with them involves — a call, a dose review, a lab form, a conversation — with a count on each. Any card can be set aside for a week, or until the finding gets worse; one set aside until it gets worse comes back the moment it does.
And on the second: not in alphabetical order.
Two lists, kept apart: Act now, for readings past your thresholds and patients waiting on a reply, and Drifting, for patients who are fine today but heading the wrong way.
Drifting
- R. MehtaGlucose · 4 readings below 70 mg/dL112 mg/dL
- K. SinghEngagement · Last reading 23 days ago
- A. ReddyChanging · Average up 31 mg/dL on the previous fortnight164 mg/dL
The second of two lists: patients who are fine today but heading the wrong way. Unsafe readings, and patients waiting on a reply, are in the other one, Act now.
And one thing the patient list will not do: put a glucose number next to each name. A single figure in a column invites ranking people by it at a glance. The queue shows an average only beside the reasons someone is on it.
Then: one patient, one screen, no training.
Everything on it is something they recorded and chose to share with you.
- Overview
- Readings & logs
- Meals & nutrition
- Prescriptions
- Private notes
- Emergencies
- Patient details
- 82.1%
- In range, 70–180
- 129mg/dL
- Average
- 3.4%
- Below 70
Weight — not shared. Your patient has chosen not to share this with you. There is no figure behind the card: the server never sent one.
- Overview
- Time in range, averages, time spent low, and readings laid out by time of day — so a problem that only happens after dinner looks like one. Next to it: the medicines they logged as taken, HbA1c over time, and whichever vitals they share.
- Readings & logs
- Everything they entered, filterable by type and by period. A blood sugar reading carries the day and the meal they logged it against — written down, not remembered in your room.
- Meals & nutrition
- The meals they logged, day by day: their own note, and the estimate made from the photograph — what the dish is, the figures, and what it assumed. Never the photograph itself, and only if they share Meals.
- Prescriptions
- What you have written to them, and whether they have marked it read. Once they have, you cannot quietly edit it — so the record of what you advised, and when, holds up later.
- Private notes
- Your own notes about this patient. Nothing sends them to the patient, and no screen in their app shows them. The one place they travel is the assistant: ask it about your notes, and their text goes to the AI provider that writes its answer.
- Emergencies
- Alerts they have raised, who saw each one and the note they left. An alert reaches you by email, in the panel's emergency bell and on the phone app. It does not reach an ambulance or any emergency service, and their app tells them that plainly.
- Patient details
- What they have chosen to tell you about themselves. Nothing more.
Prescriptions reach them. Private notes never do.
What you put in Prescriptions lands on their phone. What you put in Private notes never does — nothing in the system carries it to them. The one place it travels is the assistant, if you ask it about your notes.
And a notebook of your own
Protocols, dosing tables, the numbers you keep looking up. It belongs to no patient and goes nowhere — and every member of staff has a private one too.
What is built
- A dashboard for the day, with a queue in six groups
- A population view over ninety days
- A patient record in tabs, from Overview to Emergencies
- Private notes, and a notebook of your own
What it asks of you
How much work is this? Almost none.
That is the point. A tool that makes more paperwork gets dropped within a fortnight, however good the charts are.
- Nothing to install
- The panel opens in the browser you already use. No software, no plugin, nothing to connect to whatever the clinic runs. The phone app is there for the team that wants it, not something the panel needs.
- Nothing to type in
- You are not entering patient data. They record it as they go; you are looking at it.
- Nothing to look after
- No server of yours, no backups of yours, no upgrade weekend. If a patient never connects you, it takes none of your time.
Appointments
A diary, and the things that go wrong with one.
Patients see the times you actually have free and ask for one; you accept it or decline it with a reason, or book one for them. The booking is the easy part — the rest is not.
- It opens on the day
- One day as a list, morning to evening: who is coming, what came of each visit, and what is left to do. A visit that happened with nothing written up against it is marked “Not written up” until somebody records it — that is the one that quietly gets lost.
- And a calendar, two ways
- The day's slots as a list of who is coming and when you are free, or drawn to scale. Both stay, and the panel remembers which one you used last.
- Set your hours once
- Say which hours each provider works and how long a slot is, and requests fill them in. Each has their own diary, and time can be blocked.
- Three bells, kept apart
- One for emergencies, one for booking requests and cancellations, and one for patients asking to connect. Each refreshes on its own and opens beside the day rather than on top of it — and a person who may not act on one never sees it.
- Two people cannot take the same slot
- If two requests arrive for 09:30 a second apart, the database itself refuses the second one. Checking first and booking after is what lets both through — and then somebody arrives for an appointment that is not there.
- Only what has happened can be written up
- A later day cannot be recorded as seen, and that is refused by the server, not merely hidden on the screen. A finished visit shows the patient what you recorded.
What is built
- A day view and a calendar, per doctor
- Weekly hours and slot length per provider
- A double booking refused by the database
- Walk-ins, blocked time and visits written up
Your practice
Everyone gets their own login.
A clinic is not one person, and a system that assumes it is ends up with everybody sharing one password.
- Everyone signs in as themselves
- No shared password with the front desk. Every action has a name against it.
- You choose what each person sees
- Your receptionist can run the diary without being given a single tab of anyone's record. That is the whole point of the feature.
- And whose diary they can open
- Giving someone the appointments module gives them no diary at all — you pick which ones. Otherwise one tick lets the front desk read every doctor's day.
- Staff run by an account of their own
- A new practice sets up one HR account first, so the team is run from an account that is not the doctor's. Whoever holds it can add people and set their access — but only within what they hold themselves, never their own, and every change is kept with who made it.
- Everybody chooses their own password
- Each person is emailed an invitation and sets their own. Access can start from a template — receptionist, nurse, practice manager, accountant — and be adjusted from there.
- More than one doctor
- Add the practice's other doctors from the panel; each signs in once we have checked their registration. Someone who works for two doctors chooses whose patients and diary they are on.
| Module | You | Jr. doctor | Nurse | Reception |
|---|---|---|---|---|
| Patient list | granted | granted | granted | not granted |
| Prescriptions | granted | granted | not granted | not granted |
| Private notes | granted | not granted | not granted | not granted |
| Appointments | granted | granted | granted | granted |
Reception runs the diary without a single tab of anyone’s record.
A small thing with a real effect: a job title that holds its own appointments gets a diary automatically; one that does not gets none, and you can change it either way. Nurse practitioner does, nurse does not.
What is built
- Staff logins with access per module
- Whose diary each person may open
- Templates for receptionist, nurse, practice manager and accountant
- Two-factor sign-in
Your team
Hours, leave and pay, for everybody who works there.
Attendance, leave and payroll sit in the same panel as your patients — so the diary knows who is away, and a payslip can be read back to the days behind it.
- It starts with your own week
- You set the practice's shifts, leave types and holidays once. Everybody is put on a usual week, and a single day that differs is an exception rather than a new week.
- Checking in, with a photo and the place
- Each person checks in and out from their own account, in a browser or on the phone, and the time is Glycoz's own, not the device's. Every punch asks for a photo of the person and their location: switch on the practice's rule and both are required, leave it off and both are optional. Photos are deleted after 45 days, and only the person, the owner and whoever you give attendance to can see them.
- A day nobody marked is not an absence
- It reads as not marked, because absent is the one that costs somebody a day's pay. When somebody forgets to check out, they ask for the day to be put right with a reason, and whoever approves settles it. A wrong entry is struck out rather than deleted.
- Leave, with the approvers you choose
- Balances by type, requests to whoever you name — one person, any of several, or several in turn — and a reason on every refusal. Approved leave closes that person's appointment book for those days; appointments already made are shown to the approver first, and never cancelled by it.
- A month, run once it has ended
- Salary structures, and a monthly run that will not lock while any day in it is unsettled. Preparing a month and approving it are separate permissions, and a month that was wrong is reversed and run again rather than edited.
- Payslips people can check
- Numbered by the practice, never changed once issued, and each showing the days behind its figures. Everybody opens their own; the email saying one is ready never says the amount.
- Everyone sees their own
- Every member of staff has their own hours, leave and payslips with nothing granted. Seeing anybody else's is a permission you give, person by person.
- Doctors can be on the books too
- Any doctor, you included, can check in, take leave and be paid in the same run — without a second account.
- Nobody sets their own salary
- A doctor on the books cannot change their own pay. The practice owner can set theirs, and a month with it inside says so to whoever approves it.
What it does not do: move money, or work out statutory deductions for you. A practice pays people the way it already does; Glycoz works out what is owed from the days, records what you deduct, and produces the document for your practice to confirm. HR and payroll are additions to a practice’s plan.
Attendance, leave and payroll, on one page: staff and payroll for clinics.
What is built
- Shifts, rosters and holidays
- Check-in with a photo and the location
- Leave with approver chains
- Monthly pay runs and numbered payslips
- Doctors on the HR books
- A clinic dashboard with no patient on it
Wards and beds
Wards, beds and the bill — from admission to follow-up.
For a practice that admits patients. It is switched on for a practice that asks, and priced per bed. The desk runs it in the panel; the ward runs it on the phone.
- A board of every bed
- Every ward and every bed: free, occupied — who, since when, under which doctor — being cleaned, or out of service. Occupied is worked out from the admissions, so the board cannot disagree with them, and two people can never be in one bed: the database refuses it.
- Admit and transfer
- Admit from a free bed — a patient you already have, or somebody new. Each admission is numbered per practice and per financial year, with no gaps. A transfer closes one bed and opens the next, so no day is charged twice.
- Care given, at the bedside
- Medicines, injections, drips, nursing, procedures, consultations and investigations, recorded on the phone with one confirm. An entry is never edited or deleted: a mistake is struck out with a reason and a name, and stays visible as struck. The price is copied onto the entry, so a new price list never reprices a stay already running.
- A bill that holds up
- Room days are counted by the midnight, at each ward's day rate; a stay with no midnight is one day. Deposits and payments are recorded as they come. The bill is a snapshot with its own number: nothing on it moves when the records under it do, and a wrong one is voided with a reason and issued again.
- Discharge, and the summary
- Discharge needs the bill issued and settled, or a discharge with the balance due recorded by somebody allowed to — the software never holds a patient on a ward. A printable discharge summary carries the care given and your note in your own words.
- Follow-up on the patient's app
- The summary carries a one-time code. When the patient types it into their own app they connect to the admitting doctor — their consent, as with any code — and the stay appears in their app, with its care, every bill, the payments and the reports. From then on you follow them up like any connected patient, under their own sharing choices.
- Reports, both ways
- Attach a report to a stay at the desk, and the patient has it in their app. Ask for a test after discharge, and the patient sends the lab report from the same screen; it arrives on that patient's Hospital tab with a notification. You can hide a patient's upload from your own list, never delete it — it is theirs.
- Who was admitted, on the patient list
- Patients you admitted are marked — in hospital now, or admitted before — with a filter for them, and each has a Hospital tab in the panel and on the phone: every stay, the care given, the bills and the reports.
Access, as for everything else: admissions, bedside care, hospital billing and ward setup are separate permissions, and the templates start sensibly — a nurse records care, reception admits and takes payments, an accountant sees the bills and the stock. Nothing about a stay is ever shown to us.
Plainly: it does not do pharmacy counter sales, lab orders or insurance claims.
The hospital side, for nursing homes and hospitals, on one page: Glycoz for hospitals.
What is built
- Wards, beds and the bed board
- Admissions, transfers and discharge
- Bedside care recorded on the phone
- Room charges, deposits, bills and payments
- A printable discharge summary
- A follow-up code, and the stay in the patient's app
- Reports both ways, and a Hospital tab on each patient
Stock
Stock that says when it is running low.
For a clinic with a store cupboard or a hospital with a stock room. Switched on per branch, with or without wards.
- A ledger, not a number
- Stock on hand is the sum of every delivery, issue, return and adjustment at a branch, each with who and when. There is no stored total to drift out of step.
- Running low, said once a day
- Each item has a reorder level. Anything below it goes on the reorder list, and once a day the people who order at that branch get one notification saying how many items — never which patient used them.
- Orders and deliveries
- Draft a purchase order from what is low, mark it sent, and receive the delivery against it with batch and expiry on each line — on the panel or the phone. Every order is numbered for the year and prints as a sheet for the supplier.
- Care draws on stock
- With wards switched on, care given at the bedside draws on the branch's stock, so the store and the bill agree. Stock may go below zero when care is recorded faster than deliveries are entered — refusing to record an injection because the count is behind would make the record wrong about what a patient was given — and negative stock is shown in red, as something to sort out.
What is built
- Items, suppliers and stock per branch
- A reorder list, and one notification a day
- Purchase orders, printed for the supplier
- Deliveries with batch and expiry
- Ordering and receiving on the phone
Branches
More than one place, run as one practice.
Two clinics in one city are usually one business with two addresses. Glycoz runs them that way.
- One practice, several doors
- A practice that works from more than one place keeps one record, one team, one payroll and one bill, with a branch for each place. It is switched on for a practice that asks.
- Staff, at the branch they work at
- Each person has a home branch and the branches they may work at. The roster says which, day by day, and a check-in is recorded where they are. HR can be given for one branch only — it then sees that branch's team and nobody else's. Payroll is always the whole practice.
- Doctors' hours, branch by branch
- A doctor is placed at one branch or several, with weekly hours at each. Every appointment says which branch it is at, and a doctor is never booked at two branches at the same time.
- Wards and stock, per branch too
- A ward can belong to a branch, stock is counted branch by branch, and access to admissions, bedside care, hospital billing and stock can each be limited to one branch.
And patients nearby can find you.
Your listing is what someone searching in the app sees. It is the one part of Glycoz that brings you patients rather than organising the ones you have.
- Someone nearby finds you and asks
- A patient searching in the app sees your listing, your fee and the languages you speak, and asks to connect. Until you say yes, you see only what the request carries — their name, age, city, diabetes type and a note — and none of their records.
- You write all of it
- Photo, fee, languages, and a pin you place on the map yourself. Nothing shows until you fill it in — there is no profile of you sitting there getting it wrong.
- And you can say no, usefully
- With a reason they can act on: not taking new patients, outside the area you cover, or not the kind of care you provide.
Your name
Your speciality
Your qualifications
- 2.4 km away
- Your city
- Gujarati
- Hindi
A patient who opens it sees your fee and can ask to connect. You accept or decline — they are not connected to you until you accept.
Plainly: a doctor appears once their registration is verified, their map pin is confirmed, they have agreed to the listing terms and switched the listing on — on an active plan that includes a listing, never a trial. The directory is new, and only as useful as the clinics in it.
What is built
- A branch for each place, on one account
- HR limited to one branch when you want it
- Doctors never booked at two branches at once
- A Find a Doctor listing, from Solo up
Glycoz For Doctors
The practice, on a phone.
Glycoz For Doctors is an Android app for doctors and their staff. Each person sees what the panel already gives them, and nothing more.
- Home, as the practice's day
- A dashboard of what each person holds: emergencies first, then checking in and their day, today's appointments with the week as bars, what is waiting on them, who is at work and who is off, the ward in one bar, stock to reorder, pay, the team — and for the owner, the plan. Nobody in a bed is named on it, and no health value appears.
- The Diary
- The appointment book, whole: accept a request or decline it with a reason the patient reads, book a patient or a walk-in, record a visit, block time and change the weekly hours.
- The ward, at the bedside
- The bed board; an admitted patient's bed, days, doctor and care so far; recording care with one confirm; admitting to a free bed, transferring, and setting a bed free, being cleaned or out of service. Each admitted patient's Hospital tab, with their stays, bills and reports. Discharge and bills stay at the desk.
- Stock, where the delivery is
- What is low, an order drafted from it, marking it sent, receiving a delivery with batch and expiry, and correcting a count.
- HR, decided from a pocket
- Leave requests and attendance corrections waiting for you, who is in today, and what needs sorting before the month can be paid. Everybody's own attendance, leave and payslips, each payslip as the practice's own PDF. Setting HR up and running payroll stay on the panel.
- A patient, on the phone
- Their details and medicines, the latest of every area they share, their readings a page at a time and their emergency history — plus prescriptions, checked on a screen showing exactly what the patient will see, and your private notes. Charts stay on the panel.
- The plan, for the owner
- What the practice is on and its add-ons, every plan and add-on to compare, a change asked for with a live estimate, and every invoice with its PDF. It asks; we approve and send one invoice.
And what reaches the phone.
Everything a doctor or member of staff is emailed also arrives as a notification, and the bell keeps every one. Tapping it opens the place it is dealt with. Who is told what follows the access you already set on the panel — there is no second set of switches.
- No patient on a lock screen
- A notification says what kind of thing is waiting — “A patient asked for Friday 3 October at 11:00” — and never a name, a reading or an amount.
- No record kept on the phone
- Each screen asks for what it shows and keeps it only while it is open. The patient list on a phone is names, and nothing else.
- The phone's own lock, every time
- It opens behind the phone's fingerprint, face or PIN every time, and does not open at all on a phone with no screen lock.
Plainly: it is on Android, installed directly for now, and in English. It is added to a practice’s plan; without it the panel works exactly the same. Emergency alerts pass every billing gate on the phone, as they do on the panel.
What is built
- Home, as a dashboard of the day
- The diary
- The ward and bedside care
- Stock orders and deliveries
- HR decisions and everyone's own payslips
- The plan and invoices, for the owner
The assistant
Questions about your own patients, in your own words.
“Who should I look at first this week?” “Has his fasting sugar changed since March?” It answers from records you can already open — on its own page, or in a panel beside a patient's record, the same conversation in both.
- Five kinds of question
- A summary over a period, whether something is changing, two patients compared, who needs you first, and what you wrote in your own notes. Typed in your own words, with shortcuts if you want them and none if you do not.
- It reads what you can, as you
- It opens records as the signed-in person, so it reaches nothing they could not open themselves. Areas a patient has not shared are named under the answer, not skipped.
- The figures come first
- Every figure is worked out from the record before a sentence is written, and the table it drew on is shown under the answer — so a claim can be checked against the chart beside it.
And it can be talked to.
- A greeting gets a greeting. Asking what it can do, or what it is, gets a straight answer — and none of these uses the practice's assistant credits.
- “How was he last week?” is read as last week. Ask for a period it cannot look back over and it says which one it did read.
- After an answer: “shorter”, “more detail”, “just the figures”, or “and before that?”.
- Ask where to do something in the panel and it names the screen and the button — and says so when a thing does not exist.
- Past conversations can be searched and reopened without asking again, and reading one costs nothing.
What it is not.
A second opinion. It will not advise on a dose, choose a medicine, name a condition or its cause, forecast readings or plan care — it says so before it reads a single record. It finds nothing you could not open yourself, and nothing it says is a clinical recommendation. Every judgement is still yours.
Up to 200 questions a day for each person. Conversations are kept for 90 days. A member of staff can use it once you give them it; they ask as themselves, it reaches only what their own access opens, and nobody reads anybody else’s conversations.
Limits
What you will never see, said now.
Finding out a limit later feels like being misled. Being told at the start reads as the system working — which is what it is.
- Anything the patient has held back from you.
- What they ask the assistant. There is no permission for it and no screen that could show it — and they cannot share it with you either, on purpose.
- The photographs behind their meal estimates. You see their note and the estimate, never the picture.
- Their record, from the moment they disconnect — which they can do without telling you.
- Their password. Nobody holds it, including us — it is stored in a form that cannot be turned back.
- A patient who has not connected you. Ask for one and the panel answers as though there is nobody there.
And the other way round: what you can open is the patient’s to decide, area by area, and it is decided where the records are rather than in the page that draws them. A category they have switched off is refused, not hidden: you are told it is not shared, so you always know whether you are looking at a whole record or part of one.
And what we can see, which is less.
You are being asked to put patient records on somebody else’s servers. What that somebody can read is a fair question, and it has a specific answer.
- We cannot open a patient record
- Not support, not the people who build this. It is blocked in the code rather than by leaving a button out, and a test checks that it stays blocked. The same holds for your wards, bills and stock.
- What we see is accounts, not health
- For your practice: how many patients are connected, how many staff you have, your plan and what has been invoiced. For a patient's own account — to carry out an erasure they ask for — their contact details and how many records it holds. Never a reading, a note or any other clinical value, and never a check-in photo.
- Archived, not deleted
- What a doctor or a practice removes is archived, and restoring it brings back exactly what was archived. Nothing a doctor, a practice or a plan does erases a patient's record. A patient can ask to be erased.
Money
Four things money never touches.
A patient record that changes because an invoice went unpaid is a record nobody can rely on. These four are why that does not happen.
- Nothing is deleted to enforce a limit
- Not when you change plan, not when one lapses, not if you leave. A practice above its patient limit keeps every patient it has — it just cannot add another until it is back under.
- Your patients never see your billing
- If a practice has not paid, its own staff go read-only. The patient's app does not change, and you are never shown to them as unpaid or suspended.
- Emergencies are never blocked
- A practice behind on payment still gets emergency alerts and can still acknowledge them, on the panel and on the phone. There is no money problem that closes that path.
- Refusals say what is missing
- “You have view-only access to appointments”, not the word Forbidden. An error nobody can act on becomes a phone call to us.
Asked for once, invoiced once.
Every plan and add-on is listed with its price, on the panel and on the phone. The owner asks for a change — a plan, add-ons in or out, monthly or yearly — with an estimate; we approve it and send one itemised invoice for everything in the request, paid by bank transfer.
And we check every doctor by hand.
Accounts are checked by a person, not approved by a form — so it is not instant, and your request gets read rather than processed. Choose a plan first, then request access: the call starts from what you chose.
What to send
- The plan you chose on the pricing page, and any add-ons — the request form fills them in when you come from there.
- Your name, and the clinic or hospital you work at.
- Your registration details, so we can check them.
- The email address the account should use.
- Roughly how many patients you would connect, how many staff would sign in, and how many beds you run — so we can check the plan fits.
What is built
- Plans and add-ons, listed with their prices
- Changes asked for from the panel or the phone
- One itemised invoice per approved request
- Invoices and receipts as PDFs
Before you ask
Questions doctors ask.
What does it cost?
Can it run a hospital ward?
Is there an app for doctors and staff?
Can it run my staff's attendance and pay?
How do I pay?
How do I get an account?
Can I trust the numbers?
What if a patient disconnects me?
Can I write prescriptions in it?
Can my staff use the assistant?
How is it protected?
Bring the practice, the team and the ward onto one platform.
Choose a plan, ask for an account, and a person sets it up with you.
Glycoz keeps records and carries messages. It is not intended to be used as a medical device and has not been assessed as one; it does not diagnose, and it does not make clinical recommendations. Every clinical decision stays yours.
