Custom Omnihis Scipio integration
Scipio is the GP information system from Omnihis, made for and by GPs and owned since 2000 by a cooperative of its users. Omnihis has merged with Promedico to form Sanday, which offers Scipio practices an upgrade to the Sanday platform. Care groups, health centres and suppliers that use data from Scipio want that flow to keep working, both now and after the switch. Appfront builds the integration between Scipio and your own application, using only the data that is permitted and needed.
What is an integration with Omnihis Scipio?
An Omnihis Scipio integration connects the GP information system Scipio to the applications around it. Scipio runs on Mac and Windows and includes, among other things, an assistant module for repeat prescriptions and appointments, the Omnihis Messaging Service for text message reminders, a prescriber integration for cost-effective prescribing and the Data Extraction module (DEX). According to Sanday, DEX lets the practice make data available securely and automatically to external parties, for example for collaboration with care partners or research. The integration takes that data into your application and converts it into the structure you need.
The trigger is often collaboration or a switch of system. A care group organising chain care for diabetes or COPD needs data from the systems of the connected practices, and those practices are far from all using the same system. In addition, Sanday offers Scipio practices an upgrade to the Sanday platform, with one-way synchronisation instead of a conversion. Sanday takes care of migrating the patient record. What does not move across automatically are the integrations and reports you built yourself on top of Scipio.
We build custom because every application needs different data: which data, from which practices, on what legal basis and with what consent, and which system it needs to end up in. Scipio does not publish public API documentation. In the first step, together with you, the practices and Sanday, we look at what output the practice can provide via DEX or another route, and under what conditions. Medical data is only shared where that is permitted.
Practice connected
Data from Scipio in your application.
Only what is permitted
With legal basis and consent.
Switch covered
Your integrations move across.
How we build your integration with Omnihis Scipio
We start with your application: which data you need, from which practices, on what legal basis, and how things work today. Then, together with the practices and Sanday, we look at what output Scipio can provide for this, and we build the first integration for a few practices. Once the data is correct, the other practices connect. If a practice switches to Sanday or another system, we adapt the integration so that your application keeps receiving the same data. After that, we maintain the integration when systems or rules change.
Data, practices, legal basis.
Integration reviewed together.
More practices, even after the upgrade.
Go-live, monitoring, and maintenance when things change.
What an integration with Omnihis Scipio actually does
The components below appear in almost every integration with Scipio. Which ones you need depends on your application and on the practices taking part.
Extraction
Output from DEX processed.
Selection
Only the data that is needed.
Permission
Per practice and patient.
Validation
Checked per practice.
Switching
Integration moves across to Sanday.
Reporting
For a care group or health centre.
Who we build an integration with Omnihis Scipio for
The integration is intended for those who use data from Scipio outside the system itself, and for practices that want to keep their own integrations when they switch. The more practices take part, the more it delivers.
Care groups
Chain care with data from the practice.
Health centres
Your own dashboard and overview.
Suppliers
Your application to Scipio.
Practices that are switching
Keeping your integrations.
Technology and integrations
This page is about Scipio from Omnihis. For the Sanday platform and the systems that were formerly called Promedico ASP and Apro, see our page on the Sanday integration; if your practices work with Medicom, see our page on the Medicom integration, and for referrals to secondary care see our page on the ZorgDomein integration. You can read about our approach on building software.
Why Appfront for your Omnihis Scipio integration?
A chain care report that suddenly comes up empty after a practice switches systems, data shared without a clear legal basis, or an assistant retyping what is already in the record: each costs a practice time and trust. That is what we build around: only data that is permitted and needed, checked per practice, and an integration that keeps working when the system changes.
Only what is permitted
Legal basis recorded up front.
Reviewed
Checked per practice.
Ongoing
Also after the switch.
Security and privacy for an Omnihis Scipio integration
The integration processes patients' medical data, which falls under the strictest rules of the GDPR and medical confidentiality. It uses only the data for which there is a legal basis and which the application needs, works with its own account holding exactly the rights required for that, and logs every exchange with time and result.
The integration runs in a European data centre, with encrypted connections and storage. Who at the care group or health centre may see which data is agreed in advance with you and the practices, and temporary copies are deleted as soon as they are no longer needed.
Frequently asked questions about an Omnihis Scipio integration
Questions that GPs, practice managers and care groups ask before they get started.
A GP information system from Omnihis, made for and by GPs. Since 2000, Omnihis has been owned by a cooperative of its users. Scipio runs on Mac and Windows and includes an assistant module, text message reminders and a data extraction module, among other things.
Omnihis merged with Promedico to form Sanday. Sanday still offers Scipio alongside its own platform, and offers Scipio practices an upgrade to Sanday with one-way synchronisation instead of a conversion.
No. Scipio is software for the GP practice. Hospitals use different systems and interfaces; this page is about primary care.
Scipio does not publish public API documentation. With the Data Extraction module, the practice can make data available to external parties. What output is available for your application, and under what conditions, we will look at with you, the practices and Sanday.
Sanday migrates the record. An integration or report you built yourself on Scipio will then need to pull data from Sanday. We adapt the integration so that your application keeps receiving the same data.
A Sanday integration concerns Sanday's new platform and the systems that were previously called Promedico ASP and Apro. Medicom is PharmaPartners' GP information system. The approach is similar, but the interfaces differ per system.
For care groups and health centres with multiple practices, for suppliers of an application that needs data from the record, and for practices with their own reports that need to survive the switch. A practice without its own integrations can usually carry on with Sanday's upgrade.
Data from Scipio in your own application?
Tell us what data you need from Scipio and for which practices. We will show you how an integration handles that securely, even after the switch.