Your application connected to the GP information system Only the data you're permitted to share, with no retyping Via the route offered by PharmaPartners

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 through which the GP enrols patients from the record, and for the patient portal. This allows GPs to work together with other care providers without constantly switching systems.

Anyone with their own application, for example for a chronic care programme, telemonitoring or a regional service, often works alongside Medicom rather than within it. A patient is enrolled in two systems. A measurement or report from the separate application is retyped into the record. And the practice support worker has to look in two systems to get the full picture of a patient.

We build custom solutions because applications differ, but we do not promise an integration that PharmaPartners does not permit. Which integration options are available for your application, and under which conditions, we establish in the first step, together with you and with PharmaPartners. Which data may be shared is decided by you with your data protection officer, and the integration adheres to that.

Connected to the GP IS

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

No retyping

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

Reconciled

Via the integration options provided by PharmaPartners, 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, which data is needed, and where re-keying happens today. We then review with PharmaPartners which route is available. Because integrations with other applications already exist, there is often an established pattern to connect to. We then test with one or two practices before the integration is rolled out more widely.

1
Mapping the application

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

2
Route with PharmaPartners

The integration option and conditions that fit.

3
Build integration

Messages in both directions, legal basis and audit log.

4
Go-live and management

Go-live at practices, monitoring, and management of changes.

What a Medicom integration concretely does

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

Enrolment

Patients from the record.

Outcomes

Measurements or reports returned.

Legal basis

Consent and legal basis recorded.

Practices

Set up per practice.

Errors

Reported and handled.

Audit log

Every message recorded.

Who we build Medicom integrations for

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

Care groups

Chronic care for many practices. The results are the core.

Telemonitoring

Measurements from patients at home. Getting them into the record matters most.

Health centres

Multiple disciplines. Reducing duplicated work is what's needed.

Software suppliers

A product for primary care. The integration is at its 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 way of working under custom software development.

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

Why choose Appfront for your Medicom integration?

A patient enrolled in two systems, and a measurement retyped by hand, cost time and can go wrong. We build around that: connected to the GP information system, with no retyping, and aligned with PharmaPartners.

One record

The GP sees it in Medicom.

No manual re-keying

Results return automatically.

Reconciled

Through a route 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 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 work with it, so an integration with Medicom for a regional application often reaches many practices at once.

Yes, with several applications, such as 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 aren't listed, such as a care group's own programme or a regional service working with many practices.

Through the integration options that PharmaPartners offers, under the conditions that come with them. We'll look at which route fits and what it requires 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 this with your data protection officer.

Where the route allows it, measurements or reports from your application can be returned to the record, so the GP and practice nurse can see them without retyping. We discuss with PharmaPartners and the practices what can be returned and in what form.

The integration reports the failure 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 who 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.

Connect your application to Medicom?

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

Edit content