Software for healthcare organisations and medical teams

Working with medical organisations changes what a project is about before any of it gets built.

The obvious part is the data. A care platform where a patient, the family member holding everything together and the clinician treating them all need the same record — and where none of them may see all of it — is a permissions problem first and an interface second. Get that wrong and it is not a bug, it is a disclosure.

The less obvious part is who is actually using it: a cardiologist between clinics, an intern submitting a talk summary at eleven at night, a carer logging a missed dose on a phone in a hospital corridor. None of them is going to learn a system. Anything that needs explaining does not get used, and anything that does not get used stops being true — which in a medical context is worse than never having had it.

Three of these are scientific societies and one is a care-coordination platform in Switzerland. They share a domain rather than a shape, which is the point: the constraints come from the field, not from the software.