Fs reasoncode
- 1. Reason code Management – Functional Specifications Load Reasons Popup: The user clicks on the Reasons button to bring the master set of reasons as a popup. The popup seamlessly popsup and is placed in the center of the screen The focus is now set on the first item on the grid and the item is highlighted The grid renders itself with the reason name ordered in the ascending order The grid will be a read-only view of the reasons. The reasons category will be populated from the master set of reason categories Hitting Enter will be treated as clicking “Ok” and shall dismiss the popup and accept any items that have been selected in the grid and hitting Escape is equivalent to clicking cancel and shall also dismiss the popup but ignore any selected items in the grid. The user can choose multiple items by checking the checkbox to the side. Upon hitting Ok, items chosen will be populated in the reasons text box and hitting cancel or esc will ignore any other chosen items. Appropriately the maximum duration is chosen and populated into the control for durations If there are conflicts in the scheduler, changes are made to the scheduler grid however an error/warning notification is presented with appropriate text. Jeff will identify the text to be display for all the contexts. Also, corresponding Templates will be loaded in the rich-text box Deleting or changing the reasons will not clear out the already loaded templates in the rich text box. If 2 reasons share the same notes and special instructions, it is added only once in the rich text control UX Specifications: Refer to document TFS 2356 – ReasonCode_Management.pptx for UX slides 2- slides 16 for other UX related specifications.
- 2. Note: Rules listed in this document override any specifications listed in the Powerpoint deck. Also, some features in the Powerpoint deck not detailed out functionally in this documentis out of scope for development. Corp Admin - Reasons grid: The corporate admin can add/edit reason code and its attributes with the exception of Note-templates Reason name and duration are the only mandatory fields. The Add button is disabled when the mandatory fields are blank and is enabled when the input controls have a valid input from the user. Reason names should be unique. The activate checkbox is checked by default. The corporate admin will not have the ability to view, edit or add notes templates that have been added from the local hospital end. Categories and Notes templates are multiple selections which imply that a reason can belong to multiple categories such as Sick, Wellness, Surgery and can be related with multiple note templates. However, Reasons can exist without any categories and templates as well. The Activated column should be yes/no. What happens to rows marked as deactivated at the corporate side. They would be replicated but should they show up on the hospital side. What should happen if the hospital has already overridden and using it??? Upon navigating to the reasons grid, the grid loads with reason names in the ascending order. No other columns need to be ordered The grid will be editable inline. Reason names will present with a simple text box, Categories and note templates should have a multi-select dropdown in their edit states and duration will have a numeric spinner (to be decided) The display state for the multi-select values will be comma-separated values. There will be no navigational link for categories and note-templates. However, the note-templates upon hover will present with a tooltip??? The grid is auto-save enabled and hence will save cell data lost focus of the grid’s cell. The corporate admin has the right to delete a reason??? UX Specifications Refer to document TFS 2356 – ReasonCode_Management.pptx for UX slides 20 - slides 21 for other UX related specifications.
- 3. Note: Rules listed in this document override any specifications drawn in the powerpoint deck. Also, some features in the powerpoint deck not detailed out functionally may be out of scope for development. Replication rules: Added/edited/deleted reason codes at the corporate level will be replicated to all the hospital databases. However, if a particular reason codes attributes are overridden at the hospital database, the changes made at the hospital will take precedence. The corporate admin will not be able to view locally overridden values from the corporate side. Corp Admin – Note templates: The corporate admin does not require the ability to manage note templates for reasons. Note templates are considered to be transactional data and hence will flow only from the hospital to the corporate. However, during deployment a set of note templates will be identified for the reasons and shall be initialized from the corporate physical location with the respective hospital id so it syncs with the corresponding hospital databases. Hospital Admin – Reasons Grid Loading the grid: The grid is loaded based on the role and the privilege of the user. If the system detects the user to be a hospital admin, the grid loads the reasons with the values inherited from the corporate database combined with any local overrides. In the case of a reason having two durations, one from the corporate and one from the local hospital, the one from the local hospital is alone shown. It is not required to show the corporate stipulated values in the grid. Add reasons: The hospital admin is not entitled to add new reasons to the grid. All controls pertaining to adding a new reason to the grid is not shown to the hospital admin. Edit reasons: The hospital admin is allowed to change the duration and the templates associated with the reason.
- 4. The reason name and the category columns are shown in gray text indicating that they are disabled for the user. Delete reasons: The hospital admin cannot delete reasons The hospital admin can however, deactivate a reason. A deactivated reason will not show up in the auto-suggested values in the reasons textbox of the appointment details. Associate templates: The hospital admin can create and associate multiple templates. When multiple templates are associated to a reason, they are shown as comma separated values in the grid. Associating multiple templates and modifying them however will not impact already created appointments in any form. Show default values (In scope?) Restore default values (Not in scope) UX Specifications Refer to document TFS 2356 – ReasonCode_Management.pptx for UX slides 26 - slides 30 for other UX related specifications. Note: Rules listed in this document override any specifications drawn in the powerpoint deck. Also, some features in the powerpoint deck not detailed out functionally may be out of scope for development. Note templates - Navigation and load: The note-templates are accessible by clicking on the link next to the reasons link inside the hospital configuration section. Note templates are considered transactional data and are meant to be created at the hospital and managed by the hospital themselves. The corporate is not required to access the note templates for Release 2.0 Upon load, the set of note templates are displayed in a grid sorted by the note template name. Like reasons, a note template for a reason can be activated or deactivated Deactivated note templates don’t appear in the rich text box for the appointment notes. The Add and delete buttons are disabled by default.
- 5. The cursor focus is within the template name upon load. Add Note templates: Every note template needs a unique name to be added. The add button is disabled by default and is enabled upon a valid input. The delete button is disabled at this point Upon successful addition, the template entry is added to the note-templates grid and is available for association with reasons in the reasons grid if the activate checkbox button is checked. The template itself can be created with rich-text formatting using the rich text control in the templates section. Edit Note templates: The note template can be edited by selecting a row from the grid. The appropriate template and template’s data is populated in the respective controls. The Add button’s text now reads Save and the delete button is enabled. Upon editing and hitting save, the changes will be saved. Delete: The hospital admin may choose to delete the loaded template by clicking on the delete button. The association between the reason and the template is mooted and is not shown in the templates grid for further changes. UX Specifications Refer to document TFS 2356 – ReasonCode_Management.pptx for UX slides 22 - slides 24 for other UX related specifications. Note: Rules listed in this document override any specifications drawn in the powerpoint deck. Also, some features in the powerpoint deck not detailed out functionally may be out of scope for development.