WithinEHR — the clinician record, the patient portal, the consultation

Health software is unusual in that the interesting problems are almost never "make this screen exist".

They are the states that actually happen to a clinician. A consultation interrupted halfway through. A record that must not be saved half-written. A connection that drops on a ward with bad signal, on a device that was already three years old when it arrived. Get those wrong and the software is worse than paper, because paper does not silently lose the middle of a sentence.

I built the interface across four surfaces, each with a different user wanting a different thing from the same underlying record.

The clinician EHR is the core of it, and it needs density — tables, filters, a lot of information at once, and no hunting for the thing you need mid-consult. The patient portal needs the opposite: one thing at a time, in language nobody has to decode, for someone who may be anxious and is definitely not a clinician. The telehealth consultation needs the call to hold while both of them are doing something else. And an embeddable widget had to carry a slice of all that into somebody else's page without bringing the whole application with it.

The thing that made three surfaces tractable was treating the component system as the actual product. Tables, forms, filters, modals and navigation were built once, properly, and then reused — so a new screen is an afternoon rather than a week, and all three surfaces stay consistent without anybody policing it.

Everything sat on REST APIs owned by other engineers, which meant the work ran on agreed contracts and frequent conversations rather than assumptions. On a platform handling patient data, where correctness and access control are not negotiable, that is the only way it works.