MedicusBuilt on shift, for the shift.
Medicus is written by a practicing emergency physician who was tired of finishing charts after the shift ended.
Every documentation tool an emergency physician is handed was designed for somewhere else. Clinic software assumes one patient, one room, one uninterrupted conversation. The emergency department is the opposite: eight rooms open at once, a story that changes when the labs land, and a chart that has to hold together at the end of it.
Medicus started as a spreadsheet on a shift. Notes went in one side, and the sections a chart actually needs came out the other. It grew into a desktop app because that is where the work happens, and because a chart that lives on your own machine is easier to defend than one that does not.
It does not listen to the room. There is no microphone, no recording, and nothing to consent to or store. It works from the notes the department already produces, the way you already write them.
It writes the way your department writes. The rules that shape every draft are written in plain language by the physicians who use it, versioned, and published to every install. They are not a vendor's template.
Four things that decide what gets built.
The physician signs the chart.
Medicus drafts. Every word is reviewed, edited and attested by the clinician before it enters the record. Nothing is written on your behalf that you did not supply.
Nothing is recorded.
No ambient audio, no transcription, no retention policy for a microphone that never existed. That is a design decision, not a feature we have not gotten to.
Say what the software does.
No compliance badges we have not earned, no numbers we have not measured. If something is planned rather than shipped, the site says so.
Built at the pace of the department.
The person writing the code works the shifts the software is for, which is why it is judged on a busy night rather than in a demo.
Desktop first, signed, and yours to control.
A desktop app
Windows today, macOS in progress. Charts are saved on the machine that wrote them, not in our cloud.
Signed releases
The installer and every update are code-signed and verified before they run, so an install cannot be quietly replaced.
Rules you publish
Your department's documentation rules live in your organization's hosted library, versioned, with draft, publish and rollback.
See it on your own notes.
Bring a de-identified chart to a 20-minute demo and let the board do the talking.
Request a demo Download for Windows