For municipalities

The school-law side of student health for the whole municipality, without an advertised procurement.

Incidents, cases, student-health-team meetings and accommodations in one system for all the municipality's schools. Need-to-know access, all data in the EU, and a price set so that a four-year agreement always stays under the direct-procurement threshold.

Built for direct procurement

The price has an absolute ceiling of SEK 170,000/year, or SEK 148,000/year with Skolshield-managed BankID. That means the agreement's value over four years always stays below the direct-procurement threshold — no advertised procurement is needed, the agreement can be signed directly.

4 × 170 000 kr = 680 000 kr < 700 000 kr

With Skolshield-managed BankID:

4 × 148 000 kr + 5 000 kr + 4 × 25 000 kr = 697 000 kr < 700 000 kr

The ceiling is absolute — index adjustment can never lift the agreement above the threshold. Setup, migration, digital training of super users, support and operation are included in the price. Priced add-ons count: an on-site training day fits (SEK 695,000 over four years), and with Skolshield-managed BankID the cap is lowered to SEK 148,000/year so the agreement still fits (SEK 697,000, then without a training day).

If the municipality instead runs an advertised tender, or wants extended scope — integrations, e-services for guardians, implementation projects or multiple school forms — we are glad to take part and quote per engagement. The cap applies to the standard scope of the direct-procurement package.

Calculate for your student numbers

How Skolshield works for a whole municipality

One installation for the authority. Each school unit works separately with its own students, and the central level sees what it should see. Nothing more.

kommun-demo.skolshield.se
Central student health's start page: municipality overview per school unit, escalated cases and watch list

Central student health's view in the municipality demo: per-unit overview, escalated cases and watch list. Click to explore it yourself.

School units are kept separate

A principal sees their own school's students and cases, not the neighbouring school's. Permissions follow the school unit throughout the system, from student lists to statistics.

Central student health sees the picture, not everything

The central level gets aggregated overviews across all school units. Individual student cases reach the central level only when the school escalates them.

An escalation ladder with full traceability

Teacher to the school's health team or principal, and on to central student health when needed. The same case all the way, with a stated reason and a log entry at every step.

Access-log review for the principal and DPO

A built-in review view shows who opened which student records. What gets flagged is the concrete rule: access outside any case, with no teaching relationship and no granted permission. Material for a formal log review can be exported.

The student registry syncs per school unit

Each school unit connects to its student registry via SS12000, or SchoolSoft's legacy API, and syncs every night. Students who change schools within the municipality are moved automatically, with a traceable log.

Teachers take part in the case

All teachers are included at no extra cost and take part in their students' cases instead of reporting into a mailbox. That is the difference from a medical-record system.

kommun-demo.skolshield.se
Access-log review: the audit view showing who opened which student records, with flags for access that needs review

The access-log review in the municipality demo: every access to student records classified as within the school, justified across school lines, or in need of review.

Updated for the 1 August 2026 amendment (SFS 2026:1096)

Education Act ch. 6 at authority level

Principals' reports under ch. 6 s. 10 land in the responsible authority's inbox for the whole municipality: acknowledgment, a daily reminder until the report is acknowledged, and printable material for the investigation under s. 10 a. The grounds (serious, repeated, or a member of staff being accused) are stated when the school flags the event, and cases that stay at school level show as exactly that.

kommun-demo.skolshield.se
The responsible authority's inbox in the municipality demo: ch. 6 s. 10 reports from the municipality's school units with acknowledgment status

The responsible authority's inbox in the municipality demo: reports from all school units, with acknowledgment status and supporting material.

Where Skolshield sits

The school-law side of student health, next to the medical record. Not instead of it.

The school nurse, school doctor and psychologist keep their record in Prorenata, PMO or Asynja. The principal, counsellor, special educator, mentor and teacher get a system for their part of the law, and whoever holds a case on the student is told automatically when something new happens.

