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. 

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:

Discretionary

The following Epic build tools may be included with a Builder's scope of work, subject to additional training and/or demonstrated competence and special approval:


Out of Scope

In exceptional circumstances, Master Builders may have attained competency in some of the above 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).

The following activities are out-of-scope (without an approved exception) for Builders: