prime-simplereport icon indicating copy to clipboard operation
prime-simplereport copied to clipboard

Backend for the uELR admin panel

Open mindyatwork opened this issue 8 months ago • 1 comments

Description

As an admin user, I want to set up the test orders and specimens that are available for my facility to report on.

Proposed solution

  • [ ] Implement the backend work necessary to support the Test Order section as detailed in this prototype. This should be under app/settings/facilities
  • [ ] This work includes storing names, descriptions, and associated specimens for each test order

Points of contact

  • [ ] Work with @mpbrown for eng direction (ex. how to populate the data and use the right feature flag)
  • [ ] @khayeni-SL for questions on the UX prototype
  • [ ] @mindyatwork for product questions

mindyatwork avatar Apr 21 '25 19:04 mindyatwork

Currently waiting on:

  • uELR PR to be merged
  • feedback from admin users

mindyatwork avatar Apr 23 '25 20:04 mindyatwork

~~Posted these on Slack, but pasting here for record keeping. Referring to the prototype here: https://www.figma.com/proto/LglkDsGZDKMZm3XCkJPhfR/SimpleReport-2023---April-2025?node-id=9527-2392&t=YF4SW3CcaocYbGWB-0&scaling=min-zoom&content-scaling=fixed&page-id=9368%3A22533&starting-point-node-id=9540%3A3540~~

~~When should changes be propagated or "saved" when it comes to the name + description? Should they be propagated to the database once the user clicks "Save"?~~

~~What should the "Reset" buttons do?~~

~~When should changes be propagated for the Added Specimen Types? For example, should they be propagated immediately when a user clicks "Add specimen" on a specimen in the list?~~

~~If the above are true, should the Confirm button behave exactly as the Cancel button and the X button (only closes the modal)?~~

EDIT: Realized this questions are better suited for the front-end task, so I'll move them there.

kevinfiol avatar Jun 03 '25 20:06 kevinfiol