Skip to content
View the demo
Menu

Openness

Our decisions, in the open

How we make product choices: with date, status, reason and consequences. A decision is called proposed until it is taken.

SI-BDR-0002 · Date: 22 Nov 2026Decided

The hospital pays; professionals and employers use Siimsa free of charge

Why
The hospital is responsible for the access process. In the US, representatives pay themselves, with much resistance.
Decision
The hospital pays one all-in price; professionals and employers never pay. The amounts are a proposal and are shown on the site as indicative.
Consequences
No payment function for professionals. The price counts operating rooms in use; other departments are included.
SI-BDR-0003 · Date: 22 Nov 2026Decided

European languages, with AI translations clearly marked

Why
Hospitals in other countries and foreign service engineers need to use Siimsa in their own language.
Decision
Dutch is the source language, then English. Other languages are AI-translated and say so on every page until a native speaker has read them.
Consequences
A text change applies to all languages at once; a test enforces this.
SI-ADR-0001 · Date: 22 Nov 2026Decided

The demo runs on the real architecture

Why
A throwaway demo costs double work later and shows no real rules.
Decision
Screens talk to one data interface. The demo and, later, the EU database use the same rules; the data model with row-level permissions is tested on Postgres.
Consequences
Going from demo to app means a new implementation of one interface, not a rebuild.
SI-ADR-0002 · Date: 22 Nov 2026Proposed

Minimal data: vaccination yes/no only, no copy of the ID, no location

Why
What you do not store cannot leak. Vaccination status can be health data.
Decision
Vaccination is a yes/no declaration. The employer confirms the ID check; Siimsa keeps no copy and no national ID number. Presence comes from the QR code at the entrance, not from GPS. What a hospital sees is defined in one place.
Consequences
A hospital that wants to know more arranges that outside Siimsa.
SI-ADR-0003 · Date: 22 Nov 2026Proposed

One QR code per entrance, scanned with one's own phone

Why
No extra work for the theatre team and no scanners; the check happens before the visit.
Decision
Each entrance has one code; there are no personal QR codes. Check-in tests the status at that moment; checking out is never refused.
Consequences
A photographed code is a risk; a changing code on a screen is an option for the pilot. A solution for poor reception is in development.
SI-ADR-0004 · Date: 22 Nov 2026Proposed

The audit log is append-only, also for administrators

Why
A log that can be changed afterwards proves nothing in an audit or incident.
Decision
Every change writes a line with who, when, what, why, competent until and the version of the requirements. The database refuses changes and deletions; an export is recorded too.
Consequences
Retention periods get a separate, documented archiving process.
SI-ADR-0005 · Date: 22 Nov 2026Proposed

Renewed evidence reopens the pass without a new review

Why
A certificate that the employer renews and confirms should not create work for the theatre team.
Decision
The status is always computed from the rules; an approval remains valid as long as all requirements are valid.
Consequences
Open question for hospitals: do they want to look again themselves at a new certificate?
SI-ADR-0006 · Date: 22 Nov 2026Proposed

The site only promises what is built

Why
Hospitals buy on trust; a promise that does not hold costs that trust.
Decision
Features carry a status label, prices are indicative, and nowhere does the site claim that Siimsa makes a hospital compliant with a law or standard. Tests check this.
Consequences
The site changes with what is built.
SI-ADR-0007 · Date: 22 Nov 2026Proposed

An exception at the desk exists only if the hospital switches it on

Why
In an emergency an expired certificate can hold up a procedure; the desk must not bypass a hospital decision.
Decision
Off by default. Only for an expired pass or a pending request, never after a rejection or revocation; always with a reason and the name of who approved it, recorded separately.
Consequences
Exceptions can be found in the audit.
SI-ADR-0008 · Date: 22 Nov 2026Proposed

Branding per hospital, safe and readable

Why
Professionals should recognise where they are; a logo must not be a security risk.
Decision
A logo is always shown as an image, up to 300 KB. An accent colour must have a contrast of at least 4.5:1 with white text. A welcome text is plain text.
Consequences
Still to decide: allow SVG or only PNG in the real app.
SI-ADR-0009 · Date: 22 Nov 2026Proposed

Product decisions are public

Why
Hospitals want to know how their supplier makes choices.
Decision
Product and architecture decisions are listed on this page with date, status, reason and consequences. A decision is called proposed until it is taken. Business agreements remain internal.
Consequences
Every new product choice gets a decision in this register.

Business agreements, such as ownership and partnership, are not in this public register.