Nursana — a project by Ahsan Mahmood
Cross-platform SaaS for nurses bundling calculators, credential tracking, an on-device shift brain sheet, wellbeing, and more into one app.
A nurse's phone already has six applications on it and none of them talk.
One for the drug calculation. One tracking when a licence expires. A notes application standing in for a handover sheet. Something for the practice questions.
And the things with no application at all, which end up on paper in a pocket and go through the wash.
Nursana is an attempt to make that one thing.
Nine modules, and the list reads oddly until you notice what they have in common: offline calculators for the point of care, a wallet tracking licences and continuing education, an on-device shift sheet, anonymous wellbeing check-ins, schedule tracking with fatigue flags, practice questions, finance tools, a private incident vault, and a verified community.
They have in common that each one is a thing somebody currently improvises.
The improvised versions are a calculator application, a phone reminder, a folded piece of paper and a group chat. None of those were designed for the job, and the paper one goes home in a uniform pocket carrying information it should not be carrying.
Which is why the brain sheet stays on the device.
It holds patient information, and the design keeps that off servers entirely rather than protecting it on them. There is an export in a handover format for when it needs to leave. That constraint is not a compromise made to save money. It is the thing that makes the feature safe enough for one person to have built.
The product draws three lines and stays inside them.
Reference rather than advice. Wellness rather than therapy. Documentation rather than legal guidance. Each marks where the software stops and a human takes over.
Those lines matter more than any module above them.
A calculator returns a number and does not decide whether a drug should be given. A check-in records how somebody is and does not treat them. A vault holds a record of what happened and does not say what anybody's rights are. Software for a clinical audience that blurs those boundaries is not being helpful, it is accumulating liability on behalf of its user.
The wellbeing check-ins are anonymous by design, and route outward.
Where a response indicates someone needs more than an application, the design points to external help. The important word is external. Noticing and pointing outward is a legitimate thing for software to do; responding is not, and the distinction is the difference between a wellbeing feature and one pretending to be a service it is not.
There is a reason a subscription product for nurses is difficult to build on a free tier, and it shapes the module list.
Anything genuinely clinical would need a maintained data source, a validation process and somebody accountable for it. So the modules that exist are the ones where correctness lives in arithmetic and in the user's own records rather than in a body of knowledge somebody has to keep current. That is a real boundary on what this can become, and it is drawn deliberately rather than discovered later.
What it cost is time.
This is early. The architecture, the branding, the design system and the module scaffolding exist. The platform layer and the modules themselves are being completed in waves, there is no confirmed address and no store listing, and nobody is relying on any of it during a shift. On a product for clinicians that gap is the most important thing on the page, and it belongs near the top as well as here.
What it does, and what that costs to build
- Offline point-of-care calculators for drip rates, weight-based doses, and conversions
- Credential wallet tracking nursing licenses, certifications, and CE renewals
- On-device shift brain sheet with EHR-ready SBAR export and zero PHI on servers
- Anonymous-by-design wellbeing check-ins with high-risk routing to external help
- Schedule tracking with fatigue-safety and circadian flags
- NCLEX-style practice questions with rationales for students and new grads
- Private advocacy and incident vault with state-rights references
- Runtime theme customizer with five accent palettes and light/dark support
Built with
- React 19
- TypeScript
- Vite 6
- Capacitor 8
- Tailwind CSS v4
- Radix UI
- Zustand
- TanStack Query
- React Router 7
- Firebase (Firestore, Auth, Functions)
- Cloudflare Workers
- D3
Worth knowing
- nursing
- healthtech
- saas
- cross-platform
- capacitor
- react
- firebase
- privacy-first
What state is Nursana in?
Early. The record puts it at an initial version with the architecture, branding, design system and module scaffolding in place, while the platform layer and the feature modules are still being completed in waves. There is no confirmed live web address and no published store listing. So the nine modules described below are designed and scaffolded rather than finished, and nothing here should be read as a tool anybody is currently relying on during a shift.
What are the safe lanes?
Three boundaries the product is designed inside: reference rather than advice, wellness rather than therapy, and documentation rather than legal guidance. Each marks where the software stops. A calculator gives a number and does not decide whether to give a drug. A check-in records how somebody is and does not treat them. A vault holds a record of an incident and does not tell anybody what their rights are in law.
Why is the brain sheet on the device?
Because it holds patient information and patient information does not need to be on anybody's server. A shift brain sheet is the working note a nurse keeps through a shift, and the design keeps it local, with an export in a handover format when it needs to leave. Nothing about that is a limitation being worked around. It is the reason the feature can exist at all inside a product built by one person.
How do the wellbeing check-ins work?
Anonymously by design, with routing to external help where a response indicates it. The important word is external: the product's role is to notice and to point outward, not to respond itself, because responding would be therapy and this is not that. What that routing points to is not something this page will state, since a support contact printed in a portfolio and left there is worse than no contact at all.
Does Nursana work on iPhone?
There is no Apple release. One codebase targets web, mobile through Capacitor and desktop, and the record lists iOS among its intended targets, which describes configuration rather than something published. No Apple Developer account sits behind this work and nothing I build has shipped to the App Store. The record also confirms no live address and no store listing, so there is nothing to open on any platform yet.
https://aoneahsan.com/projects/com.aoneahsan.nursana