-
Notifications
You must be signed in to change notification settings - Fork 2
Description
Describe the feature
Views should be fully customisable and editable so that users can build their own views for tasks and patients and be able to filter/sort by patients and tasks. Ideally we would have a button where we can build custom filters based on properties for each table. The filters then have to be conditional based on the property type:
- Text
- equals
- does not equal
- starts with
- ends with
- contains
- does not contain
- date
- is
- before
- after
- ideally these would also be possible as a relative date, e.g. a filter that checks which patients equal "today" on a property called "suspected discharge date"
- number
- is
- is not
- gt
- lt
- get
- let
- checkbox
- checked
- unchecked
- tags
- is
- is not
For all: is empty/is not empty
User Flow:
- User clicks a button for adding a filter
- Menu (maybe a modal) opens up for adding that filter to the table
- users have to select the property, filter type and maybe a value (depending on the filter, e.g. a text that should be checked for or a number to compare to
- accept -> Filter is added to the table, decline -> Process is discarded
- filter gets placed on top of the table as a little icon, maybe a pill that indicates that the table is currently being filtered
Ideally:
Filters could be saveable and that way made persistent! An additional dropdown menu in the sidebar with custom filters for example that the user can save there.
Suggested Flow:
- button click on "add filter" button in the sidebar -> Modal opens up for filter creation
- first: Selection if tasks or patients should be filtered => Main decision gate
- then: All available properties and data can be selected as filter options (so team, clinic, location in case of a patient, as well as all properties)
- filter has to be named
- button on save -> Saves the filter permanently, button discard -> discards the process
- remember to include a button where a once created filter can be edited and a button where a filter can be deleted.
Why is this feature needed?
Users have different needs on what they want to see and how they want it to be presented. E.g. a card based view on regular wards grouped by rooms, a list based view of all patients grouped by the facility they're in, a list view sorted by name etc.
Additional context
Checkout notion filter for databases for a nice UI flow
