Custom Sanday integration development
Appfront builds integrations with Sanday, the supplier of, among other things, the GP information system formerly called Promedico ASP and the pharmacy system formerly called Apro. Sanday already integrates with many parties, such as telephony and healthcare platforms. For care groups, health centres and suppliers with their own application, we build the connection where Sanday allows it: data that is permitted and necessary, without the practice having to retype anything.
What is a Sanday integration?
Sanday supplies software for primary care, including the GP information system formerly known as Promedico ASP and the pharmacy system formerly known as Apro. Sanday integrates with many parties, for example for telephony, medication and patient communication. For applications not on that list, a custom integration is needed, if Sanday offers the option for it.
A care group running chain care for diabetes or COPD needs data from the systems of its affiliated practices. A health centre wants its own dashboard, or a patient app that draws on the record. Without an integration, data is copied across by hand or exported, and the practice assistant retypes what is already in the system. That takes time, and every retyped detail can be wrong.
We build custom solutions because every application needs different data: which data, from which practices, on what legal basis and with what consent, and into which system it should go. Which integration options Sanday offers and under which conditions, we look at in the first step, together with you and with Sanday. Medical data is only shared where that is permitted.
Practice and application connected
Data from the Sanday system into your own application, without exports or retyping.
Only what is permitted
Only the data that is permitted and needed, with consent where that is required.
Less work in the practice
The assistant does not retype what is already in the system.
How we build your Sanday integration
We start with your application: which data, from which practices, on what legal basis, and how it works today. An integration with a GP or pharmacy system requires agreements with the supplier and with the practices taking part. We factor those agreements into the first step, so the build does not stall on a consent that is still missing.
Your application, the data, the practices, legal basis and consent.
The integration option Sanday offers, and the conditions that apply to it.
The exchange between Sanday and your application, with logging.
Testing with live practices, going live, and maintenance through updates.
What a Sanday integration does in practice
The components below come up in almost every Sanday integration. Which ones you need depends on your application.
Retrieving data
Data from the Sanday system for your application.
Data back
Results sent back to the record where possible.
Consent
Only what is permitted, with consent where required.
Practices
Which data is shared, per practice.
Validation
Checks on completeness and errors, per message.
Audit log
What has been exchanged and when, per message.
Who we build Sanday integrations for
The integration is intended for anyone who wants to connect their own application with Sanday.
Care groups
Integrated care with many practices. Data per programme is the core.
Health centres
Multiple disciplines under one roof. A custom dashboard matters most.
Practices and pharmacies
Your own app or way of working. Less retyping is the goal.
Care software vendors
A product for primary care. The integration is at its core.
Technology and integrations
This page is about integrations with Sanday. For referrals, see our page on a ZorgDomein integration; for billing, our page on a VECOZO integration; and for pharmacies, our page on pharmacy software. You can read about our approach under building software.
If the practices work with Medicom from PharmaPartners, there is our page on a Medicom integration.
For care data according to the national building blocks, there is our page on a zibs integration.
Why choose Appfront for your Sanday integration?
Every piece of data that is retyped in the practice costs time and can be wrong. We build on that: practice and application connected, only what is permitted, and less work for the assistant.
Less retyping
Data comes from the system itself.
Within the rules
Only what is permitted, with consent where required.
Up to date
The application works with today's data.
Security and privacy in a Sanday integration
The integration processes patients' medical data, which is special category personal data. Only data that is permitted and necessary is exchanged, connections are encrypted, access is set up per role, and every message is logged.
The integration runs in a European data centre or in the environment that the agreements with Sanday require, with encrypted storage, daily back-ups and sign-in with a second factor.
Frequently asked questions about a Sanday integration
Questions that care groups and suppliers ask before they start.
Sanday supplies software for primary care, including the GP information system formerly known as Promedico ASP and the pharmacy system formerly known as Apro. Many GP practices and pharmacies use it, and applications from care groups and suppliers want to exchange data with it.
Yes, with many parties, for example for telephony, medication and patient communication. If your application is among them, a custom integration is not needed. A custom integration is for applications that are not on that list.
Through the integration options Sanday offers, under the conditions Sanday sets for them. Which route fits and what it requires, we look at in the first step, together with you and with Sanday.
Only the data your application needs and that may be shared. What is permitted depends on the legal basis and the patient's consent; you determine this with your data protection officer.
Where Sanday allows it, results from your application can be sent back to the patient record, so the GP sees them without any manual entry. Examples include a measurement a patient takes at home, or a report from a care group programme. We agree what may be returned, and in what form, with Sanday and with the practices.
The integration reports the failure and records what went wrong. The exchange is retried or set aside for review, so that no data is lost.
For care groups, health centres and practices with their own application, and for suppliers who want to integrate their product with Sanday.
Is your application connected to Sanday?
Tell us which application you use, which data is needed and which practices you work with. We'll show you what the integration will look like.