Your application connected to the GP information system Data that is permitted to flow, without retyping Via the route PharmaPartners offers

Custom Medicom integration

Appfront builds integrations with Medicom, the GP information system from PharmaPartners. Many GP practices use it, and integrations already exist with telemedicine, patient apps and the patient portal, among others. For care groups, health centres and suppliers with their own application, we build the integration via the route PharmaPartners provides, so data does not have to be retyped.

What is a Medicom integration?

Medicom is a GP information system from PharmaPartners, which many GP practices use to maintain their patients' records. There are integrations with other applications, for example for telemedicine, for a patient app for which the GP registers patients from the record, and for the patient portal. This is how GPs work with other care providers without constantly switching systems.

If you have your own application, for example for a chain care programme, telemonitoring or a regional service, you often end up working alongside Medicom rather than with it. A patient is registered in two systems. A measurement or report from your own application is retyped into the record. And the practice nurse has to check two systems to get a complete picture of a patient.

We build custom integrations because applications differ, but we don't promise an integration that PharmaPartners does not permit. Which integration options exist for your application, and under which conditions, we examine in the first step, together with you and with PharmaPartners. Which data may be shared is determined by you together with your data protection officer, and the integration adheres to that.

Connected to the GP information system

Your application connected to the system in which the GP maintains the record.

Without retyping

Registering from the record, and results back, where that is the route.

Agreed

Via PharmaPartners' integration options, and under the conditions that come with them.

How we build your Medicom integration

We start with your application: what it does, which practices you work with, what data is needed, and where information is currently retyped. Then we look with PharmaPartners at which route is available. Because integrations with other applications already exist, there is often an established pattern to build on. After that, we test with one or two practices before the integration is rolled out more widely.

1
Mapping your use case

Your application, practices, data and what is currently duplicated.

2
Route with PharmaPartners

The integration options and conditions that fit.

3
Building the integration

Messages in both directions, legal basis and log.

4
Go-live and maintenance

Go-live at practices, monitoring, and maintenance when things change.

What a Medicom integration actually does

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

Registration

Patients from the record.

Results

Measurements or reports sent back.

Legal basis

Consent and legal basis recorded.

Practices

Set up per practice.

Errors

Reported and resolved.

Log

Every message recorded.

Who we build a Medicom integration for

The integration is intended for parties that work with GPs in Medicom.

Care groups

Chain care for many practices. The results are what matter most.

Telemonitoring

Measurements from patients at home. Having them back in the record matters most.

Health centres

Multiple disciplines. What you need is less duplicated work.

Software suppliers

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

Technology and integrations

This page is about integrations with Medicom. For a different GP and pharmacy system, see our page on a Sanday integration; for regional collaboration, our page on a VIPLive integration; and for referrals, our page on a ZorgDomein integration. You can read about our approach on building software.

If some of your practices work with the Scipio GP information system instead of Medicom, read more about our Omnihis Scipio integration.

Medicom PharmaPartners GP information system Integration options Registration from the record Results sent back Legal basis and consent Chain care Telemonitoring Log per message

Why Appfront for your Medicom integration?

A patient registered in two systems and a measurement that gets retyped cost time and can go wrong. That is what we build on: connected to the GP information system, no retyping, and aligned with PharmaPartners.

One record

The GP sees it in Medicom.

No retyping

Results come back automatically.

Agreed

Via a route that PharmaPartners supports.

Security and privacy in a Medicom integration

The integration processes medical data, which is particularly sensitive. Only data for which there is a legal basis or consent is exchanged, connections are encrypted, and every message is logged.

The integration runs in a European data centre or in your own environment, with encrypted storage, daily backups and strict role-based access.

Frequently asked questions about a Medicom integration

Questions that care organisations ask before getting started.

Medicom is a GP information system from PharmaPartners, which GP practices use to maintain their patients' records. It has integrations with, among others, telemedicine, patient apps and the patient portal. Many practices in the Netherlands use it, so a Medicom integration for a regional application often reaches many practices at once.

Yes, with various applications, such as for telemedicine, patient apps and the patient portal. If your application is among them, you don't need a custom integration. A custom integration is for applications that are not listed, such as a care group's own programme or a regional service that works with many practices.

Via the integration options that PharmaPartners offers, under the conditions that come with them. Which route fits and what it requires, we look at in the first step, together with you and PharmaPartners.

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 the route allows, measurements or reports from your application can be sent back to the record, so the GP and the practice nurse see them without retyping. What may be sent back, and in what form, we agree with PharmaPartners and the practices.

The integration reports the problem and records what went wrong. The message is retried or set aside for review, so no data is lost. The log shows, per practice, what was exchanged and when.

For care groups, health centres and providers of their own application that work with GPs in Medicom, and for suppliers who want to connect their product to Medicom. If you work with practices that use different GP information systems, the Medicom integration can sit alongside integrations with other systems.

Is your application connected to Medicom?

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

Edit content