Current recall widget

[madjenjen]

User story of Feature #7

As a user, I want to see clear recall information about my input so that I can immediately know whether to take action regarding a food, drug, or device.

Acceptance criteria:

• Widget is top-most on the results page
• Widget only displays relevant recalls if their status is set to "Ongoing" or "Pending"
• If no "Ongoing" or "Pending" recalls relevant to the input exist, then the widget displays a message that says "There are no current recalls for [input]"
• Widget displays "Ongoing" recalls first as a group
• Widget displays "Pending" recalls second as a group
• Each group of recalls is sorted by severity (from most severe to least severe)
• Widget displays information about each recall including: product name, product description, reason for recall, recalling firm, report date, and status
• Widget displays condensed version of multiple results if there is more data than can be displayed clearly
• Widget is styled according to the style guide

[hwharding]

mockup here:

[TheConnMan]

If there are multiple recalls which match your criteria should they each be their own card or all be placed into a single card?

[ventrea]

The acceptance criteria seems to imply that the widget is always present but only data if there is a recall matching your criteria. Is that the intent? "Widget only displays relevant recalls if their status is set to "Ongoing" or "Pending"

[ventrea]

Disregard above! Third bullet effectively covers the use case in question: "If no "Ongoing" or "Pending" recalls relevant to the input exist, then the widget displays a message that says "There are no current recalls for [input]".

[madjenjen]

@jeffsouthard is working on designing what widget will look like when too many results come back. @TheConnMan could you display all for now so we can see what it looks like for now and then we can determine how many is "too many"?

[TheConnMan]

Added current recalls, assigning to Andy to add styling.

[AndyCouch]

We don't actually have severity data, so we can't have the recalls "sorted by severity (from most severe to least severe)" All we have is a field that states whether the recall was voluntary or mandated and it's not a boolean or enum, so we'd have to do string matching to sort by that data. Regardless, how the recall was issued still isn't exactly the same as severity.

[ventrea]

Severity data is included in the "classification" field and either Class I, Class II, or Class III.

https://open.fda.gov/drug/enforcement/reference/ https://open.fda.gov/food/enforcement/reference/ https://open.fda.gov/device/enforcement/reference/

[jeffsouthard]

Class I = Dangerous or defective products that predictably could cause serious health problems or death. Examples include: food found to contain botulinum toxin, food with undeclared allergens, a label mix-up on a lifesaving drug, or a defective artificial heart valve. Class II = Products that might cause a temporary health problem, or pose only a slight threat of a serious nature. Example: a drug that is under-strength but that is not used to treat life-threatening situations. Class III = Products that are unlikely to cause any adverse health reaction, but that violate FDA labeling or manufacturing laws. Examples include: a minor container defect and lack of English labeling in a retail food.

[jeffsouthard]

Here is the current design (supplied by Andy Couch) with suggestions. Assuming that the initial card needs to just give the user enough to identify if the recall is relevant to them, the product_description and distribution_pattern seem most important. I've redesigned with that in mind and am suggesting that the card expands or goes to another page which contains all the recall information. See attached image for all the suggestions.

[jeffsouthard]

And here is suggestion for how to treat multiple results and abbreviated "row" version of each recall.

[madjenjen]

@jeffsouthard I created a new user story for the aggregated view. Let's move mockups and conversation to #84.

[madjenjen]

Accepted!