Note: This topic applies to the hierarchy of regulations-contracts-contract terms, as well as the hierarchy of regulations-compliance programs-requirements.
In certain Compliance scenarios, such as Joint Commission Interim Life Safety Measures (ILSM), the same set of requirements must be created over and over again for new pre-construction projects. In cases such as this, to create the new set of requirements, you can copy a compliance program along with all of its requirements, or a regulation along with all of its programs and requirements.
When copying requirements, you can select to copy a requirement's locations, notification templates, events, or event notifications to the new requirement.
When you select to copy the child items, you can specify to advance all date fields for the item by a specific number of years, months, or days that you define.
You access this feature from the “Copy As New” action in the Define tab of the following tasks:
To copy child records for existing regulations, programs, requirements, contracts, or contract terms to new ones you are defining:
The Manage Regulations, Manage Compliance Programs, or Manage Requirements form appears, depending on the task you selected.
The Define Regulation, Define Compliance Program, or Define Requirement form appears.
The Regulation, Compliance Program Code, or Requirement Code field clears, so that you can enter the unique identifier for the new record.
The Copy as New Regulation / Program / Requirement form appears. The following image shows the form that appears when you select to create a new regulation by copying an existing one.
Advance Date By:
Select how you want to advance dates for the items you are copying;
A workflow rule creates the following for the new regulation, program, or requirement you are creating:
If you select to copy... | The following are copied |
---|---|
Compliance Programs (regprogram) | Copy all programs from one regulation to another. Copy all fields. Advance all date fields by selection. |
Compliance Requirements (regrequirement) | Copy all requirements from one regulation-program to another. Copy all fields. Advance all date fields by selection. |
Regulation Locations (regloc) | Copy all source regulation locations (regloc.reg_program is NULL) to new regulation. Copy all fields. |
Program Locations (regloc) | Copy all source program locations (regloc.reg_program is NOT NULL and regloc.reg_requirement is NULL) to new program. Copy all fields. |
Requirement Locations (regloc) | Copy all source requirement locations (regloc.reg_requirement is NOT NULL) to new requirement. Copy all fields. |
Program Notify Templates (regnotify) | Copy all source program template assignments (regnotify.reg_requirement is NULL) to new program. Copy all fields. |
Requirement Notify Templates (regnotify) | Copy all source requirement template assignments (regnotify.reg_requirement is NOT NULL) to new requirement. Copy all fields. |
Requirement Events (activity_log, activity_type=’COMPLIANCE – EVENT’) | Copy all source requirement events to new requirement. Advance all date fields below by selection. Set status=’SCHEDULED’, and copy only the following fields:
|
Event Notifications (notifications) | Copy all notifications for the requirement being copied to the new requirement. Advance all date fields by selection. Copy all fields, except set the following: Set is_active=1 (that is, yes), notify_count=0, date_sent=NULL |
Advance Dates By | Advance all date fields of new record (regulation, program, requirement) by this setting, if selected. Also used (if selected) to advance date fields of child records where specified above. Dropdown selections are: Years, Months, Days |
Copyright © 1984-2019, ARCHIBUS, Inc. All rights reserved. |