What connects to what.
Every entity is a node. Every relationship is an edge. Any cell of the grid — this therapist × this room × this equipment × this hour × this patient — is either available or it is not.
Credentials · caseload · shift pattern · supervision · languages
A therapist node carries licence type, certifications with expiry, discipline, supervision requirements and working pattern. The planner will not allocate a session the credential does not permit.
A schedule you can query from any direction.
Because the relationships are real, the same data answers an operator's question and a clinician's question without a second system.
Which hydrotherapy hours went unused last month, and what was on the wait-list at the time?
Room → session → wait-list, joined at query time.
Can this stroke patient keep the same physiotherapist for the full six-week episode?
Plan → therapist continuity constraint in the allocator.
Which assets are due calibration in the next 30 days, and what will they block?
Equipment → maintenance window → affected sessions.
What is revenue per therapy hour by facility, net of no-shows?
Session → billing → facility roll-up.
Bring us a question the current system cannot answer.
We will show you the query path through the Matrix, live, in a 30-minute session.