Clinical Errors / Schema Validation Errors should be updated to include an identifying value (for example primary_diagnosis_id) or other detailed information related to the specific record with the error
See attached screenshot where DO251485 has two records, both have lymph_nodes_examined_method marked as an error, but only one of the two records has the value Yes which is triggering the error
This is because the front end does not have enough information to distinguish which record has an error
May be able to leverage 'Index' property on Errors on Platform UI to fix this
Otherwise, solution will most likely involve changes on both Lectern Client (processRecords) to populate Error Records with additional data, and Argo Clinical (Clinical Errors) to return correct Error Record objects
demariadaniel
commented
3 months ago
Clinical Errors / Schema Validation Errors should be updated to include an identifying value (for example
primary_diagnosis_id) or other detailed information related to the specific record with the errorSee attached screenshot where DO251485 has two records, both have
lymph_nodes_examined_methodmarked as an error, but only one of the two records has the valueYeswhich is triggering the errorThis is because the front end does not have enough information to distinguish which record has an error
May be able to leverage 'Index' property on Errors on Platform UI to fix this Otherwise, solution will most likely involve changes on both Lectern Client (processRecords) to populate Error Records with additional data, and Argo Clinical (Clinical Errors) to return correct Error Record objects