Different components of the Medblocks stack
Medblocks is a set of microservices that can be run individually or together. Each service is a docker container that can be configured using environment variables. Most of the services are directly built from a source repository and can be updated by updating the docker image.
Below are the main components of Medblocks, each handled by one or more containers.
It is responsible for answering the question: “Who is accessing the data?”.
It is responsible for answering the question: “Does this user have access to do this?”.
Stores logical data and provides a mapping to other services to provide a consistent FHIR API.
Use HAPI JPA Server to provide the full FHIR REST API on multiple resources that do not directly represent clinical content - eg: Patient, Practitioner, Organisation, Appointment, Invoice. Resources like Observation and Condition that represent clinical content are mapped from EHRBase and are provided as a read-only API using HAPI Plain Server and EHRBase FHIR Bridge.