Integration Platform. Days, not quarters.
No hospital replaces its estate to adopt a vault. MediVault speaks HL7 FHIR R4, bridges HL7 v2, and ships SDKs and signed webhooks so the systems already running in your building can read and write without a bespoke integration project.
- Certified connectors
- 18
- FHIR resources
- 23
- Median read (p50)
- 38 ms
- Sandbox setup
- < 5 min
It has to work with
what you already run.
No hospital replaces its estate to adopt a vault. MediVault connects to the systems already in the building through HL7 FHIR R4, an HL7 v2 bridge, REST endpoints, signed webhooks and first-party SDKs.
- EHR / EMR
- Hospital information systems
- Patient portals
- Laboratory (LIS)
- Imaging (RIS / PACS)
- Pathology
- Pharmacy
- Billing & TARMED
- Scheduling
- Healthcare apps
- Analytics platforms
- Research registries
GET /fhir/r4/Patient?identifier=756.1234.5678.97
Host: api.medivaultzurich.site
Authorization: Bearer {access_token}
X-MV-Purpose-Of-Use: TREATMENT
Accept: application/fhir+json
200 OK
{
"resourceType": "Bundle",
"type": "searchset",
"total": 1,
"entry": [{
"resource": {
"resourceType": "Patient",
"id": "pat_8f2c41ba",
"meta": { "versionId": "14", "security": [
{ "code": "R", "display": "Restricted" }
]},
"active": true
}
}]
}Eighteen systems
already in production.
A certified connector is one we test against every release, monitor in production and support under the same SLA as the platform itself. It is not a code sample in a repository.
EHR & EMR
Bidirectional patient, encounter and document synchronisation with the electronic record already used by your clinicians.
Hospital information systems
Admissions, discharges and transfers via HL7 v2 ADT feeds, normalised into FHIR Encounter resources on arrival.
Laboratory (LIS)
Order and result exchange with LOINC coding, reference ranges and abnormal-flag preservation.
Imaging (RIS / PACS)
DICOM study indexing with pointers into your existing archive. Pixel data is never migrated or duplicated.
Pharmacy
Medication lists, prescriptions and administration records, with interaction data left to your clinical system of record.
Billing & TARMED
Coded procedure export for Swiss billing workflows, with clinical narrative deliberately withheld from the billing scope.
Do not see your system? Enterprise customers get custom connectors built and maintained by our integration team as part of the contract. Typical delivery for a documented interface is 6–10 weeks.
The contract
we hold ourselves to.
- Primary standard
- HL7 FHIR R4 (4.0.1). Conformance statement published and validated against the Touchstone test suite. R5 conformance in progress.
- Resources supported
- 23 resource types including Patient, Encounter, Observation, DocumentReference, DiagnosticReport, Consent, AuditEvent and Practitioner.
- Legacy interoperability
- HL7 v2.x bridge covering ADT, ORM, ORU and MDM message types, translated to FHIR on ingest and back on egress.
- Authentication
- OAuth 2.0 client credentials and SMART on FHIR scopes. Machine clients may use mutual TLS with certificates rotated every 24 hours.
- Rate limits
- 1,000 requests/hour on Klinik, 10,000 on Spital, unlimited on Unternehmen. Limits are per tenant, not per client, and are published in response headers.
- Webhooks
- HMAC-SHA256 signed payloads with a timestamped signature, 5-minute replay window, automatic retry with exponential backoff over 24 hours.
- SDKs
- First-party TypeScript, Python and Java SDKs with typed resources, automatic retries, pagination handling and built-in purpose-of-use propagation.
- Sandbox
- Isolated sandbox tenants with synthetic patient data, provisioned in under 5 minutes. No commercial commitment required to start building.
- Performance
- 38 ms median (p50) and 94 ms (p95) for an authorised FHIR read from the Swiss edge.
- Versioning
- Date-based API versions. Breaking changes ship as a new version with a minimum 12-month deprecation window and written notice to every affected tenant.
From sandbox
to certified partner.
For healthtech vendors and EHR suppliers building on MediVault, certification is a four-step path with a named engineering contact from week one.
Sandbox
Self-serve tenant with synthetic data, full API surface and no production risk. Most teams have a working read path within an afternoon.
Conformance
We review your integration against the FHIR conformance statement and our purpose-of-use requirements, and return a written gap list.
Security review
Joint review of your credential handling, data retention and audit propagation. This is where most integrations get materially safer.
Certification
Certified connectors are listed publicly, receive advance notice of API changes and get a named engineering contact.
Start building
this afternoon.
Provision a sandbox tenant with synthetic patient data, read the FHIR conformance statement and make your first authorised call — before you talk to anyone in sales.
Sandbox tenants are free and require no commercial commitment