REST doesnot specify concept or obs causing error

Hi all,

We are using REST v2.11.dae2e2 for creating patients and encounters. Our form can have 20-40 questions and answers. Problem is during encounter submission, if there is anything wrong in creating obs, like uuid of concept is wrong or specified answer doesnot match concept data type, it just throws exception mostly conversion exception but no clue of which obs caused the issue. This becomes difficult to trouble shoot as one submission could have many obs. An example submission is

Is this issue targeted in next version of REST? Or is there any way to guess which obs could be reason of error as rightnow its checking each and every obs for data type and uuid ?

That was my intention when creating

It requires an important task of analyzing all possible wrong inputs to show the proper error messages.

I commented on the ticket @lluismf created