OpenClinTech

Clinician-engineers

What is a clinician-engineer?

A clinician-engineer is a clinician who can also build software. They understand clinical work from the inside, and they know enough about health data, standards and engineering to design, build and ship the tools that support it. (You'll also see it written without the hyphen, as clinician engineer. It's the same role.)

Why healthcare needs more of them

Most healthcare software is built by people who have never worked a clinical shift, and most clinicians who see what's broken have never been able to build the fix. Clinician-engineers close that gap. They can spot a workflow problem on the floor, understand how the data behind it moves, and build or direct the software that fixes it.

AI coding tools have made that path far more reachable than it was a few years ago. A clinician no longer needs a computer science degree to ship working software, but they do need to understand what they're building and why.

What clinician-engineers know

  • Clinical workflows, and where they break.
  • Health data standards: the HL7® FHIR® standard, clinical terminologies and Implementation Guides. See interoperability training.
  • Clinical informatics: how EHRs, clinical decision support and health data flow work in practice.
  • AI: what large language models can and can't do, and how to use them safely. See Basics of Artificial Intelligence.
  • How software ships: repositories, deployments, databases and authentication, enough to own a product from idea to launch. See the bootcamp.

Who becomes a clinician-engineer

Physicians often start with a workflow they live with every day: an order set, a handoff, a documentation burden. Many already work in clinical informatics, and building lets them prototype a fix instead of only specifying one.

Nurses sit at the center of documentation and care coordination, and nursing informatics is one of the longest-established informatics specialties. Nurses see where information gets lost between people and systems.

Pharmacists work where medication data, clinical decision support and safety meet. Pharmacy informatics is how OpenClinTech's founder started.

Dentists often run their practices on their own software, and dental informatics covers records, imaging and the gap between dental and medical care.

Biomedical and health informatics professionals already bridge clinical and technical work. Building skills let them test ideas directly.

Not a clinician? Engineers, product managers (including AI product managers), policy teams and leaders work beside clinician-engineers every day. Start with the interoperability courses or Basics of AI.

How to become one

  1. Learn how health data moves. Start with the HL7® FHIR® standard: interoperability training.
  2. Understand what AI can and can't do. Basics of Artificial Intelligence.
  3. Build something small and real. Building Simple Web Apps in Healthcare.
  4. Ship a real app with a cohort. The Clinician-Engineer Bootcamp, two weeks with 1:1 mentorship.
  5. Thinking about a career move? Navigating Health Tech (Pro).

From the founder

OpenClinTech's founder has written about both halves of the path:

  • Path of The Clinician Engineer: why to start with computer science fundamentals before chasing AI, how public health shifts your thinking from individual patients to populations, and why learning to program isn't the same as learning computer science.
  • Building Healthcare Software as a Pharmacist: teaching himself software development as a pharmacist, from SQL and FHIR® to clinical decision support and AI projects, by learning, tinkering and failing.
Join the bootcampExplore courses