Synching to an OpenHIM instance about fhir-data-pipes HOT 13 CLOSED

Our starting place maybe Identifying the metrics to extract out of analytics engine. we may need to break this issue down further

from fhir-data-pipes.

So far Tested using Streaming-atomfeed

 mvn compile  exec:java -pl streaming-atomfeed \
    -Dexec.args=" --openmrsUserName=admin --openmrsPassword=Admin123 \
    --openmrsServerUrl=http://localhost:8080/openmrs \
    --fhirSinkPath=http://localhost:5001/baseR4 \
    --sinkUser=hapi --sinkPassword=hapi123 "

The analytics engine can sync data to an openHIM instance ,
in the above case

• http://localhost:5001 is the endpoint at which the OpenHIM listens to client requests

• --sinkUser=hapi --sinkPassword=hapi123 are the credentials to authenticate the client into my OpenHIM local instance

• I have tested with this public hapi fhir server http://hapi.fhir.org/ >> that is IP 35.229.94.143 and Port 80

so my OpenHIM Chanel was routing the fhir data to 35.229.94.143:80

• screen shot of successful transaction

• Request PayLoad and Response to and from the Hapi FHir through the OpenHim Instance

will do some detailed documentation

from fhir-data-pipes.

CC: @mozzy11 @k-joseph @gitcliff @Akayeshmantha

from fhir-data-pipes.

@gitcliff , at the basic setup , we would simply use OpenMHIM as just a pass thruouh,
but because we wold also want to integrate OpenCR , we will need to work on a custom mediator to route Patient demographics data to OpenCR and also route patient longitudinal data to the SHR

from fhir-data-pipes.

thanks @mozzy11 for the positive feedback

from fhir-data-pipes.

Thanks @ibacher for filing this. Can you or @mozzy11 please assign a priority label to this as well, depending on when you think this needs to be done for the PLIR project? It feels like a P1 but I am not sure.

from fhir-data-pipes.

sure @bashir2

from fhir-data-pipes.

thanks @ibacher for creating this and i think this should be a pass through mediator since we don't intend to adapt the FHIR formatted data flowing from the analytics engine to openHIM into any new format.
Unless we intend on enriching a message with a client’s unique identifier retrieved from a client registry then we can make this an Orchestration mediator.
@ibacher @mozzy11 WDYT?

from fhir-data-pipes.

we at least would need Patient,Observations and Encounters ,

from fhir-data-pipes.

nice work here!

from fhir-data-pipes.

Thanks Allan.
ya ,ill document the setup and also dockerise it

from fhir-data-pipes.

demo video https://youtu.be/U1Sz3GUKbIw

from fhir-data-pipes.

cc @kimaina
Integrated OenHIM into the pipe line with basic configurations
#90

from fhir-data-pipes.