Skip to content
View the demo
Menu

Quality

How Siimsa itself is built and tested

A hospital must be able to trust its suppliers. Here is how we work, which standards we follow and how far we are. Honestly: what exists and what does not yet.

Way of working

Privacy as a starting point

We only ask what is needed to decide whether someone may enter. No medical documents, no copy of the ID, no location. What a hospital sees is defined in one place.

Rules in one place, automatically tested

When someone is authorised, what expires and what is reused lives in one module shared by the demo and the database. With every change, automated tests run on those rules, on the whole demo flow and on the languages.

Permissions in the database itself

Every table has row-level permissions: a hospital sees only its own part, an employer only its own staff, a professional only themselves. Those permissions are tested on a real Postgres database.

A log that cannot be changed

Every decision, check-in and exception is recorded with who, when and why. The database refuses changes and deletions, also for administrators.

Honest about where we stand

The site only promises what is built; the rest is called 'in development'. Prices are a proposal. On laws and standards we never write that Siimsa makes you compliant: you remain responsible, we help you demonstrate.

Public decisions

We record product choices with reasons and consequences, and publish them. A decision is called proposed until it is taken.

Open about AI

We use AI tools for development, writing and translation; every change is tested automatically, and AI translations are marked until they have been proofread. The app itself contains no AI and sends no data to AI services.

Standards and requirements: where we stand

Per standard or requirement: what exists now. 'Built and tested' means: in the code and covered by automated tests, not externally certified.

GDPR: data minimisation
Only data that is needed; vaccination as yes/no; sharing per hospital is the professional's choice.
Built and tested
Roles and permissions
Professional, employer, administrator, reviewer and reception each see only their own part, enforced in the database.
Built and tested
Access logging
Who, when, why and competent until, unchangeable. In the spirit of NEN 7513 (Dutch logging standard); formally that standard covers access to patient records.
Built and tested
Accessibility (WCAG 2.1 AA)
Labels, contrast and keyboard use are part of the design; there is no external assessment yet.
In development
NEN 7510
The design follows the Dutch standard for information security in healthcare; Siimsa is not certified yet.
In development
ISO 27001
Not certified yet.
In development
DPIA and data processing agreement
Drawn up before the first hospital enters real data.
In development
Cbw (Dutch NIS2 law) as a supplier
Agreements on incidents and supply-chain security become part of the contract.
In development
Hosting in the EU
The real app will run in Frankfurt (Supabase, Vercel). The demo now runs only in your browser.
In development
Penetration test
An independent test before the first real data, then yearly.
In development
Sign-in with the hospital account
Microsoft Entra ID and SAML for hospital staff.
In development
Exit and full export
The audit export exists; a full export of all data on leaving is still being built.
In development
MDR (medical devices)
In our assessment Siimsa has no medical purpose and is therefore not a medical device.
Not applicable

What the automated tests guard