AJ FHIR Platform Architecture Overview: Five-Layer Structure and Interoperability Flow
Architecture Overview | AJ FHIR Platform
Summary
This article details the modular, five-layer architecture of the AJ Smart FHIR Platform. Each layer—from applications to infrastructure—is independently deployable and replaceable, outlining a detailed technical flow for EHR launch and component interaction.
Details
The AJ Smart FHIR Platform utilizes a modular, five-layer architecture: Layer 5 (Applications), Layer 4 (Auth & Identity), Layer 3 (FHIR Data Layer), Layer 2 (Compliance & Audit), and Layer 1 (Infrastructure). A key feature is that each layer can be deployed or replaced independently. The EHR launch flow demonstrates the technical sequence: a clinician logs in, fetches patient data from HAPI FHIR, and initiates an OAuth2/PKCE-based authentication via the Auth Server. The process involves generating launch tokens and redirecting to the SMART Client. Technically, communication is secured by multiple mechanisms. The SMART Client interacts with the Auth Server using OAuth2 + PKCE. Meanwhile, HAPI FHIR JPA data access is protected by a SmartScopeInterceptor utilizing RS256 JWTs. Furthermore, every data access triggers an audit record via the AuditService, ensuring compliance with standards like GDPR and HIPAA. This architecture provides a robust blueprint for achieving both security and scalability in complex healthcare interoperability environments.
Original content copyright by respective publishers