Design Decisions

Every product reaches moments where multiple paths seem reasonable.

These are the decisions that fundamentally shaped HealthFirst.

One timeline. Many outputs.

One of the earliest decisions was deciding where clinical information should live. Everything else followed from there.

Most hospital software asks users to choose a document before they start writing. Progress notes, nursing sheets, OT records, discharge summaries and insurance papers all become separate workflows with their own forms.

HealthFirst stores everything in a single patient timeline. Doctors, nurses and staff contribute to the same clinical record, while every document is generated from that shared history. Writing information once and reusing it everywhere eliminated duplicate forms and kept every document consistent.

Generate documents. Don’t edit them.

Hospitals traditionally treat documents as the primary record. That works until something changes.

Updating a diagnosis or medication often means finding every affected document and editing each one separately. It doesn’t take long before different copies disagree.

HealthFirst stores structured clinical information instead. Discharge summaries, insurance papers, certificates and reports are generated whenever they’re needed. Updating the patient’s record automatically updates every future document without creating conflicting versions.

Workflow gates instead of reminders.

Our first instinct was simple: remind people when documentation was missing.

The reminders worked.

People still continued.

The real problem wasn’t awareness—it was that the workflow allowed patients to move forward with incomplete documentation.

HealthFirst eventually stopped treating reminders as the solution. Critical documentation became part of the workflow itself. Patients cannot move to OT without verified consent, cannot leave Recovery without required assessments, and cannot be discharged until mandatory reviews are complete.

Configuration instead of customization.

Every hospital had its own way of working. Some required digital signatures, others preferred OTP verification. Some enforced strict discharge reviews, while others followed different approval processes.

Building separate versions of the product for every hospital wasn’t sustainable. Building one rigid workflow wasn’t practical either.

HealthFirst keeps the core workflow consistent while exposing hospital-specific policies as configuration. Hospitals adapt the software to their processes without creating another product to maintain.

Start with the complete admission.

Most hospital software begins with OPD because it’s the largest workflow.

HealthFirst deliberately started with IPD.

The biggest documentation problems appeared after admission—daily progress notes, nursing documentation, OT records, discharge preparation and insurance paperwork. Solving those workflows first meant building around the complete patient journey rather than adding inpatient care to an OPD-first product later.

OPD was introduced afterwards, but the product was designed around the entire admission from the beginning.

One application for every device.

Doctors move between desktops, tablets and phones throughout the day, but the workflow rarely changes.

Maintaining separate Android, iOS, Windows and macOS applications would have multiplied engineering effort without improving the experience for hospital staff.

HealthFirst was built as a Progressive Web App. A single codebase runs across every supported device, simplifies deployment and ensures users always have the latest version without managing platform-specific releases.

A modular monolith.

Microservices were an option from the beginning.

We deliberately ignored them.

HealthFirst was changing every week, served only a handful of hospitals and was being built by a single founder. Splitting the system into independently deployable services would have increased operational complexity without solving a customer problem.

A modular monolith kept the product easy to change while maintaining clear boundaries between domains such as patients, documentation, AI, billing and administration.

Keep the AI replaceable.

One thing became obvious very quickly: the AI layer was going to change.

Prompts changed.

Models changed.

Even the way information was extracted changed as we learned from hospitals.

Rather than coupling the product to a specific model or provider, HealthFirst was designed so that AI could evolve behind the workflow. As long as structured clinical information reached the patient timeline, the surrounding product remained unchanged.

The workflow became the stable part of the system. The AI could improve independently.

Security follows hospital policy.

Hospitals differ in how they manage access. Some allow personal devices, others require hospital-owned computers, while some restrict access to approved networks.

Instead of enforcing a single security model, HealthFirst lets each hospital define its own access policy using combinations of registered devices, network restrictions and role-based permissions.

The software adapts to existing hospital policies rather than asking hospitals to change how they operate.