HAPI-FHIR in Spring Cloud environment

[Dimitar Dimitrov]

Hi team.

We start to develop a Spring Cloud based project which will implement HIS for one of our clients. So now we are trying to use HAPI FHIR for domain model, servlet and persistence layers. 

My idea is to produce some microservices which will be common for whole microservice infrastructure. For example patients did not have any relation to other structures so it could be developed as a single microservice.

This requires the persistence layer to be more granular and should have a separate DAO for each FHIR resourceType. So my question is, how we can persist the Patient class directly without using some intermediate infrastructure. 

Is there some kind of utilities classes that produces a POJO  which can be persisted directly no mater the persistence layer technology which is used (for example SQL or NoSQL).

Thanks in advance.

Dimitar

[Kevin Mayfield]

Do you mean - multiple micro-services persisting to one HAPI instance?

If so I've been doing something similar using Apache Camel (one interface is for HL7 v2 and another is for more complex FHIR messages plus normal HAPI https://github.com/KevinMayfield/Jorvik)

[Dimitar Dimitrov]

Hi Kevin. 

Actually I mean that I am truing  to develop a distributed FHIR server with Repository layer which is not strictly bonded to specific persistence technology. 

Also If I use JPA for example I would like to persist every resource in separate table. I am not sure but with HAPI-FHIR it seems that the service layer did not give me the possibility to integrate with some Integration framework (for example messaging with ActiveMQ) as in your case.

As far as I know the Workflow part of the FHIR specification, have some automation behavior, which should be managed by more complex logic. For example Scheduling, where the AppointmentResponces should update the Schedule state. Is this mechanism is already implemented in HAPI FHIR?

Regards

Dimitar

[pete...@gmail.com]

Not sure exactly what you are looking for but see example here

https://blog.healthdataintegrator.com/2020/05/29/extending-the-hapi-fhir-jpa-project

where you can send a message to a queuing system for further processing as you see fit.
You can use the kafka queue as suggested as a starting point to a different storage system or to kick off any automation you need even using spring cloud components.