Glycoz for Clinicians
A brief, in nine parts
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, sleep and activity. When one connects you, what they share appears in your browser exactly as they recorded it.
- They already keep the record
- You read what they chose to share, as they recorded it. Nothing to import and nothing to chase.
- No integration, and almost no admin
- A browser, and a code you give a patient. No software to install and nothing to connect it to.
- What you can open is theirs
- Decided area by area, by the patient, and enforced where the records are rather than in the page.
The gap
Three problems, and one cause.
Your patient lives with this every day. You see a slice of it every few weeks, and the slice arrives second-hand.
- 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.
- What you can open is theirs to decide
- Area by area, and separately for each doctor. They can close one at any time without telling you, and it takes effect on your very next request — so the panel is always showing you what they are content for you to see.
Where to start
The list tells you who to look at first.
Not in alphabetical order. Two lists, kept apart: Act now, for unsafe readings and patients waiting on a reply, and Drifting, for patients who are fine today but heading the wrong way. A dangerous low and a slow drift need different things from you.
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
- Wearable analytics
- Wearable data
- 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.
- Wearable analytics and Wearable data
- Sleep, resting pulse, steps and oxygen from the watch they already wear, as charts and as a log. Kept apart from what they typed — when the two disagree, both are true, and merging them would quietly pick a winner.
- 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. An alert reaches you by email and in the panel's emergency bell. 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.
Worth knowing before you write anything. 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 sits in the sidebar, belongs to no patient, and goes nowhere. Everyone keeps this somewhere; this is somewhere sensible.
What it asks of you
How much work is this? Almost none.
That is the point. A tool that makes more admin gets dropped within a fortnight, however good the charts are.
- Nothing to install
- It opens in the browser you already use. No software, no plugin, nothing to connect to whatever the clinic runs.
- 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, 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 in amber, “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. They answer different questions and neither is the simple version of the other.
- 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.
- Two bells, kept apart
- One for emergencies, one for booking requests and cancellations. Both update on their own and open beside the day rather than on top of it, so you can still read 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.
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.
| 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. It is the kind of default that is either right or causes a fortnight of confusion.
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. Just “declined” tells someone nothing about where to look next.
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: the directory is new, and it is only as useful as the number of clinics in it. 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 — and their practice has an active subscription, not a trial, on a plan that includes a listing. Nobody is listed in it yet, and it will be thin for a while. We would rather say that now than let you find out after you have filled the form in.
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 doctor, so it reaches nothing you could not open yourself. 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.
What it is not.
A screening tool or a second opinion. It declines dosing, choosing a medicine, diagnosis, prediction, treatment planning and naming a cause before it reads a single record. It does not spot, flag or catch anything, and nothing it says is a clinical recommendation. Every judgement is still yours.
Up to 200 questions a day. Conversations are kept for 90 days. It is for the practice’s own doctor; staff accounts cannot ask it questions.
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.
- 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.
- 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. 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.
And we check every doctor by hand.
Glycoz is early. Accounts are checked by a person, not approved by a form — so it is not instant, and your request gets read rather than processed.
What to send
- 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, and how many staff would sign in — that decides which plan fits. The assistant is on every plan.
Before you ask
Questions doctors ask.
What does it cost?
How do I pay?
How do I get an account?
How much of my time does it take?
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?
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.