Enhance usability of Achilles Heel

[t-abdul-basser]

Cleans up Achilles Heel including

• enhance the text in the Achilles Heels error/warning/notifications for readability
• add category description to each error/warning/notifications
• adding sortability by n
• Organization/developers involved in the implementation

Overlaps with @alondhe recent efforts.

[vojtechhuser]

What do you mean by sortability by n ? (this is atlas item in my view.
Achilles simply must have a good table to capture it but display is in atlas.

[t-abdul-basser]

Good catch. I meant sort by arbitrary column and yes that should go in Atlas.

[cukarthik]

In this refactoring, would it be possible to add the ability for a site to reorganize the Achilles message types? Based on how we populate our data, it would be nice to reclassify some ERRORS as NOTIFICATIONS. For example, we do not populate locations so do not want to have those messages tagged as an error.

[PRijnbeek]

I very useful feature would be if the Achilles Heel report would have the option to download the rendered SQL that is behind that query. This would allow you to very easily find the problem instead of first dive into the code base to find the query and then have to render and translate to your own dialect.

[alondhe]

Hi @PRijnbeek - there is a sqlOnly option, also, the return value of the achilles or achillesHeel functions does include it

[PRijnbeek]

Thanks that helps a bit already. From: Ajit Londhe <notifications@github.com> Reply-To: OHDSI/Achilles <reply@reply.github.com> Date: Friday, 18 May 2018 at 13:51 To: OHDSI/Achilles <Achilles@noreply.github.com> Cc: Peter Rijnbeek <p.rijnbeek@erasmusmc.nl>, Mention <mention@noreply.github.com> Subject: Re: [OHDSI/Achilles] Enhance usability of Achilles Heel (#209) Hi @PRijnbeek<https://github.com/PRijnbeek> - there is a sqlOnly option, also, the return value of the achilles or achillesHeel functions does include it — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#209 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AG6oiSK0AdZoZYPVV6d9YWeUtyU6k-inks5tzrWxgaJpZM4OxZQA>.

[vojtechhuser]

@PRijnbeek ad your question about

This would allow you to very easily find the problem

please look into file called Rule Drill Down here: https://github.com/OHDSI/Achilles/blob/master/inst/csv/rule_drill_down.csv
(and scroll down to column code)

For non-umbrella rules, this allows to find exactly what you want. I developed this knowledge base with the goal to display it as a hyperlink in Atlas next to the heel message output. (for developer to "drill down"). Hence the name of the CSV fille. - rule-drill down.

[MaximMoinat]

I was looking into the readability of Achilles Heel output as well. One thing I would really like to do, is sorting on the count. An example of how I now organise the Achilles Heel report:

The count as percentage of total row count would be even better.

[vojtechhuser]

I do like the percentage option. My newest additions to Heel were using the percentage paradigm. See - for example - the newest unmapped data rules. And I am suggesting R as a way to compute it. Because simple things fit in memory and can be done simpler than translating it into 7 sql dialects.

[PRijnbeek]

@vojtechhuser thanks, yes i had seen that before.

What i have done for our ETL is that i have a sql file with all the errors found in earlier sprints in our SQL dialect that will give me a list of all the patients the are in the count of that error so we can dive deeper.

The drilldown csv is now in T-SQL probably and needs translation with SQLRender.

I like to the idea to have a link or maybe even a button next to the error that will execute the query against the CDM and will show me the (top X) problematic records (with an export function).

This can be in the Achilles Heel report/sheet itself or maybe we can have a simple Shiny-App the can do this using R and all the nice tools we have there..

[alondhe]

The new Shiny app addresses these ideas, closing this ticket, but if there are ideas on how to improve the Shiny app, please feel free to open a new issue.