Enterprise pricing for API integration
The cost of an API integration depends on the volume of data, the number of facilities, and the expected level of compliance. This page presents Vitalink HealthData pricing options for a hospital environment or clinic. Exact amounts are determined by quote, based on your specific case.
The scope determines the price, not the grid
The volume of processed measurements, the number of device sources, and the number of target systems influence the price. A single-site project does not have the same constraints as a multi-facility deployment. The level of support and compliance requirements are also taken into account. We provide a quote after understanding your architecture.
In other words: describe your workflows first, then we provide a quote. A clinic connecting two types of blood pressure monitors does not purchase the same scope as a hospital group connecting four sites to the same electronic patient record.
- Measurement volume Number of blood glucose series and wearable device readings ingested each month, along with their synchronization frequency.
- Device sources How many models of glucometers and watches you are connecting, and through which manufacturers their data is retrieved.
- Target systems The electronic patient record(s) and middleware receiving the data, and the HL7 FHIR profiles they expect.
- Support and compliance The desired level of support, security reviews, and data retention or localization requirements.
Three offers, one common integration foundation
No amounts are displayed: each hospital deployment has its own volume and compliance level. Choose the column that matches your project, then request the corresponding quote.
Entry-level offer
Suitable for projects starting with a limited number of devices and a single target system.
- API access and OAuth authentication
- Test environment provided
- Standard channel support
- Single target FHIR profile
- Ideal for validating a first workflow in real-world conditions
Clinical offer
For facilities integrating multiple device types and multiple FHIR profiles at one site.
- All entry-level offer foundations
- Integration support
- Enhanced support
- Role-based access scopes
- Detailed exchange logging
- Aims for production deployment at one site
Enterprise offer
Covers multi-site deployments and advanced governance needs.
- All clinical offer foundations
- Access rights definition with your teams
- Dedicated contact person
- Assisted facility-side security reviews
- Sizing according to your volumes
- Multiple target systems and multiple sites
What is added to the base offer
Depending on your facility, additional compliance requirements may apply. These concern log preservation, data localization, and retention periods. These options are defined with your compliance officer. They are added to the base offer and appear separately in the quote so that the budget line remains clear.
The Swiss legal framework (FADP) and the European regulation (GDPR) are not handled the same way depending on whether your data remains in Switzerland or transits to a European partner. These trade-offs are made with your compliance team, not via a checkbox.
See the security and encryption page- Preservation of access and exchange logs, with a duration agreed upon in writing.
- Data localization: hosting in Switzerland or in a defined European region.
- Retention periods for measurements and metadata, aligned with your internal policy.
- Processing of patient access and rectification requests, documented with your teams.
- Record of processing activities maintained by the facility, supported by our technical descriptions.
These elements are discussed before signing, never after production deployment.
The scope of the quote
Vitalink does not provide devices or patient terminals. We do not replace your existing electronic patient record (EPR) or middleware. The API integrates with your environment; it does not replace it.
This boundary avoids misunderstandings during the quoting process. If your tender includes the purchase of blood glucose meters, the replacement of legacy middleware, or a complete migration of the EPR, these items are handled by your usual suppliers. Our quote covers the integration layer and service operation, nothing else—which makes the comparison between offers honest.
Four steps, then a figure
A technical demonstration may precede this step. It is performed on your test environment, not on a generic mockup.
-
You describe your use case
Device types, estimated monthly volumes, target systems. An approximate architecture is enough to start the discussion.
-
We identify endpoints and FHIR profiles
We list the relevant resources, the flows to be opened, and the access control points to be set up with your teams.
-
A quote is established with applicable options
The document distinguishes the base offer from compliance options, so that each item can be discussed separately internally.
-
You validate the scope
Volume, support, or retention adjustments before signing. Final sizing is based on your actual figures.
Invoicing and commitment
Purchasing procedures for Swiss hospital facilities follow their own channels. The quote adapts to them.
Personal data processing and compliance commitments are detailed in the site's privacy policy. It describes the Swiss (FADP) and European (GDPR) framework applied to the health data you entrust to us.
Privacy policyScope matters more than the displayed price
The choice depends less on the displayed price than on the scope: number of sources, target systems, level of support. A single-site project is often satisfied with the entry-level or clinical offer. A multi-site deployment justifies the enterprise offer. Start by describing your architecture, the rest follows.
If you are starting out
A single target system, a few device models: the entry-level offer is enough to prove the flow before expanding.
If you are deploying widely
Multiple sites, multiple EPRs, governance to maintain: the enterprise offer and its dedicated contact person make the difference.
A question about endpoints, encryption schemes, or connecting to your middleware? The API documentation describes the available resources, and the security page details the encryption schemes applied to health data.
Let's talk about your architecture before talking about numbers
The quote is not built blindly. Describe your devices, your estimated volumes, and your target systems: we will get back to you with a clear scope and the compliance options that apply to your facility.
Request a quote- Vitalink HealthData AG
- Seefeldstrasse 45, 8008 Zürich, Schweiz
- +41 21 581 78 71
- [email protected]
- Monday – Friday: 09:00 – 18:00 (CET)
For an initial technical discussion, indicate the type of devices and the target EPR: we will prepare the demonstration accordingly.