Executive summary
A person receiving support from a large community service provider may be a participant in a disability program, a client in a housing program, a member of a community group and a family in a support service, all within the same organisation, and appear as four unrelated people in four systems.
The cost of that fragmentation falls first on the person, who repeats their history to each team, and second on the provider, which duplicates assessment, misses risk that is only visible across programs, and cannot answer basic questions about who it serves.
A connected view is not a licence for every worker to read everything. The design objective is that the organisation knows the person is the same person, while access to detail remains governed by role, purpose and consent.
1. How fragmentation happens
- Funding shaped systems. Each program is funded separately, procures separately and reports separately, so a system is chosen per program rather than per person.
- Program specific intake. Each intake creates a new record because the fields differ, and matching against existing clients is manual or absent.
- Legitimate confidentiality. Family violence, child protection and clinical information carry genuine access restrictions that are often implemented as a separate system rather than as a permission.
The third cause is the important one, because it means the fix cannot simply be to merge everything. Confidentiality has to survive the consolidation.
2. What it costs
For the person, retelling is not neutral. Repeating a history of violence, disability or loss to a fourth worker is a burden, and it teaches people that the organisation does not communicate with itself.
For the provider, invisible risk. Escalating patterns are frequently visible only when housing instability, missed appointments and a change in mental state are read together. Split across systems, each looks minor.
For the organisation, unanswerable questions. How many people do we serve, how many receive more than one service, and what does a person's whole journey with us look like. These should be simple and usually are not.
3. Identity and matching
A connected view depends on knowing that two records describe the same person. In this sector that is harder than in most, because names change, addresses are unstable, dates of birth are estimated and people sometimes deliberately do not want to be linked.
Match probabilistically, confirm with a human. Automated merging of client records is dangerous. Surfacing a likely match for a worker to confirm or reject is safe and effective.
Support deliberate separation. In family violence and child protection contexts, keeping records apart can be a safety requirement. The system must permit an enforced separation that cannot be casually overridden.
4. Consent aware sharing
The workable model is that existence is shared and detail is governed. A worker can see that the person is also known to another program, and who to contact, without seeing that program's notes unless purpose and consent permit it.
- Purpose based access. Access granted for a stated reason, recorded, rather than by blanket role permission across the whole organisation.
- Recorded consent. What the person agreed to share, with whom, for what purpose and when it was last confirmed, visible on the record.
- Break glass with accountability. Emergency access is sometimes necessary and should always be logged, reviewed and explainable afterwards.
5. What the connected view should show
Show the shape, not everything. Programs involved, current workers, active plans, upcoming appointments, consent status and any safety alert the worker is entitled to see.
Do not show clinical or protected detail by default. Detail should require a purpose, and the person should be able to find out who looked.
6. Limitations
Information sharing obligations differ by jurisdiction, program and legislation, particularly in child protection and family violence. This paper is not legal advice. Alvacomm operates the Konetic One platform and has a commercial interest in this subject.
References
- 1.Office of the Australian Information Commissioner, Australian Privacy Principles guidelines.
- 2.NDIS Quality and Safeguards Commission, Regulatory priorities and provider obligations, Australian Government.
- 3.Department of Social Services, Data Exchange, program reporting and the SCORE outcomes framework.
- 4.Australian Charities and Not-for-profits Commission, Governance Standards for registered charities.
Previously published
Beyond case management, what providers actually need from technology
Why case management alone does not address workforce management, funding oversight, governance, compliance, service capacity and multi program operations.
Read the paperAbout the publisher
Alvacomm Pty Ltd, ABN 61 627 262 873, is an Australian technology and cybersecurity organisation. Konetic One is a platform and service operated by Alvacomm.
This paper is published under the Alvacomm name and is general in nature. It is not legal, financial or clinical advice.