radiology module: dependency on emrapi

Development
, ,
1

Dear @judy, @sunbiz and others,

I just wanted to clarify why we chose to use the EMR API in the radiology module.

The reason is that for creating an Order via the OpenMRS OrderService.saveOrder we need to create an Encounter. An encounter can be created without a Visit but the Visit is used to group Encounters. So we thought that it would be great to also create a Visit and attach our radiology Enounter created for the RadiologyOrder to that Visit. So later it is easy to get all Encounters created during this Visit. Now the EMR API has already solved this part giving us the EmrEncounterService. It not only creates a radiology Encounter for us, it also creates a Visit if there is no active Visit for the patient we want to create an order for and attaches the Encounter to that Visit. If there is an active Visit it attaches the new Encounter to this Visit.

So now because of our dependency to the EMR API we now need to install a bunch of other modules:

I understand that this is more work for the implementer.

We could remove the dependency again, this would just mean a lot of work from our side to implement the behavior described above. We just do not have a lot of resources available for the radiology module.

Let me know what you think.

1 Like
2

I agree to use the platform and depend on the Emrapi

The question to the larger community is if we need to split these dependencies out of Emrapi and leave only critical ones

3

Removing some dependencies from the emrapi module is discussed here:

There are several dependencies that can and should be removed, provided someone does the work. Anyone is welcome to do that!

1 Like
4

Thanks for the info, I’ll have a look!