EN
Contact

API

Two API approaches.

Pure FHIR R4 for healthcare experts, or REST DTOs (JSON, snake_case) for developers without FHIR knowledge — mapped bidirectionally and roundtrip-tested.

Bidirectional mapping

Both approaches are mapped bidirectionally and roundtrip-tested.

OpenAPI

Complete OpenAPI specifications for both APIs.

X-Tenant-ID

X-Tenant-ID header on all endpoints.

Option 1

Pure FHIR Gateway API

/fhir/*

For teams with FHIR expertise or specific compliance requirements.

  • Direct FHIR R4-compliant endpoints
  • Full ISiK Stufe 5 compliance
  • Native FHIR Bundle and Resource handling

Option 2

REST API Translation Service

/api/v1/*

For rapid development without a FHIR learning curve.

  • Familiar REST patterns (GET, POST, PUT, DELETE)
  • Automatic FHIR ↔ REST translation in the backend
  • Simplified JSON structures
  • ISiK compliance is ensured automatically

Example endpoints.

The same resources on both approaches — side by side, as in the product specification.

ResourcePure FHIR R4REST translation
PatientGET /fhir/Patient?identifier=123456789GET /api/v1/patients?identifier=123456789
ObservationPOST /fhir/ObservationPOST /api/v1/observations
OrganizationGET /fhir/Organization?type=hospitalGET /api/v1/organizations?type=hospital
ConditionPUT /fhir/Condition/{id}PUT /api/v1/conditions/{id}

Three pillars, one platform.

Hospitals, medical practices and care facilities onboard independently via three lateral, equal REST paths. Two API approaches per pillar.

KKH

/api/v1/*

Hospital, MVZ, university clinic

ISiK Stufe 5 (ISiK resources)

PVS

/api/v1/kbv/*, /api/v1/eau/*

Medical practice, dental practice, pharmacy, laboratory

KBV, eAU, E-Rezept

Pflege

/api/v1/pflege/*

Care home, outpatient care

ISiP basis module

Each pillar can be onboarded independently — a care home does not need an ISiK license, a practice does not need an ISiP dependency.