Natively in Aidbox

Context diagram

EHR Systems: External systems (Epic, Meditech, etc.) send data in different formats: HL7v2, CDA, X12, eRx.
Aidbox (with Native Converters): Central platform that natively converts incoming messages into FHIR resources, validates them, stores them, and exposes FHIR API. No custom intermediate integration layer is needed.
Data Platform / Alert System: Downstream consumers for analytics, reporting, and alerting, using standardized FHIR data from Aidbox.

FHIR_Server (Aidbox FHIR Server)
- Core application handling FHIR REST API, GraphQL, subscriptions, and operations.
- Processes incoming FHIR resources, performs validation, and enforces business logic.
- Exposes resources to downstream systems (analytics, alerting, reporting).
FHIR_DB (AidboxDB – PostgreSQL with FHIR extensions)
- Stores all FHIR resources in a highly optimized PostgreSQL database with JSONB support and FHIR-specific extensions.
- Provides ACID-compliant storage and indexing for efficient queries and transactions.
Native_Converters / Integrations
- Converts external messages from multiple formats (HL7v2, CDA, X12, eRx) into standardized FHIR resources.
- Acts as the integration layer for incoming data from hospital systems.
Security_Service (Security & Access Control)
- Handles authentication, authorization, and audit logging for all system operations.
- Ensures regulatory compliance and secure access to sensitive medical data.
EHR_System (External Systems)
- Hospital systems like Epic, Meditech, or others sending messages in HL7v2, CDA, X12, or eRx formats.
- Sends messages via MLLP (through built-in listener), SFTP, or REST API.
Data_Platform / Alert System (External Consumers)
- Downstream consumers using standardized FHIR resources for analytics, dashboards, reporting, and real-time alerts.