System integration · SwitzerlandIn development
Your CHMED16A1 output
already does this.
We just built the patient side.
Meditag Connect will let your practice management system or EHR automatically provision medication reminders for patients — using the CHMED16A1 payload your software already generates. One API call. No new data format. We're looking for pilot partners for technical validation now; talk to us if your practice software or EHR would be a candidate for an early integration.
The integration
The complete integration is one API endpoint.
Hospital IT teams have seen integration projects run for months with shifting scope. Meditag Connect is deliberately narrow. Here is the complete integration surface.
What your system sends: A single authenticated POST /v1/provider/enroll containing the CHMED16A1 payload you already produce — the same data that prints on the patient's medication plan. Nothing additional is required.
What Meditag does: Parses the payload, provisions timed reminders on the patient's phone, and returns an enrollment confirmation. Health data is end-to-end encrypted — Meditag's servers hold ciphertext only.
What your system never needs to do: There is no webhook to maintain. No patient identity federation. No HL7 FHIR adapter to configure. No write-back to your EHR.
Integration scope in full: One endpoint. One payload format you already produce. Estimated developer effort: one to two days for a developer familiar with your CHMED16A1 export. Your internal change advisory board, security review, and any procurement process run on your own timeline — we provide the documentation package to support that review, not accelerate it arbitrarily. The technical side will be ready at pilot start.
Compatible systems
Every certified Swiss practice system already speaks CHMED16A1.
Any practice management or hospital information system that generates eMediplan QR codes is compatible with Meditag Connect — no conversion or middleware required.
Standards roadmap
On the CH EMED migration path — ready when you are.
Operationally we read CHMED16A today — the standard every certified Swiss practice system issues. For medication enrichment we ingest the BAG Spezialitätenliste and Swissmedic Refdata directly from the regulatory data sources.
IG eMediplan has announced the transition to FHIR — explicitly: "We ask that you do not plan any new integration of the existing IG eMediplan standards." Source: emediplan.ch/softwareanbieter. The successor is CHMED20AF, a FHIR Bundle mapping within CH EMED.
We have specified the CHMED20AF import at library level (decision D-048) and are ready to implement as soon as the first practice partner hands over a CHMED20AF payload — on pilot-start timeline, with no additional lead time on our side. Until then CHMED16A remains in indefinite legacy support per IG eMediplan; your existing QR exports work the same before and after the FHIR migration. No dual-implementation burden, no big-bang cutover.
Change management
What stays exactly the same
for your clinical staff.
Your workflow
Doctors generate the eMediplan QR code as they do today. Nothing about their process changes — the integration runs in the background at the system level.
Your data
Meditag never writes back to your EHR. There is no risk of data corruption or reconciliation conflict. Your system remains the single source of truth.
Your helpdesk scope
Patients install Meditag from the App Store or Play Store. Reminders are provisioned automatically. Your IT support team's scope does not expand.
Data protection
nDSG compliant. Swiss servers. No PHI on ours.
End-to-end encrypted
Medication data is encrypted on the patient's device before any transmission. Meditag servers hold ciphertext only — we cannot read patient health data.
Swiss data residency
All servers are hosted in Switzerland. No patient data crosses Swiss borders. Compliant with cantonal data protection requirements that exceed nDSG.
DPA ready from day one
We provide a pre-drafted Swiss-law Data Processing Agreement. Your legal team does not wait months — we have this ready before the first pilot discussion.
Getting started
A pilot designed to reduce your risk, not ours.
We're setting up a time-boxed pilot programme with agreed success metrics and a no-cost exit clause. You will define what success looks like. If we don't hit it, you walk away at no charge.
Scoping call
We map your CHMED16A1 export to our API. We sign an NDA and outline the DPA. Typically one meeting, under an hour.
Technical integration
Your developer implements the single API call. A sandbox environment for testing against real CHMED16A1 payloads will be provided at pilot start. Planned timeline: days to a few weeks.
60-day pilot
Live with a defined patient cohort. We track adherence metrics you agree upfront. You retain a no-cost exit right throughout the pilot period.
Rollout
Billed per active patient per month. No minimum commitment, no per-site licence fee. Volume tiers available for larger deployments.
Commercial model
Priced to fit a medication adherence budget.
Per active patient per month. A patient is active for as long as their current medication plan is running in the system — no charge for discharged or inactive patients.
There is no per-site licence fee, no minimum commitment, and no billing integration required on your side. Volume tiers with step discounts apply for larger deployments.
Pricing is discussed in the scoping call, not published — we tailor it to your deployment size and context. Write to dev@meditag.ch to start that conversation.
For context: a single avoidable readmission in Switzerland generates CHF 8,000–12,000 in additional DRG pressure. Reducing that by even two or three cases per year across your discharge cohort pays for Meditag Connect many times over — and that is a conservative estimate.
Ongoing care
When the medication plan changes.
When a prescriber issues an updated CHMED16A1 payload for an already-enrolled patient, Meditag Connect supersedes the existing reminder set automatically — the patient is not re-enrolled as a new patient and does not receive duplicated reminders. The app shows the incoming changes alongside the current plan and applies them once the patient confirms.
This makes Meditag Connect equally suited to chronic disease management in GP networks and outpatient clinics, not only to single-event hospital discharge workflows.
For individual practices
Not evaluating a system integration?
Meditag Connect is designed for practice software vendors and hospital systems that want to automate patient enrollment at scale.
If you are a GP or specialist recommending Meditag to individual patients, no integration is needed — give the patient their eMediplan QR code and direct them to the app. It works immediately.
Integration partnership
Ready to talk?
We reply within one working day. Bring your CHMED16A1 export format and a sense of your patient volume — that's all we need for a first call.