Diagnosis Posting Error in Bahmni: Boolean Concept Issue

Hi there. I’m encountering an error when trying to post a diagnosis, specifically when attempting to include the additional concepts for Bahmni. The issue seems to occur with “Bahmni Diagnosis Revised” when it tries to convert the ‘false’ concept, leading to a “Caused by: org.hibernate.LazyInitializationException”. I’ve tried various values for ‘false’, including the UUID, false, 0, and no, but none have worked.

Any help would be greatly appreciated. Also, is there a better approach to posting Bahmni diagnoses? I I am posting on /obs, using the latest docker images and my payload is something like this

{
    //visit diagnosys
    "concept": "b9e87e0d-f496-11ed-b02c-0242ac150003",
    "groupMembers": [
        { //cough
            "concept": "b9eb8b5f-f496-11ed-b02c-0242ac150003",
            "value": "116128AAAAAAAAAAAAAAAAAAAAAAAAAAAAAA",
            "obsDatetime": "",
            "person": ""
        },
        { //diag certainty
            "concept": "b9ec5423-f496-11ed-b02c-0242ac150003",
            "value": "b9edd03d-f496-11ed-b02c-0242ac150003", //confirmed
            "obsDatetime": "",
            "person": ""
        },
        { //Diag Order
            "concept": "b9ef1fe8-f496-11ed-b02c-0242ac150003",
            "value": "b9f01632-f496-11ed-b02c-0242ac150003", //secundary
            "obsDatetime": "",
            "person": ""
        },
        //initial diag
        {
            "concept": "baa2596f-f496-11ed-b02c-0242ac150003",
            "value": "none",
            "obsDatetime": "",
            "person": ""
        },
        //revised
        {
            "concept": "baa2c983-f496-11ed-b02c-0242ac150003",
            "value": "488b58ff-64f5-4f8a-8979-fa79940b1594",
            "obsDatetime": "",
            "person": ""
            
        }
    ],
    "obsDatetime": "",
    "person": "",
    "encounter": ""
}

Full error: bahmni post diag error - Pastebin.com

Weirdly, in my localhost it worked, but on my aws server that error happens. A solution, for now, was to add hibernate.enable_lazy_load_no_trans=true in openmrs-runtime.properties on onpenmrs container.