Medicity

Problem

Medicity spans patient, doctor, laboratory, franchise and employee operations across a super-franchise → franchise → sub-franchise structure — and needed to integrate with lab/medical instruments over connections that can't be assumed reliable.

Engineering challenge

Healthcare software cannot assume the network will always cooperate. Instrument and lab integrations needed to survive a dropped connection without losing or duplicating a result, which meant designing for offline capture and reconciliation as a first-class case, not an edge case.

What I built

• Integration workflows for medical/lab instruments built around offline capture, retry and deterministic reconciliation back into the CRM record
• Franchise hierarchy (super-franchise → franchise → sub-franchise) enforced through access, ownership and data segregation rather than convention
• Multi-level employee approval workflows spanning branch transfers, leave and role-specific permissions
• Domain modelling across interconnected doctor, patient and membership modules — specialization, consultation configuration, membership plans and renewals

How it works

Outcome

Reliability work here means the boring outcome is the good one: instrument results reconcile correctly even when the connection didn't cooperate, and franchise data stays segregated without manual policing.

Domain

Selected implementation and client details are intentionally omitted — this work was delivered as client engagement.