What inspired this Wish List Request?
JMP Clinical 19.0 introduced a number of new reports that are summary level, not patient level reports, and based on past customer questions about drilling down to patient level information, it seems prudent to add such buttons to make this process/workflow easier to explore patient live data from these summary level reports. Creating Review Subject Filter and Derive Population Flags buttons are the main request, but getting subject level data directly with a click of a button for select items in a graph or table is good too (like Correlated Findings report).
There are the current list of summary level reports that do not have drill down buttons to get to the patient IDs: Medical Query Distribution, Dynamic Survival, Subgroup Screening, Recurrence, Nearby Occurrence, Co-Occurrence, AE Risk Report, Medical Query Risk Report, Algorithmic Medical Risk Report, Custom Medical Query Risk Report, Event Risk Report, Intervention Risk Report, Correlated Findings (Show Findings button does give list of subjects), Frequencies, and more.
Please describe the new or improved feature or solution you would like to see.
A Jira was created for Recurrence report and there is the link: https://jmpdiscovery.atlassian.net/browse/JMPCLINICAL-5096.
This is a general request and in it may not make sense to add these kinds of drill downs in some reports. It depends on the workflow of the user and the type of report. Usually this type of question/request comes from wanting to know more about the patients that drive the particular signal of interest that the report is highlighting.
What would the value be to you and/or other users if this new feature is provided?
Save time to get at patient level and reduce the number of clicks to get there.
Is this an external customer request?
None for the new reports because they are new, but for previous reports this question would come up with existing reports and we would show a work around.
Is there a competitive software package that has this feature or solution that we should be aware of?
Not that I am aware of
Will this impact a renewal, expansion, or adoption at a customer, and does this put an account at risk if we do not address this?
Not that I am aware of.