Practice and your own applications on the same data Only what is permitted and necessary Less retyping in the practice

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 communication with patients. For applications that are not on that list, a custom integration is needed, provided Sanday offers the option.

A care group organising chain care for diabetes or COPD needs data from the systems of the affiliated practices. A health centre wants its own dashboard, or a patient app with data from the record. Without an integration, data is copied by hand or exported, and the assistant retypes what is already in the system. That takes time, and every retyped item can be wrong.

We build custom integrations because every application needs different data: which data, from which practices, on what legal basis and with what consent, and in which system it needs to end up. We look at which integration options Sanday offers and under what conditions 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 in your own application, without exports or retyping.

Only what is permitted

Only the data that is permitted and necessary, with consent where required.

Less work in the practice

The assistant doesn't 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 things work now. An integration with a GP or pharmacy system requires agreements with the supplier and with the participating practices. We include those agreements in the first step, so the build doesn't stall on a consent that is still missing.

1
Application and data mapped out

Your application, the data, the practices, legal basis and consent.

2
Route with Sanday

The integration option Sanday offers, and the conditions that come with it.

3
Building the integration

The exchange between Sanday and your application, with an audit log.

4
Testing and maintenance

Testing with real practices, going live, and maintenance through updates.

What a Sanday integration actually does

The components below appear in almost every Sanday integration. Which ones you need depends on your application.

Retrieving data

Data from Sanday's system for your application.

Data back

Results written back to the patient record where possible.

Permission

Only what is permitted, with consent where required.

Practices

Which data is shared, per practice.

Validation

Checks for completeness and errors per message.

Log

What was exchanged and when, per message.

Who we build a Sanday integration for

The integration is intended for anyone who wants to connect their own application to Sanday.

Care groups

Chain care with many practices. Data per programme is the core.

Health centres

Multiple disciplines under one roof. A dashboard of your own matters most.

Practices and pharmacies

Your own app or way of working. Less retyping is what you need.

Healthcare software vendors

A product for primary care. The integration is the core.

Technology and integrations

This page is about integrations with Sanday. For referrals, see our page on a ZorgDomein integration, for claims our page on a VECOZO integration, and for pharmacies our page on pharmacy software. You can read about our approach on building software.

If your practices still use Omnihis Scipio and you want to take your own integrations with you when upgrading to Sanday, take a look at our Omnihis Scipio integration.

If the practices work with Medicom from PharmaPartners, see our page on a Medicom integration.

For health data based on the national building blocks, see our page on a zibs integration.

Sanday GP information system Pharmacy system Sanday integration options Data per practice Consent Write-back to the record Check per message Your own application Log per message

Why Appfront for your Sanday integration?

Every piece of data retyped in the practice costs time and can be wrong. That is what we build on: practice and application connected, only what is permitted, and less work for the practice 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 for 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 required by the agreements with Sanday, with encrypted storage, daily backups and two-factor login.

Frequently asked questions about a Sanday integration

Questions that care groups and suppliers ask before they get started.

Sanday supplies software for primary care, including the GP information system formerly called Promedico ASP and the pharmacy system formerly called Apro. Many GP practices and pharmacies work with it, and applications from care groups and suppliers want to exchange data with it.

Yes, with many parties, for example for telephony, medication and communication with patients. If your application is among them, you don't need a custom integration. A custom integration is for applications that aren't.

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 that together with your data protection officer.

Where Sanday allows it, results from your application can be written back to the record, so the GP sees them without retyping. Think of a measurement a patient takes at home, or a report from a care group programme. What may be written back, and in what form, we discuss with Sanday and with the practices.

The integration reports it and records what went wrong. The exchange is retried or queued for review, so no data is lost.

For care groups, health centres and practices with their own application, and for suppliers who want to connect their product to Sanday.

Your application connected to Sanday?

Tell us which application you have, which data is needed and which practices you work with. We'll show you what the integration looks like.

Edit content