Architecture Diagram
Last updated
Last updated
The SPICE platform supports the standard.
Represents external Electronic Health Record (EHR) or Electronic Medical Record (EMR) systems. These are external healthcare data systems that provide or consume patient-related information, enabling data interoperability with the SPICE platform.
A mobile application used by healthcare professionals or field workers for managing patient records, accessing clinical workflows, and syncing data with the SPICE platform.
A web-based application for administrators and healthcare managers to manage system configurations, users, and Client Facing Reports (CFR). It serves as a central portal for administration and data visualization.
The core system enables healthcare data management and interoperability. It integrates multiple components to ensure seamless data flow between external systems and the FHIR server.
Subcomponents of SPICE Platform:
FHIR Converter: Transforms non-FHIR data from external systems or the SPICE Mobile App into FHIR-compliant resources to be stored in the FHIR server.
SPICE Core: The central processing engine handling data synchronization, queue management, and core business logic.
Queue: A mechanism to handle offline data sync from the mobile app, ensuring data integrity even in low-connectivity scenarios.
User Management: Manages authentication, authorization, and user roles within the SPICE platform.
Notification: Sends alerts, updates, or confirmations to users via email, SMS, or push notifications.
A reference to the World Health Organization’s SMART (Standards-Based, Machine-Readable, Adaptive, Requirements-Based, and Testable) guidelines that define healthcare data workflows and best practices. The SPICE platform aligns with these guidelines for standardization.
A server implementing the HL7 FHIR standard using the HAPI FHIR JPA Server. It stores and retrieves FHIR-compliant healthcare data.
A PostgreSQL database serves as the backend storage for the FHIR server. It securely stores all FHIR resources (e.g., Patient, Observation, etc.).
A separate PostgreSQL database for storing administrative and metadata information required by the SPICE platform, such as user roles, configurations, and system logs.
