Form Management Challenge – Healthcare Document and Form List Views

Design Challenge

The purpose of this screen is to allow a Solution Admin to configure one or more form list views. A form list view will have a Name property and will contain all the forms defined in the associated form query. What the Solution Admin needs is a way to arrange the forms in a list for use by the healthcare staff take are relative to their department or function. The forms list view can have categories and sub-categories (folders), and Packets (which are just a grouping of forms that are always used together) in a specific order.

The following was the legacy application interface. This image was provided by the product manger and explains some of the existing screen componentry. Figure 2 shows an example of the end result is that the healthcare staff will see after a forms view list is created and published to use for selecting form(s) to add to an encounter record.

Figure 2

My Solution

Form Manager

View Userflows

Project Date: 4-19-2023

Requirements Form List Views: Create, Add, Edit, Delete with Subcategories

1. Ability to create, edit or remove a list?
2. Yes, user can drag forms to any tile on the right and drop it – without confirmation, order of forms is same order a library.
3. Library setup should follow a tasking logic for the user: Group files according to the common grouping in the industry. This will reduce the need for reorganizing forms in the list.
4. User must select a department before creating a list. Requires error prompt to select first. I did not build the list creation modal. Add list would require user to add a title for the list and a description text area input. Possibly inline editing here, would confirm inline edits with dev teams. Save, creates list. User starts adding forms from the left.
5. Add New packet(workflow), remove, edit… goes to workflow diagram.

1. Infotip opens form editor overlay or navigates to WYSIWYG with form loaded – either read only – or read write depending on role permissions.
2. Presets based on Tags.
3. The database tags the groupings in the library as packets, files, folders – just like an operating system.
4. Preset in configuration either the user setups the departments or software creators preset. Departments, categories fall under departments. Library grid features:
5. Order the files inside of the packets and categories.
6. There are two views tiles and table view.