Medical Group Internal Platform (EIP)
The client had an ERP of its own — this platform touches none of it
What was missing was not an ERP
The client already had one, and it did its job. What was missing was different: staff across branches had no way to know what the others were doing, whether a doctor was in today, where the notices were, or who to call when something broke. So this platform touches the ERP not at all; the line is drawn on the human side.
"Visibility" is not "approval"
Leave and clinic closures appear here as a category on a shared calendar, not as an approval workflow. The question the system answers is "who is not in today", not "is this leave granted". Turning it into an approval flow would have forced the client to change a leave process that was working — not what they asked for, and not my call to make.
The calendar on the home page was built from scratch, deliberately
Off-the-shelf calendar components existed, but they did too little. This one had to gather a dozen kinds of dated item — notices, leave, closures, maintenance, group-buying, appraisals — and keep growing, roughly the flexibility everyone now expects from Google Calendar. Rather than be limited by what someone else's component could do, I built one I controlled completely, so anything added later was my decision to make.
The appraisal module turned into something else
Appraisals here were built as a scored questionnaire: change the settings and the same thing becomes a poll, an exam, an appraisal, or a Q&A. I later folded that abstraction into my own content module and used it for years afterwards.
FAQ
Something similar in mind?
Tell us the thing that is currently costing you the most time. We will tell you whether it is worth building before we talk about how.
Request a quote