Builder Scope of Work
Through Epic Clinical Builder basic and advanced courses, Builders learn how to use and customize a wide range of tools. The level of effort required to use these tools safely, and the level of system impact when used inappropriately, varies from tool to tool. It is important to balance the knowledge of the Builder (clinically and technically) with the risks for system disruption or patient harm.
The following categorization includes representative examples. These can be used as "complexity comparators" when builder projects are contemplated. Irrespective, builder work needs to be reviewed by an appropriate analyst. In general, any build impacting system-level configuration (profiles) should be supervised by designated analysts and, as appropriate, approved by Connect Care oversight groups. Builders are responsible for inventorying their competence and reviewing their understanding before undertaking any build.
The Builder Scrum should be used as a clearinghouse for all build assignments. This will allow the many build tools not addressed above to be considered for a match to builder capabilities and certifications. This can help minimize unintended impacts on system build while working to reduce unhelpful variations and duplication.
In Scope
The following Epic build tools fall within the potential scope of expertise and work for a Connect Care Builder who has satisfactorily completed basic training and the associated project requirements:
Documentation
SmartPhrases, SmartTexts, SmartLists, SmartLinks
Basic SmartForms and SmartBlocks
Basic PrintGroups (copy template and edit parameters)
Basic Rules (CER) when used with SmartTools (e.g., SmartForms)
Basic Extensions (LPP) when copied for use with SmartTools (e.g., SmartForms)
Documentation Flowsheets and Questionnaires
Review Flowsheets and Synopsis Reports
Decision Supports
Order Sets, SmartSets, SmartGroups, Order Panels
Best Practice Advisories
Inquiry Supports
Basic Reporting Workbench Reports (copy from template and customize)
Specialty Dashboards (using existing and approved components)
Workflow
Edits to Specialty Preference Lists for commonly changed elements, including:
Chief Complaint, Diagnosis, Labs, Diagnostic Imaging, Panels, Other Orders, Billing Codes, and Medications.
Discretionary
The following Epic build tools may be included with a Builder's scope of work. New builders interested in developing these items will be required to meet with Master Builders or designate Program Leads to assess and determine the necessary support prior to commencing the project.
Documentation
Advanced SmartForms (e.g., Problem SmartForms, Flowsheet SmartForms, Workflow SmartForms)
These can affect SmartData elements and incur extra maintenance at system upgrades.Documentation Forms (e.g., letter templates, consent templates)
SmartData Elements
Advanced Rules (e.g., nested rules, score rules) and Scoring Systems
CER rules require fastidious testing to consider and evaluate all contexts and scenarios that might affect rule behaviours.Print Templates, Groups and Reports
Such work needs to be done in close collaboration with an Analyst assigned to a particular domain (e.g., ambulatory) for such tools.Patient-entered Questionnaires (MyChart)
Decision Supports
Care Paths
Health Maintenance Reminders
Treatment Plans (Oncology)
Basic Therapy Plans (from Templates)
New Report and List Columns (PAF records)
Inquiry Supports
New Reporting Workbench Reports
Slicer-Dicer Sessions
Reporting Workbench, Slicer-Dicer or Radar templates that include individual or group provider performance measures
Registries
Workflow
Custom Navigators
The development and approval of specialty navigators is strictly controlled and must follow provincially standardized templates. This allows for easier testing, maintenance and consistency for users who work in multiple settings.Custom Activities (E2N records)
EpicACT Links
Research Topics
Build items which are going through the research group should be carefully managed and reviewed with that group prior.
Out of Scope
In exceptional circumstances, Master Builders may have attained competency in some of the below areas. Nonetheless, any build should be done in very close collaboration with an analyst like-skilled and experienced with the high-risk tool and builders should preferentially use the Sandbox environment to generate suggestions for Analysts to implement in pre-production environment(s). New Builders interested in developing these items will be required to meet with Master Builders or designate Program Leads to assess and determine the necessary support prior to commencing the project.
The following activities are out-of-scope for most Builders:
Documentation
System Patient List Templates
Decision Support
Procedures (ERX and EAP records)
Programming Extensions (LPP) using net new cache programming calls (not copied from foundation)
New Therapy/Treatment/Protocol build
Inquiry Support
Reporting Workbench templates
Workflow
User Profile Settings and other System Definitions
Workflow Engine Rules
Medication Administration Record tools
Provider Care Team Configuration
System Navigator Activities
Integration Engine Records and Settings
Procedures
Device integrations, including printer, workstation and mappings