Custom AGB code integration
The Vektis AGB register is the public register of care providers and healthcare professionals in the Netherlands. The AGB code is the key that health insurers, care providers and other parties use to link claims, contracts and referrals to the right healthcare professional. Vektis offers a lookup service that lets systems query the register automatically. Appfront builds the integration that connects your own system to that service and keeps the data up to date.
What is an AGB code integration?
An AGB code integration ensures your system works with the same care provider data as the AGB register. Vektis manages that register on behalf of the health insurers. It contains the data needed for billing and contracting, and according to Vektis the AGB code is the unique key for administrative processes in healthcare. The register has three types of party: companies, branches and healthcare professionals. A healthcare professional is linked to one or more branches where they work, and a branch to a company. The AGB code also shows what care someone is permitted to provide.
For manual lookups, Vektis offers the AGB Webzoeker. For systems, there is the AGB Raadpleegdienst (AGB consultation service), a machine-to-machine integration that provides basic information on companies, locations and healthcare providers, the relationships between them and changed AGB codes. For this, Vektis publishes REST API documentation, OpenAPI specifications, test cases and release notes. If you want to use the service, you enter into an agreement with Vektis that refers to the purpose limitation in the terms and conditions, and you name a contact person. The register is linked to source registers such as the KvK register (Dutch Chamber of Commerce) and the BIG register (register of healthcare professionals), so that changes there carry through to the AGB registration.
We build custom integrations because every system uses the data differently. A health insurer checks claims and contracts, a referral platform shows care providers by location, and a care group keeps track of which healthcare providers work at which practice. The integration retrieves the data you need, processes changed codes and relationships, and shows where your own records differ from the register. The owner of an AGB code remains responsible for the accuracy of their registration; the integration flags differences, but does not change the register.
From the register
Data via the Raadpleegdienst.
Up to date
Changes processed automatically.
Unambiguous
Healthcare provider, location, company.
How we build your AGB code integration
We start with your use case: what you use AGB data for, what data you currently maintain yourself and where differences from the register cause problems. You then arrange the agreement for the Raadpleegdienst with Vektis, and we build the integration based on the Vektis OpenAPI specifications and test cases. We begin by retrieving and comparing your existing data, so you can see where it differs. Processing changes and connecting to the processes that use the data follow. When Vektis releases a new version of the service, we update the integration.
Use, data, differences.
Agreement and test cases.
Your data alongside the register.
Go-live, monitoring, and maintenance when new versions arrive.
What an AGB code integration actually does
The components below appear in almost every integration with the AGB register. Which ones you need depends on your role in healthcare and on the processes that use the data.
Lookup
Via the Vektis Raadpleegdienst.
Contacts
Healthcare provider, location, company.
Changes
Changed codes processed.
Comparing
Differences with your records.
Access
Permissions per role.
Log
Every lookup traceable.
Who we build an AGB code integration for
The integration is intended for organisations that use AGB data on an ongoing basis in claims, contracts, referrals or overviews of care provision. The more care providers you keep track of, the more it delivers.
Health insurers
Claims and contracts.
Care groups
Who works where.
Referral platforms
Up-to-date care provision.
Software builders
AGB in your software.
Technology and integrations
This page is about retrieving and maintaining data from the AGB register. If you want to exchange claims and messages with health insurers, see our page on the VECOZO integration; for the services and tariffs in mental health care and forensic care, there is the zorgprestatiemodel integration. For company data from the Trade Register, read more about the KVK API integration, and for integrations based on an OpenAPI specification, the OpenAPI integration. You can read about our approach on building software.
Why Appfront for your AGB code integration?
A claim rejected because a healthcare professional is listed at a different location, a referral to a practice that no longer exists, or a list of healthcare providers maintained by hand: all of these cost time and cause errors. That is what we build on: data taken from the register itself, changes that come in automatically and an overview of where your records deviate.
From the source
Data straight from Vektis.
Kept up to date
Changes processed automatically.
Visible
Deviations in the log.
Security and privacy in an AGB code integration
The AGB register contains data about healthcare professionals, and that is personal data, even when it is public. The integration only uses the data that fits the purpose stated in your agreement with Vektis, with a dedicated account that has exactly the permissions required for that, and it logs every lookup with its time and result. Under the GDPR, this means we store no more than your process needs.
The integration runs in a European data centre, with encrypted connections and storage. Keys and certificates for the Raadpleegdienst (lookup service) are kept secure and are not visible to staff. Who in your organisation may view and use the data is something we agree with you in advance.
Frequently asked questions about an AGB code integration
Questions that health insurers, healthcare providers and healthcare software suppliers ask before getting started.
The AGB code is the unique key for healthcare providers and healthcare professionals in the AGB register, the public register that Vektis maintains on behalf of the health insurers. Healthcare professionals who want to claim from a health insurer need an AGB code.
Data about companies, locations and healthcare professionals and the relationships between them, such as which locations a professional works at. The AGB code also shows which care someone is allowed to provide. The register is linked to source registers such as the KvK (Chamber of Commerce) register and the BIG register.
Via Vektis's AGB Raadpleegdienst (lookup service), a machine-to-machine integration. Vektis publishes REST API documentation, OpenAPI specifications, test cases and release notes for it. You enter into an agreement with Vektis for this.
Basic information about companies, locations and healthcare professionals, their relationships and changed AGB codes. Recipients use the public data for claims and referrals, among other things. Which data you may use depends on the purpose stated in your agreement.
No. The owner of an AGB code remains responsible for the accuracy of their registration, and changes go through Vektis. The integration flags where your own records deviate from the register, so you know what needs to be done.
Healthcare providers and health insurers use VECOZO to exchange claims and messages. An AGB code integration is about the data of the healthcare providers themselves: who is who, where someone works and which code belongs to them. The two often occur together in a claims process.
For organisations that keep track of many healthcare providers, use AGB data in several processes, or, as a supplier, want to include the register in their own software package. If you only look up a code now and then, Vektis's AGB Webzoeker (web search) is enough.
The AGB register in your own system?
Tell us what you use AGB data for and which system it sits in. We'll show you how an integration keeps it up to date.