Custom EDEXML integration development
Appfront builds EDEXML integrations for suppliers of digital learning materials, assessment and practice software and other education applications, and for schools and boards with their own software. EDEXML is the Edustandaard standard for exchanging data about pupils, groups and teachers between a school's pupil administration system and other applications. We build the integration that reads, creates, checks and processes EDEXML, using only the data that is needed, so that groups and pupils are not entered by hand and a new pupil is immediately available.
What is an EDEXML integration?
EDEXML is the Dutch standard for exchanging administrative data on pupils, along with the associated groups and teachers. It was developed by suppliers of pupil administration systems, educational publishers and providers of digital assessments, and is maintained by Edustandaard. EDEXML is used, among other things, as the format for exchanging pupil data and results. An EDEXML integration allows your application to read in or supply that data.
Without integration, schools enter groups and pupils by hand, or upload an export that is not always accurate. A pupil who changes group still appears in the old group in the application. A teacher who leaves keeps their access. And the supplier sometimes receives more data than necessary, which is not intended under the GDPR and the agreements in education.
We build custom work because the integration must match your application and the schools you serve: which version of EDEXML, which pupil administration systems, whether data arrives directly or via an exchange service, which data your application genuinely needs, and how changes during the school year are handled. The standard is fixed; how your application works with it is the work.
According to the standard
Pupils, groups and teachers imported or delivered according to the version of EDEXML used by the school and the pupil administration system.
Changes tracked
New, transferred and departed pupils and teachers processed with each delivery, so the application matches the school.
Only what is needed
Only the data needed per application, in line with the GDPR and the privacy agreements in education.
How we build your EDEXML integration
We start with your application: which data you need, from which schools and pupil administration systems, and how it currently arrives.
Your application, the data that is genuinely needed, the pupil administration systems of your schools, and the route the data takes.
Importing or creating EDEXML according to the correct version, with validation against the schema.
Processing new, changed and departed pupils and teachers, and keeping a log for each delivery.
Testing with files from real pupil administration systems, going live school by school, and managing new versions.
What an EDEXML integration does in practice
The components below feature in almost every EDEXML integration. Which ones you need depends on your application.
Import
Importing EDEXML files from the pupil administration system, per school or per board.
Validation
Checking against the schema and for missing or conflicting data, with a notification to the school.
Groups and teachers
Groups with their pupils and teachers, so classes are accurate in the application.
Changes
New, transferred and departed pupils and teachers processed, without leaving old data behind.
Minimisation
Only the fields the application needs are stored; the rest is not saved.
Audit log
For each delivery, what was imported, what was changed and what was rejected.
Who we build an EDEXML integration for
The integration is intended for applications that use pupil data from schools.
Suppliers of learning materials
Digital teaching materials per group. Accurate groups and pupils are the core.
Testing and practice platforms
Results per pupil. The integration of pupils and their changes matter most.
School boards with their own software
Custom applications for multiple schools. Delivery per school is what is needed.
Suppliers of education apps
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 pupil administration 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.
For transferring a pupil's file when moving to a new school, see our page on an OSO integration.
Why choose Appfront for your EDEXML integration?
A teacher who sees the wrong group loses confidence in the application. That's what we build on: data that follows the standard, changes that are processed, and no more data than necessary.
No manual work for schools
Groups and pupils come from the school's pupil administration system. The school enters nothing by hand.
Up to date throughout the year
Transfers and departures are processed with every delivery. The application stays in step with the school.
Privacy under control
Only the data that is needed is retained. That fits with GDPR and the arrangements within education.
Security and privacy for an EDEXML integration
The integration processes data about pupils, often minors, and about 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 back-ups. Data about 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 about pupils, groups and teachers, managed by Edustandaard. It is intended for primary and secondary education.
To transfer pupil, group and teacher data from the school's pupil administration system to other applications, such as digital learning materials and assessment tools. It is also used as a format for exchanging pupil data and results.
The version your schools and their pupil administration systems use. We will confirm which that is in the first step; when a new version is released, we update the integration as part of ongoing management.
Only the data the application genuinely needs is retained. Schools and suppliers set out those arrangements in a data processing agreement; in education, there are also agreements on privacy for digital learning tools. What applies to your application is determined together with the schools.
At the next delivery, the integration detects the change and places the pupil in the new group. A pupil who has left is deregistered and, after the agreed period, deleted.
An integration with a specific package uses that package's own API. EDEXML is a standard format that multiple pupil administration systems can supply. Which route suits you best depends on your schools.
Check that first. There are services that handle 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 within your application.
Pupils and groups that are correct, without manual work?
Tell us what your application does, which data you need and which schools you serve. We'll show you what reading in the data, handling changes and data minimisation look like.