Architectural Layers
FOSPS is structured using a three-layer architecture that separates concerns and enables modularity.
FOSPS is structured using a three-layer architecture that separates concerns and enables modularity.
Connectors are modules responsible for modularizing access to external Trusted Sources of Information (TSI) and performing necessary format transformations into FHIR format.
The FHIR Server is an internal component of FOSPS, often implemented using the HAPI FHIR JPA Server Starter, responsible for managing FHIR resources.
FOSPS is the overall software platform designed using a microservices-based, three-layer architecture to support the G-lens solution.
G-lens is the pioneering solution supported by FOSPS that empowers patients to access trustworthy, personalized Electronic Product Information (ePI).
Istio is the service mesh used by FOSPS for network management, providing traffic control, security, and acting as the Service Mesh and Gateway.
FOSPS uses Kubernetes (k8s) as the underlying orchestration technology and Helm Charts as the packaging system for deploying components.
FOSPS uses OpenAPI Specification (OAS) as the standard for API documentation, exposed through Swagger UI deployment.