Interop Service — AI Integration
Status: populated Owner: TBD Last updated: 2026-04-18 Companion: Service Template · 03 platform-services · 02 DDD
1. Current AI Usage
The interop-service does not invoke AI/ML models directly. It is a pure infrastructure/integration layer. No vendor AI SDKs are used.
2. Relationship to AI Gateway
The interop-service is the routing intermediary for AI-relevant clinical data:
- The
ai-gateway-servicereads clinical FHIR resources through the FHIR gateway (interop-service) using service-to-service auth + minimum-necessary ABAC scoping. - The interop-service enforces that AI service reads are audited and tenant-scoped, the same as any other FHIR consumer.
3. Future: AI-Assisted Mapping (Tier B)
| Feature | Purpose | HITL | Status |
|---|---|---|---|
| HL7 v2 segment mapping suggest | When an unknown message type is received, suggest a mapping to FHIR resources | Yes — integration admin accepts/rejects | Not implemented |
| FHIR profile gap detection | Detect missing required fields in submitted resources before routing | Rule-based (not LLM) | Not implemented |
4. Rationale
Integration mapping is a high-precision technical operation. Automated AI-suggested mappings without human validation would risk data corruption. Baseline implementation uses deterministic, tested mapping functions. AI assistance is a stretch goal for complex edge cases.