For organisations
The same discipline, applied to people you are responsible for.
Alongside the personal app there is an organisation layer, built for teams who carry a duty of care. It is kept deliberately separate from personal accounts, with its own portal and its own sign in.
Organisations and roles
Members join an organisation by invitation, and what they can see follows from their role rather than from who knows which link. Every capability is checked on the server on every request.
Care assignments
A member of staff is connected to the people they are responsible for, explicitly. There is no ambient access to everyone in the organisation just because you have an account.
Consent that cannot be rewritten
Consent records are append only. Withdrawing consent supersedes the old record rather than deleting it, so the history of who agreed to what, and when, stays intact.
Clinician workspaces
A deliberately minimal view. Clinicians see what they need for the person in front of them, not a person's entire private planning history.
Appointments
Organisation owned appointments with a lifecycle that is recorded as it happens, rather than edited after the fact.
Audit as a first class record
Sensitive actions write an audit event. Those events are append only too, enforced right down to the database role the application runs under.
Being honest about where this is
Rolling out gradually, on purpose.
The organisation layer is not switched on for everyone. Each part of it stays behind a gate until the checks for that part pass in the environment it is going to run in, which is the right way to handle data about people who did not choose the software themselves.
If you are considering it for a team, the conversation starts with what you actually need and what you are required to prove. Write to us and we will tell you plainly whether it is ready for you yet.
Email support@theconsiliom.comAlready part of an organisation? Open the organisation portal