When you look at obs and Order are already handled in the Encounter openmrs-core/Encounter.java at master · openmrs/openmrs-core · GitHub We shall need to create a ticket for handling the diagnosis.
Please advise. cc: @ibacher @dkayiwa
Regards,
When you look at obs and Order are already handled in the Encounter openmrs-core/Encounter.java at master · openmrs/openmrs-core · GitHub We shall need to create a ticket for handling the diagnosis.
Please advise. cc: @ibacher @dkayiwa
Regards,
We have the patientdiagnoses
resource as per the tests in this class: openmrs-module-webservices.rest/DiagnosisController2_2Test.java at master · openmrs/openmrs-module-webservices.rest · GitHub
This would work for a single entry(diagnosis), Remember the encounter stores visit note text as Obs then we also have multiple Diagnosis which is primary and secondary or Multiple values in each category which this rest-end point doesn’t support.
@abertnamanya , Can we create a ticket in core for supporting rest end point for patient diagnosis that is not supported for this case,. Will this one be of help ?
You can make more than one REST call.