Ghasi e-Prescribing Gateway Service — AI Integration
Status: populated Owner: TBD Last updated: 2026-04-18 Companion: Service Template · 03 platform-services · 02 DDD
AI Usage Status
No AI orchestration in ghasi-eprescribing-gateway-service v1 through v3 (Phase 0–3).
The gateway is a medication interoperability and routing service, not a clinical decision support or content generation service. AI involvement in prescription routing would introduce latency, non-determinism, and regulatory complexity incompatible with the core mission (accurate, fast, auditable prescription mediation).
Rationale for explicit N/A:
- Prescription routing, FHIR profile validation, and ETag concurrency are deterministic operations — AI adds no value and introduces risk.
- Clinical CDS (e.g., drug interaction detection) is the responsibility of the EHR (orders-service) per platform boundaries. Any CDS passthrough to the gateway is a Phase 4 P2 gated feature requiring a separate ADR and clinical governance review.
- No patient-facing text generation occurs in this service.
Future Consideration (Phase 4 only — gated)
| Feature | Description | Gate condition |
|---|---|---|
| CDS passthrough | Forward structured CDS Hooks requests to ai-gateway-service for drug interaction / allergy checks | Separate ADR; clinical governance sign-off; latency SLO defined; Phase 4 only |
If any AI integration is added, it MUST:
- Route exclusively via Kong
/v1/ai/*→ai-gateway-service(no direct vendor SDK). - Have HITL for any clinically significant output.
- Be documented in a revision of this file.
- Pass security reviewer sign-off.
Platform Reference
See ai-gateway-service/AI_INTEGRATION.md for platform AI governance model.