Counsel raises $25M Series A. Access now open to all.learn more

Why we built our own EHR

Team insights

Why we built our own EHR

Table of Contents

icon

      The modern front door to healthcare is just one click away

      KEY TAKEAWAY

      Walk into any clinic today and ask a physician how they feel about their EHR. Odds are, you’ll hear about inefficiency, clunky interfaces, and how much time it takes away from patient care. That’s because most EHRs weren’t designed by people who actually practice medicine.

      At Counsel, we’re both.

      We’re physicians and engineers rethinking the foundation of clinical care. Our mission is to multiply the world’s clinical capacity, and to do that, we’re building an asynchronous-first care model from the ground up. Deciding whether to build or buy a homegrown EHR wasn’t an easy decision. We had many late-night discussions and constantly went back and forth, but ultimately realized that our vision wouldn’t be possible with legacy EHRs that are built for a visit-based, reimbursement world. We needed infrastructure purpose-built for how we deliver care, not the other way around.

      So, we built our own custom EHR.

      What is an EHR?

      An electronic health record (EHR) is a secure digital system that stores all of a patient's health information, including medical history, prescriptions, lab results, and doctors’ notes. EHRs enable clinicians to access accurate, up-to-date information quickly, facilitating safer and more personalized care. 

      When designed well, they create a seamless health story that enhances coordination and improves patient outcomes.

      5 common EHR usability challenges

      Despite their benefits, most electronic health record systems create common frustrations for clinicians. Here are the main EHR usability challenges seen in practice:

      1. Inefficiency: Many EHRs slow down care by requiring clinicians to complete redundant forms, switch between multiple screens, and repeat steps that don’t align with their workflow. This added complexity means doctors spend more time on the computer and less time directly with patients.​
      2. Clunky interfaces: Interfaces are often confusing, cluttered, and unintuitive. Poor design can make it hard to find vital information, leading to delays and frustration.​
      3. Lack of interoperability: Some systems don’t integrate well with others, hindering the easy sharing of patient information across different clinics or departments, even when continuity of care depends on it.​
      4. Mismatch with clinical workflow: Workflows built into EHRs often don’t match real clinical practice, forcing clinicians into workarounds and extra steps that lead to errors or missed tasks.​
      5. Risky automation and defaults: Automated settings, such as default drug dosages or auto-filled dates, can be unclear and lead to mistakes unless clinicians review them with every entry.

      Solving these challenges is key to making EHRs safer, faster, and more helpful for every patient and care team.

      Building vs buying an EHR

      When we set out to transform healthcare, we faced a simple but critical choice: Should we buy an EHR system, or build our own from scratch.

      When we started evaluating EHRs, We found most EHRs to not only be visit-centric, but also built around scheduling, billing codes, and in-person clinic workflows, which limits their utility to supercharge our care model. While newer EHRs provide UI flexibility, most don’t meet the requirements for enabling the speed and flexibility required to iterate and build a best-in-class asynchronous care experience.

      Off-the-shelf EHRs get clinics up and running faster, but they have their own set of limitations. They can’t easily adapt to advanced personalization, fast iteration, or unique workflows.

      Our vision demanded more. Building a custom EHR gave us full control to design smart routing, secure messaging, and continuous care features that evolve with the needs of both patients and physicians. While this required a higher upfront investment, the flexibility and ownership it gave us were essential for truly personalized care.

      Why our model doesn’t fit traditional systems

      Counsel offers unlimited, on-demand access to licensed physicians via messaging. That means no appointments, phone trees, or waiting rooms. Patients message us directly through our app and hear back from physicians within minutes. This model is optimized for accessibility and continuity, with physicians providing ongoing support and advice through a friendly, easy-to-use chat interface.

      Unlike traditional in-person care or telehealth appointments, Counsel is creating a new care model that’s designed for responsiveness, personalization, and longitudinal support.

      The advantages of owning our full EHR stack

      To build the kind of care experience we envisioned, we needed full control over the underlying infrastructure. A custom EHR allowed us to:

      • Own the request cycle end to end: By implementing the frontend UI and backend ourselves, we have full agency on how to architect our application. This includes configuring how to load components, what data to cache on the client vs server, etc.
      • Define our own data schema: We built a schema tailored to our unique workflows, tying directly into our app’s core logic, including authentication, routing, and patient context.
      • Integrate AI across the product experience: Our stack allows us to embed AI at every layer, from context-aware summarization to LLM-powered note generation. We control which models we use and how they’re deployed, giving us freedom to experiment and iterate.
      • Avoid prescriptive vendor limitations: Controlling both frontend and backend lets us rapidly experiment with new clinical workflows, rather than being limited by an EHR vendor’s APIs or rigid setup.

      The result of owning our EHR: speed, flexibility, and personalization

      This ownership has allowed us to move quickly and build with precision. Many of our most-used features were developed directly from physician feedback, sometimes in less than 24 hours. Highlights include:

      • Queue-based triage: Physicians work through structured message queues, not arbitrary inboxes
      • Smart routing: Messages go to the right physician, even across shifts, user profiles and time zones
      • Scheduled messages: Physicians can queue messages to send later, enabling proactive follow-up
      • Contextual UI: Our EHR surfaces details about patients’ payer or employer context to tailor care and documentation
      • Outbounds: Physicians can proactively send outbound messages to patients to stay in touch about their health in a personalized manner over a patient’s preferred medium (sms or push).
      • Physician co-pilot tools: LLM-powered features like conversation summarization, note drafting, and context recall reduce cognitive burden

      By building for our exact needs, we’ve created an EHR that not only powers our current care model, but also adapts with us as we scale and evolve.

      Why now is the right time to build an EHR System

      Just a few years ago, building an EHR meant starting from scratch. Today, a growing ecosystem of modular, API-driven tools has made it possible to build what we need. We’re not reinventing the wheel, but assembling best-in-class building blocks that let us focus on our differentiators: experience, care quality, and the physician-patient relationship.

      None of this is easy. Building an EHR requires significant investment. Collecting and structuring data across multiple systems to make it actionable is complex and ongoing. Each third-party integration also brings trade-offs and operational complexity. However, we’re confident the investment is worth it. Over time, our system will develop a working memory of patient-physician conversations with minimal documentation burden.

      That’s not just better infrastructure. That’s better access to the highest quality healthcare.

      For us, building an EHR wasn’t just a tech decision. It was a clinical one, as well.

      The modern front door to healthcare is just one click away

      Sources
      Dr. Dave Whitehead
      Dr. Dave Whitehead
      Clinical Product Lead

      Dr. David Whitehead is a member of the Clinical Product team at Counsel Health. A practicing emergency physician, he focuses on building clinical tools that empower clinicians to deliver high-quality asynchronous care. Previously, Dr. Whitehead advised digital health startups on clinical, operational, and strategic challenges and led the development of an asynchronous care program at Brigham and Women’s Hospital to improve post–ED discharge care transitions.

      Dr. Dave Whitehead
      Dr. Rishi Khakhkhar
      Chief Medical Offier

      Dr. Rishi Khakhkhar is CMO at Counsel Health. A practicing emergency physician and founding team member, he leads the clinical team in building best-in-class asynchronous care models. Previously, he served as Medical Director of Mount Sinai’s Virtual Urgent Care, the health system’s largest telemedicine service, and led emergency department operations for Hospital-at-Home while supporting mobile integrated health initiatives across the care continuum.

      Our content is created for informational purposes and should not replace professional medical care. For personalized guidance, talk to a licensed physician. Learn more about our editorial standards and review process.

      Counsel raises $25M Series A. Access now open to all.learn more