Schematic of where Skolshield sits in student health Responsible authority (huvudman) In Skolshield: the huvudman inbox for reports under the Education Act ch. 6 § 10, read by central roles · situation views per school unit Context, not a data flow: supervised by the Schools Inspectorate, the Child and School Student Representative (BEO) and DO (discrimination) SKOLSHIELD Secrecy boundary · OSL ch. 23 § 2 | OSL ch. 25 § 1 Independent schools: duty of confidentiality under the Education Act ch. 29 § 14 and the Patient Safety Act instead of OSL. The classroom Education Act ch. 6 § 10 · OSL ch. 23 § 2 second para. Teacher Mentor • Reports in under a minute • Informs the principal about degrading treatment (ch. 6) • The mentor follows their own students' cases Incident ch. 6 flag: serious · repeated · staff Teacher outside the case: limited view Other students' names masked server-side Guardians are contacted by the mentor and up, the contact is logged on the incident. Student health · school-law side Education Act ch. 2 § 25, ch. 3 · OSL ch. 23 § 2 First para., strong secrecy: counsellor, psychologist, special educator Second para.: principal, teacher, other student support Principal Counsellor Special educator • EHT meeting, minutes, decisions with an owner • Case, investigation, action programme (ch. 3) • The principal's reporting chain, ch. 6 §§ 10–10 a Case on the student EHT request · support · ch. 6 case · mentorship case auto-created → principal notifies everyone holding a case on the student case handler reads and comments • The case handler controls what is shared • Annulment with a reason, trail kept • School change: other students masked Principal reports · Education Act ch. 6 § 10 Student health · health care Health care act · patient data act · OSL ch. 25 § 1 School nurse School doctor Psychologist ◀ consultation: Skolshield ▶ assessment: patient record • Health visits, vaccinations, assessments • Duty to keep a patient record • Sits in the EHT meeting, reads the school side • Read-only in Skolshield Patient record Prorenata · PMO · Asynja Visph Care staff write here. Not in Skolshield. Across the boundary Reminder: care notes belong in the record · harm assessment Traceability Every student page, incident and file read is logged · access log review · audit trail · DPO and guardians get answers from the log

Swipe sideways, or tap the drawing for full screen.

The teacher reports. The mentor follows. Student health finds out, automatically. Care staff write in their own record. The principal reports upward. All of it logged.

Blue frame = what Skolshield covers: the classroom, the school-law side of student health, the crossing of the secrecy boundary and traceability.
Green lane = health care. Same team, different law. The record stays in Prorenata, PMO or Asynja; Skolshield does not replace it.
Dashed line = the secrecy boundary. The psychologist stands on it: consultation is school work, assessment is care.

What your data protection officer will ask about

The municipality is the data controller for sensitive data about children. Skolshield is built so that you can answer — not just promise.

Who has read a child's records?

Every access to student data is logged — reads included. You can answer a parent's question from the log, not guess.

All data in the EU

Operation in Helsinki, encrypted backups in Germany. No US cloud services in our operation.

Data processing agreement on the SKR template

We sign the data processing agreement on the template your lawyer already recognises, with a sub-processor register. No school goes live without a signed agreement.

Archives Act built in

For a municipal responsible authority the records are public documents. The system supports preservation under the Archives Act: disposal happens only according to your records-management plan, never by an automatic time limit.

We are not a medical record

School nurses, school doctors and psychologists get a standing reminder in the system: care documentation belongs in the medical record system. Skolshield is the Education Act side of the student file and does not replace PMO or Prorenata, and the confidentiality boundary between the school (OSL ch. 23 s. 2) and health care (OSL ch. 25 s. 1) is visible in the sharing notices.

Need-based access control

Teachers outside a case see a limited view in which the names of students they do not teach are masked on the server. The handlers control what is shared. A mandatory requirement in municipal tenders that here is built in per viewer, not a policy.

No open report link

Some systems receive incident reports through an open web link with no sign-in. In Skolshield every report is tied to a signed-in, verified person, including the quick report from a locked screen. That is Article 32 in practice, and it means the log holds up as evidence.

Strong sign-in without an add-on licence

Passkeys and Microsoft Authenticator with number matching go directly against the municipality's Entra tenant (requires Entra ID P1, included in Microsoft 365 A3/A5); one-time code and PIN are included without any licence. BankID is added per role through your own bank agreement. Google Workspace sign-in is planned.

Your history comes with you

Reports of degrading treatment are the responsible authority's evidence and must be kept for many years. Switch systems without keeping the old one alive for the archive's sake: ready-made migration of students, incidents, cases and meetings, with ID mapping, tested on real exported data. A trial migration on your own exported data can be part of the pilot.

The price is the whole price

No separate cloud invoice, no operation of your own to manage, no support billed per case. Compare with today's systems, where hosting in your own cloud environment often costs SEK 5,500–7,000 a month per school on top of the licence.

BankID via your own bank agreement

BankID identification is primarily arranged through the municipality's own bank agreement and paid directly to the bank; the cost therefore does not count toward the contract value in a direct procurement. If you lack an agreement, we help you sign one at no markup. Skolshield-managed BankID is available as a priced alternative (SEK 5,000 activation + SEK 25,000/year). It counts toward the contract value, so the cap is then lowered to SEK 148,000/year; the four-year agreement still stays under the threshold, but then without an on-site training day.

Reduced vendor dependence

Your statutory retention obligation must never depend on a single vendor's survival. That's why you're protected at several independent levels: a full export of all your data in open formats on request, a current copy in your own Microsoft 365 environment, and source-code escrow that releases the system to you if Skolshield were to cease operating. Your data is always yours — and always accessible.

Take a look — then we talk

Open demo, open price list, real screenshots. Book a no-obligation call and we'll show you what Skolshield looks like for your municipality.