Custom EDEXML integration development
Appfront builds EDEXML integrations for suppliers of digital learning materials, assessment and practice software and other education applications, as well as for schools and school boards with their own software. EDEXML is the Edustandaard standard for exchanging data about students, classes and teachers between a school's student administration and other applications. We build the integration that reads or generates EDEXML, validates it and processes it, using only the data that is needed. So classes and students are not entered by hand, and a new student is in the system straight away.
What is an EDEXML integration?
EDEXML is the Dutch standard for exchanging administrative data about students, with their associated classes and teachers. It was developed by suppliers of student administration systems, educational publishers and providers of digital assessments, and is maintained by Edustandaard. EDEXML is used, among other things, as a format for exchanging student data and results. An EDEXML integration lets your application read or deliver that data.
Without an integration, schools enter classes and students by hand, or upload an export that is not always correct. A student who changes class still appears in the old class in the application. A teacher who leaves keeps their access. And the supplier sometimes receives more data than needed, which is not intended under the GDPR and the agreements in the education sector.
We build this custom because the integration has to fit your application and the schools you serve: which version of EDEXML, which student information systems, whether data arrives directly or via an exchange service, which data your application genuinely needs, and how changes are handled during the school year. The standard is fixed; how your application works with it is the real work.
According to the standard
Students, groups and teachers imported or supplied in the EDEXML version used by the school and its student information system.
Changes tracked
New, transferred and departed students and teachers processed with every delivery, so the application stays in line with the school.
Only what's needed
Only the data each application needs, in line with the GDPR and the agreements on privacy in education.
How we build your EDEXML integration
We start with your application: which data you need, from which schools and student information systems, and how it currently comes in.
Your application, the data it genuinely needs, your schools' student information systems, and the route the data takes.
Importing or generating EDEXML in the correct version, with validation against the schema.
Processing new, changed and departed students and teachers, with a log for every delivery.
Testing with files from real student information systems, going live school by school, and maintenance as new versions appear.
What an EDEXML integration actually does
The components below appear in almost every EDEXML integration. Which ones you need depends on your application.
Import
Importing EDEXML files from the student information system, per school or per school board.
Validation
Checking against the schema and for missing or conflicting data, with a notification to the school.
Groups and teachers
Groups with their students and teachers, so that classes in the application are correct.
Changes
New, transferred and departed students and teachers processed, without leaving outdated data behind.
Data minimisation
Only the fields the application needs are stored; everything else is not retained.
Log
For each delivery: what was imported, what changed and what was rejected.
Who we build an EDEXML integration for
The integration is intended for applications that use student data from schools.
Learning material suppliers
Digital learning material per group. Accurate groups and students are the core.
Testing and practice platforms
Results per student. Linking students correctly and handling changes matter most.
School boards with their own software
In-house applications for multiple schools. What you need is delivery per school.
Education app vendors
A new application that schools want to connect. The standard and data minimisation are the core.
Technology and integrations
This page is about the EDEXML standard. For integrations with the student information systems themselves, see our pages on a ParnasSys integration, an ESIS integration and a Somtoday integration. You can read about our approach at custom software development.
If you want to build the chain pseudonym from Nummervoorziening into your learning resource or platform, read more about our ECK iD integration.
For transferring a student's file when they move to a new school, see our page on an OSO integration.
Why Appfront for your EDEXML integration?
A teacher who sees the wrong group loses trust in the application. That is what we build around: data that follows the standard, changes that get processed, and no more data than necessary.
No manual work for schools
Groups and students come from the student information system. The school enters nothing by hand.
Up to date all year round
Class changes and departures are processed with every delivery. The application stays in sync with the school.
Privacy in order
Only the data that is needed is stored. This fits with the GDPR and the agreements in place in education.
Security and privacy in an EDEXML integration
The integration processes data on pupils, often minors, and on teachers. Only what the application needs is stored. Access is limited to those who need it, and every delivery is logged.
The integration runs in a European data centre, with encrypted storage and daily backups. Data on pupils who have left is deleted in line with the agreements with the school.
Frequently asked questions about an EDEXML integration
Questions that suppliers and schools ask before getting started.
EDEXML is the Dutch standard for exchanging administrative data on pupils, classes and teachers, managed by Edustandaard. It is intended for primary and secondary education.
To pass pupil, class and teacher data from the school's student administration system to other applications, such as digital learning materials and tests. It is also used as a format for exchanging pupil data and results.
The version your schools and their student administration systems use. We look at which ones those are in the first step; when a new version is released, we adapt the integration as part of ongoing maintenance.
Only the data the application genuinely needs is stored. Schools and suppliers agree on this in a data processing agreement; in education, there are also agreements on privacy for digital learning resources. What applies to your application is something you determine together with the schools.
At the next delivery, the integration picks up the change and places the pupil in the new class. A pupil who has left is closed off and deleted after the agreed period.
An integration with a specific package uses that package's own API. EDEXML is a standard format that multiple student administration systems can deliver. Which route suits you best depends on your schools.
Check that first. There are services that handle the exchange between schools and suppliers, and these are often the best route. Custom work is then needed on your side: reading in and processing the data in your application.
Pupils and classes that are accurate, without manual work?
Tell us what your application does, which data you need and which schools you serve. We will show you what the data import, the changes and the data minimisation look like.