The Choices behind the WorkValues are how we Show up.
Especially when it’s Difficult.
These are the standards we want to hold ourselves to—in a design discussion, a code review, a difficult conversation and the way we treat one another.
01 / Care before CodeStart with the Person, not the Feature.
A clinician’s busy day. A patient repeating their history. A team trying to find the right information. Understanding those experiences is where useful engineering begins.
In practice: ask who a decision helps, and who it might make things harder for.02 / Curiosity without EgoAsk the Question that needs asking.
Nobody has every answer. We value people who listen closely, challenge an assumption thoughtfully and make room for a perspective they haven’t considered.
In practice: understand the workflow before deciding what to build.03 / Ownership with HonestyBe someone others can Count on.
Trust grows when people know what is happening. We believe in making commitments carefully, raising risks early and staying involved when a problem needs solving.
In practice: bring the issue, the context and a path forward.04 / Craft that LastsCare about what happens after Launch.
The next engineer should be able to understand the system. The next user should be able to trust it. Good work includes the testing, documentation and less-visible details.
In practice: make the handover as thoughtful as the first demo.05 / Progress TogetherShare what you Learn.
A useful discovery should not stop with the person who made it. We want questions, feedback and knowledge to move freely—inside our team and through the open-source work we share.
In practice: explain the why, help a teammate and leave things clearer.06 / Human Judgment MattersUse Technology with Responsibility.
AI can expand what we build. People still bring empathy, context and accountability. We believe the strongest healthcare products respect that distinction.
In practice: keep meaningful oversight and clear ownership in the workflow.