Restricting the number of times an observation template can be added

gchan · May 21, 2017, 4:53am

Hi, I’m trying to restrict the number of times that an observation template can be added. For example in the End-TB configuration trying to save a second Baseline template will return the error: “Baseline template is already filled for this treatment”.

I’d like to be able to add a similar restriction to other observation templates. I couldn’t find any keys in the clinical app json files that looked like they controlled this behaviour. Is this behaviour configurable or is it coded into an omod? If the former, would appreciate some help on how to configure this.

Thanks

arjun · May 21, 2017, 7:14am

Hi Geoff, Searching for the code, looks like its done part of the endtb omod and even the form names are hard-coded

github.com

Bahmni/openmrs-module-bahmniendtb/blob/master/omod/src/main/java/org/openmrs/module/bahmniendtb/formconditions/RulesForFormFilled.java#L55


HashMap<String, List<BahmniObservation>> mapOfTemplateForms= new HashMap();
for (BahmniObservation observation : bahmniEncounterTransaction.getObservations()) {
    if (mapOfTemplateForms.containsKey(observation.getConcept().getName())) {
        mapOfTemplateForms.get(observation.getConcept().getName()).add(observation);
    }
    else mapOfTemplateForms.put(observation.getConcept().getName(), new ArrayList<>(Arrays.asList(observation)));
}
for (Map.Entry<String, List<BahmniObservation>> templateObs: mapOfTemplateForms.entrySet()) {
    String conceptName = templateObs.getKey();
    switch (conceptName) {
        case "Baseline Template":
        case "Treatment Initiation Template":
        case "Outcome End of Treatment Template":
            if (isFormFilledAlready(templateObs.getValue(), conceptName, patientProgramUuid)) {
                throw new RuntimeException(conceptName + " is already filled for this treatment");
            }
            break;
        case "Monthly Treatment Completeness Template":
            if (isFormFilledAlreadyForCurrentMonthYear(templateObs.getValue(), conceptName, bahmniEncounterTransaction)) {
                throw new RuntimeException(conceptName + " is already filled for this month and year for this treatment");
            }

I doubt if Bahmni provides a configuration for such validation, though it provides a hook EncounterDataPreSaveCommand which is used by this omod.
I would let someone confirm that there doesn’t exist a configuration for this in Bahmni. In case it’s important and urgent i can think of a couple of options for you

modify this omod to add forms that you need to validate and rebuild and deploy it.
Creating and deploying a new simple omod that has a Java class implementing the above mentioned interface/hook EncounterDataPreSaveCommand. In case you see more needs like this you can may be think of creating a custom omod for your implementation on similar lines as bahmniendtb omod.

gchan · May 21, 2017, 8:58am

Thanks @arjun. That’s good info and helpful to understand how this has been set up. I think the first option you outlined sounds feasible and will try it out when I get the chance.