Integration process
We welcome new information systems or other healthcare applications and patient apps to integrate with us.
But how does that work, connecting with ZorgDomein Integrator?
This page will guide you through the integration process step by step.
First mail (6)
- Interface specifications on Integrator
- Usecase and Goal
- Certifications ISO/NEN
- Do we already have shared customers?
- Market segment
- Project planning
First meeting (8)
- Introduction of parties
- In depth on usecase and goal
- Development planning
- Discuss data exchange (e.g. PKIO)
- Discuss development process
- Technical design interface of supplier
- Explanation of interface
- Discuss validation criteria
Development (8)
- Implement FHIR server in XIS
- Configure network to expose FHIR endpoints
- Implement FHIR profiles
- Implement interface security
- Configure ZorgDomein TIO environment
- Implement auto-activation
- Implement SSO (Referrals and Reports)
- Pre-validation checklist specific for usecase(s)
Collaboration agreement (1)
- Finalize and sign collaboration agreement
Validation (2)
- Validation will only start after a signed collaboration agreement
- Functional validation
- Technical validation
Configure on production (2)
- Configuration on production will only happen after a successful validation
- Configure production endpoints
- Configure production certificates
Pilot (4)
- Involve pilot customer(s)
- Activate FHIR connection
- Evaluate FHIR connection
- Implement necessary fixes and improvements
Communication for Live (3)
- Going Live will only happen after a successful pilot
- Coordinate marketing
- Inform Operations (Support & Implementation)
- Closing email to supplier + CSAT
Engage & Explore
Get to know each other and design your connector
Do you know ZorgDomein already? If not, please visit zorgdomein.com for more information about our application and company. When you are discovering the possibilities of building a connector with ZorgDomein we’d like to hear from you. So please contact us so we can get to know each other.
Once you decide to develop a connector you are assigned to a ZorgDomein consultant that will guide you through the development process. During this phase we will explore your use case and goals, discuss your certifications (ISO/NEN), identify shared customers, understand your market segment, and create a project planning together.
Developing a good connector starts with good preparations. Therefore we advise you to make a design of the connector within the architecture of your application. On the one hand you will need a functional design in which you define how your application interacts with ZorgDomein on a functional level, and how your users will interact with these functionalities. On the other hand you will need a technical API design that defines how the different backend components of your application will interact with ZorgDomein. We are happy to review your design or help you make the right design choices.
Build
Start building the connector
When the design has been finalized you can start defining a global planning for the development of your connector. Based on this planning you can start building. During this process you will implement the FHIR server in your system (XIS), configure network access to expose FHIR endpoints, implement the required FHIR profiles, and set up interface security. You’ll also implement auto-activation, and add SSO support for referrals and reports. We’ll configure the ZorgDomein TIO environment to test your connector.
Throughout the development process the ZorgDomein consultant can help you to configure the ZorgDomein application and resolve technical issues. Make sure to complete the pre-validation checklist specific for your use-case before moving to the next phase.
Validate
Formalize collaboration and validate your connector
Before validation can begin, we first need to formalize our collaboration. We propose to draw up a mutual collaboration agreement in which we record our agreements towards hosting, availability, future product development, liability and more. This way we aim to ensure a smooth and unambiguous collaboration.
🔒 Once the collaboration agreement is signed, ZorgDomein will schedule a validation session to verify that the connector meets the relevant validation criteria. Which criteria you have to apply to depends on the components you implement in your connector. Please read the documentation of the components to find the relevant criteria. Next to the component specific criteria you also need to meet the general technical validation criteria.
The validation includes both functional validation to ensure the connector works as expected from a user perspective, and technical validation to verify compliance with all technical requirements and security standards.
Pilot
Connect the first customers
🔒 After successful validation, we are ready to configure your connector on the production environment. This includes setting up production endpoints, configuring production certificates, and ensuring all security measures are in place.
Once the production configuration is complete, we will select one or two pilot customers together to implement the connector. The first implementations require some extra attention, so we take extra care in these implementations. You’ll activate the FHIR connection, evaluate its performance, and implement any necessary fixes and improvements based on real-world usage. ZorgDomein will offer extra support to address any unforeseen issues in these first implementations.
Live
Release the connector
🔒 After a successful pilot, we are ready to release the connector to all other customers. This is an exciting milestone that requires coordination between both our organizations.
Before going live, we inform our Operations team (Support & Implementors) to ensure they are prepared to assist customers with the new connector. This is also the moment to communicate the launch of the new connector externally and potentially start a marketing campaign. We’d like to synchronize our mutual marketing efforts to address a larger audience with a consistent message. Finally, we close the integration process with a summary email to you and a CSAT.
Questions or comments?
Leave your details below, we will contact you asap.