Safe learning demonstration
How an organisation could set up a service.
This page is a guided, made-up example. It shows three parts of setting up an information relationship. It does not send information anywhere and it is not connected to a real service.
1. Describe the service
Before sharing anything, an organisation should define the service and its boundaries: what it is for, what records it uses, and which people are responsible.
In the software this is called a “program”. Think of it as a documented service agreement, not a marketing program. Each program has its own rules and does not automatically give staff access to other programs.
| Example service | Plain-language purpose | Example record type | Status |
|---|
2. Set up a connection
In a real service, this creates a separate connection between one person and one program. The connection uses an internal reference instead of putting a person’s general identity into every record.
Why make connections separate? A receipt from one service should not automatically reveal a person’s relationship with another service. Keeping connections separate limits unnecessary sharing.
3. Send a record
This example sends a made-up receipt. A real organisation should only send a record when it has a lawful purpose, a clearly communicated reason, and suitable safeguards.
What happens after a record is accepted? The service receives a dated receipt confirming its record was accepted. That receipt helps staff investigate a problem without silently changing history.