Custom OSO integration development
Appfront builds integrations with the Overstapservice Onderwijs (OSO, the Dutch school transfer service) for suppliers of student administration and care or support systems, and for school boards and regional partnerships with their own software. OSO is the set of agreements, standards and secure connections that schools use to digitally transfer a student's transfer file to the new school. We build the integration that creates, sends, receives and processes files according to OSO's agreements.
What is an OSO integration?
When a pupil changes school, for example from primary to secondary education, a transfer file goes with them containing details about the pupil, their educational results and the support they receive. OSO ensures this handover happens digitally and securely: the current school creates the file in its own pupil administration, and it reaches the new school via a secure connection. OSO is the service approved for this purpose by the ministry and the sector councils.
The well-known student administration systems support OSO. If you have your own software, such as a support system, a regional enrolment system or a school board's own administration, you have to arrange the connection yourself. Without an integration, data from the file is copied by hand, or stays in a different system from the one the mentor works in.
We build custom because the integration has to fit your software and your schools: which data you include in or process from a file, which transfers you support, how the connection to OSO is arranged for your situation, and how schools want to see the status of a file. OSO's agreements and standard are fixed; we discuss the connection and the conditions with OSO's administrator.
According to the standard
Transfer files created and processed according to the OSO agreements and standard, for the transfers you support.
From and to your software
Files taken directly from your own administration or support system, and received files processed straight away where the school works with them.
Status per file
For each pupil, you can see whether the file has been prepared, sent, received and processed.
How we build your OSO integration
We start with your software: which transfers, which data, how it works now, and what is needed to connect to OSO.
Your software, the transfers you support, the data in the file, and the connection requirements.
Files created from your data according to the standard, and received files processed in your software.
Connection to OSO's secure channel, with status and log per exchange.
Testing according to OSO's agreements, go-live, and maintenance when new versions of the standard are released.
What an OSO integration actually does
The components below appear in almost every OSO integration. Which ones you need depends on your software.
Creating a file
The transfer file built from the data in your software, according to the standard.
Sending
The file sent to the new school via the secure connection.
Receiving
Received files read in and processed in your administration or support system.
Status
For each pupil, the status of the file, for both the old and the new school.
Data minimisation
Only the data that belongs in the file, and nothing more.
Log
For each exchange, what was sent or received, when and by whom.
Who we build an OSO integration for
The integration is intended for software that needs to create or process transfer files.
Administration software vendors
An administration that needs to support OSO. The standard is the core.
Care system vendors
Care and support data in the record. Processing it matters most.
Regional application systems
The transfer from primary to secondary education in a region. What you need is the status of each file.
School boards with their own software
Your own administration system for multiple schools. The connection is what matters most.
Technology and integrations
This page is about the Overstapservice Onderwijs (OSO). For exchanging student data with learning materials, see our page on an EDEXML integration, and for integrations with student administration systems, see our pages on a ParnasSys integration and a Somtoday integration. You can read about our approach on building software.
Why Appfront for your OSO integration?
A transfer file sent on paper or by email is slow and insecure. We build on something better: files that follow the standard, sent from and to your own software, with a status everyone can see.
Transferred securely
The file travels over OSO's secure connection, not by email.
No retyping
Data comes from your software and is processed in the new school's software.
Status visible to both schools
The old and the new school can see where the file stands.
Security and privacy in an OSO integration
The integration processes data on students, often minors, including data on their support. Only the data that belongs in the file is exchanged. Access is limited to those who need the file, and every exchange is logged.
The integration runs in a European data centre, with encrypted storage and daily backups. Exchange takes place only via OSO's secure connection.
Frequently asked questions about an OSO integration
Questions that suppliers and school boards ask before they start.
The Overstapservice Onderwijs is the set of agreements, standards and secure connections that schools use to digitally transfer a student's transfer file to the new school, for example from primary to secondary education.
The well-known student administration systems do, so you don't need your own integration. An integration is needed for your own software, such as a support system, a regional enrolment system or an in-house administration.
OSO supports the transfer from primary to secondary education, as well as transfers within primary and within secondary education. Which ones you need determines the integration.
In line with the conditions set by the OSO administrator. What your software needs, such as testing and agreements, we discuss in the first step.
Data about the student, their educational results and their support, as the standard prescribes. The integration does not exchange more than belongs in the file.
Yes. The file is read into the new school's software, so mentors and support staff can work with it without retyping.
EDEXML is the standard for exchanging student, group and teacher data with learning materials and other applications. OSO is about transferring the file when a student changes schools. EDEXML has its own page on this site.
Transfer files from and to your own software?
Tell us which software you use, which transfers you support and how files are currently handled. We will show you what the integration looks like.