Healthcare / FHIR API
Standard compliance
FHIR R4Mediloop FHIR interoperability behavior, supported FHIR R4 conventions and implementation boundaries.
Authentication
OAuth 2.0
Bearer token
Scope
healthcare.read
Required
Standard
HL7 FHIR R4
FHIR R4
Rate limit
600 requests / min
Default
Response
Bundle / JSON
application/fhir+json
FHIR version
Mediloop exposes HL7 FHIR R4-compatible endpoints. Resource/profile support is explicitly declared in server metadata.
Profiles
| Area | Approach |
|---|---|
| Base resources | FHIR R4 structures |
| National/EU profiles | Applied where integration contracts require them |
| Mediloop extensions | Namespaced, documented and minimized |
Terminology
Code systems and value sets are preserved where possible; mapping rules are documented when Mediloop internal codes differ.
Identifiers
External identifiers retain their assigning system URI to avoid collisions across hospitals, registries and national systems.
Extensions
Extensions must not be used to bypass standard fields. New extensions require governance and documentation.