Request types
Request templates (request types) define each kind of request staff can submit: its form, its printed document, its approval chain, and where the finished record goes.
- Where
- Menu › Administration › Request Templates
- Who
- Administrators. Anyone with
view_request_typescan look. - Permissions
view_request_types,add_request_types,edit_request_types,delete_request_types,manage_request_templates. See Requests permissions.- How-to
- Build a request type
Screens
- The list
- Search by name, code or description; filter by category and status; New request type.
- A template's page
- Tabs Submitter view, Approver view and Approval chain, and a summary with the number of open requests. Actions: Edit, New request of this type, Deactivate / Activate, Delete (only with no open requests; types with history can only be deactivated).
- The editor
- Five tabs over one draft, saved with Save or Save & close.
Editor tabs
- Details
- Basics (name, code, category, icon, active, description, help text), Reference numbers, Who can submit, Registry access, Payment follows approval, Registries, Dispatch on approval.
- Form
- The fields submitters fill in, from a palette of field types, with validation and conditional visibility.
- Template
- The printed document: rich text, variables, blocks (form fields, items table, approval chain, signatures, attachments, distribution list) and page setup.
- Approvals
- The ordered chain of recommend and approve steps, with who each step goes to and its decision wording.
- Preview
- Try the form and see the document approvers will read.
Good to know
- Submitted requests keep the version of the template they were submitted with.
- The code is locked once saved; the hospital's codes look like
fin-req-001and reference numbers like{code}/{YYYY}/{seq:4}. - Staff see the templates as the choices on New request.