Open lg-king opened 1 year ago
Potential future iterations — if information from Model field seems to be insufficient — could explore displaying more information on search, similar to device code lookup design. Example:
@lg-king One other thought: I checked on some of the devices that don't include the manufacturer name in the Model field (Abbott and Quidel devices, among some others) and it seems to be consistent with how they're branded. For example, it seems likely that someone testing with an Abbott ID Now device would know it as "ID NOW."
To be safe, though, I wonder if we want to make devices also searchable by Manufacturer, even if we only display Model name?
@lg-king Updated sketch with diseases instead of LOINC code, per our conversation yesterday:
@lg-king Updated sketch with diseases instead of LOINC code, per our conversation yesterday:
Description
We're going to be pulling COVID/flu device information from ReportStream's LIVD table API and need to decide what information to display from the table so users can select the right device — in other words, which columns from the LIVD table should we include in the name? Our current system uses names that we've specially created, primarily drawn from the Model column.
Users can select device names in the following locations:
Design considerations
Google doc exploring ideas: https://docs.google.com/document/d/1C6rDRANcW3wKIXOAIseDiucA8yZ8zTW4AT2wYoJZvG4/edit?usp=sharing
Update 2/21: Laura to add device code lookup vs. admin setup sketches, waiting for feedback from engineering.
Update 3/13: Recommended using just "Model" field for name for first iteration.
Latest sketch: