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 travels with them, containing information about the pupil, their educational results and their support. OSO ensures this transfer happens digitally and securely: the current school creates the file in its pupil administration system, and it reaches the new school over a secure connection. OSO is the service approved for this 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 in line with OSO's agreements and standard, for the transfers you support.
To and from your software
Files taken directly from your own administration or guidance system, and incoming files processed immediately where the school works with them.
Status per file
For each pupil, visible 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 things work now, and what is needed for the connection to OSO.
Your software, the transfers you support, the data in the file, and the connection requirements.
Files created to the standard from your data, and incoming files processed in your software.
Connection to OSO's secure channel, with status and a log for each exchange.
Testing in line with OSO's agreements, go-live, and maintenance when new versions of the standard are released.
What an OSO integration does in practice
The components below come up in almost every OSO integration. Which ones you need depends on your software.
Creating a file
The transfer file from the data in your software, in line with the standard.
Sending
Sending the file over the secure connection to the new school.
Receiving
Incoming files read in and processed in your administration or guidance system.
Status
For each pupil, the status of the file, for both the old and the new school.
Minimisation
Only the data that belongs in the file, and nothing more.
Audit log
For each exchange, what was sent or received, when and by whom.
Who we build OSO integrations for
The integration is intended for software that needs to create or process transfer files.
Administration system vendors
An administration system that must support OSO. The standard is the core.
Care system vendors
Care and guidance data in the record. Processing matters most.
Regional registration systems
The move from primary to secondary school within a region. Status per record is what's needed.
School boards with their own software
A custom administration for multiple schools. Connectivity is the core.
Technology and integrations
This page is about the Overstapservice Onderwijs (OSO). For exchanging pupil data with learning resources, see our page on an EDEXML integration, and for integrations with pupil administration systems, our pages on a ParnasSys integration and a Somtoday integration. You can read about our approach under custom software development.
Why choose Appfront for your OSO integration?
A transfer record sent on paper or by email is slow and insecure. That's what we build around: records that follow the standard, going out of and into your own software, with a status everyone can see.
Transferred securely
Files travel over OSO's secure connection, not by email.
No manual re-keying
Data comes from your software and is processed in the new school's software.
Status for both schools
The old and new school can both see where the record stands.
Security and privacy in an OSO integration
The integration processes pupil data, often relating to minors, including information about support and guidance. Only the data that belongs in the transfer file is exchanged. Access is restricted 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 vendors and school boards ask before starting.
The Overstapservice Onderwijs (OSO, the Dutch education transfer service) is the set of agreements, standards and secure connections that allows schools to pass a pupil's transfer file digitally to their new school, for example when moving 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 transfers from primary to secondary education, as well as within primary and within secondary education. Which ones you need determines the integration.
According to the terms set by the OSO administrator. We discuss what your software needs, such as testing and agreements, in the first step.
Information about the pupil, their educational results and their support, as the standard prescribes. The integration exchanges no more than the transfer file should contain.
Yes. The record is imported into the new school's software, so mentors and guidance staff can work with it without retyping.
EDEXML is the standard for exchanging pupil, group and teacher data with learning materials and other applications. OSO covers the transfer of the record when a pupil changes school. EDEXML has its own page on this site.
Transfer records out of and into your own software?
Tell us which software you use, which transfers you support and how files currently move. We will show you what the integration would look like.