Eleven modules · one clinical record · See all
The capture engine

Attribute Box
coded at the speed of writing.

Every terminology-bound clinical system asks the clinician to walk a hierarchy. This one asks them to type what they were going to write anyway — and does the binding underneath.

No internet — still working
Type 1 fever or 4 pcm 650 1-1-1 x3d
1 complaint · 2 test · 3 diagnosis · 4 medicine
1complaint2test 3diagnosis4medicine

This is the real control — try it.

Standards & complianceSNOMED CT·LOINC·ICD-10/11·ATC·UCUM·NLEM
The inversion

A search bar, not a hierarchy.

The reason terminology-bound software fails at the point of care is not the terminology. It is the interface built on top of it.

Conventional
Search, scroll, drill

Type a term. Read fifteen results. Walk an eight-level hierarchy breadcrumb. Set duration across four fields. Add a relationship. Commit.

60–90 seconds. For one complaint.

The Attribute Box
Type what you would write

1 fever 4d — domain key, the word you already use, and the duration in the shorthand you already write.

Under 4 seconds. Coded.

The clinician never sees a code, a hierarchy or a dialog. The record is fully coded anyway.

The grammar

One control. Four keys.

The first character selects the clinical domain and the terminology behind it. Everything after it is the query, in the words the clinician already uses.

1
Complaint or finding — SNOMED CT

1 fever 4d · duration, severity and laterality captured as attributes, all optional.

2
Investigation — LOINC

2 cbc · orders from the consultation, results attached to the same encounter.

3
Diagnosis — ICD-10 / ICD-11

3 typhoid confirmed · 33 dengue differential. Held apart, because they are different clinical assertions.

4
Medication — ATC

4 pcm 650 1-1-1 x3d · positional frequency, because that is how Indian prescriptions are already written. Brand resolves to substance.

Where it is hard. Digits collide with clinical numerals. 2 days of vomiting looks like an investigation query; 3rd episode looks like a diagnosis. The parser enters a domain speculatively and reverts to plain narrative, silently and with no keystroke lost, when nothing matches — and a unit and ordinal exclusion list catches the rest before a domain is ever opened. This is the hardest correctness problem in the design and it is measured in the field, not assumed away.
What is stored

The code, and the words
that produced it.

AlwaysOriginal text

Verbatim, on every entry, including coded ones. The only ground truth when a mapping is later found wrong.

AlwaysCode + system + version

Distinguishable from a later revision of the same terminology, permanently.

AlwaysProvenance

Author, registry identifier, device, timestamp, input mode, index version.

OptionalAttributes

Duration, severity, laterality, dose, frequency, route. Skipping every one still yields a valid coded entry.

Voice, in the same path.

Speech is transcribed and routed through the same parser as typing — there is one capture path, not two. Spoken domain cues map to keys; every voice entry is visually distinguished and requires an explicit commit.

Medication dose and frequency derived from speech are always displayed for confirmation before commit. A silent misparse of a dose is a patient-safety event, and this is the control that prevents it.

Outcome — a coded record produced by work the clinic already wanted to do.
Get started

See it against your own pad.

Time yourself. If it is not faster, that is the most useful thing you can tell us.