Codification Kick-off Meeting Standard Operating Procedures

1. Codification Kick-off MeetingStandard Operating Procedures December 4, 2013

2. SOP PIG Exercise Bottom left Intersection Bottom right Intersection

3. SOP PIG Exercise Top left Intersection Top right Intersection Bottom right Intersection Bottom left Intersection

4. SOP PIG Exercise

5. Lunch

6. Codification Kick-off Agenda • Introductions/PIG Exercise • Lunch • Background/Need • Codification Charge/Deliverables • Timeline • Project Roles/Structure • Planning and Project Management • Next Steps

7. IS CODIFICATION NECESSARY?

8. Background • Dr. Azziz called for the codification of all standardized operating procedures (SOPs) • The codification process was complicated by the demands of consolidation • Under the leadership of the Compliance/Legal Team, the Enterprise Codification Process will become a part of our team effort to develop standard operating procedures across the Enterprise

9. Need for Codification • To ensure the internal business consistency of unit operations and continuity in delivery for vital services in the event of a major disruption in services or unanticipated change in leadership • To ensure consistency of information and communication of the service and process functions of the enterprise • To address the lack of an enterprise-wide catalogue of services that hinders institutional consolidation and transition management efforts

10. How do I? External Customer Employees What processes do you have that have only an internal impact within your unit Ex.: Triage process for a Hotline call • What processes do you have that deal with outward facing customers • Outside facing customers can include other units within the enterprise • Ex.: Management of an outside audit These are the processes that need to standardized and codified!

11. Terms/Definitions • The following terms provide clarification: • Codification is to arrange/sort policies and/or procedures into an organized system or code. • Policies mandate action or constraints. A policy is a concise formal statement of principles that indicate how an enterprise entity will act in a particular area of its operation. • Procedures are the steps that make a policy happen, the method by which a policy can be accomplished. For the purpose of codification initiatives, procedures are outward facing instructions, those steps that are provided to our customers to help them accomplish a task mandated by a policy. • Reconciliation is the process of review for ensuring procedures are consistent/compatible with institutional policies. • Standard Operating Procedures (SOPs) are inward facing instructions for staff, documentation of the standard for how internal tasks are done. SOPs describe workflow, and the inputs and outputs of a process. Well-written SOPs provide direction, improve communication, reduce training time, and improve work consistency across the Enterprise.

12. Project Scope Each Enterprise Unit will… • Produce a list of services provided and major decisions supported by the actions of the unit. • Produce a set of SOPs that give step-by-step explanation of the process used by the unit to deliver the identified list of services or to support its decision making responsibilities. • Have codified standard operating procedures. All SOPs will be collected into an internal library of services and procedures that will be reviewed and updated annually.

13. Stage I: Contact / Service Directory • For each core function performed internally – that is, an operational function -- list SOPs needed to carry out those functions. • Identify any SOP you believe should remain confidential • For each service you provide for an internal customer, list SOPs for those services. • Location of the Unit’s Base of Operation • Main Phone Number, Contact Number for services, Email Contact Information • List core functions of the Unit, including key services How do I …employee Contact Info/List of services servicesrmation How do I…internal customer

14. Stage II: SOP Codification

15. Codification - Timeline Audit SOPs/ Electronic database STAGE II: Develop/Update SOPs STAGE I: Identify needed SOPs/ List of Services Kick-off Aug-Dec 2014 Feb-Jul 2014 Jan-Feb 2014 Dec 2013 Progress reported monthly (20%)

16. Codification Project Sponsor Dr. Azziz Advisory/Steering Team Risk Management Steering committee FunctionalLeader Jim Rush Project Manager Karen Ribble Project Resources IT support services, Communications and Marketing Enterprise Project Core Team GRHealth SOPs Team University SOPs Team Shared Services SOPs Team SOP=Standard Operating Procedure

17. Functional Teams - Codification

18. The Role of Project Manager Facilitates the project management processes by… • Developing documentation • Ensuring sponsor agreement • Identifying stakeholder communications • Helping remove obstacles • Monitoring and tracking issues

19. Communications Process Stakeholder Analysis Questions/ Issues Status Reports Project Management Team Core Team Monthly Meetings Effective Meetings Request for support Document Management via BOX

20. Project Management Accountability vs. Responsibility

21. Next Steps Assign staff to represent area(s) on team (by 12/20) Identify responsible persons within each units Invitation to connect to BOX folder for SOP Project documents/templates Establish team meeting dates for January Work on list of services for unit

22. Questions? SHARED SERVICES Jim Rush Chief Integrity Officer Office of Compliance and Risk Management 706-721-1626 jrush@gru.edu UNIVERSITY Lee Little General Counsel Legal Affairs 706-721-4018 llittle@gru.edu HEALTH SYSTEM Susan James General Counsel Legal Affairs 706-721-5709 susjames@gru.edu