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
API
Pure FHIR R4 for healthcare experts, or REST DTOs (JSON, snake_case) for developers without FHIR knowledge — mapped bidirectionally and roundtrip-tested.
Both approaches are mapped bidirectionally and roundtrip-tested.
Complete OpenAPI specifications for both APIs.
X-Tenant-ID header on all endpoints.
Option 1
/fhir/*
For teams with FHIR expertise or specific compliance requirements.
Option 2
/api/v1/*
For rapid development without a FHIR learning curve.
The same resources on both approaches — side by side, as in the product specification.
| Resource | Pure FHIR R4 | REST translation |
|---|---|---|
| Patient | GET /fhir/Patient?identifier=123456789 | GET /api/v1/patients?identifier=123456789 |
| Observation | POST /fhir/Observation | POST /api/v1/observations |
| Organization | GET /fhir/Organization?type=hospital | GET /api/v1/organizations?type=hospital |
| Condition | PUT /fhir/Condition/{id} | PUT /api/v1/conditions/{id} |
Hospitals, medical practices and care facilities onboard independently via three lateral, equal REST paths. Two API approaches per pillar.
/api/v1/*
Hospital, MVZ, university clinic
/api/v1/kbv/*, /api/v1/eau/*
Medical practice, dental practice, pharmacy, laboratory
/api/v1/pflege/*
Care home, outpatient care
Each pillar can be onboarded independently — a care home does not need an ISiK license, a practice does not need an ISiP dependency.