Custom AORTA-LSP integration development
Through the Landelijk Schakelpunt (LSP, the national exchange point), GPs, pharmacies, hospitals and other care providers share medical data, such as out-of-hours GP and medication data. VZVZ manages the LSP, and the arrangements are set out in the AORTA framework. A care information system that wants to connect must be qualified by Nictiz and accepted by VZVZ. Appfront builds the integration into your system and prepares it for both assessments.
What is an AORTA-LSP integration?
An AORTA-LSP integration enables your care information system to share and retrieve medical data via the Landelijk Schakelpunt. AORTA's starting point is that data is not stored centrally but stays at the source. The LSP itself holds no medical data, but a referral index that records where data about a patient can be retrieved. The care information broker in the LSP coordinates the traffic, checks the authentication and authorisation of care providers and logs the message traffic. Care applications run on this infrastructure, such as out-of-hours GP data, pharmacy medication data, LSP Ketenzorg (chain care), record transfer in youth healthcare and urgent referrals from out-of-hours GP services to A&E.
According to VZVZ, VZVZ provides the technology and manages the infrastructure, while Nictiz develops the content of what is exchanged through the care applications. That is why there are two assessments. First, Nictiz qualifies your system against the information standards; XIS qualification is a prerequisite for acceptance. You then go through an acceptance test with VZVZ, based on an acceptance test script, which checks, among other things, whether the secure connection works and whether interoperability over the LSP meets the requirements. For testing, you request a test connection on VZVZ's test network, with simulators that VZVZ says are set up identically to production. An accepted system is called a Goed Beheerd Zorgsysteem (GBZ, a well-managed care system).
We build the integration into your system: registering data with the referral index, supplying data when another care provider requests it, and retrieving and displaying data in your own screens. Only care providers with a UZI card can consult records via the LSP; a personal staff card only under the mandate of a care provider. The system identifies itself with a UZI server certificate, and data is only made available if the patient has given consent. If you later change anything in the interface with the LSP, VZVZ will ask for re-acceptance; we therefore keep the integration as a separate component, with its own test set. We establish with you in the first step which care applications and which AORTA version apply to you.
Registration
Data in the referral index.
Requesting
Data from other care providers.
Accepted
Ready for both assessments.
How we build your AORTA-LSP integration
We start with your care application: which data your system needs to share or retrieve, for which healthcare providers, and which information standard and AORTA documentation apply. Then, for each message, we define which data comes from your system, which checks apply and what happens if the patient has not given consent. We fully build one transaction first and test it on VZVZ's test connection. This prepares the qualification with Nictiz and the acceptance test with VZVZ, which you request yourself as a supplier or care provider. The remaining transactions and the set-up for GBZ management follow.
Data, roles, documentation.
Consent, permissions, errors.
Test connection, qualification, acceptance.
GBZ management, and re-acceptance after changes.
What an AORTA-LSP integration actually does
The components below appear in almost every integration with the National Switch Point (LSP). Which ones you need depends on the care application and on what your system already supports.
Registration
Data in the referral index.
Delivery
Response to a request.
Requesting
Data in your screens.
UZI credentials
Card and server certificate.
Test set
Ready for the acceptance test.
Log
Every message traceable.
Who we build an AORTA-LSP integration for
The integration is intended for suppliers who want to have their healthcare information system qualified and accepted for the LSP, and for care providers with their own software who want to share or retrieve data via the LSP.
Software builders
Your package as a GBZ.
Out-of-hours GP services
Retrieving observation data.
Pharmacies
Sharing medication data.
Institutions
Mental health care, GZ, long-term care and youth health care.
Technology and integrations
This page is about connecting a healthcare information system to the National Switch Point. If you only need healthcare providers to log in with their UZI card, or need the server certificate for your system, see the UZI card integration. You can read about the legal obligation to exchange certain data electronically under the Wegiz integration, and about the transfer of medication data under the medication transfer integration. For exchange with patients themselves, there is the MedMij integration. You can read about our approach on building software.
Why choose Appfront for your AORTA-LSP integration?
An acceptance test that has to be redone because one transaction is wrong, data that is delivered without consent, or an update that quietly affects the interface: all of these cost a supplier time and a care provider trust. That is what we build around: checks defined in advance, a dedicated test set per transaction and an integration that can be tested separately whenever something changes.
Prepared
Towards qualification and acceptance.
Checked
Consent and permissions verified.
Testable separately
With every change.
Security and privacy in an AORTA-LSP integration
Medical data is shared via the LSP, and the patient must give consent beforehand. The integration only delivers data if that consent is in place, only to healthcare providers with the right UZI card, and only the data the care application prescribes. Every message is logged with the time, healthcare provider and result, in addition to the logging the LSP itself keeps.
A GBZ must meet technical and organisational requirements, including availability requirements (24/7) and a GBZ administrator who acts as the contact person in the event of disruptions. The integration runs in your own environment or with your hosting partner, with the private key of the server certificate protected. We supply the documentation your GBZ administrator needs and agree in advance who has which role.
Frequently asked questions about an AORTA-LSP integration
Questions that healthcare software suppliers, information managers and GBZ administrators ask before getting started.
A national infrastructure that healthcare providers use to exchange their patients' medical data. The LSP itself holds no medical data, but a referral index that records where data about a patient can be retrieved. VZVZ manages the LSP.
The set of agreements that defines who exchanges data via the LSP, how, and under which conditions. It describes the infrastructure and the healthcare applications that run on it, such as GP out-of-hours data and pharmacy medication data.
In qualification, Nictiz tests whether your system complies with the information standards, in other words the content of the messages. In acceptance, VZVZ tests, among other things, the secure connection and interoperability over the LSP. XIS qualification is a prerequisite for acceptance.
A healthcare information system that has been accepted for the LSP and meets requirements for both the software product and the management of the specific installation. A GBZ administrator, internal or external, handles technical management and is the contact person for disruptions.
A UZI server certificate for the system's identity and a UZI card for the healthcare professional. A healthcare professional's card can log in to the LSP independently, a named staff card only under the mandate of a healthcare professional, and a non-named staff card not at all.
According to VZVZ, when the requirements change or when a change to your system (potentially) affects the interface with the LSP. You report the change with documentation to the VZVZ Test Team, after which VZVZ's Change Advisory Board provides feedback.
For vendors who want to have their healthcare information system qualified and accepted for the LSP, and for healthcare providers with their own software. If your package is already on the list of accepted systems for the healthcare application you need, your own integration is usually not necessary.
Connecting your system to the National Switch Point?
Tell us which healthcare application you need and which system you work with. We'll show you how an integration helps you through qualification and acceptance.