Our Work

Artemis

Clinical care · Pediatric heart transplant

A pediatric heart transplant team's shared signout and patient course, from referral and evaluation through listing, mechanical support, transplant, and long-term follow-up.

Field
Clinical care
Platform
Web, on the hospital network
Technology
Elixir, Phoenix LiveView, Yjs, and SQLite
Status
Preparing for clinical use

Two People, One Note

Signout follows I-PASS: illness severity, patient summary, interval events, if/then contingencies, a note for each system, the to-do list, medications, the device's last reading, and the last biopsy.

The free text is a shared document. Two people can type in the same box at once, and their edits merge character by character. Nothing locks, and everyone sees who else is in the chart.

The Protocol, Where It Applies

The program's own guidelines are converted from Word into Artemis, searchable by section, and quoted in the chart where they apply to the child in front of you.

Where the chart does its own arithmetic from the protocol, such as when a child's 1A status must be recertified, or the tacrolimus target at this point after transplant, automated tests check every number against the guidelines. If a new edition changes one, the tests fail, and the software is updated before it can disagree with the document.

Protocols
Pediatric Heart Transplant and MCS Clinical GuidelinesFor clinicians · 2026 edition

8.6 Why good hearts get declined — and how we guard against it

Herding (being influenced by the number of prior refusals), loss aversion, attention to recent bad outcomes, and program metrics all push toward declining. The program counters these by:

  • deciding on the donor data and this recipient's risk, not on the offer's sequence position;
  • requiring the cardiologist to state the recipient's expected waiting risk when declining;
  • reviewing every decline monthly, including what happened to the heart and to the candidate;
  • reviewing the program's offer acceptance rate ratio (SRTR / OPTN MPSC metric) at QAPI.
An excerpt from the program's guidelines, written by our founder.

Medications With a Memory

Medicines are entered from a built-in formulary of about 170, found by generic name, brand, or shorthand. Every start, change, hold, resume, stop, and drug level is logged: when it took effect, why, and who entered it. Per-kilogram doses are worked out at the current weight.

Built for Protected Health Information

Every read or change of a chart is checked against the person's role on the server, not just hidden in the page. The audit log records every sign-in, chart opened, print, and change, naming the fields and never the values. No patient detail is ever written to a log.

Live co-editing

A shared document per patient, so edits merge as people type and every change is signed.

Exception renewals

Renewed every 14 days; checking one off writes the next onto the to-do list.

Mechanical support

Device, strategy, and readings: speed, flow, power, PI, MAP, LDH, and INR.

The course, in order

A timeline with phase and status changes written in on their own.

Ready for rounds

A print view of the whole signout, laid out for paper.

Readable for everyone

Each person sets the text size on each computer, from 90 to 150 percent.

Designed by a Pediatric Cardiologist

Artemis was designed by Archetyp's founder around the way a transplant team actually hands off: severity first, the contingencies spelled out, and the next deadline never out of sight.

0locks, so everyone can edit at once
170medicines in the built-in formulary
14days between exception renewals, scheduled for you