SCC https://policy.umn.edu/ en Academic Calendars: Twin Cities, Crookston, Morris, Rochester https://policy.umn.edu/education/academiccalendar <span class="field field--name-title field--type-string field--label-hidden">Academic Calendars: Twin Cities, Crookston, Morris, Rochester</span> <span class="field field--name-uid field--type-entity-reference field--label-hidden"><a title="View user profile." href="/user/1" lang="" about="/user/1" typeof="schema:Person" property="schema:name" datatype="" class="username">oitadmin</a></span> <span class="field field--name-created field--type-created field--label-hidden">Wed, 12/17/2014 - 00:00</span> <div class="field field--name-field-category field--type-entity-reference field--label-above"> <div class="field__label">Category</div> <div class="field__items"> <div class="field__item"><a href="/taxonomy/term/65" hreflang="en">Education</a></div> </div> </div> <section class="field field--name-field-comments field--type-comment field--label-above comment-wrapper"> <h2 class="title comment-form__title">Add new comment</h2> <drupal-render-placeholder callback="comment.lazy_builders:renderForm" arguments="0=node&amp;1=1717&amp;2=field_comments&amp;3=policy_comment" token="S9oAmQgg6VaW5nihC322YmqP6EeCKgemYYtkcSCrzeo"></drupal-render-placeholder> </section> <div class="field field--name-field-owner field--type-entity-reference field--label-above"> <div class="field__label">Owner</div> <div class="field__items"> <div class="field__item"><a href="/user/203" hreflang="en">mcmaster</a></div> <div class="field__item"><a href="/user/322" hreflang="en">slanyon</a></div> </div> </div> <div class="field field--name-field-urlcategory field--type-list-string field--label-above"> <div class="field__label">urlcategory</div> <div class="field__item">Education</div> </div> <div class="field field--name-field-path-slug field--type-string field--label-above"> <div class="field__label">Path slug</div> <div class="field__item">ACADEMICCALENDAR</div> </div> <div class="field field--name-field-sme field--type-entity-reference field--label-above"> <div class="field__label">Primary Contact</div> <div class="field__items"> <div class="field__item"><a href="/user/308" hreflang="en">tidball</a></div> </div> </div> <div class="clearfix text-formatted field field--name-field-revisiondescription field--type-text-long field--label-above"> <div class="field__label">Revision Description</div> <div class="field__item">Updated Morris contact.</div> </div> <div class="field field--name-field-subtype field--type-list-string field--label-above"> <div class="field__label">SubType</div> <div class="field__item">Administrative Policy</div> </div> <div class="clearfix text-formatted field field--name-field-faq field--type-text-long field--label-above"> <div class="field__label">FAQ</div> <div class="field__item"><ol> <li><strong>Can each campus set its own academic calendar?</strong> <p>Yes, each campus is responsible for setting its own academic calendar. The Faculty Senate approves the University of Minnesota, Morris and University of Minnesota, Twin Cities calendars. The University of Minnesota, Duluth and University of Minnesota, Crookston calendars are transmitted to the Faculty Senate for information only. The University of Minnesota, Rochester follows the Twin Cities academic calendar.</p> </li> <li><strong>Can instructors assign work to students prior to the beginning of the academic term?</strong> <p>No. Instructors cannot assign work until the term starts.</p> </li> <li><strong>Does the University of Minnesota hold regularly scheduled classes the day before a holiday?</strong> <p>Yes. Scheduled classes, including evening classes, are held the day before a holiday. For example, classes are held the Wednesday evening before the Thanksgiving holiday. Refer to the current academic calendar for University holidays.</p> </li> <li><strong>When may a school or program have a calendar that varies from the campus calendar?</strong> <p>Schools and programs must follow the standard, approved campus calendar with an exception provided for professional school programs (i.e., D.D.S., D.V.M, J.D., L.L.M., M.D., Pharm.D. degrees).</p> </li> </ol></div> </div> <div class="field field--name-field-daterevised field--type-datetime field--label-above"> <div class="field__label">Last Revised</div> <div class="field__item"><time datetime="2019-04-17T12:00:00Z" class="datetime">Wed, 04/17/2019 - 12:00</time> </div> </div> <div class="field field--name-field-dateeffective field--type-datetime field--label-above"> <div class="field__label">Effective Date</div> <div class="field__item"><time datetime="2009-04-08T12:00:00Z" class="datetime">Wed, 04/08/2009 - 12:00</time> </div> </div> <div class="clearfix text-formatted field field--name-field-policystatement field--type-text-long field--label-above"> <div class="field__label">Policy Statement</div> <div class="field__item"><p>Academic calendars must be established at least four years in advance so that students may plan their schedules and University units may plan events. Changes in dates to previously approved calendars must be made at least two years before the start of the academic year of that calendar.</p> <p>The proposed and approved calendars must meet the requirements stated in section A and B below.</p> <h3>A. Fall and Spring Semesters</h3> <ol> <li>The academic calendar has a fall and a spring semester, each of which includes a minimum of 70 days of instruction, a maximum of 75 days of instruction, and approximately one week of final examinations (including Saturdays but not Sundays).</li> <li>Courses shorter or longer than the semester are subject to the approval of appropriate college or academic unit review committees.</li> </ol> <h3>B. Summer Term</h3> <p>The academic calendar has a summer term, which has May and summer sessions. A May session includes a minimum of 14 instructional days. Summer term starts after spring term is complete and concludes prior to the first day of fall semester.</p> <p>No college or academic unit will be obligated to offer courses during summer term.</p> <h3>C. Revisions of Calendars</h3> <p>Requests for changes in dates to previously approved Twin Cities/Rochester and Morris calendars must be submitted to the Senate Committee on Educational Policy at least two years in advance of that academic year.</p> <p>All calendars and any subsequent revisions or exceptions must be approved by faculty governance.</p> <h3>Exclusions</h3> <p>This policy is not applicable to the Duluth campus.</p> <p>Professional schools are permitted to have calendars that vary from the requirements of this policy.</p></div> </div> <div class="clearfix text-formatted field field--name-field-policyreason field--type-text-long field--label-above"> <div class="field__label">Reason for Policy</div> <div class="field__item"><p>Establishing an academic calendar at least four years in advance allows students to plan their degree programs and enables University units to schedule events at times that do not conflict with other key activities. This policy implements requirements of federal financial aid regulations.</p></div> </div> <div class="clearfix text-formatted field field--name-field-policycontacts field--type-text-long field--label-above"> <div class="field__label">Contacts</div> <div class="field__item"><div class="tablewrapper"> <table> <thead> <tr><th scope="col">Subject</th><th scope="col">Contact</th><th scope="col">Phone</th><th scope="col">Email</th></tr> </thead> <tbody> <tr><th scope="row"><strong>Primary Contact(s)</strong></th> <td><a href="http://www.umn.edu/lookup?UID=tidball">Stacey Tidball</a></td> <td>612-626-0075</td> <td>tidball@umn.edu</td> </tr> <tr><th scope="row">Crookston Campus</th> <td><a href="http://www.umn.edu/lookup?UID=jtangqui">Jason Tangquist</a></td> <td>218-281-8424</td> <td>jtangqui@crk.umn.edu</td> </tr> <tr><th scope="row">Duluth Campus</th> <td><a href="http://www.umn.edu/lookup?UID=vfrench">Vickery French</a></td> <td>218-726-7104</td> <td>vfrench@d.umn.edu</td> </tr> <tr><th scope="row">Morris Campus</th> <td><a href="http://www.umn.edu/lookup?UID=rvaneps">Robin Van Eps</a></td> <td>320-589-6015</td> <td>rvaneps@morris.umn.edu</td> </tr> <tr><th scope="row">Rochester Campus</th> <td><a href="http://www.umn.edu/lookup?UID=douglasd">Diane Douglas</a></td> <td>507-258-8008</td> <td>douglasd@r.umn.edu</td> </tr> </tbody> </table> </div></div> </div> <div class="clearfix text-formatted field field--name-field-policydefinitions field--type-text-long field--label-above"> <div class="field__label">Definitions</div> <div class="field__item"><p>There are no definitions associated with this policy.</p></div> </div> <div class="field field--name-field-committee-review field--type-entity-reference field--label-above"> <div class="field__label">Committee Involvement</div> <div class="field__items"> <div class="field__item"><a href="/taxonomy/term/5" hreflang="en">SCEP</a></div> <div class="field__item"><a href="/taxonomy/term/4" hreflang="en">SCC</a></div> </div> </div> <div class="field field--name-field-policy-responsible-executi field--type-entity-reference field--label-above"> <div class="field__label">Senior Leader</div> <div class="field__items"> <div class="field__item"><a href="/user/74" hreflang="en">provost</a></div> </div> </div> <div class="field field--name-field-policy-responsible-officer field--type-entity-reference field--label-above"> <div class="field__label">Responsible Officer</div> <div class="field__items"> <div class="field__item"><a href="/user/74" hreflang="en">provost</a></div> </div> </div> <div class="clearfix text-formatted field field--name-field-description field--type-text-long field--label-above"> <div class="field__label">Revision Description for Review/Update Page</div> <div class="field__item"><p>Comprehensive Review, Minor Revision. 1.&nbsp; Incorporates minor edits to improve understandability and removes the December 23rd date for end of fall term due to equity concerns. 2.<span> </span>Re-wrote summer term section to increase accuracy across all our campuses and remove extraneous information about sessions.&nbsp;</p></div> </div> <div class="field field--name-field-ucmcontentid field--type-string field--label-above"> <div class="field__label">UCMContentID</div> <div class="field__item">ACADEMICCALENDAR</div> </div> <div class="field field--name-field-studenttype field--type-list-string field--label-above"> <div class="field__label">Student Type</div> <div class="field__item">All Students</div> </div> <div class="clearfix text-formatted field field--name-field-policyresponsibilities field--type-text-long field--label-above"> <div class="field__label">Responsibilities</div> <div class="field__item"><dl><dt>Campus Office of the Registrar or Campus Calendar Contact</dt> <dd>Submits the academic calendar proposal annually to the Senate Committee on Educational Policy.</dd> <dt>Faculty Senate</dt> <dd>Reviews and approves final academic calendars (Twin Cities/Rochester and Morris); receives Crookston and Duluth calendars for information.</dd> <dt>Senate Committee on Educational Policy (SCEP)</dt> <dd>Reviews and approves final academic calendars (Twin Cities/Rochester and Morris) prior to forwarding to the Faculty Senate for approval.</dd> </dl></div> </div> <div class="clearfix text-formatted field field--name-field-policyrelatedinformation field--type-text-long field--label-above"> <div class="field__label">Related Information</div> <div class="field__item"><h3>Campus Calendar Information</h3> <p>University calendars are available on the <a href="http://usenate.umn.edu/resources/academic-calendars?j=2545327&amp;sfmc_sub=38671849&amp;l=591_HTML&amp;u=64263049&amp;mid=6327455&amp;jb=1">University Senate office website</a> once approved. Each campus publishes dates and deadlines on their One Stop website.</p> <ul> <li><a href="http://onestop.umn.edu/"><em>Twin Cities</em></a></li> <li><a href="http://onestop.crk.umn.edu/"><em>Crookston</em></a></li> <li><a href="http://onestop.morris.umn.edu/"><em>Morris</em></a></li> <li><a href="http://onestop.d.umn.edu/"><em>Duluth</em></a></li> <li><a href="http://onestop.r.umn.edu/"><em>Rochester</em></a></li> </ul> <p>Administrative Policy: <a href="https://policy.umn.edu/education/exam">Scheduling Examinations, Final Examinations, and Study Days: Twin Cities, Crookston, Morris, Rochester</a></p></div> </div> <div class="clearfix text-formatted field field--name-field-policyhistory field--type-text-long field--label-above"> <div class="field__label">History</div> <div class="field__item"><dl> <dt>Amended:</dt><dd>April 2019 - Comprehensive Review, Minor Revision. 1. Incorporates minor edits to improve understandability and removes the December 23rd date for end of fall term due to equity concerns. 2. Re-wrote summer term section to increase accuracy across all our campuses and remove extraneous information about sessions. </dd> <dt>Amended:</dt><dd>December 2009 - Policy now applies to the Crookston campus.</dd> <dt>Effective:</dt><dd>April 2009</dd></dl></div> </div> <div class="field field--name-field-date-comp-review field--type-datetime field--label-above"> <div class="field__label">Date Comp Review</div> <div class="field__items"> <div class="field__item"><time datetime="2019-04-17T12:00:00Z" class="datetime">Wed, 04/17/2019 - 12:00</time> </div> </div> </div> <div class="field field--name-field-date-comp-review-due field--type-datetime field--label-above"> <div class="field__label">Date Comp Review Due</div> <div class="field__item"><time datetime="2023-04-17T12:00:00Z" class="datetime">Mon, 04/17/2023 - 12:00</time> </div> </div> <div class="field field--name-field-senate-involvement field--type-list-string field--label-above"> <div class="field__label">Senate Involvement</div> <div class="field__items"> <div class="field__item">F Senate (info)</div> </div> </div> <div class="field field--name-field-d7-nid field--type-integer field--label-above"> <div class="field__label">D7 NID</div> <div class="field__item">9493</div> </div> <div class="field field--name-field-d7-vid field--type-integer field--label-above"> <div class="field__label">D7 VID</div> <div class="field__item">244486</div> </div> <div class="field field--name-field-date-comp-review-stamp field--type-timestamp field--label-above"> <div class="field__label">Date of Comprehensive Review - Time Stamp</div> <div class="field__item">Wed, 04/17/2019 - 00:00</div> </div> Wed, 17 Dec 2014 06:00:00 +0000 oitadmin 1717 at https://policy.umn.edu Academic Unit Authority over the Curriculum and Major: Twin Cities, Crookston, Morris, Rochester https://policy.umn.edu/education/curriculumauthority <span class="field field--name-title field--type-string field--label-hidden">Academic Unit Authority over the Curriculum and Major: Twin Cities, Crookston, Morris, Rochester</span> <span class="field field--name-uid field--type-entity-reference field--label-hidden"><a title="View user profile." href="/user/1" lang="" about="/user/1" typeof="schema:Person" property="schema:name" datatype="" class="username">oitadmin</a></span> <span class="field field--name-created field--type-created field--label-hidden">Wed, 12/17/2014 - 00:00</span> <div class="field field--name-field-category field--type-entity-reference field--label-above"> <div class="field__label">Category</div> <div class="field__items"> <div class="field__item"><a href="/taxonomy/term/65" hreflang="en">Education</a></div> </div> </div> <section class="field field--name-field-comments field--type-comment field--label-above comment-wrapper"> <h2 class="title comment-form__title">Add new comment</h2> <drupal-render-placeholder callback="comment.lazy_builders:renderForm" arguments="0=node&amp;1=1758&amp;2=field_comments&amp;3=policy_comment" token="tGFQ3BIbFE45M0J3sIAG4799GV-Nn2CNa9qFLKcb53g"></drupal-render-placeholder> </section> <div class="field field--name-field-owner field--type-entity-reference field--label-above"> <div class="field__label">Owner</div> <div class="field__items"> <div class="field__item"><a href="/user/203" hreflang="en">mcmaster</a></div> <div class="field__item"><a href="/user/322" hreflang="en">slanyon</a></div> </div> </div> <div class="field field--name-field-urlcategory field--type-list-string field--label-above"> <div class="field__label">urlcategory</div> <div class="field__item">Education</div> </div> <div class="field field--name-field-path-slug field--type-string field--label-above"> <div class="field__label">Path slug</div> <div class="field__item">CURRICULUMAUTHORITY</div> </div> <div class="field field--name-field-sme field--type-entity-reference field--label-above"> <div class="field__label">Primary Contact</div> <div class="field__items"> <div class="field__item"><a href="/user/401" hreflang="en">jkuecker</a></div> <div class="field__item"><a href="/user/251" hreflang="en">starry</a></div> </div> </div> <div class="clearfix text-formatted field field--name-field-revisiondescription field--type-text-long field--label-above"> <div class="field__label">Revision Description</div> <div class="field__item">Updated link to Higher Learning Commission.</div> </div> <div class="field field--name-field-subtype field--type-list-string field--label-above"> <div class="field__label">SubType</div> <div class="field__item">Administrative Policy</div> </div> <div class="clearfix text-formatted field field--name-field-faq field--type-text-long field--label-above"> <div class="field__label">FAQ</div> <div class="field__item"><ol> <li><strong>What is a change in major requirements? </strong> <p>The academic department(s) responsible for a major may add, delete, or modify the published degree requirements for a major in that department. As examples, required courses may be added or deleted, or changed; admissions requirements for a major may be changed.</p> </li> <li><strong>What are some examples of the levels of academic unit authority</strong>? <p>A department, or a group of departments working collaboratively, has the authority to establish the course requirements for a major, minor, or certificate program, including prerequisite requirements; for example, the particular courses required to receive an M.A. degree in History.</p> <p>A college has the authority to establish college-wide requirements for particular types of academic programs, for example, a second language requirement for a B.A. degree granted within that college.</p> <p>A campus has the authority to establish campus-wide requirements for groups of academic programs.&nbsp; Some examples are a first-year writing requirement for all undergraduate degrees, the minimum number of credits required for a baccalaureate degree, and a minimum GPA requirement for graduation.</p> </li> <li><strong>How does expiration of old credits show on a student's transcript?</strong> <br> <br> <p>"Expiration of old credit" refers to coursework a student has completed too long ago for that subject matter to be current in the discipline. The academic unit may determine that the student must take additional, current coursework in that subject matter in order to fulfill the requirements for an academic program. The prior credits are not removed from the student’s transcript; however, they do not count toward satisfying requirements for the particular major, minor, or certificate.</p> </li> </ol></div> </div> <div class="field field--name-field-daterevised field--type-datetime field--label-above"> <div class="field__label">Last Revised</div> <div class="field__item"><time datetime="2016-06-02T12:00:00Z" class="datetime">Thu, 06/02/2016 - 12:00</time> </div> </div> <div class="field field--name-field-dateeffective field--type-datetime field--label-above"> <div class="field__label">Effective Date</div> <div class="field__item"><time datetime="2009-04-08T12:00:00Z" class="datetime">Wed, 04/08/2009 - 12:00</time> </div> </div> <div class="clearfix text-formatted field field--name-field-policystatement field--type-text-long field--label-above"> <div class="field__label">Policy Statement</div> <div class="field__item"><p>Departments, colleges, and campuses have the authority to establish, change, and discontinue academic plans and sub-plans that appear on official University transcripts, subject to appropriate consultation with other units and subject to the final approval of the Board of Regents. (See Administrative Policy: <a href="/education/academicprogram"><em>Adding, Changing or Discontinuing Academic Plans</em></a>).</p> <h3>Establishing and changing academic plan requirements</h3> <ol> <li>Academic units (departments, colleges, and campuses) have the authority to establish their curricula and the requirements, including prerequisite courses, for academic plans, subject to the final authority of the Board of Regents. Academic plans include: <ul> <li>undergraduate degrees,</li> <li>graduate degrees;</li> <li>professional degrees;</li> <li>majors;</li> <li>minors;</li> <li>undergraduate certificates; and</li> <li>post-baccalaureate certificates.</li> </ul> </li> <li>Academic units have the authority to add to or remove courses, including prerequisite courses, from academic plans. The additions or deletions of courses from the academic plan requirements must be in accordance with Board of Regents policies and in compliance with rules established by the college and campus.</li> <li>Changes to academic plans must have an effective date, based on the start of an academic term (e.g., fall semester 2018). Changes to requirements may not be made in the middle of an academic term. Changes to academic plans should be announced far enough in advance so that students, including continuing students and prospective first-year and prospective transfer students, can plan accordingly.</li> <li>Students must follow the requirements of the academic plan in effect during the term in which they entered the plan. Academic units may offer the choice of moving to the new requirements to currently enrolled students who have already been admitted to an existing academic plan. However, the academic unit cannot mandate a new requirement of students who are currently enrolled in the plan without having sought and received prior approval of the dean of the college or the appropriate official on a campus.</li> <li>Academic units must clearly communicate their policies and decisions regarding new or revised requirements for academic plans to prospective and current students. This includes changes to a major, minor, or certificate program, including changes in required prerequisites.</li> </ol> <h3>Expiration of old credits</h3> <p>To ensure that students receiving a degree or certificate will be up-to-date in the discipline, an academic unit (a department or comparable unit) may decide not to accept course work towards satisfying requirements for the major, minor, or certificate if the course was taken too long ago.</p> <p>Students returning from an approved leave of absence are subject to the specific conditions/requirements identified in Administrative Policy: <a href="/education/readmissionloa"><em>Leave of Absence and Readmission for Undergraduates: Twin Cities, Crookston, Morris, Rochester</em></a><em>.</em></p> <h3>Exclusions</h3> <p>This policy is not applicable to the Duluth campus.</p></div> </div> <div class="clearfix text-formatted field field--name-field-policyreason field--type-text-long field--label-above"> <div class="field__label">Reason for Policy</div> <div class="field__item"><p>Departments, colleges and campuses are best suited to determine curricula and requirements for majors and minors, for graduate and professional degrees, and to add or remove course offerings. It is in students’ best interests if changes in requirements do not occur frequently or arbitrarily, and students are provided with advance notice of such changes.</p> <p>This policy implements criteria and requirements for accreditation established by the Higher Learning Commission.</p></div> </div> <div class="clearfix text-formatted field field--name-field-policycontacts field--type-text-long field--label-above"> <div class="field__label">Contacts</div> <div class="field__item"><table> <thead> <tr><th scope="col">Subject</th><th scope="col">Contact</th><th scope="col">Phone</th><th scope="col">Email</th></tr> </thead> <tbody> <tr><th scope="row">Primary Contact(s)</th> <td><a href="http://www.umn.edu/lookup?UID=jkuecker">Jessica Kuecker Grotjohn</a> <br> <a href="http://www.umn.edu/lookup?UID=starry">Karen Starry</a></td> <td>612-624-1328<br> 612-625-2815</td> <td>jkuecker@umn.edu<br>starry@umn.edu</td> </tr> <tr><th scope="row">Crookston Campus</th> <td><a href="http://www.umn.edu/lookup?SET_INSTITUTION=UMNTC&amp;UID=jtangqui">Jason Tangquist</a></td> <td>218-281-8424</td> <td>jtangqui@crk.umn.edu</td> </tr> <tr><th scope="row">Morris Campus</th> <td><a href="http://www.umn.edu/lookup?UID=ericksja">Janet Ericksen</a></td> <td>320-589-6015</td> <td>ericksja@morris.umn.edu</td> </tr> <tr><th scope="row">Rochester Campus</th> <td><a href="http://www.umn.edu/lookup?UID=douglasd">Jeffrey Ratliff-Crain</a></td> <td>507-258-8006</td> <td>ratliffj@r.umn.edu</td> </tr> </tbody> </table></div> </div> <div class="clearfix text-formatted field field--name-field-policydefinitions field--type-text-long field--label-above"> <div class="field__label">Definitions</div> <div class="field__item"><dl><dt>Academic Program</dt><dd>Undergraduate, graduate, and professional degrees, majors, minors, and certificates that appear on official University transcripts.</dd><dt>Academic Major</dt><dd>A student's main field of specialization during the student's undergraduate or graduate studies. The major is recorded on the student's transcript.</dd><dt>Academic Minor</dt><dd>A student's declared secondary field of study or specialization during the student's undergraduate or graduate studies. A minor typically consists of a set of courses that meet specified guidelines and is designed to allow a sub-major concentration in an academic discipline or in a specific area in or across disciplines. The minor is recorded on the student's transcript.</dd><dt>Certificate</dt><dd>A particular set of courses or coursework that typically addresses new knowledge or practice areas emerging from technological, social, or economic changes to which particular professions or occupations must adjust. The certificate is recorded on the student’s transcript.</dd><dt>Curriculum</dt><dd>The set of courses offered by a unit.</dd></dl></div> </div> <div class="field field--name-field-committee-review field--type-entity-reference field--label-above"> <div class="field__label">Committee Involvement</div> <div class="field__items"> <div class="field__item"><a href="/taxonomy/term/5" hreflang="en">SCEP</a></div> <div class="field__item"><a href="/taxonomy/term/4" hreflang="en">SCC</a></div> <div class="field__item"><a href="/taxonomy/term/12" hreflang="en">PACC</a></div> </div> </div> <div class="field field--name-field-policy-responsible-executi field--type-entity-reference field--label-above"> <div class="field__label">Senior Leader</div> <div class="field__items"> <div class="field__item"><a href="/user/74" hreflang="en">provost</a></div> </div> </div> <div class="field field--name-field-policy-responsible-officer field--type-entity-reference field--label-above"> <div class="field__label">Responsible Officer</div> <div class="field__items"> <div class="field__item"><a href="/user/74" hreflang="en">provost</a></div> </div> </div> <div class="clearfix text-formatted field field--name-field-description field--type-text-long field--label-above"> <div class="field__label">Revision Description for Review/Update Page</div> <div class="field__item"><p>Comprehensive Review, Major Revision: 1. Defines "academic plan" to include majors, minors, and certificates (i.e., to include all academic plans that are documented on the transcript). Certificates were not included in the past, as their requirements were not formally documented in PCAS until two years ago. 2. Provides examples of levels of academic units authority in FAQ #5, to clarify for advisors and faculty who has authority over a particular requirement. 3. Includes a definition of a certificate, consistent with the definitions in other policies 4. Outlines the responsibilities at the department/program level, college/campus level, SVPP level, and Regents level. 5. Aligns with Administrative Policy: Adding, Changing or Discontinuing Academic Plans.</p> </div> </div> <div class="field field--name-field-ucmcontentid field--type-string field--label-above"> <div class="field__label">UCMContentID</div> <div class="field__item">CURRICULUMAUTHORITY</div> </div> <div class="field field--name-field-studenttype field--type-list-string field--label-above"> <div class="field__label">Student Type</div> <div class="field__item">All Students</div> </div> <div class="clearfix text-formatted field field--name-field-policyresponsibilities field--type-text-long field--label-above"> <div class="field__label">Responsibilities</div> <div class="field__item"><dl><dt>Academic Department(s) Responsible for the Academic Program</dt><dd> <ul> <li>Maintain complete, up-to-date descriptions of the requirements for its academic programs, including all prerequisite courses</li> <li>Determine requirements for admission to particular academic programs/plans.</li> <li>Maintain up-to-date curricular offerings, regularly scheduled, in order to allow students to make timely progress toward completing an academic program.</li> <li>Provide full and timely information regarding course content and scheduling.</li> <li>Clear students for graduation, certifying that they have met the requirements for the major, minor, or certificate.</li> <li>Review and provide final approval for requests for waivers of particular requirements for the major, minor, or certificate.</li> </ul> </dd><dt>College/Campus</dt><dd> <ul> <li>Maintain up-to-date descriptions of the collegiate and campus requirements for academic programs within that college and campus.</li> <li>Review and provide final approval for requests for waivers of particular academic program requirements at the college/campus level.</li> </ul> </dd><dt>Executive Vice President and Provost</dt><dd> <ul> <li>Review and recommend approval of academic proposals for Board of Regents consideration and final action.</li> </ul> </dd><dt>Board of Regents</dt><dd> <ul> <li>Review and provide final approval of proposals for new, changed, or discontinued academic programs/plans.</li> </ul> </dd></dl></div> </div> <div class="clearfix text-formatted field field--name-field-policyrelatedinformation field--type-text-long field--label-above"> <div class="field__label">Related Information</div> <div class="field__item"><ul> <li>Administrative Policy: <a href="/education/academicprogram">Adding, Changing or Discontinuing Academic Plans</a></li> <li>Administrative Policy:&nbsp;<a href="/education/readmissionloa" target=""><em>Leave of Absence and Readmission for Undergraduates: Twin Cities, Crookston, Morris, Rochester</em></a></li> <li><a href="https://www.hlcommission.org/Policies/criteria-and-core-components.html">Higher Learning Commission, Criteria and Requirements for Accreditation</a></li> </ul></div> </div> <div class="clearfix text-formatted field field--name-field-policyhistory field--type-text-long field--label-above"> <div class="field__label">History</div> <div class="field__item"><dl> <dt>Amended:</dt><dd>June 2016 - Comprehensive Review, Major Revision: 1. Defines "academic plan" to include majors, minors, and certificates (i.e., to include all academic plans that are documented on the transcript). Certificates were not included in the past, as their requirements were not formally documented in PCAS until two years ago. 2. Provides examples of levels of academic units authority in FAQ #5, to clarify for advisors and faculty who has authority over a particular requirement. 3. Includes a definition of a certificate, consistent with the definitions in other policies 4. Outlines the responsibilities at the department/program level, college/campus level, SVPP level, and Regents level. 5. Aligns with Administrative Policy: Adding, Changing or Discontinuing Academic Plans.</dd><dt>Amended:</dt><dd>September 2014 - Clarifications related to Higher Learning Commission accreditation requirements.</dd><dt>Amended:</dt><dd>August 2010 - Added questions 2-4 to Frequently Asked Questions.</dd><dt>Amended:</dt><dd>December 2009 - Policy now applies to Crookston.</dd><dt>Effective:</dt><dd>April 2009</dd></dl></div> </div> <div class="field field--name-field-date-comp-review field--type-datetime field--label-above"> <div class="field__label">Date Comp Review</div> <div class="field__items"> <div class="field__item"><time datetime="2016-06-02T12:00:00Z" class="datetime">Thu, 06/02/2016 - 12:00</time> </div> </div> </div> <div class="field field--name-field-date-comp-review-due field--type-datetime field--label-above"> <div class="field__label">Date Comp Review Due</div> <div class="field__item"><time datetime="2020-06-02T12:00:00Z" class="datetime">Tue, 06/02/2020 - 12:00</time> </div> </div> <div class="field field--name-field-senate-involvement field--type-list-string field--label-above"> <div class="field__label">Senate Involvement</div> <div class="field__items"> <div class="field__item">F Senate (action)</div> </div> </div> <div class="field field--name-field-d7-nid field--type-integer field--label-above"> <div class="field__label">D7 NID</div> <div class="field__item">9534</div> </div> <div class="field field--name-field-d7-vid field--type-integer field--label-above"> <div class="field__label">D7 VID</div> <div class="field__item">269441</div> </div> <div class="field field--name-field-date-comp-review-stamp field--type-timestamp field--label-above"> <div class="field__label">Date of Comprehensive Review - Time Stamp</div> <div class="field__item">Thu, 06/02/2016 - 00:00</div> </div> Wed, 17 Dec 2014 06:00:00 +0000 oitadmin 1758 at https://policy.umn.edu Acquiring and Use of the U Card https://policy.umn.edu/operations/ucard <span class="field field--name-title field--type-string field--label-hidden">Acquiring and Use of the U Card</span> <span class="field field--name-uid field--type-entity-reference field--label-hidden"><a title="View user profile." href="/user/1" lang="" about="/user/1" typeof="schema:Person" property="schema:name" datatype="" class="username">oitadmin</a></span> <span class="field field--name-created field--type-created field--label-hidden">Tue, 09/23/2014 - 00:00</span> <div class="field field--name-field-category field--type-entity-reference field--label-above"> <div class="field__label">Category</div> <div class="field__items"> <div class="field__item"><a href="/taxonomy/term/92" hreflang="en">Safety and Access</a></div> </div> </div> <section class="field field--name-field-comments field--type-comment field--label-above comment-wrapper"> <h2 class="title comment-form__title">Add new comment</h2> <drupal-render-placeholder callback="comment.lazy_builders:renderForm" arguments="0=node&amp;1=1908&amp;2=field_comments&amp;3=policy_comment" token="fX8lECo92h_KsS012kcNQbopbLGcueWf3gQYGpJJ9UM"></drupal-render-placeholder> </section> <div class="field field--name-field-owner field--type-entity-reference field--label-above"> <div class="field__label">Owner</div> <div class="field__items"> <div class="field__item"><a href="/user/404" hreflang="en">mclau001</a></div> </div> </div> <div class="field field--name-field-policy-related-procedures field--type-entity-reference field--label-above"> <div class="field__label">Policy Related Procedures</div> <div class="field__items"> <div class="field__item"><a href="/operations/ucard-proc01" hreflang="en">Obtaining and Maintaining the U Card</a></div> </div> </div> <div class="field field--name-field-urlcategory field--type-list-string field--label-above"> <div class="field__label">urlcategory</div> <div class="field__item">Operations</div> </div> <div class="field field--name-field-path-slug field--type-string field--label-above"> <div class="field__label">Path slug</div> <div class="field__item">UCARD</div> </div> <div class="field field--name-field-sme field--type-entity-reference field--label-above"> <div class="field__label">Primary Contact</div> <div class="field__items"> <div class="field__item"><a href="/user/397" hreflang="en">cour0096</a></div> </div> </div> <div class="clearfix text-formatted field field--name-field-revisiondescription field--type-text-long field--label-above"> <div class="field__label">Revision Description</div> <div class="field__item">Senior Leader update.</div> </div> <div class="field field--name-field-subtype field--type-list-string field--label-above"> <div class="field__label">SubType</div> <div class="field__item">Administrative Policy</div> </div> <div class="clearfix text-formatted field field--name-field-faq field--type-text-long field--label-above"> <div class="field__label">FAQ</div> <div class="field__item"><p>For answers to Frequently Asked Questions visit the <a href="http://ucard.umn.edu/umtc/u-card-faq" target="">UCard FAQ</a>.</p></div> </div> <div class="clearfix text-formatted field field--name-field-appendices field--type-text-long field--label-above"> <div class="field__label">Appendices</div> <div class="field__item"><h3>Components of the U Card</h3> <p>See the website associated with your respective campus (see table below) for specific rates, descriptions of the U Card benefits, services, and other program features for all University of Minnesota Campuses.</p> </div> </div> <div class="clearfix text-formatted field field--name-field-forms field--type-text-long field--label-above"> <div class="field__label">Forms</div> <div class="field__item"><p>See the website associated with your respective campus (see table below) for specific instructions regarding how to obtain the U Card and for details on the benefits associated with your U Card.</p></div> </div> <div class="field field--name-field-daterevised field--type-datetime field--label-above"> <div class="field__label">Last Revised</div> <div class="field__item"><time datetime="2019-07-01T12:00:00Z" class="datetime">Mon, 07/01/2019 - 12:00</time> </div> </div> <div class="field field--name-field-dateeffective field--type-datetime field--label-above"> <div class="field__label">Effective Date</div> <div class="field__item"><time datetime="1997-12-01T12:00:00Z" class="datetime">Mon, 12/01/1997 - 12:00</time> </div> </div> <div class="clearfix text-formatted field field--name-field-policystatement field--type-text-long field--label-above"> <div class="field__label">Policy Statement</div> <div class="field__item"><p>The U Card is the official University photo identity authentication card used on all University campuses and facilities for eligible members of the University community. The U Card is required for personal identification and may be required as certification of eligibility for University-related services and secured physical access to designated University buildings. Students, faculty, and staff are required to carry their University issued U Card when in University buildings outside of public hours.</p> <p>All individuals who have received a U Card must comply with the conditions set forth in this policy and the Administrative Procedure:&nbsp;<em><a href="/operations/ucard-proc01">Obtaining and Maintaining the U Card</a></em>.</p> <p>Individuals who are required to wear the U Card as a condition of employment must wear the card face up at all times when in non-public spaces, high-security areas, or mandatory use situations.&nbsp;Departments are responsible for monitoring and addressing non-compliance of individuals to whom this requirement applies. Employees in non-public or high-security areas are encouraged to approach any individual seen accessing a restricted work space without wearing a U Card and offer to provide assistance. For additional information regarding U Card requirements within University facilities see Administrative Policy:&nbsp;&nbsp;<em><a href="/operations/buildingaccess">Getting Access to University Buildings</a></em>.</p> <p>University campuses, colleges, departments or units who do or will require the establishment of an identity authentication method to verify service eligibility or for secured facility access must use the U Card.</p> <p>Units may not retain U Cards as collateral for departmental services.</p> <p>The individual cardholder is responsible for maintaining their U Card. Departments cannot retain U Cards at graduation or upon termination or separation of employment. Cardholders should not give their U Cards to their former departments as collateral, nor should they return their U Card to the U Card Office. Some value accounts on the U Card may remain active even after a person has left the University.</p> <h3>Eligibility</h3> <p>Eligibility for the U Card is determined by an individual's relationship to the University, both role and status.</p> <p><strong>Students:</strong>&nbsp;Undergraduate, graduate and professional students must be currently admitted and/or registered for classes at the University of Minnesota to be eligible for the U Card.</p> <p><strong>Faculty/Staff/Regents:</strong>&nbsp;Faculty, staff, and University Regents must be entered into the Human Resource Management System (HRMS) to be eligible for the U Card. An indication that you have been entered into HRMS is when you have received an official University e-mail address and/or are listed in the online directory.</p> <p><strong>Visitors:</strong>&nbsp;Affiliated academics, staff, students and all other visitors must be sponsored by a University department to be eligible for the U Card. See procedure:&nbsp;<em>Obtaining and Maintaining the U Card</em>.</p> <h3>Access</h3> <p>Physical access to designated buildings and eligibility for some campus services will be electronically authenticated via the U Card. Access and eligibility may change based on a change in an individual's role or status. The U Card Office does not assign or manage access to secured doors. Departments may request that secured door access be added to a U Card. See Administrative Policy: <em>Getting Access to University Buildings</em>.</p> <h3>Requirements and Restrictions</h3> <p>Stolen or fraudulent use of a U Card should be reported to the University of Minnesota Police or local law enforcement.</p> <p>Found U Cards should be returned to the U Card Office and not held by departments.</p> <p>Lost or stolen U Cards should be deactivated on the U Card website. If a replacement U Card is issued, the previous U Card will be deactivated. Deactivation is permanent and cannot be reversed.</p> <p>A new photo is required when an individual replaces their U Card 6 months or more after original issuance. The U Card holder is responsible for any applicable replacement fees.</p> <p>Unauthorized and/or fraudulent use of a U Card may result in confiscation, deactivation, disciplinary action and/or prosecution.</p> <p>While some services are deactivated when a user no longer has an eligible status, many of the services associated with the U Card never expire. Therefore, U Cards may be retained by cardholders indefinitely. U Card holders must comply with all terms and conditions for the services used.</p></div> </div> <div class="clearfix text-formatted field field--name-field-policyreason field--type-text-long field--label-above"> <div class="field__label">Reason for Policy</div> <div class="field__item"><p>The U Card provides and promotes a user friendly, one-card identity authentication access system to campus goods and services by using state-of-the art card technologies and integrated software solutions to provide authentication of identity, thereby eliminating the need for multiple forms of identification.</p></div> </div> <div class="clearfix text-formatted field field--name-field-policycontacts field--type-text-long field--label-above"> <div class="field__label">Contacts</div> <div class="field__item"><div class="tablewrapper"> <table> <thead> <tr><th scope="col">Subject</th><th scope="col">Contact</th><th scope="col">Phone</th><th scope="col">Email</th></tr> </thead> <tbody> <tr><th scope="row">Primary Contact(s)</th> <td><a href="http://www.umn.edu/lookup?UID=cour0096">Stephen Courchane</a></td> <td>612-626-9909</td> <td>cour0096@umn.edu</td> </tr> <tr><th scope="row">General U Card Inquiries</th> <td>U Card Office, Twin Cities</td> <td>612-626-9900</td> <td>ucard@tc.umn.edu <br><a href="https://ucard.umn.edu">Twin Cities Campus UCard Office</a></td> </tr> <tr><th scope="row">U Card Crookston</th> <td>9 Hill Hall</td> <td>218-281-8548</td> <td><a href="https://ucard.umn.edu/umc/home">Crookston Campus UCard Office</a></td> </tr> <tr><th scope="row">U Card Duluth</th> <td>127 Kirby Plaza <br> 1208 Kirby Drive</td> <td>218-726-8814</td> <td><a href="https://ucard.umn.edu/umd/home">Duluth Campus UCard Office</a></td> </tr> <tr><th scope="row">U Card Morris</th> <td>205 Behmler Hall</td> <td>320-589-6156</td> <td><a href="https://ucard.umn.edu/umm/home">Morris Campus UCard Office</a></td> </tr> <tr><th scope="row">U Card Rochester</th> <td>Student Resource Center, Suite 369 <br> University Square</td> <td>507-258-8069</td> <td><a href="https://ucard.umn.edu/umr/home">Rochester Campus UCard Office</a></td> </tr> <tr><th scope="row">U Card Twin Cities</th> <td>Coffman Memorial Union, Room G22 <br> <br> Coffman Memorial Union, Info Desk <br> <br> St. Paul Student Center, Room 32</td> <td>612-626-9900</td> <td>ucard@umn.edu<br><a href="https://ucard.umn.edu/umtc/home">Twin Cities Campus UCard Office</a></td> </tr> </tbody> </table> </div></div> </div> <div class="clearfix text-formatted field field--name-field-policydefinitions field--type-text-long field--label-above"> <div class="field__label">Definitions</div> <div class="field__item"><dl> <dt>Affiliated</dt> <dd>Individuals who provide a service for the University but are not paid by the University. Also called "without salary" appointments.</dd> <dt>Government Issued Photo Identification</dt> <dd>Existing document that must be presented to verify identity when an individual obtains the U Card. Includes: driver's license, passport, state, military or tribal identification documents.</dd> <dt>Sponsoring Department</dt> <dd>University department sponsoring U Card eligibility for individuals in the following categories: Affiliated academics, staff, students, visiting students, short-term employees&nbsp;<em>and others. Use of the term "sponsor" for the U Card indicates the relationship between the department and the individual, and has no relationship to "sponsored projects".</em></dd> <dt>Eligible Individuals for Sponsored U Cards</dt> <ul> <li>Students admitted to the University and all other students registered for day and/or extension credits.</li> <li>Regents, faculty, academic staff, staff and retirees.</li> <li>Visiting students, affiliated faculty, affiliated academic staff and affiliated staff, if sponsored by a University department.</li> </ul> <dt>U Card</dt> <dd>The U Card is the official identity authentication card for the University. The U Card is comprised of the physical card, the data and the photograph printed on and/or encoded in the card. The U Card serves as a multi-authentication of identity, and verifies eligibility for discretionary campus services and building access, as may be required by a University department.</dd> </dl></div> </div> <div class="field field--name-field-committee-review field--type-entity-reference field--label-above"> <div class="field__label">Committee Involvement</div> <div class="field__items"> <div class="field__item"><a href="/taxonomy/term/8" hreflang="en">SCFA</a></div> <div class="field__item"><a href="/taxonomy/term/4" hreflang="en">SCC</a></div> </div> </div> <div class="field field--name-field-policy-responsible-executi field--type-entity-reference field--label-above"> <div class="field__label">Senior Leader</div> <div class="field__items"> <div class="field__item"><a href="/user/76" hreflang="en">frans</a></div> </div> </div> <div class="field field--name-field-policy-responsible-officer field--type-entity-reference field--label-above"> <div class="field__label">Responsible Officer</div> <div class="field__items"> <div class="field__item"><a href="/user/8" hreflang="en">berth004</a></div> </div> </div> <div class="clearfix text-formatted field field--name-field-description field--type-text-long field--label-above"> <div class="field__label">Revision Description for Review/Update Page</div> <div class="field__item"><p>Comprehensive Review: Updated content to match current practices. This included clarifying eligibility, access and requirements. Additional information was added to clarify building access policies and procedures.</p></div> </div> <div class="field field--name-field-ucmcontentid field--type-string field--label-above"> <div class="field__label">UCMContentID</div> <div class="field__item">UCARD</div> </div> <div class="clearfix text-formatted field field--name-field-policyresponsibilities field--type-text-long field--label-above"> <div class="field__label">Responsibilities</div> <div class="field__item"><dl><dt>Card Holder</dt><dd>Provide government issued photo identification and follow the process for acquiring a U Card (see also Administrative Procedure: <em>Obtaining and Maintaining the U Card</em>). Read and adhere to the requirements for maintaining a U Card. Keep the U Card secure and report any lost, stolen or fraudulent uses. Protect the U Card from damage that will impact functionality and access to services.</dd><dt>Sponsoring Department</dt><dd>Complete and submit the online sponsored account application form in order for affiliated members of the University community to obtain a U Card. The applicant's legal name is required. A current and eligible EFS number is required for payment. Review, and as appropriate, renew the U Card for affiliated University community members associated with their department.</dd><dt>U Card Office</dt><dd>Determine eligibility requirements for providing U Cards (not services or access). Issue the physical U Cards. Set standards and determine picture quality for all photos (in-person or submitted) to be printed on U Cards. Educate users about U Card policies, procedures, and connected services. Providing a functional and professional card.</dd><dt>Departments</dt><dd>Set local policy and monitor compliance regarding the use of the U Card for identification in secure areas. Identify departmental liaison for obtaining and mailing U Cards to remote employees (Twin Cities campus only).</dd></dl></div> </div> <div class="clearfix text-formatted field field--name-field-policyrelatedinformation field--type-text-long field--label-above"> <div class="field__label">Related Information</div> <div class="field__item"><ul> <li>Administrative Policy:&nbsp;<a href="/it/itresources"><em>Acceptable Use of Computers, Networks and Electronic Information Systems Technology</em></a></li> <li>Administrative Policy:&nbsp;<a href="/it/securedata"><em>Information Security</em></a></li> <li>Administrative Policy:&nbsp;<em><a href="/operations/buildingaccess">Getting Access to University Buildings</a></em></li> </ul></div> </div> <div class="clearfix text-formatted field field--name-field-policyhistory field--type-text-long field--label-above"> <div class="field__label">History</div> <div class="field__item"><dl compact="compact"> <dt>Amended:</dt><dd>July 2019 - Comprehensive Review: Updated content to match current practices. This included clarifying eligibility, access and requirements. Additional information was added to clarify building access policies and procedures.</dd> <dt>Amended:</dt><dd>September 2014 - The policy now includes language originally included in the Security ID Badge around the use of required identification badges, and specifies that departments are responsible for the monitoring and addressing of non-compliance with the requirement.</dd><dt>Amended:</dt><dd>April 2013 - Comprehensive Review, Minor Revision:&nbsp;Title&nbsp;change&nbsp;and re-written to: specify required use&nbsp;and conditions for expanded use of the U Card; assign&nbsp;responsibilities of the user, sponsoring department, and U Card office; enumerate and define categories of eligibility; and&nbsp;revise the procedure for obtaining and maintaining the U Card.</dd><dt>Amended:</dt><dd>December 2008 - Comprehensive review: Clarified policy statement; updated definitions; updated roles and responsibilities. Title changed in both policy and procedure.</dd><dt>Amended:</dt><dd>March 2007 - Clarified U Card eligibility in Policy Statement; Updated Definitions and Responsibilities section.</dd><dt>Amended:</dt><dd>January 2004 - Updated U Card Photo Specifications under Cardholder in Responsibilities section.</dd><dt>Amended:</dt><dd>September 2000 - Policy completely written to reflect the business process change associated with Peoplesoft Implementation. Responsible University Officer has changed to Assoc. VP of Aux. Serv. Policy Statement has been changed to reflect the increased number of services associated with the U Card. Contacts have been reduced to only the U Card Office to correct out of date U Card contact info and eliminate HR contacts due to the PeopleSoft implementation. Special Situations has changed to reflect the number of services associated with the card, not just the financial component. Rates have changed for replacements and affiliate cards. Eligible Individuals have been updated to reflect the changes due to the PeopleSoft conversion. Responsibilities have been changed to delete Human Resources due to PeopleSoft. The Administrative Procedure: <em>Applying for a UCard</em> was changed as follows: Students were changed to delete Visiting Students section. All Other Eligible Individuals was changed to reflect the changes due to the PeopleSoft conversion. University Designated Locations were updated to reflect Morris and Crookston's new addresses.</dd><dt>Amended:</dt><dd>February 1998 - Definitions section, hospital staff removed from definition of Eligible Individuals and Visiting Students definition removed, since visiting students do not need to be registered to qualify for a U Card, they only need to be departmentally sponsored.</dd><dt>Effective:</dt><dd>December 1997</dd></dl></div> </div> <div class="field field--name-field-date-comp-review field--type-datetime field--label-above"> <div class="field__label">Date Comp Review</div> <div class="field__items"> <div class="field__item"><time datetime="2019-07-01T12:00:00Z" class="datetime">Mon, 07/01/2019 - 12:00</time> </div> </div> </div> <div class="field field--name-field-date-comp-review-due field--type-datetime field--label-above"> <div class="field__label">Date Comp Review Due</div> <div class="field__item"><time datetime="2023-07-01T12:00:00Z" class="datetime">Sat, 07/01/2023 - 12:00</time> </div> </div> <div class="field field--name-field-d7-nid field--type-integer field--label-above"> <div class="field__label">D7 NID</div> <div class="field__item">9684</div> </div> <div class="field field--name-field-d7-vid field--type-integer field--label-above"> <div class="field__label">D7 VID</div> <div class="field__item">257866</div> </div> <div class="field field--name-field-date-comp-review-stamp field--type-timestamp field--label-above"> <div class="field__label">Date of Comprehensive Review - Time Stamp</div> <div class="field__item">Mon, 07/01/2019 - 00:00</div> </div> Tue, 23 Sep 2014 05:00:00 +0000 oitadmin 1908 at https://policy.umn.edu Acquisition, Use, and Disposition of Donated Human Fetal Tissue for Research (Non-Transplantation) or Teaching https://policy.umn.edu/research/fetalresearchnontrans <span class="field field--name-title field--type-string field--label-hidden">Acquisition, Use, and Disposition of Donated Human Fetal Tissue for Research (Non-Transplantation) or Teaching</span> <span class="field field--name-uid field--type-entity-reference field--label-hidden"><a title="View user profile." href="/user/2" lang="" about="/user/2" typeof="schema:Person" property="schema:name" datatype="" class="username">young041</a></span> <span class="field field--name-created field--type-created field--label-hidden">Wed, 01/13/2016 - 11:44</span> <div class="field field--name-field-category field--type-entity-reference field--label-above"> <div class="field__label">Category</div> <div class="field__items"> <div class="field__item"><a href="/taxonomy/term/101" hreflang="en">Research Ethics &amp; Compliance</a></div> </div> </div> <section class="field field--name-field-comments field--type-comment field--label-above comment-wrapper"> <h2 class="title comment-form__title">Add new comment</h2> <drupal-render-placeholder callback="comment.lazy_builders:renderForm" arguments="0=node&amp;1=1924&amp;2=field_comments&amp;3=policy_comment" token="NrOiuouw_ha2BcSwmUtIjxwpOVU38qksGUKeDmFYniY"></drupal-render-placeholder> </section> <div class="field field--name-field-owner field--type-entity-reference field--label-above"> <div class="field__label">Owner</div> <div class="field__items"> <div class="field__item"><a href="/user/189" hreflang="en">lawrenz</a></div> </div> </div> <div class="field field--name-field-policy-related-procedures field--type-entity-reference field--label-above"> <div class="field__label">Policy Related Procedures</div> <div class="field__items"> <div class="field__item"><a href="/research/fetalresearch-proc03" hreflang="en">Acquisition, Use and Disposition of Donated Human Fetal Tissue Used for Research (Transplantation and Non-Transplantation) or Teaching</a></div> </div> </div> <div class="field field--name-field-urlcategory field--type-list-string field--label-above"> <div class="field__label">urlcategory</div> <div class="field__item">Research</div> </div> <div class="field field--name-field-path-slug field--type-string field--label-above"> <div class="field__label">Path slug</div> <div class="field__item">fetalresearchnontrans</div> </div> <div class="field field--name-field-sme field--type-entity-reference field--label-above"> <div class="field__label">Primary Contact</div> <div class="field__items"> <div class="field__item"><a href="/user/189" hreflang="en">lawrenz</a></div> </div> </div> <div class="clearfix text-formatted field field--name-field-revisiondescription field--type-text-long field--label-above"> <div class="field__label">Revision Description</div> <div class="field__item"><p>Senior leader, Resp Officer change.</p> </div> </div> <div class="field field--name-field-subtype field--type-list-string field--label-above"> <div class="field__label">SubType</div> <div class="field__item">Administrative Policy</div> </div> <div class="field field--name-field-daterevised field--type-datetime field--label-above"> <div class="field__label">Last Revised</div> <div class="field__item"><time datetime="2019-05-30T12:00:00Z" class="datetime">Thu, 05/30/2019 - 12:00</time> </div> </div> <div class="field field--name-field-dateeffective field--type-datetime field--label-above"> <div class="field__label">Effective Date</div> <div class="field__item"><time datetime="2016-02-22T12:00:00Z" class="datetime">Mon, 02/22/2016 - 12:00</time> </div> </div> <div class="clearfix text-formatted field field--name-field-policystatement field--type-text-long field--label-above"> <div class="field__label">Policy Statement</div> <div class="field__item"><p>University personnel (“personnel”) may use human fetal tissue or cell lines derived from human fetal tissue ("human fetal tissue") for purposes of non-transplantation research and teaching only in accordance with applicable federal and state laws and regulations, and University policies and procedures. &nbsp;&nbsp;This policy does not apply to the use of cell lines derived from human fetal tissue that historically have been available and are widely used and distributed on a national basis.</p> <h3>Requirements that Apply to Research</h3> <p>Researchers who wish to conduct research studies involving human fetal tissue must:</p> <ul> <li>obtain approval from the Fetal Tissue Research (FTR) committee; and</li> <li>obtain approval for the research from the IRB if the researcher obtains identifying information about the person donating the human fetal tissue or meets other criteria for IRB review.</li> </ul> <p>If the research requires IRB approval, the FTR will share its assessment with the IRB. &nbsp;</p> <h3>Requirements that Apply to Research and Teaching</h3> <p>All personnel who use human fetal tissue in research or teaching must:</p> <ul> <li>submit a request for human fetal tissue to the Anatomy Bequest Program (ABP) or obtain approval from ABP for the source of human fetal tissue supplied by a research sponsor;</li> <li>participate in mandatory training provided by ABP;</li> <li>retain the human fetal tissue only for the amount of time necessary to complete the research or teaching use; and</li> <li>notify ABP when the research or teaching use is complete to arrange for disposition of any remaining human fetal tissue.</li> </ul> <h3>Prohibited Activities</h3> <p>Personnel &nbsp;may not perform research on a human fetus which meets the definition of a living human conceptus under Minnesota law (shows the presence of evidence of life, such as movement, heart or respiratory activity, or the presence of electroencephalographic or electrocardiographic activity), except to protect the life or health of the fetus.</p> <p>Personnel, regardless of source of funding, cannot:</p> <ul> <li>(when leaving the University) transfer human fetal tissue to other institutions;</li> <li>distribute acquired human fetal tissue to an internal or external researcher without the advance approval of the FTR and notification to ABP;</li> <li>offer or provide payment for any costs associated with a donor's induced abortion; nor</li> <li>buy or sell human fetal tissue, except reasonable payments are permitted associated with the transportation, implantation, processing, preservation, quality control or storage of human fetal tissue.</li> </ul> <h3>Approval of Research Prior to Acquiring Human Fetal Tissue</h3> <p>Except for research that meets the criteria for review by the Institutional Review Board (IRB), the FTR must review and approve all research with human fetal tissue or cell lines derived from human fetal tissue, before the research begins.</p> <p>The FTR has authority to approve, require modifications to or disapprove proposed research, and to suspend or terminate approved research for serious non-compliance or unanticipated problems.</p> <p>The FTR will consider whether alternatives to human fetal tissue would be sufficient for the research and will require researchers to provide a written explanation of the need for human fetal tissue from induced abortions and whether alternatives, including non-aborted human fetal tissue, can be used for the research. The FTR will submit its decisions to the University’s Institutional Review Board (IRB) for review by the IRB to ensure all alternatives have been considered.</p> <h3>Acquiring Human Fetal Tissue</h3> <p>Personnel must contact the Anatomy Bequest Program (ABP) prior to obtaining human fetal tissue from any source, and must either: 1) obtain the human fetal tissue through (ABP); or 2) obtain approval from ABP for the source of human fetal tissue supplied by a research sponsor, collaborator or other source.&nbsp; ABP will acquire human fetal tissue from tissue procurement organization or clinics outside Minnesota that operate in compliance with federal law and applicable state laws and certify they do not obtain human fetal tissue from abortions performed in Minnesota. ABP also may accept donations of human fetal tissue obtained from a stillborn infant, or an embryo or fetus that died of natural causes in utero as authorized under applicable state laws.</p> <h3>Disposing of Human Fetal Tissue</h3> <p>Personnel must notify ABP when the research or teaching use is complete. ABP will dispose of the human fetal tissue in a dignified manner through cremation, burial or other lawful disposition method.</p> <p>Personnel must contact the ABP if the intended use of the human fetal tissue changes or if the study or teaching use will take longer than anticipated.</p> <h3>Training</h3> <p>All personnel, including students, using&nbsp;human fetal issue in research or teaching must complete the training provided by ABP. The training will cover applicable federal and state laws, University policies and procedures, and other professional standards related to the respectful, humane, and ethical treatment of human fetal tissue used in research or teaching</p> <h3>Separation of Roles</h3> <p>Personnel who perform human fetal tissue research must be separate from the attending physician treating the&nbsp;person undergoing an induced abortion. The personnel may have no part in any decisions on the timing, method or procedures used to end the pregnancy and may have no part in determining fetal viability.</p> <h3>Required Reporting</h3> <p>The University must submit an annual report to the Minnesota Legislature, no later than January 15th of each year, providing information about human fetal tissue research at the University as mandated by the Legislature in a 2017 law.</p> <h3>Exclusions</h3> <p>This policy excludes the use of cell lines derived from human fetal tissue that historically have been available and are widely used and distributed on a national basis. In addition, this policy does not address the acquisition or use of excess in vitro fertilization human embryos or embryonic stem cells or stem cell lines derived from such embryos, (see Administrative Policy:&nbsp;<a href="/research/embryonicstemcells"><em>Conducting Research with Human Embryos or Embryonic Stem Cells</em></a>.)</p> <p>Personnel conducting research with human fetal tissue for the purpose of transplantation must follow Administrative Policy:&nbsp;<a href="/research/fetalresearch"><em>Acquisition, Use, and Disposition of Donated Human Fetal Tissue for Transplantation Research</em></a>.</p> </div> </div> <div class="clearfix text-formatted field field--name-field-policyreason field--type-text-long field--label-above"> <div class="field__label">Reason for Policy</div> <div class="field__item"><p>Research and education using human fetal tissue or cell lines derived from human fetal tissue for therapeutic purposes shows much promise for treating serious diseases and disorders such as diabetes, sepsis, HIV/AIDS, spinal cord injuries and neurodegenerative diseases. This policy is intended to inform and assist University personnel who wish to use human fetal tissue in research or teaching, while at the same time assuring that all such activity conducted at the University meets legal and policy requirements. This policy also specifies the official unit responsible for the acquisition and disposition of fetal tissue used in research or teaching, thereby reducing legal, reputational, financial, and other risks to the University and researchers.</p> </div> </div> <div class="clearfix text-formatted field field--name-field-policycontacts field--type-text-long field--label-above"> <div class="field__label">Contacts</div> <div class="field__item"><!-- The div "tablewrapper" provides a class to edit the base table properties without changing current base table formating. --> <div class="tablewrapper"> <table> <thead> <tr> <th scope="col">Subject</th> <th scope="col">Contact</th> <th scope="col">Phone</th> <th scope="col">Email</th> </tr> </thead> <tbody> <tr> <th scope="row">Primary Contact(s)</th> <td><strong>Frances Lawrenz</strong></td> <td class="nowrap"><strong>612-625-2046</strong></td> <td><strong>lawrenz@umn.edu</strong></td> </tr> <tr> <th scope="row">Anatomy Bequest Program (APB)</th> <td>Angela McArthur</td> <td class="nowrap">612-625-0618</td> <td>mcarthur@umn.edu</td> </tr> <tr> <th scope="row">Funding/Accounting Questions</th> <td>Associate VP for Research, Sponsored Projects Administration</td> <td class="nowrap">612-624-1648</td> <td>612-626-6949<br /> ospa.umn.edu</td> </tr> <tr> <th scope="row">Fetal Tissue Review Committee ( FTR)</th> <td>Greg Park</td> <td class="nowrap">612-625-5193</td> <td>parkx479@umn.edu</td> </tr> <tr> <th scope="row">Institutional Review Board (IRB)</th> <td>Debbie Dykhuis</td> <td class="nowrap">612-626-5654</td> <td>irb@umn.edu</td> </tr> </tbody> </table> </div> </div> </div> <div class="clearfix text-formatted field field--name-field-policydefinitions field--type-text-long field--label-above"> <div class="field__label">Definitions</div> <div class="field__item"><dl> <dt>Cell Line</dt> <dd>A mass of cells descended from the original, sharing its genetic characteristics. Batches of cells can then be separated from the cell line and distributed to researchers.</dd> <dt>Disposition Records</dt> <dd>An accurate, continuous and current record used to track the acquisition, use and disposal of a human fetal tissue.</dd> <dt>Human Fetal Tissue</dt> <dd>Tissue, cells, or organs obtained from a dead human embryo or fetus after a spontaneous or induced abortion or after a stillbirth. Human fetal tissue does not include tissue or cells obtained from a placenta, umbilical cord or amniotic fluid.</dd> <dt>Induced Abortion</dt> <dd>Premature ending of a pregnancy brought about purposefully by drugs or surgical means. Induced abortion is distinguished from a spontaneous abortion, which is a naturally occurring loss of the fetus, usually before the 20th week of gestation, and a stillbirth, which is the delivery of a fetus dead at birth, usually after the 20th week of gestation.</dd> <dt>Non-aborted fetal tissue</dt> <dd>Term used under Minnesota law 137.47, defined as: “fetal tissue that is available as a result of a miscarriage or stillbirth, or fetal tissue from a living unborn child.” Fetal tissue from a living unborn child may not be used in research except to protect the life or health of the fetus. See Prohibited Activities above.</dd> <dt>Research</dt> <dd>Systematic investigation, including development, testing and evaluation designed to develop or contribute to generalizable knowledge.</dd> <dt>Research for Therapeutic Purposes</dt> <dd>Research intended to develop new medical therapies and/or administer such therapies to patients/research participants or in the basic science and biology/physiology of fetal cells that might lead to therapies in the future.</dd> <dt>Tissue Procurement Organization</dt> <dd>An organization that procures human fetal tissue for medical research.</dd> </dl> </div> </div> <div class="field field--name-field-committee-review field--type-entity-reference field--label-above"> <div class="field__label">Committee Involvement</div> <div class="field__items"> <div class="field__item"><a href="/taxonomy/term/6" hreflang="en">SRC</a></div> <div class="field__item"><a href="/taxonomy/term/4" hreflang="en">SCC</a></div> </div> </div> <div class="field field--name-field-policy-responsible-executi field--type-entity-reference field--label-above"> <div class="field__label">Senior Leader</div> <div class="field__items"> <div class="field__item"><a href="/user/394" hreflang="en">oakes007</a></div> </div> </div> <div class="field field--name-field-policy-responsible-officer field--type-entity-reference field--label-above"> <div class="field__label">Responsible Officer</div> <div class="field__items"> <div class="field__item"><a href="/user/394" hreflang="en">oakes007</a></div> </div> </div> <div class="clearfix text-formatted field field--name-field-description field--type-text-long field--label-above"> <div class="field__label">Revision Description for Review/Update Page</div> <div class="field__item"><p>Legal Review.&nbsp; Language to clarify the respective roles of the Fetal Tissue Review Committee (FTR) and the Institutional Review Board (IRB). Minor wording and formatting changes to match new language in the transplantation policy on transfer of tissue and the annual legislative report.&nbsp;&nbsp;</p> </div> </div> <div class="field field--name-field-ucmcontentid field--type-string field--label-above"> <div class="field__label">UCMContentID</div> <div class="field__item">FETALRESEARCHNONTRANS</div> </div> <div class="clearfix text-formatted field field--name-field-policyresponsibilities field--type-text-long field--label-above"> <div class="field__label">Responsibilities</div> <div class="field__item"><dl> <dt>Anatomy Bequest Program (ABP) Director</dt> <dd>Facilitate acquisition of human fetal tissue. Approve source of tissue supplied by a research sponsor. Maintain a database of human fetal tissue acquisition and disposition. Arrange the transportation of human fetal tissue for research or teaching. Arrange for the lawful disposition of human fetal tissue remains. Provide training for all employees and students using human fetal tissue in research or teaching.</dd> <dd>Draft the mandatory annual human fetal tissue research legislative report in consultation with the FTR for review by University senior officials and transmission to the Legislature.</dd> <dt>Researcher or Instructor</dt> <dd>Disclose intended human fetal tissue use. For researchers: Obtain FTR approval, and IRB approval where required. Contact ABP when human fetal tissue is needed or obtain approval from ABP to use fetal tissue supplied by a research sponsor or another source. Properly track and use human fetal tissue. Maintain sufficient laboratory records documenting the acquisition, use, storage location, and processing procedures of the human fetal tissue while the tissue is in the custody of the laboratory. Notify the ABP when the remaining tissue is ready for disposition.</dd> <dd>Attend the required human fetal tissue research training. Ensure that all personnel working with human fetal tissue have received the required training. Create and maintain human fetal tissue training records for lab personnel.</dd> <dt>Institutional Research Board (IRB)</dt> <dd>Review research with human fetal tissue that meets the criteria for IRB review under federal regulations. For other research that uses human fetal tissue, review FTR decisions to assure consideration of all alternatives as required under Minnesota law.</dd> <dt>Fetal Tissue Research (FTR) committee</dt> <dd>Review the scientific merit and ethical justification of proposed research involving human fetal tissue and cell lines derived from human fetal tissue. Consider whether alternatives to human fetal tissue would be sufficient for the research. Determine whether to approve, require modifications to or disapprove the research.</dd> <dd>The FTR will submit its decisions to the University’s Institutional Review Board (IRB) for review.</dd> <dt>Research Compliance Office (RCO)</dt> <dd>Carry out oversight responsibilities related to these projects.</dd> <dt>Office of the General Counsel</dt> <dd>Provide advice to University personnel and administrators on the laws, regulations and University policy requirements related to use of human fetal tissue in research or teaching.&nbsp;</dd> </dl> </div> </div> <div class="clearfix text-formatted field field--name-field-policyrelatedinformation field--type-text-long field--label-above"> <div class="field__label">Related Information</div> <div class="field__item"><ul> <li>Administrative Policy:&nbsp;<a href="https://policy.umn.edu/research/fetalresearch"><em>Acquisition, Use, and Disposition of Donated Human Fetal Tissue for Transplantation Research</em></a></li> <li>Administrative Policy:&nbsp;<a href="https://policy.umn.edu/research/embryonicstemcells"><em>Conducting Research with Human Embryos or Embryonic Stem Cells</em></a></li> </ul> </div> </div> <div class="clearfix text-formatted field field--name-field-policyhistory field--type-text-long field--label-above"> <div class="field__label">History</div> <div class="field__item"><dl> <dt>Amended:</dt> <dd>May 2019 - Legal Review.&nbsp; Language to clarify the respective roles of the Fetal Tissue Review Committee (FTR) and the Institutional Review Board (IRB). Minor wording and formatting changes to match new language in the transplantation policy on transfer of tissue and the annual legislative report. <p>As the result of an audit in 2018 by the Office of the Legislative Auditor, the University agreed to clarify its Fetal Tissue Research policies (Non-Transplantation) and Transplantation. &nbsp;Other language and formatting changes recommended by the Policy Program.</p> </dd> <dt>Amended:</dt> <dd>January 2018 - Comprehensive Review. <ol> <li>Includes language addressing the new UMN requirements as determined by legislative changes to Minnesota § 137.47.</li> <li>Provides new language addressing the exclusion of historical, publically available fetal cell lines from the policy.</li> <li>Adds language broadening the scope of the policy to include teaching uses.</li> <li>Clarifies responsibilities of UMN staff.</li> <li>Includes new language which would prevent the transfer of fetal tissue from one researcher to another, or from the UMN to another institution without advance approval of the Fetal Tissue Research committee.</li> <li>Modifies the title to standardize the language across all three documents.</li> </ol> </dd> <dt>Amended:</dt> <dd>April 2016 - Stem Cell Research Oversight Panel (SCRO) changed to Fetal Tissue Research (FTR) committee to prevent confusion about stem cell research which is the SCRO and Fetal Tissue Research which is not about stem cells.</dd> <dt>Effective:</dt> <dd>February 2016 - New Policy, Comprehensive Review: 1. Incorporates a new requirement to procure and dispose of human fetal tissue, through the Anatomy Bequest Program. 2. Specifies that research using human fetal tissue must be reviewed and approved by the Stem Cell Research Oversight (SCRO) Panel unless subject to IRB review and approval. 3. Identifies research that is prohibited.</dd> </dl> </div> </div> <div class="field field--name-field-date-comp-review field--type-datetime field--label-above"> <div class="field__label">Date Comp Review</div> <div class="field__items"> <div class="field__item"><time datetime="2019-05-30T12:00:00Z" class="datetime">Thu, 05/30/2019 - 12:00</time> </div> </div> </div> <div class="field field--name-field-date-comp-review-due field--type-datetime field--label-above"> <div class="field__label">Date Comp Review Due</div> <div class="field__item"><time datetime="2023-05-30T12:00:00Z" class="datetime">Tue, 05/30/2023 - 12:00</time> </div> </div> <div class="field field--name-field-senate-involvement field--type-list-string field--label-above"> <div class="field__label">Senate Involvement</div> <div class="field__items"> <div class="field__item">U Senate (info)</div> </div> </div> <div class="field field--name-field-d7-nid field--type-integer field--label-above"> <div class="field__label">D7 NID</div> <div class="field__item">11216</div> </div> <div class="field field--name-field-d7-vid field--type-integer field--label-above"> <div class="field__label">D7 VID</div> <div class="field__item">244391</div> </div> <div class="field field--name-field-date-comp-review-stamp field--type-timestamp field--label-above"> <div class="field__label">Date of Comprehensive Review - Time Stamp</div> <div class="field__item">Thu, 05/30/2019 - 00:00</div> </div> Wed, 13 Jan 2016 17:44:00 +0000 young041 1924 at https://policy.umn.edu Acquisition, Use, and Disposition of Donated Human Fetal Tissue for Transplantation Research https://policy.umn.edu/research/fetalresearch <span class="field field--name-title field--type-string field--label-hidden">Acquisition, Use, and Disposition of Donated Human Fetal Tissue for Transplantation Research </span> <span class="field field--name-uid field--type-entity-reference field--label-hidden"><a title="View user profile." href="/user/1" lang="" about="/user/1" typeof="schema:Person" property="schema:name" datatype="" class="username">oitadmin</a></span> <span class="field field--name-created field--type-created field--label-hidden">Tue, 12/30/2014 - 00:00</span> <div class="field field--name-field-category field--type-entity-reference field--label-above"> <div class="field__label">Category</div> <div class="field__items"> <div class="field__item"><a href="/taxonomy/term/104" hreflang="en">Clinical Human Research Participants</a></div> </div> </div> <section class="field field--name-field-comments field--type-comment field--label-above comment-wrapper"> <h2 class="title comment-form__title">Add new comment</h2> <drupal-render-placeholder callback="comment.lazy_builders:renderForm" arguments="0=node&amp;1=1791&amp;2=field_comments&amp;3=policy_comment" token="WYEojUBvaaZXN_lKtTbZ2EkQw5Lu9biOW056zZQdBZ8"></drupal-render-placeholder> </section> <div class="field field--name-field-owner field--type-entity-reference field--label-above"> <div class="field__label">Owner</div> <div class="field__items"> <div class="field__item"><a href="/user/189" hreflang="en">lawrenz</a></div> </div> </div> <div class="field field--name-field-policy-related-procedures field--type-entity-reference field--label-above"> <div class="field__label">Policy Related Procedures</div> <div class="field__items"> <div class="field__item"><a href="/research/fetalresearch-proc03" hreflang="en">Acquisition, Use and Disposition of Donated Human Fetal Tissue Used for Research (Transplantation and Non-Transplantation) or Teaching</a></div> <div class="field__item"><a href="/research/fetalresearch-proc01" hreflang="en">Preparing to Conduct Donated Human Fetal Tissue Transplantation Research Ineligible for Federal/State Funding</a></div> <div class="field__item"><a href="/research/fetalresearch-proc02" hreflang="en">Conducting Research Using Donated Human Fetal Tissue for Transplantation into Designated Recipients</a></div> </div> </div> <div class="field field--name-field-urlcategory field--type-list-string field--label-above"> <div class="field__label">urlcategory</div> <div class="field__item">Research</div> </div> <div class="field field--name-field-path-slug field--type-string field--label-above"> <div class="field__label">Path slug</div> <div class="field__item">FETALRESEARCH</div> </div> <div class="field field--name-field-sme field--type-entity-reference field--label-above"> <div class="field__label">Primary Contact</div> <div class="field__items"> <div class="field__item"><a href="/user/189" hreflang="en">lawrenz</a></div> </div> </div> <div class="clearfix text-formatted field field--name-field-revisiondescription field--type-text-long field--label-above"> <div class="field__label">Revision Description</div> <div class="field__item"><p>Ownership changes from Chris Cramer to Michael Oakes.</p> </div> </div> <div class="field field--name-field-subtype field--type-list-string field--label-above"> <div class="field__label">SubType</div> <div class="field__item">Administrative Policy</div> </div> <div class="field field--name-field-daterevised field--type-datetime field--label-above"> <div class="field__label">Last Revised</div> <div class="field__item"><time datetime="2019-05-30T12:00:00Z" class="datetime">Thu, 05/30/2019 - 12:00</time> </div> </div> <div class="field field--name-field-dateeffective field--type-datetime field--label-above"> <div class="field__label">Effective Date</div> <div class="field__item"><time datetime="2003-12-01T12:00:00Z" class="datetime">Mon, 12/01/2003 - 12:00</time> </div> </div> <div class="clearfix text-formatted field field--name-field-policystatement field--type-text-long field--label-above"> <div class="field__label">Policy Statement</div> <div class="field__item"><p>University researchers (“researchers”) may conduct research on the transplantation of human fetal tissue or cell lines derived from human fetal tissue (“human fetal tissue”) for therapeutic purposes only in accordance with applicable federal and state laws and regulations and University policies and procedures.&nbsp; These researchers must do all the following:</p> <ul> <li>obtain approval from the Fetal Tissue Research committee (FTR) for the use of human fetal tissue and obtain approval for the research from the Institutional Review Board (IRB);</li> <li>submit a fetal tissue acquisition form to the Anatomy Bequest Program (ABP) or obtain approval from ABP for the source of human fetal tissue supplied by a research sponsor;</li> <li>register the research with the Research Compliance Office (RCO) in the Office of the Vice President for Research;</li> <li>follow Food and Drug Administration (FDA) requirements under an approved Investigational New Drug (IND) application;</li> <li>follow the necessary accounting standards if the research is not eligible for federal funding; and</li> <li>use the appropriate source of funds;</li> <li>retain the tissue only for the amount of time necessary to complete the research; and</li> <li>notify ABP when the research is complete to arrange for disposition of any remaining human fetal tissue.</li> </ul> <p>Research ineligible for federal or state funding must use only private funding.</p> <p>Researchers may accept and/or use human fetal tissue for transplantation into a relative of the donor or other individual designated by the donor (i.e., donor-designated recipient) only if the tissue is obtained from a spontaneous abortion or stillbirth.</p> <h3>Prohibited &nbsp;Activities</h3> <p>University personnel (“personnel”) may not perform research on a human fetus which meets the definition of a living human conceptus under Minnesota law (shows the presence of evidence of life, such as movement, heart or respiratory activity, or the presence of electroencephalographic or electrocardiographic activity), except to protect the life or health of the fetus.</p> <p>Personnel, regardless of source of funding, cannot:</p> <ul> <li>receive or use human fetal tissue which is obtained through an induced abortion for the purpose of transplantation into a relative of the donor or other recipient designated by the donor;</li> <li>(when leaving the University) transfer human fetal tissue that was not used for transplantation to other institutions;</li> <li>distribute acquired human fetal tissue to an internal or external researcher without the advance approval of the FTR and notification to the ABP;</li> <li>offer or provide payment for any costs associated with the donor's induced abortion; nor</li> <li>buy or sell human fetal tissue, except reasonable payments are permitted associated with the transportation, implantation, processing, preservation, quality control or storage of human fetal tissue.</li> </ul> <h3>Approval of Research Prior to Acquiring Human Fetal Tissue</h3> <p>Researchers must apply for approval from the FTR for the use of human fetal tissue and apply for approval from the IRB to conduct human fetal tissue transplantation research. The application to FTR will include a written explanation of the need for human fetal tissue from induced abortions. FTR will assess whether alternatives, including non-aborted human fetal tissue can be used for the research, and share that assessment with the IRB before the IRB makes its decision.</p> <h3>Acquiring Human Fetal Tissue</h3> <p>Researchers must contact the Anatomy Bequest Program (ABP) prior to obtaining human fetal tissue from any source. Researchers must either: 1) obtain the human fetal tissue through ABP or 2) obtain approval from ABP for the source of human fetal tissue supplied by a research sponsor or collaborator. ABP will procure fetal tissue from tissue procurement organization or clinics outside Minnesota that operate in compliance with federal law and applicable state laws and certify they do not obtain tissue from abortions performed in Minnesota. ABP also may accept donations of tissue obtained from a stillborn infant, or an embryo or fetus that died of natural causes in utero as authorized under applicable state laws.</p> <h3>Disposing of Human Fetal Tissue</h3> <p>Researchers must notify ABP when the research is complete. ABP will dispose of the human fetal tissue in a dignified manner through cremation and/or burial.</p> <p>Researchers must contact the ABP if the intended use of the fetal tissue changes or if the study will take longer than anticipated.</p> <h3>Training</h3> <p>The Principal Investigator, other project staff, and departmental financial staff must obtain training from Sponsored Projects Administration relative to the financial management of costs related to research ineligible for federal funding (“ineligible study”) prior to beginning an ineligible study involving human fetal tissue transplantation research.</p> <p>All personnel, including students, using human fetal issue in research must complete the training provided by ABP. The training will cover applicable federal and state laws, University policies and procedures, and other professional standards related to the respectful, humane, and ethical treatment of human fetal tissue used in research.</p> <h3>Separation of Roles</h3> <p>Personnel who performs human fetal tissue transplantation research must be separate from the attending physician treating the person undergoing an induced abortion. Personnel may have no part in any decisions on the timing, method or procedures used to end the pregnancy and may have no part in determining fetal viability.</p> <h3>Required Reporting</h3> <p>The University must submit an annual report to the Minnesota Legislature, no later than January 15<sup>th</sup> of each year, providing information about human fetal tissue research (including transplantation research) at the University as mandated by Legislature in a 2017 law.</p> <h3>Funding Restrictions</h3> <p>Researchers who wish to use federal funds for human fetal tissue transplantation research must meet the requirements imposed under federal law to obtain and use federal funds for this purpose. Federal funds are allowable only when:</p> <ul> <li>the recipient of the transplant is&nbsp;<em>unknown&nbsp;</em>to the donor;</li> <li>the recipient of the transplant is&nbsp;<em>not&nbsp;</em>a relative of the donor;</li> <li>the recipient of the transplant&nbsp;<em>has not been&nbsp;</em>designated by the donor;</li> <li>all other federal requirements are satisfied.</li> </ul> <p>In situations where use of federal and/or state funds is not allowable units must charge direct costs associated with a registered study to a private source of funding. A registered study must have in place a method of separating the costs of supporting the research so that any of the facilities and administrative (F&amp;A) costs allocable to the ineligible research are excluded from the rates established and used to charge F&amp;A costs to federal/state funded research. In addition, the principal investigator and the responsible laboratory administrator must carefully and consistently allocate all costs of the ineligible research to a private funding source.</p> <p>Administrative Procedures:&nbsp;<a href="/research/fetalresearch-proc01"><em>Preparing to Conduct Human Fetal Transplantation Research Ineligible for Federal/State Funding</em></a>&nbsp;and&nbsp;<a href="https://policy.umn.edu/research/fetalresearch-proc02"><em>Conducting Research Using Human Fetal Tissue for Transplantation into Designated Recipients</em></a>&nbsp;do not apply to human fetal tissue transplantation research where the recipient of the transplant is unknown to the donor and all other federal requirements are satisfied.</p> <h3>Exclusions</h3> <p>This policy does not address the acquisition or use of excess in vitro fertilization human embryos or embryonic stem cells or stem cell lines derived from such embryos, (see Administrative Policy:&nbsp;<a href="/research/embryonicstemcells"><em>Conducting Research with Human Embryos or Embryonic Stem Cells</em></a><em>.)</em></p> <p>Research for non-transplantation purposes using human fetal tissue is covered in Administrative Policy:&nbsp;<a href="/research/fetalresearchnontrans"><em>Acquisition, Use, and Disposition of Donated Human Fetal Tissue for Research (Non-Transplantation) or Teaching</em></a></p> </div> </div> <div class="clearfix text-formatted field field--name-field-policyreason field--type-text-long field--label-above"> <div class="field__label">Reason for Policy</div> <div class="field__item"><p>Research on the transplantation of human fetal tissue for therapeutic purposes shows much promise in treating serious diseases and disorders such as those amenable to blood and bone marrow transplantation (leukemia, congenital and acquired bone marrow failure syndrome, selected inborn errors of metabolic and immuno-deficiencies) and spinal cord injuries. This policy is intended to inform and assist University researchers who wish to conduct human fetal tissue transplantation research, while at the same time assuring that all such research conducted at the University meets legal, policy and funding requirements. This policy also specifies the official unit responsible for the acquisition and disposition of fetal tissue used in research, thereby reducing legal, reputational, financial and other risks to the University and researchers.</p> </div> </div> <div class="clearfix text-formatted field field--name-field-policycontacts field--type-text-long field--label-above"> <div class="field__label">Contacts</div> <div class="field__item"><div class="tablewrapper"> <table> <thead> <tr> <th scope="col">Subject</th> <th scope="col">Contact</th> <th scope="col">Phone</th> <th scope="col">Email</th> </tr> </thead> <tbody> <tr> <th scope="row"><strong>Primary Contact</strong></th> <td><strong>Frances Lawrenz</strong></td> <td class="nowrap"><strong>612-625-2046</strong></td> <td><strong>lawrenz@umn.edu</strong></td> </tr> <tr> <th scope="row">Anatomy Bequest Program (ABP )</th> <td>Angela McArthur</td> <td>612-625-0618</td> <td>mcarthur@umn.edu</td> </tr> <tr> <th scope="row">Fetal Tissue Review Committee ( FTR)</th> <td>Greg Park</td> <td>612-625-5193</td> <td>parkx479@umn.edu</td> </tr> <tr> <th scope="row">Institutional Review Board (IRB)</th> <td>Debbie Dykhuis</td> <td>612-626-5654</td> <td>irb@umn.edu</td> </tr> <tr> <th scope="row">Funding/Accounting Questions</th> <td>Associate VP for Research, Sponsored Projects Administration</td> <td>612-624-1648</td> <td>612-626-6949<br /> ospa.umn.edu</td> </tr> </tbody> </table> </div> </div> </div> <div class="clearfix text-formatted field field--name-field-policydefinitions field--type-text-long field--label-above"> <div class="field__label">Definitions</div> <div class="field__item"><dl> <dt>Cell Line</dt> <dd>A mass of cells descended from the original, sharing their genetic characteristics. Batches of cells can then be separated from the cell line and distributed to researchers.</dd> <dt>Designated Recipient</dt> <dd>A relative of the donor or other individual designated by the donor</dd> <dt>Electrocardiographic Activity</dt> <dd>The presence of electric currents produced by the contraction of the heart muscle as recorded and displayed on an instrument called an electrocardiograph.</dd> <dt>Electroencephalographic Activity</dt> <dd>The presence of electric currents in the brain as recorded and displayed on an instrument called an electroencephalograph.</dd> <dt>Human Fetal Tissue Transplantation Research</dt> <dd>A form of experimental clinical research where human fetal tissue obtained from a spontaneous or induced abortion or stillbirth is transplanted into a human recipient to treat a serious disease or disorder.</dd> <dt>Human Fetal Tissue</dt> <dd>Tissue, cells, or organs obtained from a dead human embryo or fetus after a spontaneous or induced abortion or after a stillbirth. For purposes of this policy, human fetal tissue includes cell lines derived from a dead human embryo or fetus after a spontaneous or induced abortion or after a stillbirth IF they are used or intended for transplantation into a human recipient. Human fetal tissue does&nbsp;<strong>not&nbsp;</strong>include tissue or cells obtained from a placenta, umbilical cord or amniotic fluid.</dd> <dt>Induced Abortion</dt> <dd>Premature ending of a pregnancy brought about purposefully by drugs or surgical means. Induced abortion is distinguished from a spontaneous abortion, which is a naturally occurring loss of the fetus, usually before the 20th week of gestation, and a stillbirth, which is the delivery of a fetus dead at birth, usually after the 20th week of gestation.</dd> <dt>Ineligible Research</dt> <dd>Human fetal tissue transplantation research where the intended recipient is a relative of the donor or other individual designated by the donor and thus, cannot be supported, directly or indirectly, with federal funds or funds from the State of Minnesota.</dd> <dt>Non-aborted fetal tissue</dt> <dd>Term used under Minnesota law 137.47, defined as: “fetal tissue that is available as a result of a miscarriage or stillbirth, or fetal tissue from a living unborn child.” Fetal tissue from a living unborn child may not be used in research except to protect the life or health of the fetus. See Prohibited Activities above.</dd> <dt>Research for Therapeutic Purposes</dt> <dd>Research intended to develop new medical therapies and/or administer such therapies to patients/research participants or in the basic science and biology/physiology of human fetal cells that might lead to therapies in the future.</dd> </dl> </div> </div> <div class="field field--name-field-committee-review field--type-entity-reference field--label-above"> <div class="field__label">Committee Involvement</div> <div class="field__items"> <div class="field__item"><a href="/taxonomy/term/6" hreflang="en">SRC</a></div> <div class="field__item"><a href="/taxonomy/term/4" hreflang="en">SCC</a></div> </div> </div> <div class="field field--name-field-policy-responsible-executi field--type-entity-reference field--label-above"> <div class="field__label">Senior Leader</div> <div class="field__items"> <div class="field__item"><a href="/user/394" hreflang="en">oakes007</a></div> <div class="field__item"><a href="/user/64" hreflang="en">tolar003</a></div> </div> </div> <div class="field field--name-field-policy-responsible-officer field--type-entity-reference field--label-above"> <div class="field__label">Responsible Officer</div> <div class="field__items"> <div class="field__item"><a href="/user/394" hreflang="en">oakes007</a></div> <div class="field__item"><a href="/user/64" hreflang="en">tolar003</a></div> </div> </div> <div class="clearfix text-formatted field field--name-field-description field--type-text-long field--label-above"> <div class="field__label">Revision Description for Review/Update Page</div> <div class="field__item"><p>Legal Revisions. Language is added to: a) prohibit or regulate the transfer of human fetal tissue that was not used for transplantation; b)) clarify the role of the Fetal Tissue Research Committee (FTR) when research requires review and approval by the IRB; c) include fetal tissue transplantation research activities (to the extent there are any) in the required annual report to the legislature; and d) add a responsibilities section for the FTR</p> </div> </div> <div class="field field--name-field-ucmcontentid field--type-string field--label-above"> <div class="field__label">UCMContentID</div> <div class="field__item">FETALRESEARCH</div> </div> <div class="clearfix text-formatted field field--name-field-policyresponsibilities field--type-text-long field--label-above"> <div class="field__label">Responsibilities</div> <div class="field__item"><dl> <dt>Anatomy Bequest Program (ABP) Director</dt> <dd>Facilitate acquisition of human fetal tissue. Approve source of tissue supplied by a research sponsor. Maintain a database of human fetal tissue acquisition and disposition. Arrange for transporting the tissue for studies. Arrange for cremation and disposition of human fetal tissue remains.</dd> <dd>Draft the mandatory annual human fetal tissue research legislative report in consultation with the FTR for</dd> <dd>review by University senior officials and transmission to the Legislature.</dd> <dt>Department Head</dt> <dd>Attend training session regarding financial management of costs related to research ineligible for federal funding.</dd> <dt>Department Administrator and Accounting Personnel</dt> <dd>Attend training session regarding financial management of costs related to research ineligible for federal funding. When using an Internal Services Organization (ISO) in connection with research ineligible for federal funding, verify that the ISO was not supported with federal funds. When preparing financial transactions, include complete documentation. Notify Sponsored Projects Administration of changes to project.</dd> <dt>Fetal Tissue Research Committee (FTR)</dt> <dd>Review and act on applications for the use of human fetal tissue in transplantation research. Share FTR assessment with the Institutional Review Board.</dd> <dt>Institutional Review Board (IRB)</dt> <dd>Route applicable forms to Sponsored Projects Administration. Confirm education status of project personnel before approving IRB application. Review and act on IRB applications for human fetal tissue transplantation research.</dd> <dt>Office of the General Counsel</dt> <dd>Provide advice to University researchers and administrators on the laws, regulations and University policy requirements related to human fetal tissue transplantation research.</dd> <dt>Researcher/Principal Investigator</dt> <dd>Prepare proposal budget. Disclose intended human fetal tissue transplantation research. Obtain FTR, IRB and FDA approval. Use the APB to obtain the human fetal tissue or obtain approval from the ABP if the fetal tissue has been supplied by a research sponsor. Register research with the Research Compliance Office. Attend training session regarding financial management of costs related to research ineligible for federal funding. Notify the ABP when the remaining fetal tissue may be disposed of.</dd> <dt>Project Personnel (co-investigators, laboratory staff, student workers)</dt> <dd>Attend training session regarding financial management of costs related to research ineligible for federal funding.</dd> <dt>Research Compliance Office (RCO)</dt> <dd>Carry out oversight responsibilities related to these projects.</dd> <dt>Sponsored Projects Administration</dt> <dd>Obtain information about the proposed project. Register project with the RCO. Review project records during project period. (Assoc. Director of F&amp;A Costs). Schedule and conduct training session regarding financial management of costs related to research ineligible for federal funding.</dd> <dd>This document has been edited with the free version of the instant HTML edior. Try it <a href="https://htmleditor.tools/">here</a> and use it every time for your projects.</dd> </dl> </div> </div> <div class="clearfix text-formatted field field--name-field-policyrelatedinformation field--type-text-long field--label-above"> <div class="field__label">Related Information</div> <div class="field__item"><ul> <li>Administrative Policy:&nbsp;<a href="/research/cost"><em>Charging of Direct and Facilities and Administrative (Indirect) Costs</em></a></li> <li>Administrative Policy:&nbsp;<a href="/research/fetalresearchnontrans"><em>Acquisition, Use, and Disposition of Donated Human Fetal Tissue for Research (Non-Transplantation) or Teaching</em></a></li> <li>Administrative Policy:&nbsp;<a href="/research/embryonicstemcells"><em>Conducting Research with Human Embryos or Embryonic Stem Cells</em></a></li> <li><a href="http://www.ecfr.gov/cgi-bin/text-idx?tpl=/ecfrbrowse/Title02/2cfr200_main_02.tpl"><em>OMB Uniform Guidance</em></a></li> <li><a href="http://www.research.umn.edu/subjects/"><em>Research Subjects' Protection Programs</em></a></li> <li><a href="http://grants.nih.gov/grants/oer.htm"><em>National Institutes of Health, Office of Extramural Research</em></a></li> <li><a href="http://www.research.umn.edu/subjects/"><em>Research Subjects' Protection Programs</em></a></li> <li><a href="http://grants.nih.gov/grants/oer.htm"><em>National Institutes of Health, Office of Extramural Research</em></a></li> </ul> </div> </div> <div class="clearfix text-formatted field field--name-field-policyhistory field--type-text-long field--label-above"> <div class="field__label">History</div> <div class="field__item"><dl> <dt>Amended:</dt> <dd>May 2019 - Legal Revisions. Language is added to: <ol type="a"> <li>prohibit or regulate the transfer of human fetal tissue that was not used for transplantation;</li> <li>clarify the role of the Fetal Tissue Research Committee (FTR) when research requires review and approval by the IRB;</li> <li>include fetal tissue transplantation research activities (to the extent there are any) in the required annual report to the legislature; and</li> <li>add a responsibilities section for the FTR</li> </ol> </dd> <dt>Amended:</dt> <dd>January 2018 - Comprehensive Review, Major Revision. 1. Includes language addressing the new UMN requirements as determined by legislative changes to Minnesota § 137.47. 2. Clarifies responsibilities of UMN staff. 3. Modifies the title to standardize the language across all three documents.</dd> <dt>Amended:</dt> <dd>April 2016 - Stem Cell Research Oversight Panel (SCRO) changed to Fetal Tissue Research (FTR) committee to prevent confusion about stem cell research which is the SCRO and Fetal Tissue Research which is not about stem cells.</dd> <dt>Amended:</dt> <dd>February 2016 - Comprehensive Review, Major Revision. 1. Incorporates a new requirement to procure and dispose of human fetal tissue, through the Anatomy Bequest Program. 2. Specifies that the Institutional Review Board (IRB) will obtain input from the Stem Cell Research Oversight (SCRO) Panel when reviewing research involving the transplantation of human fetal tissue into human recipients.</dd> <dt>Amended:</dt> <dd>December 2014 - Reference to A-21 changed to OMB Uniform Guidance in Related Information.</dd> <dt>Amended:</dt> <dd>April 2014 - Comprehensive Review. Minor Revision. The policy and procedures were updated to reflect change in ownership and, align with Vice President for Research current organizational structure. The other changes were minor enhancements to the language.</dd> <dt>Effective:</dt> <dd>December 2003</dd> </dl> </div> </div> <div class="field field--name-field-date-comp-review field--type-datetime field--label-above"> <div class="field__label">Date Comp Review</div> <div class="field__items"> <div class="field__item"><time datetime="2018-01-05T12:00:00Z" class="datetime">Fri, 01/05/2018 - 12:00</time> </div> </div> </div> <div class="field field--name-field-date-comp-review-due field--type-datetime field--label-above"> <div class="field__label">Date Comp Review Due</div> <div class="field__item"><time datetime="2022-01-05T12:00:00Z" class="datetime">Wed, 01/05/2022 - 12:00</time> </div> </div> <div class="field field--name-field-senate-involvement field--type-list-string field--label-above"> <div class="field__label">Senate Involvement</div> <div class="field__items"> <div class="field__item">U Senate (info)</div> </div> </div> <div class="field field--name-field-d7-nid field--type-integer field--label-above"> <div class="field__label">D7 NID</div> <div class="field__item">9567</div> </div> <div class="field field--name-field-d7-vid field--type-integer field--label-above"> <div class="field__label">D7 VID</div> <div class="field__item">240231</div> </div> <div class="field field--name-field-date-comp-review-stamp field--type-timestamp field--label-above"> <div class="field__label">Date of Comprehensive Review - Time Stamp</div> <div class="field__item">Fri, 01/05/2018 - 00:00</div> </div> Tue, 30 Dec 2014 06:00:00 +0000 oitadmin 1791 at https://policy.umn.edu Activities Involving Potentially Hazardous Biological Agents https://policy.umn.edu/research/biosafety <span class="field field--name-title field--type-string field--label-hidden">Activities Involving Potentially Hazardous Biological Agents</span> <span class="field field--name-uid field--type-entity-reference field--label-hidden"><a title="View user profile." href="/user/1" lang="" about="/user/1" typeof="schema:Person" property="schema:name" datatype="" class="username">oitadmin</a></span> <span class="field field--name-created field--type-created field--label-hidden">Mon, 10/27/2014 - 00:00</span> <div class="field field--name-field-category field--type-entity-reference field--label-above"> <div class="field__label">Category</div> <div class="field__items"> <div class="field__item"><a href="/taxonomy/term/103" hreflang="en">Research Health &amp; Safety</a></div> </div> </div> <section class="field field--name-field-comments field--type-comment field--label-above comment-wrapper"> <h2 class="title comment-form__title">Add new comment</h2> <drupal-render-placeholder callback="comment.lazy_builders:renderForm" arguments="0=node&amp;1=1739&amp;2=field_comments&amp;3=policy_comment" token="qn2RUK3O8s1X4AnX5UXhRnVCntJaK0gHI770jmHx-II"></drupal-render-placeholder> </section> <div class="field field--name-field-owner field--type-entity-reference field--label-above"> <div class="field__label">Owner</div> <div class="field__items"> <div class="field__item"><a href="/user/378" hreflang="en">kbonneso</a></div> <div class="field__item"><a href="/user/189" hreflang="en">lawrenz</a></div> </div> </div> <div class="field field--name-field-policy-related-procedures field--type-entity-reference field--label-above"> <div class="field__label">Policy Related Procedures</div> <div class="field__items"> <div class="field__item"><a href="/research/biosafety-proc01" hreflang="en">Activities Involving Potentially Hazardous Biological Agents</a></div> <div class="field__item"><a href="/research/biosafety-proc02" hreflang="en">Additional Procedures for Using Recombinant or Synthetic Nucleic Acid Molecules</a></div> <div class="field__item"><a href="/research/biosafety-proc03" hreflang="en">Additional Procedures for Storing and Using Select Agents</a></div> <div class="field__item"><a href="/research/biosafety-proc04" hreflang="en">Procedures for Dual Use Research of Concern </a></div> </div> </div> <div class="field field--name-field-urlcategory field--type-list-string field--label-above"> <div class="field__label">urlcategory</div> <div class="field__item">Research</div> </div> <div class="field field--name-field-path-slug field--type-string field--label-above"> <div class="field__label">Path slug</div> <div class="field__item">BIOSAFETY</div> </div> <div class="field field--name-field-sme field--type-entity-reference field--label-above"> <div class="field__label">Primary Contact</div> <div class="field__items"> <div class="field__item"><a href="/user/293" hreflang="en">kupsk001</a></div> <div class="field__item"><a href="/user/302" hreflang="en">parkx479</a></div> </div> </div> <div class="field field--name-field-governing-regents-policies field--type-entity-reference field--label-above"> <div class="field__label">Governing Regents Policies</div> <div class="field__items"> <div class="field__item"><a href="/policy-regents/992" hreflang="en">Activities Involving Recombinant and Synthetic Nucleic Acid Molecules or Other Potentially Hazardous Biological Agents</a></div> </div> </div> <div class="clearfix text-formatted field field--name-field-revisiondescription field--type-text-long field--label-above"> <div class="field__label">Revision Description</div> <div class="field__item"><p>Ownership update - Cramer to Oakes.</p> </div> </div> <div class="field field--name-field-subtype field--type-list-string field--label-above"> <div class="field__label">SubType</div> <div class="field__item">Administrative Policy</div> </div> <div class="field field--name-field-daterevised field--type-datetime field--label-above"> <div class="field__label">Last Revised</div> <div class="field__item"><time datetime="2015-09-23T12:00:00Z" class="datetime">Wed, 09/23/2015 - 12:00</time> </div> </div> <div class="field field--name-field-dateeffective field--type-datetime field--label-above"> <div class="field__label">Effective Date</div> <div class="field__item"><time datetime="2004-01-01T12:00:00Z" class="datetime">Thu, 01/01/2004 - 12:00</time> </div> </div> <div class="clearfix text-formatted field field--name-field-policystatement field--type-text-long field--label-above"> <div class="field__label">Policy Statement</div> <div class="field__item"><p>All University faculty, staff and students must comply with federal and state regulations and University policies and procedures when conducting research and teaching activities with potentially hazardous biological agents or conducting life sciences dual use research of concern. This includes review and approval by the Institutional Biosafety Committee (IBC), and/or the Institutional Review Entity (IRE) and compliance with inventory, reporting, storage, transport, security, handling and disposal procedures as specified in University, state and federal regulations.</p> <p>Non-University entities renting, leasing or otherwise using University property, equipment or facilities, and that are using or storing biological material or agents identified as potential dual use agents in addition to review and approval of the IBC must notify University Health and Safety (UHS). UHS has the authority to prohibit unacceptable use and storage of materials.</p> <p>This policy as it pertains to the review and approval by the IBC, and/or the IRE includes all University of Minnesota entities involved in life sciences research or teaching activities including all hospitals owned by Fairview Health Services.</p> <p>University as well as non-University entities using University property are subject to internal and external inspection of their storage, security, and handling facilities.</p> <h3>Recombinant DNA and Other Potentially Biohazardous Agents</h3> <p>Research involving the use of recombinant or synthetic nucleic acid molecules and other potentially biohazardous agents is regulated by federal guidelines, as well as state and University requirements. All recombinant or synthetic nucleic acid molecule research must be conducted in accordance with the “NIH Guidelines for Research Involving Recombinant or Synthetic Nucleic Acid Molecules”. All research on potentially biohazardous agents must be done according to the NIH-CDC publication, “Biosafety in Microbiological and Biomedical Laboratories” (BMBL). Such research is also subject to Administrative Procedure: Activities Involving Potentially Hazardous Biological Agents, including review and approval by the IBC.</p> <p>All University faculty, staff or students must obtain Institutional Biosafety Committee (IBC) approval for their research projects or other activities, such as those taking place in teaching laboratories, involving biohazardous agents or potential products prior to initiation.</p> <p>IBC and IRE approvals for each project are valid for three years and are subject to annual continuing review and approval. Approved protocols are also subject to the University of Minnesota's post approval verification, evaluation and inspection programs. Any changes to research protocols must be approved by the IBC and/or the IRE before initiation.</p> <p>Biological material must be handled and stored according to the practices and procedures defined by the current edition of the Biosafety in Microbiological and Biomedical Laboratories (BMBL).</p> <p>All persons working with potentially hazardous biological agents must be appropriately trained for use of the agents with which they are working or to which they could be exposed.</p> <h3>Select Agents</h3> <p>Select Agents are potentially hazardous biological materials and as such are subject to University Procedure and must be approved by the IBC. Persons using, storing, or transferring Select Agents must follow additional procedures described in Administrative Procedure: <a href="/research/biosafety-proc03">Additional Procedures for Storing and Using Select Agents</a>.</p> <h3>Dual Use Research of Concern (DURC)</h3> <p>Life sciences research that can be reasonably anticipated to provide knowledge, information, products, or technologies that could be directly misapplied to pose a significant threat with broad potential consequences to public health and safety, agricultural crops and other plants, animals, the environment, material, or national security must be done according the US Government (USG) Policy for DURC Oversight and is subject to review by the Institutional Review Entity (IRE) as well as review and approval by the IBC.</p> </div> </div> <div class="clearfix text-formatted field field--name-field-policyreason field--type-text-long field--label-above"> <div class="field__label">Reason for Policy</div> <div class="field__item"><p>This administrative policy implements Board of Regents' Policy: <a href="https://regents.umn.edu/sites/regents.umn.edu/files/2019-09/policy_activities_involving_recombinant_and_synthetic_nucleic_acid_molecules_or_other_potentially_hazardous_biological_agents.pdf">Activities Involving Recombinant DNA or Other Potentially Hazardous Biological Agents</a>. In addition, the University has the responsibility to protect researchers, the University community and its assets, and the environment, by assuring the safe use and storage of potentially hazardous biological material in research or teaching at the University. The University also has the responsibility to assure compliance with all federal, state, and internal requirements to prevent the theft, diversion, or misuse of potentially hazardous biological agents.</p> </div> </div> <div class="clearfix text-formatted field field--name-field-policycontacts field--type-text-long field--label-above"> <div class="field__label">Contacts</div> <div class="field__item"><table> <caption>Policy Contacts</caption> <thead> <tr> <th scope="col">Subject</th> <th scope="col">Contact</th> <th scope="col">Phone</th> <th scope="col">Email</th> </tr> </thead> <tbody> <tr> <td>Primary Contacts</td> <td>Greg Park<br /> Betty Kupskay</td> <td>612 625 9153<br /> 612-626-5590</td> <td>parkx479@umn.edu<br /> kupsk001@umn.edu</td> </tr> </tbody> </table> </div> </div> <div class="clearfix text-formatted field field--name-field-policydefinitions field--type-text-long field--label-above"> <div class="field__label">Definitions</div> <div class="field__item"><dl> <dt>Biosafety Levels</dt> <dd>Standard and special microbiological practices, safety equipment, and facilities recommended for work with a variety of infectious agents in various laboratory settings. These levels are defined by the U.S. Department of Health and Human Services in the latest edition of Biosafety in Microbiological and Biomedical Laboratories. Biosafety Level 1 (BSL-1) has the least restrictive containment requirements, Biosafety Level 2 (BSL-2) and Biosafety Level 3 (BSL-3) have increasingly more stringent containment requirements and Biosafety Level 4 (BSL-4) requires a dedicated facility. Four Animal Biosafety Levels (ABSL 1-4) describe the practices, safety equipment, and facilities for work with infected research animals.</dd> <dt>Disposal</dt> <dd>Placing of biological agents and other items used in the manipulation of these agents in the laboratory that are no longer intended for use into the waste stream.</dd> <dt>Dual Use Research of Concern (DURC)</dt> <dd>A subset of life sciences research that, based on current understanding, can be reasonably anticipated to provide knowledge, information, products, or technologies that have the potential to pose a significant threat with broad potential consequences to public health and safety, agricultural crops and other plants, animals, the environment, materiel, or national security.</dd> <dt>Handling Biological Agents</dt> <dd>Manipulation of biological material. Can also refer to manipulation of material at a specific Biosafety Level.</dd> <dt>Institutional Animal Care and Use Committee (IACUC)</dt> <dd>The committee established by the president or delegate in accordance with federal regulations to review University activities involving the use of animals. iacuc@umn.edu</dd> <dt>Institutional Biosafety Committee (IBC)</dt> <dd>The committee established by the president or delegate in accordance with federal regulations to review University activities involving recombinant or synthetic nucleic acid molecules and potentially hazardous biological agents or. ibc@umn.edu</dd> <dt>Institutional Contact for Dual Use Research (ICDUR)</dt> <dd>The institutional point of contact for questions regarding compliance with and implementation of the requirements for the DURC oversight policies</dd> <dt>Institutional Review Board (IRB)</dt> <dd>The committee established by the president or delegate in accordance with federal regulations to review University research involving human subjects. irb@umn.edu</dd> <dt>Institutional Official</dt> <dd>The official appointed by the president or delegate who ensures compliance with ethical standards, laws, regulatory requirements, institutional policies, and mandatory reporting requirements.</dd> <dt>Institutional Review Entity (IRE)</dt> <dd>Composed of at least 5 members, including persons with knowledge of US government policies and sufficient range of expertise to assess the dual use potential of research conducted at that institution</dd> <dt>NIH Guidelines</dt> <dd>The NIH Guidelines for Research Involving Recombinant or Synthetic Nucleic Acid Molecules</dd> <dt>Non-University Entity</dt> <dd>A group or individual not a part of the University, as well as University employees using University real estate for personal use and student organizations not covered by the University's liability insurance</dd> <dt>Potentially Hazardous Biological Agent</dt> <dd>Recombinant or synthetic nucleic acid (e.g., rDNA), biologically derived toxins (including mutated, truncated, or inactivated toxins), and infectious agents (including non-virulent and vaccine strains) that require handling at Biosafety Level 2 (BSL2) or above.</dd> <dt>Principal Investigator (PI)</dt> <dd>A University employee who serves as the lead investigator for their life sciences research or who is in charge of a teaching laboratory and who is responsible for all aspects of their research projects at the University, including the actions of their staff. The DURC policy requires the PI to notify the IRE as soon as they propose any work that may fall under the DURC policy (see Dual Use Research of Concern – A Companion Guide).</dd> <dt>Recombinant or Synthetic Nucleic Acid Molecule Research</dt> <dd>This includes all research involving the joining of natural or synthetic DNA segments to other DNA molecules, as well as all synthetic or natural DNA segments that are being used for gene transfer into an in vivo system. All research must be conducted in accordance with the National Institutes of Health (NIH) Guidelines for Research Involving Recombinant or Synthetic Nucleic Acid Molecules (NIH Guidelines).</dd> <dt>Research</dt> <dd>Systematic investigation, including development, testing and evaluation designed to develop or contribute to generalizable knowledge.</dd> <dt>Research Animal Resources (RAR)</dt> <dd>The program established by the president or delegate to provide veterinary services and support for activities covered under Board of Regents Policy: <em>Animal Care and Use</em>.</dd> <dt>Research Compliance Office (RCO)</dt> <dd>RCO provides independent oversight and monitoring of research activities both internally and across the University system.</dd> <dt>Responsible Official (RO)</dt> <dd>The University of Minnesota official designated to act on behalf of the University regarding the possession, receipt or transfer of Select Agents.</dd> <dt>Security</dt> <dd>Policies, procedures, or devices intended to control access to biological materials</dd> <dt>Select Agent</dt> <dd>Refers to the HHS Select Agent and Toxin list (42CFR part 73), the Overlap Select Agent and Toxin list (42CFR Part 73 and 9CFR Part 121), the plant pathogens (7CFR Part 331) and the High Consequence Livestock Pathogens and Toxins (9CFR Part 121) as amended or revised.</dd> <dt>Storage</dt> <dd>Retention of biological materials by University employees or on University property, including materials kept in open laboratory space, incubators, refrigerators, or freezers.</dd> <dt>Teaching</dt> <dd>Activities that include classroom demonstrations, laboratory exercises and research projects that are required for completion of a course at the undergraduate, graduate, or professional level.</dd> </dl> </div> </div> <div class="field field--name-field-committee-review field--type-entity-reference field--label-above"> <div class="field__label">Committee Involvement</div> <div class="field__items"> <div class="field__item"><a href="/taxonomy/term/6" hreflang="en">SRC</a></div> <div class="field__item"><a href="/taxonomy/term/4" hreflang="en">SCC</a></div> </div> </div> <div class="field field--name-field-policy-responsible-executi field--type-entity-reference field--label-above"> <div class="field__label">Senior Leader</div> <div class="field__items"> <div class="field__item"><a href="/user/394" hreflang="en">oakes007</a></div> <div class="field__item"><a href="/user/76" hreflang="en">frans</a></div> </div> </div> <div class="field field--name-field-policy-responsible-officer field--type-entity-reference field--label-above"> <div class="field__label">Responsible Officer</div> <div class="field__items"> <div class="field__item"><a href="/user/394" hreflang="en">oakes007</a></div> <div class="field__item"><a href="/user/76" hreflang="en">frans</a></div> </div> </div> <div class="field field--name-field-ucmcontentid field--type-string field--label-above"> <div class="field__label">UCMContentID</div> <div class="field__item">BIOSAFETY</div> </div> <div class="clearfix text-formatted field field--name-field-policyresponsibilities field--type-text-long field--label-above"> <div class="field__label">Responsibilities</div> <div class="field__item"><dl> <dt>Biological Safety Officer (BSO)</dt> <dd>Oversee the inspection of research facilities. Serve as a member of the IBC. Take such actions that are necessary, including the suspension of research activities in the event of an unresolved safety hazard.</dd> <dt>University Health and Safety (UHS)</dt> <dd>Manage the Select Agent Program. Conduct inspections of laboratories where biological agents are used and/or stored. Assess risks and provide information and training to the University community on the safe handling, storage, security, or disposal of biological agents.</dd> <dt>Institutional Biosafety Committee (IBC)</dt> <dd>Review and grant approval for research proposals involving the use of biological agents. Mandate practices or procedures for the handling, storage, security and disposal of biological agents used in research or teaching. Inspect research facilities or delegate inspections and disapprove research in the event of noncompliance or an unresolved safety hazard.</dd> <dt>Institutional Contact for Dual Use Research (ICDUR)</dt> <dd>Serve as institutional point of contact for questions regarding compliance with and implementation of the requirements for the DURC oversight policies; serve as liaison between the institution and the relevant USG funding agency; and consult with the relevant USG funding agency when the institution seeks advice on matters related to DURC</dd> <dt>Institutional Official (IO)</dt> <dd>Responsible for taking steps to ensure compliance with ethical standards, laws, regulatory requirements, institutional policies, and mandatory reporting requirements. The IO appoints the RO. The IO also ensures adequate resources are available for proper functioning of the IBC and HRPP.</dd> <dt>Institutional Review Entity (IRE)</dt> <dd>Review of life sciences dual use research of concern as identified by PIs: verification that the research involves one or more of the agents listed in the United States Government Policy for Oversight of Life Sciences Dual Use Research of Concern (Sept 2014) or subsequent amendments; review of the PIs assessment and final determination of whether the research meets any of the seven experimental effects; when appropriate, make a determination of whether the research meets the definition of DURC. For research determined to be DURC, the IRE: consider the risks and benefits of conducting the research; works with the appropriate Federal funding agency to develop a risk mitigation plan; reviews the risk mitigation plan at least annually and modifies the plan, as warranted</dd> <dt>Investigators/Researchers</dt> <dd>Register any projects or activities involving potentially hazardous biological materials with the IBC. Inform the IBC of any modifications to activities or storage locations and any incidents incurred during work with same. Ensure the safe use and storage of biological agents in the laboratory. When requested, inventory biological agents in the laboratory. Ensure the proper disposition of biological agents when the project is terminated. Abide by the policies and decisions of the University and the IBC.</dd> <dt>Human Research Protection Program (HRPP)</dt> <dd>Provide administrative support for the IBC</dd> <dt>Responsible Official (RO)</dt> <dd>Ensure compliance with regulations governing the possession, receipt or transfer of Select Agents. Report to appropriate federal agencies as required. Appoint alternate ROs (AROs).</dd> <dt>Sponsored Projects Administration (SPA)</dt> <dd>Verify IBC and IRE approval before setting up new awards.</dd> <dt>Vice President for Research (VPR)</dt> <dd>Provide oversight for the regulatory committees or offices involved with this policy.</dd> </dl> </div> </div> <div class="clearfix text-formatted field field--name-field-policyrelatedinformation field--type-text-long field--label-above"> <div class="field__label">Related Information</div> <div class="field__item"><h3>Related Board of Regents Policies:</h3> <ul> <li><em><a href="https://regents.umn.edu/sites/regents.umn.edu/files/2019-09/policy_activities_involving_recombinant_and_synthetic_nucleic_acid_molecules_or_other_potentially_hazardous_biological_agents.pdf">Activities Involving Recombinant or Synthetic Nucleic Acid Molecules or Other Potentially Hazardous Biological Agents</a></em></li> <li><em><a href="https://regents.umn.edu/sites/regents.umn.edu/files/2019-09/policy_research_Involving_human_participants.pdf">Research Involving Human Participants</a></em></li> <li><em><a href="https://regents.umn.edu/sites/regents.umn.edu/files/2019-09/policy_animal_care_and_use.pdf">Animal Care and Use</a></em></li> </ul> <h3>Other</h3> <ul> <li><a href="http://osp.od.nih.gov/office-biotechnology-activities/biosafety/nih-guidelines" target="">NIH - Guidelines for Research Involving Recombinant DNA Molecules</a></li> <li>Antiterrorism and Effective Death Penalty Act of 1996</li> <li>42 CFR Part 73 - <a href="http://www.ecfr.gov/cgi-bin/text-idx?tpl=/ecfrbrowse/Title42/42cfr73_main_02.tpl">Possession, Use and Transfer of Select Agents and Toxins</a></li> <li>7 CFR Part 331 - <a href="http://www.ecfr.gov/cgi-bin/text-idx?tpl=/ecfrbrowse/Title07/7cfr331_main_02.tpl">Possession, Use and Transfer of Biological Agents and Toxins (plant pathogens)</a></li> <li>9 CFR Part 121 - <a href="http://www.ecfr.gov/cgi-bin/text-idx?tpl=/ecfrbrowse/Title09/9cfr121_main_02.tpl">Possession, Use and Transfer of Biological Agents and Toxins (animal agents)</a></li> <li><a href="http://frwebgate.access.gpo.gov/cgi-bin/getdoc.cgi?dbname=107_cong_public_laws&amp;docid=f:publ056.107">Uniting and Strengthening America Act by Providing Appropriate Tools Required to Intercept and Obstruct Terrorism (USA Patriot Act) of 2001</a></li> <li><a href="http://frwebgate.access.gpo.gov/cgi-bin/getdoc.cgi?dbname=107_cong_public_laws&amp;docid=f:publ188.107">Public Health Security and Bioterrorism Preparedness and Response Act of 2002</a></li> <li><a href="http://www.cdc.gov/biosafety/publications/bmbl5/index.htm">Biosafety in Microbiological and Biomedical Laboratories (CDC/NIH)</a></li> <li><a href="http://www.phe.gov/s3/dualuse/Documents/durc-companion-guide.pdf">Dual Use Research of Concern A Companion Guide</a></li> <li><a href="http://www.research.umn.edu/ibc">Institutional Biosafety Committee</a></li> <li><a href="http://www.uhs.umn.edu/">University Health and Safety</a></li> </ul> </div> </div> <div class="clearfix text-formatted field field--name-field-policyhistory field--type-text-long field--label-above"> <div class="field__label">History</div> <div class="field__item"><dl> <dt>Amended:</dt> <dd>September 2015 – Comprehensive Review, Minor Revision. Added information on Dual Use Research of Concern. Removed outdated language, updated UMN departments, added contacts, and revised definitions. Responsibilities and Procedures updated.</dd> <dt>Amended:</dt> <dd>June 2012 - Comprehensive Review, Minor Revision. Removed outdated language, updated UMN departments, added contacts, and revised definitions. All minor updates with no substantive change to policy statement. Title of this policy should be changed to read "Potentially" rather than "Potential" in order to align with other Board of Regents policies and NIH Guidelines. Responsibilities and Procedures updated.</dd> <dt>Effective:</dt> <dd>January 2004</dd> </dl> </div> </div> <div class="field field--name-field-date-comp-review field--type-datetime field--label-above"> <div class="field__label">Date Comp Review</div> <div class="field__items"> <div class="field__item"><time datetime="2015-09-23T12:00:00Z" class="datetime">Wed, 09/23/2015 - 12:00</time> </div> </div> </div> <div class="field field--name-field-date-comp-review-due field--type-datetime field--label-above"> <div class="field__label">Date Comp Review Due</div> <div class="field__item"><time datetime="2019-09-23T12:00:00Z" class="datetime">Mon, 09/23/2019 - 12:00</time> </div> </div> <div class="field field--name-field-senate-involvement field--type-list-string field--label-above"> <div class="field__label">Senate Involvement</div> <div class="field__items"> <div class="field__item">U Senate (info)</div> </div> </div> <div class="field field--name-field-d7-nid field--type-integer field--label-above"> <div class="field__label">D7 NID</div> <div class="field__item">9515</div> </div> <div class="field field--name-field-d7-vid field--type-integer field--label-above"> <div class="field__label">D7 VID</div> <div class="field__item">269981</div> </div> <div class="field field--name-field-date-comp-review-stamp field--type-timestamp field--label-above"> <div class="field__label">Date of Comprehensive Review - Time Stamp</div> <div class="field__item">Wed, 09/23/2015 - 00:00</div> </div> Mon, 27 Oct 2014 05:00:00 +0000 oitadmin 1739 at https://policy.umn.edu Adding, Changing, or Discontinuing Academic Plans https://policy.umn.edu/education/academicprogram <span class="field field--name-title field--type-string field--label-hidden">Adding, Changing, or Discontinuing Academic Plans</span> <span class="field field--name-uid field--type-entity-reference field--label-hidden"><a title="View user profile." href="/user/1" lang="" about="/user/1" typeof="schema:Person" property="schema:name" datatype="" class="username">oitadmin</a></span> <span class="field field--name-created field--type-created field--label-hidden">Wed, 10/02/2013 - 00:00</span> <div class="field field--name-field-category field--type-entity-reference field--label-above"> <div class="field__label">Category</div> <div class="field__items"> <div class="field__item"><a href="/taxonomy/term/64" hreflang="en">Colleges, Departments, and Programs</a></div> </div> </div> <section class="field field--name-field-comments field--type-comment field--label-above comment-wrapper"> <h2 class="title comment-form__title">Add new comment</h2> <drupal-render-placeholder callback="comment.lazy_builders:renderForm" arguments="0=node&amp;1=1719&amp;2=field_comments&amp;3=policy_comment" token="fpQjNJdMwMwKmMVesBoc4UfI1Jzbk4eIncvsL2zm168"></drupal-render-placeholder> </section> <div class="field field--name-field-owner field--type-entity-reference field--label-above"> <div class="field__label">Owner</div> <div class="field__items"> <div class="field__item"><a href="/user/74" hreflang="en">provost</a></div> </div> </div> <div class="field field--name-field-policy-related-procedures field--type-entity-reference field--label-above"> <div class="field__label">Policy Related Procedures</div> <div class="field__items"> <div class="field__item"><a href="/education/academicprogram-proc02" hreflang="en">Adding New Post-Baccalaureate Academic Plans</a></div> <div class="field__item"><a href="/education/academicprogram-proc03" hreflang="en">Changing Existing Post-Baccalaureate Academic Plans</a></div> </div> </div> <div class="field field--name-field-urlcategory field--type-list-string field--label-above"> <div class="field__label">urlcategory</div> <div class="field__item">Education</div> </div> <div class="field field--name-field-path-slug field--type-string field--label-above"> <div class="field__label">Path slug</div> <div class="field__item">ACADEMICPROGRAM</div> </div> <div class="field field--name-field-policy-related-appendices field--type-entity-reference field--label-above"> <div class="field__label">Policy Related Appendices</div> <div class="field__items"> <div class="field__item"><a href="/education/academicprogram-appc" hreflang="en">Best Practices in Coursework (Plan C) Master&#039;s Degrees</a></div> </div> </div> <div class="field field--name-field-policy-related-faqs field--type-entity-reference field--label-above"> <div class="field__label">Policy Related FAQs</div> <div class="field__items"> <div class="field__item"><a href="/education/academicprogram-faq01" hreflang="en">Adding, Changing or Discontinuing Academic Plans</a></div> </div> </div> <div class="field field--name-field-sme field--type-entity-reference field--label-above"> <div class="field__label">Primary Contact</div> <div class="field__items"> <div class="field__item"><a href="/user/417" hreflang="en">slat0084</a></div> </div> </div> <div class="clearfix text-formatted field field--name-field-revisiondescription field--type-text-long field--label-above"> <div class="field__label">Revision Description</div> <div class="field__item">"Changing Requirements" paragraph 1: "...for imposing the requirement on them." I believe "for" was intended to be "before". Primary contact update.</div> </div> <div class="field field--name-field-subtype field--type-list-string field--label-above"> <div class="field__label">SubType</div> <div class="field__item">Administrative Policy</div> </div> <div class="clearfix text-formatted field field--name-field-procedures field--type-text-long field--label-above"> <div class="field__label">Procedures</div> <div class="field__item"><p>All proposals for adding, changing, or discontinuing baccalaureate-level academic plans and sub-plans must be submitted through the Program and Curriculum Approval System (PCAS). For specific procedures see: <a href="http://onestop.umn.edu/staff/pcas/index.html" target="">Program and Curriculum Approval System</a>.</p> <p>Submitting proposals to add, change, or discontinue graduate and professional education plans and sub-plans should refer to the procedures listed directly above.</p></div> </div> <div class="clearfix text-formatted field field--name-field-forms field--type-text-long field--label-above"> <div class="field__label">Forms</div> <div class="field__item"><ul> <li><a href="https://onestop2.umn.edu/pcas/">Program and Curriculum Approval System (PCAS)</a></li> </ul></div> </div> <div class="field field--name-field-daterevised field--type-datetime field--label-above"> <div class="field__label">Last Revised</div> <div class="field__item"><time datetime="2011-09-16T12:00:00Z" class="datetime">Fri, 09/16/2011 - 12:00</time> </div> </div> <div class="field field--name-field-dateeffective field--type-datetime field--label-above"> <div class="field__label">Effective Date</div> <div class="field__item"><time datetime="2002-07-01T12:00:00Z" class="datetime">Mon, 07/01/2002 - 12:00</time> </div> </div> <div class="clearfix text-formatted field field--name-field-policystatement field--type-text-long field--label-above"> <div class="field__label">Policy Statement</div> <div class="field__item"><p>Departments, colleges, and campuses have the authority to establish, change, and discontinue academic plans and sub-plans that may appear on official University transcripts, subject to appropriate consultation with other units and subject to the final authority of the Board of Regents. (See Administrative Policy: <a href="/education/curriculumauthority" target=""><em>Academic Unit Authority over the Curriculum and Major: Twin Cities, Crookston, Morris, Rochester</em></a>.) This policy includes undergraduate, graduate, and professional credit-bearing degrees, majors, minors, free-standing minors, and certificates.</p> <h3>Creating, Changing or Discontinuing a Plan or Sub-Plan</h3> <p>Collegiate units and system campuses proposing to add, change, or discontinue an academic plan or sub-plan must submit a proposal for review and approval. (See Responsibilities section below and associated procedures.) Collegiate units and system campuses must have a set of publicly available standards and internal processes for developing, reviewing, and approving new, changed, or discontinued plans and sub-plans that are consistent with these procedures.</p> <p>The Executive Vice President and Provost is responsible for reviewing and approving, as appropriate, academic proposals for Board of Regents consideration and final action.</p> <p>Every academic plan must have a home college(s) or system campus.</p> <p>Collegiate units and campuses may not advertise or initiate new and/or changed plans or recruit or admit students to them prior to formal approval by the Board of Regents.</p> <h3>Changing Requirements of an Existing Plan or Sub-Plan</h3> <p>Any approved change in plan (e.g., major) or sub-plan (e.g., track, emphasis, concentration) requirements takes effect no earlier than the following term and will not normally be imposed on currently enrolled students who have been admitted to the plan or sub-plan, but the new requirements may be offered to them as an option. If the faculty of a collegiate unit or system campus concludes that a new requirement is essential even for currently enrolled students, approval of the dean of the collegiate unit or the chief academic officer of the system campus must be obtained before imposing the requirement on them.</p> <p>Collegiate units and system campuses must communicate to prospective and current students their local policies and decisions regarding new or revised plan or sub-plan requirements.</p> <p>The <span>Executive</span>&nbsp;Vice President and Provost is responsible for reviewing and approving academic proposals for changing plan and sub-plan requirements.</p></div> </div> <div class="clearfix text-formatted field field--name-field-policyreason field--type-text-long field--label-above"> <div class="field__label">Reason for Policy</div> <div class="field__item"><p>This policy:</p> <ul> <li>Enhances quality, productivity, and efficiency in academic plan development and implementation by faculty, departments, collegiate units, and campuses.</li> <li>Ensures that academic plan development is aligned with unit compact statements and institutional, campus, and collegiate unit mission and strategic directions.</li> <li>Makes explicit commonly held assumptions about criteria for academic plans and connections to related policies.</li> <li>Fosters shared consultation, and where appropriate, planning across academic units.</li> <li>Enhances availability, consistency, and coordination of information about the University’s academic plans for transcript records, internal analysis, accountability reporting, and accreditation.</li> <li>Ensures thorough and timely review of proposals.</li> </ul></div> </div> <div class="clearfix text-formatted field field--name-field-policycontacts field--type-text-long field--label-above"> <div class="field__label">Contacts</div> <div class="field__item"><div class="tablewrapper"> <table> <thead> <tr><th scope="col">Subject</th><th scope="col">Contact</th><th scope="col">Phone</th><th scope="col">Email</th></tr> </thead> <tbody> <tr><th scope="row">Primary Contact(s)</th> <td><a href="http://www.umn.edu/lookup?UID=slat0084">Erin Slattengren</a></td> <td>612-301-1707</td> <td>slat0084@umn.edu</td> </tr> <tr><th scope="row">Policy Questions</th> <td>Emily Ronning</td> <td>612-626-8031</td> <td>ronn0044@umn.edu</td> </tr> <tr><th scope="row">Policy/Process Advice</th> <td>Office of <span>Executive</span>&nbsp;Vice President and Provost</td> <td>612-626-6544</td> <td>612-624-3814</td> </tr> <tr><th scope="row">Forms</th> <td>Program and Curriculum Approval System</td> <td>612-625-2808</td> <td>enthelp@umn.edu</td> </tr> </tbody> </table> </div></div> </div> <div class="clearfix text-formatted field field--name-field-policydefinitions field--type-text-long field--label-above"> <div class="field__label">Definitions</div> <div class="field__item"><dl><dt>Academic Major</dt><dd>A student's main field of specialization during the student's undergraduate or graduate studies. The major is recorded on the student's transcript.</dd><dt>Academic Minor</dt><dd>A student's declared secondary field of study or specialization during the student's undergraduate or graduate studies. A minor typically consists of a set of courses that meet specified guidelines and is designed to allow a sub-major concentration in an academic discipline or in a specific area in or across disciplines. The minor is recorded on the student's transcript.</dd><dt>Academic Plan</dt><dd>Undergraduate, graduate, and professional credit-bearing degrees, majors, minors, free-standing minors, and certificates that may appear on official University transcripts.</dd><dt>Academic Program</dt><dd>Undergraduate, graduate, and professional credit-bearing degrees, majors, minors, free-standing minors, and certificates that may appear on official University transcripts.</dd><dt>Certificate</dt><dd>A particular set of courses or coursework that typically addresses new knowledge or practice areas emerging from technological, social, or economic changes to which particular professions or occupations must adjust.</dd><dt>Curriculum</dt><dd>The set of courses offered by a unit.</dd><dt>Dual degree/joint degree</dt><dd>Simultaneous academic study that incorporates and integrates learning in two disciplines.</dd><dt>Electronic Course Authorization System (ECAS)</dt><dd>Provides an electronic method to propose new courses and make changes to or de-activate existing courses.</dd><dt>Free-standing minor</dt><dd>An interdisciplinary minor, not attached to a major, available to students from other academic plans.</dd><dt>Home college(s)</dt><dd>The college(s) responsible for administering the academic plan.</dd><dt>Interdisciplinary academic plan</dt><dd>A coherent integration of two or more distinct disciplines into an academic major or free-standing minor.</dd><dt>Program and Curriculum Approval System (PCAS)</dt><dd>A comprehensive database of all the requirements needed to complete each academic plan and sub-plan offered on University campuses. PCAS is a web-based approval system that automatically routes all new plans, and any changes to existing plans, to the correct approvers and approval levels. PCAS also is a resource for the Graduation Planner, the University's program that supports undergraduate students' timely progress toward graduation. All University catalogs use data from PCAS.</dd><dt>Requirements for the major and minor</dt><dd>The set of courses that constitute the program of study in a focused area for a particular degree program. These courses make up a portion of the University of Minnesota degree.</dd><dt>Sub-plan</dt><dd>A formally designated, distinct content area within a single, broader discipline (e.g., track, concentration, area) that appears on the official University transcript.</dd></dl></div> </div> <div class="field field--name-field-committee-review field--type-entity-reference field--label-above"> <div class="field__label">Committee Involvement</div> <div class="field__items"> <div class="field__item"><a href="/taxonomy/term/5" hreflang="en">SCEP</a></div> <div class="field__item"><a href="/taxonomy/term/4" hreflang="en">SCC</a></div> <div class="field__item"><a href="/taxonomy/term/12" hreflang="en">PACC</a></div> </div> </div> <div class="field field--name-field-policy-responsible-executi field--type-entity-reference field--label-above"> <div class="field__label">Senior Leader</div> <div class="field__items"> <div class="field__item"><a href="/user/74" hreflang="en">provost</a></div> </div> </div> <div class="field field--name-field-policy-responsible-officer field--type-entity-reference field--label-above"> <div class="field__label">Responsible Officer</div> <div class="field__items"> <div class="field__item"><a href="/user/74" hreflang="en">provost</a></div> </div> </div> <div class="field field--name-field-ucmcontentid field--type-string field--label-above"> <div class="field__label">UCMContentID</div> <div class="field__item">ACADEMICPROGRAM</div> </div> <div class="clearfix text-formatted field field--name-field-policyresponsibilities field--type-text-long field--label-above"> <div class="field__label">Responsibilities</div> <div class="field__item"><dl><dt>Collegiate unit/department</dt><dd>Review current academic offerings and propose new, changed, or discontinued offerings across all degree types. Submit request to collegiate dean and/or system campus chief academic officer.</dd><dt>Collegiate dean/system campus chief academic officer</dt><dd>Review proposal and make recommendation to EVPP. Take final action on plan changes that do not require EVPP or BOR approval. Transmit changes to ASR, as appropriate.</dd><dt>Graduate Education Council</dt><dd>Review Ph.D. plan proposal and make recommendation to EVPP.</dd><dt>AHC Academic Council</dt><dd>Review health sciences related plan proposal and make recommendations to EVPP.</dd><dt>EVPP (<span>Executive</span> Vice President and Provost)</dt><dd>Receive proposal and confirm all required information is complete. Review and approve new, changed, or discontinued academic plan proposal. Transmit proposal with recommendation to BOR for final action. Take final action on plan changes that do not require BOR approval. Transmit final BOR approved information to ASR.</dd><dt>BOR (Board of Regents)</dt><dd>Review and take final action on (final approval or denial) new, changed, or discontinued academic plan proposals.</dd><dt>ASR (Academic Support Resources)</dt><dd>Make approved plan and sub-plan changes to the enterprise student system.</dd></dl></div> </div> <div class="clearfix text-formatted field field--name-field-policyrelatedinformation field--type-text-long field--label-above"> <div class="field__label">Related Information</div> <div class="field__item"><ul> <li>Board of Regents Policy: <em><a href="https://regents.umn.edu/sites/regents.umn.edu/files/2019-09/policy_responsibilities_of_the_board_and_individual_regents.pdf">Responsibilities of the Board and Individual Regents</a></em></li> <li><a href="/Education" target="">Teaching and Education Policies</a></li> <li><strong>Academic Unit or Campus</strong> <br>Curriculum review and faculty governance policies</li> <li><a href="http://www.ncahlc.org/">Higher Learning Commission</a> (University's regional accrediting agency) <ul> <li><a href="https://content.springcm.com/content/DownloadDocuments.ashx?Selection=Document%2C10611003%3B&amp;accountId=5968">Handbook of Accreditation</a></li> <li><a href="https://content.springcm.com/content/DownloadDocuments.ashx?Selection=Document%2C17974153%3B&amp;accountId=5968">Principles of Good Practice in Overseas International Education Programs for Non-U.S. Nationals</a></li> <li><a href="https://content.springcm.com/content/DownloadDocuments.ashx?Selection=Document%2C10708011%3B&amp;accountId=5968">Best Practices for Electronically Offered Degree and Certificate Programs</a></li> </ul> </li> <li><strong>University of Minnesota Degree and Certificate Plans</strong> <ul> <li><a href="http://www1.umn.edu/twincities/academics.php">Twin Cities</a></li> <li><a href="http://www.umcrookston.edu/academics/">Crookston</a></li> <li><a href="http://www.d.umn.edu/academics/">Duluth</a></li> <li><a href="http://www.morris.umn.edu/academic/">Morris</a></li> <li><a href="http://www.r.umn.edu/05_programs.htm">Rochester</a></li> </ul> </li> </ul></div> </div> <div class="clearfix text-formatted field field--name-field-policyhistory field--type-text-long field--label-above"> <div class="field__label">History</div> <div class="field__item"><dl><dt>Amended:</dt><dd>September 2011: Comprehensive Review, Policy completely rewritten. Aligns policy language with current practice. Shifts the review and initial approval of new and changed non-doctoral post-baccalaureate academic plans to collegiate units, including the Duluth and Rochester campuses, from the previous centralized Graduate School model. Title changed from Review of Proposals for New and Changed Academic Programs to Adding, Changing, or Discontinuing Academic Plans.</dd><dt>Amended:</dt><dd>January 2003 - Updated phone number in contacts section and procedure.</dd><dt>Effective:</dt><dd>July 2002</dd><dt>Supercedes:</dt><dd>January 1994 <em>Policy on Approval of Academic Programs</em>, and all working versions circulated since then.</dd></dl></div> </div> <div class="field field--name-field-date-comp-review field--type-datetime field--label-above"> <div class="field__label">Date Comp Review</div> <div class="field__items"> <div class="field__item"><time datetime="2011-09-19T12:00:00Z" class="datetime">Mon, 09/19/2011 - 12:00</time> </div> </div> </div> <div class="field field--name-field-date-comp-review-due field--type-datetime field--label-above"> <div class="field__label">Date Comp Review Due</div> <div class="field__item"><time datetime="2015-09-19T12:00:00Z" class="datetime">Sat, 09/19/2015 - 12:00</time> </div> </div> <div class="field field--name-field-senate-involvement field--type-list-string field--label-above"> <div class="field__label">Senate Involvement</div> <div class="field__items"> <div class="field__item">F Senate (action)</div> </div> </div> <div class="field field--name-field-d7-nid field--type-integer field--label-above"> <div class="field__label">D7 NID</div> <div class="field__item">9495</div> </div> <div class="field field--name-field-d7-vid field--type-integer field--label-above"> <div class="field__label">D7 VID</div> <div class="field__item">236636</div> </div> <div class="field field--name-field-date-comp-review-stamp field--type-timestamp field--label-above"> <div class="field__label">Date of Comprehensive Review - Time Stamp</div> <div class="field__item">Mon, 09/19/2011 - 00:00</div> </div> Wed, 02 Oct 2013 05:00:00 +0000 oitadmin 1719 at https://policy.umn.edu Animals on Campus https://policy.umn.edu/operations/animals <span class="field field--name-title field--type-string field--label-hidden">Animals on Campus</span> <span class="field field--name-uid field--type-entity-reference field--label-hidden"><a title="View user profile." href="/user/2" lang="" about="/user/2" typeof="schema:Person" property="schema:name" datatype="" class="username">young041</a></span> <span class="field field--name-created field--type-created field--label-hidden">Mon, 06/10/2019 - 08:49</span> <div class="field field--name-field-category field--type-entity-reference field--label-above"> <div class="field__label">Category</div> <div class="field__items"> <div class="field__item"><a href="/taxonomy/term/94" hreflang="en">Health and Safety</a></div> </div> </div> <section class="field field--name-field-comments field--type-comment field--label-above comment-wrapper"> <h2 class="title comment-form__title">Add new comment</h2> <drupal-render-placeholder callback="comment.lazy_builders:renderForm" arguments="0=node&amp;1=1938&amp;2=field_comments&amp;3=policy_comment" token="poOufG29WhOlYd-iP5Y1lLew3czTCnojbTQhXiFFF-I"></drupal-render-placeholder> </section> <div class="field field--name-field-owner field--type-entity-reference field--label-above"> <div class="field__label">Owner</div> <div class="field__items"> <div class="field__item"><a href="/user/378" hreflang="en">kbonneso</a></div> </div> </div> <div class="field field--name-field-urlcategory field--type-list-string field--label-above"> <div class="field__label">urlcategory</div> <div class="field__item">Operations</div> </div> <div class="field field--name-field-path-slug field--type-string field--label-above"> <div class="field__label">Path slug</div> <div class="field__item">animals</div> </div> <div class="field field--name-field-sme field--type-entity-reference field--label-above"> <div class="field__label">Primary Contact</div> <div class="field__items"> <div class="field__item"><a href="/user/481" hreflang="en">kgreen15</a></div> </div> </div> <div class="clearfix text-formatted field field--name-field-revisiondescription field--type-text-long field--label-above"> <div class="field__label">Revision Description</div> <div class="field__item"><p>Updated Crookston DRC email address per Kirby Newhouse with&nbsp;Kate Greenberg's approval.</p> </div> </div> <div class="field field--name-field-subtype field--type-list-string field--label-above"> <div class="field__label">SubType</div> <div class="field__item">Administrative Policy</div> </div> <div class="clearfix text-formatted field field--name-field-faq field--type-text-long field--label-above"> <div class="field__label">FAQ</div> <div class="field__item"><ol> <li><strong>I have safety concerns about the environment where my Service Animal may accompany me. Who should I contact?</strong> <p>For safety questions, contact the campus disability services office to explore what is reasonable.&nbsp; Potential safety considerations could include the following:</p> <ul> <li><em>Research and Teaching Laboratories.</em> Chemicals found in many labs could be harmful to animals. Organisms naturally found on most dogs or other animals could negatively impact the outcome of certain research.</li> <li><em>Mechanical Rooms/Custodial Closets.</em> Such locations can have chemicals or machinery that could potentially harm animals.</li> <li><em>Surgical and Clinical Suites.</em> These spaces may have heightened requirements for patient safety concerns and infection control standards.</li> <li><em>Other Potentially Dangerous Areas.</em> Any room, studio, or classroom with sharp metal cuttings or glass shards on the floor; hot material such as molten metal; excessive dust; or moving machinery may pose a danger to animals.</li> </ul> </li> <li><strong>I have questions about my individual circumstance. Who should I speak with first?</strong> <p>Your campus disability services office should be your first point of contact for any questions related to service or support animals.&nbsp; Each campus has a primary contact listed at the end of this policy.</p> </li> </ol> </div> </div> <div class="field field--name-field-daterevised field--type-datetime field--label-above"> <div class="field__label">Last Revised</div> <div class="field__item"><time datetime="2020-01-02T12:00:00Z" class="datetime">Thu, 01/02/2020 - 12:00</time> </div> </div> <div class="field field--name-field-dateeffective field--type-datetime field--label-above"> <div class="field__label">Effective Date</div> <div class="field__item"><time datetime="2020-01-02T12:00:00Z" class="datetime">Thu, 01/02/2020 - 12:00</time> </div> </div> <div class="clearfix text-formatted field field--name-field-policystatement field--type-text-long field--label-above"> <div class="field__label">Policy Statement</div> <div class="field__item"><p>This policy regulates privately-owned animals, including pets, in university buildings and on university owned and controlled property.&nbsp; It governs animals not otherwise subject to the Institutional Animal Care and Use Committee (IACUC).</p> <h3>Animals Permitted on University Grounds</h3> <p>Animals are permitted on university grounds, unless an area is specifically signed as prohibited. &nbsp;No individual may tether an animal to any fence, tree, shrub, post, or other object located upon university property not designed for the purpose of securing animals.&nbsp; The prompt collection and disposal of animal waste is required.</p> <h3>Animals Permitted in University Buildings/Facilities</h3> <p>Individuals are prohibited from bringing any animal not listed below into any university building or on any university public transportation, at any time.&nbsp; If found, the animal and its handler will be asked to leave the building or public transportation immediately.</p> <p>The following animals are permitted in university buildings/facilities under this policy, with specific limitations.&nbsp; Privately owned animals may also be subject to IACUC display protocols.</p> <ul> <li>service animals</li> <li>service animals in training (with proper documentation)</li> <li>support animals (with prior approval from the campus disability services office)</li> <li>therapy animals, on days when engaged in university-sponsored therapeutic programming (with certification from PAWS program)</li> <li>animals brought for treatment to the veterinary medical facilities</li> <li>animals housed and treated in animal hospitals or shelters designed and constructed to house animals</li> <li>animals used in the delivery of instruction, during the period of instruction and in the period reasonably necessary to prepare for and conclude the instructional period</li> <li>animals brought to animal-related university-sponsored events, during the duration of the event</li> <li>animals housed in live-in professional staff apartments (when permitted by campus housing), family student housing (when permitted by campus housing), university-sanctioned pet programs in a residence hall, or Eastcliff event center and residence (Twin Cities campus)</li> <li>animals used in university-sponsored research</li> <li>animals used to carry out functional responsibilities of a university department</li> <li>animals used in support of law enforcement or disaster recovery activities</li> <li>livestock in designated animal holding facilities</li> <li>animals recognized as official NCAA mascots or participating in ceremonies in athletic venues</li> </ul> <h3>Responsibility for Animal Conduct</h3> <p>Any individual who brings an animal on university property is responsible for the behavior and actions of the animal, health and safety of individuals in proximity of or impacted by the animal, and the health and cleanliness of the campus environment.&nbsp; Animals on university property must have all current vaccinations and be licensed as required by the municipality where the animal is primarily housed.</p> <p>Any individual, owning or having under their control any animal, may only bring such animal upon university property with a leash or lead suitably attached to the animal and held by the individual responsible.&nbsp; When a leash is not an appropriate means of control, an animal must be secured in a cage.&nbsp; An exception is made for any Service Animal who cannot do their work when leashed or tethered.</p> <p>The university will seek restitution for any animal-related damage to university-controlled property, facilities, or grounds. The cleanup, repair, or replacement cost of damaged property is the sole responsibility of the owner of the animal that caused the damage.&nbsp; This applies to all animals, and is not limited to pets, service animals, and support animals.</p> <p>If any animal is or appears to be unaccompanied or a stray, or if the owner cannot be found or determined upon investigation by the campus/city police or safety officers, the animal will be impounded.</p> <h3>Service and Support Animals</h3> <h3>Service Animals</h3> <p>A Service Animal may accompany its owner on university grounds and in university buildings at all times, except under rare circumstances where the animal’s health or safety may be compromised.&nbsp; Service Animals are not required to wear any special type of harness or garment, and must be under the handler’s control at all times. &nbsp;In situations where it is not obvious that the animal is a Service Animal, university officials may ask the following two qualifying questions:</p> <ol> <li>Is the Service Animal required because of a person’s disability?</li> <li>What work or task has the Service Animal been trained to perform?</li> </ol> <p>It is a misdemeanor under Minnesota Statute 609.833 to misrepresent an unqualified animal as a Service Animal.</p> <h3>Support Animals</h3> <p>Support Animals are permitted in university housing (or on university grounds in accordance with the provisions of this policy) and limited to the room of the student who has been granted an accommodation.&nbsp; In order to live with a Support Animal in university housing, a resident must obtain prior authorization from the campus disability services office and the campus housing office. Each campus housing office may develop specific procedures and guidelines for Support Animals.&nbsp;</p> <p>Residents who are negatively affected by the presence of a Support Animal should contact their campus housing office. Campus housing and the campus disability services office will follow up with the residents involved in order to determine whether there is a need for further accommodations or other changes. The university is committed to ensuring that the needs of all residents are met and will determine how to resolve any conflicts or problems as expeditiously as possible.</p> <p>Support Animals approved in university housing are not generally permitted in other indoor public areas, private offices, classrooms, labs, etc. In all instances where a University community member or guest seeks to bring a Support Animal to campus, the individual must engage in an interactive process with the campus disability services office and any others affected by the request to determine the reasonability of the accommodation prior to bringing the animal to campus.</p> <h3>Exceptions</h3> <p>The College of Veterinary Medicine on the Twin Cities campus has exception to administer an “animals in the workplace” policy in university-owned buildings assigned to the College of Veterinary Medicine.&nbsp; Animals approved under this collegiate policy are not permitted in buildings or spaces that are not assigned to the College of Veterinary Medicine.</p> <p>Where aligned with their clinical practice, the M Health Clinics and Surgery Center on the Twin Cities campus may operate with different guidelines for Service and Support Animals.</p> </div> </div> <div class="clearfix text-formatted field field--name-field-policyreason field--type-text-long field--label-above"> <div class="field__label">Reason for Policy</div> <div class="field__item"><p>Service and Support Animals serve an important role for individuals with apparent and non-apparent disabilities. It is important that individuals who rely on these animals, as well as the greater University community, understand their rights and responsibilities under the law.</p> <p>The presence of animals on university property and in university buildings can have an adverse effect on the normal functions of the university by creating unsanitary conditions or health concerns (allergy, waste, bites, etc.), disrupting daily operations (excessive noise, unattended animals, individual conflict), or causing damage to grounds, buildings, and property.</p> </div> </div> <div class="clearfix text-formatted field field--name-field-policycontacts field--type-text-long field--label-above"> <div class="field__label">Contacts</div> <div class="field__item"><div class="tablewrapper"> <table> <tbody> <tr> <th scope="col">Subject</th> <th scope="col">Contact</th> <th scope="col">Phone</th> <th scope="col">Fax/Email</th> </tr> <tr> <th scope="row">Primary Contact</th> <td>Kate Greenberg</td> <td>612-626-2707</td> <td>kgreen15@umn.edu</td> </tr> <tr> <th scope="row">Crookston: Disability Resource Center</th> <td>Kirby Newhouse</td> <td>218-281-8587</td> <td>umcdrc@crk.umn.edu</td> </tr> <tr> <th scope="row">Crookston: Residential Life</th> <td>Erica Claybrook-Cookman</td> <td>218-281-8530</td> <td>ecookman@crk.umn.edu</td> </tr> <tr> <th scope="row">Crookston: City of Crookston Police</th> <td>Non-Emergency Line</td> <td>218-281-3111</td> <td>n/a</td> </tr> <tr> <th scope="row">Duluth: Disability Resources</th> <td>Emily Norenberg</td> <td>218-726-6101</td> <td>enorenbe@d.umn.edu</td> </tr> <tr> <th scope="row">Duluth: Housing and Residence Life</th> <td>Melissa Carlson</td> <td>218-726-6123</td> <td>umdhouse@d.umn.edu</td> </tr> <tr> <th scope="row">Duluth: University Police</th> <td>Non-Emergency Line</td> <td>218-726-7000</td> <td>umdpd@d.umn.edu</td> </tr> <tr> <th scope="row">Morris: Disability Resource Center</th> <td>Matthew Hoekstra</td> <td>320-589-6163</td> <td>hoekstra@morris.umn.edu</td> </tr> <tr> <th scope="row">Morris: Residential Life</th> <td>T.J. Ross</td> <td>320-589-6475</td> <td>tjross@morris.umn.edu</td> </tr> <tr> <th scope="row">Morris: University Police</th> <td>Non-Emergency Line</td> <td>320-287-1601</td> <td>ummpd@morris.umn.edu</td> </tr> <tr> <th scope="row">Rochester: Disability Resources</th> <td>Jeff Baier</td> <td>507-258-8021</td> <td>disability@r.umn.edu</td> </tr> <tr> <th scope="row">Rochester: Residential Life</th> <td>Will Harmon</td> <td>507-258-8028</td> <td>wharmon@r.umn.edu</td> </tr> <tr> <th scope="row">Rochester: City of Rochester Police</th> <td>Non-Emergency Line</td> <td>507-328-6800</td> <td>n/a</td> </tr> <tr> <th scope="row">Twin Cities: Disability Resource Center</th> <td>Roberta Kehne</td> <td>612-624-1801</td> <td>rlkehne@umn.edu</td> </tr> <tr> <th scope="row">Twin Cities: Housing and Residential Life</th> <td>Mannix Clark</td> <td>612-624-8488</td> <td>clark108@umn.edu</td> </tr> <tr> <th scope="row">Twin Cities: University Police</th> <td>Non-Emergency Line</td> <td>612-624-2677</td> <td>police@umn.edu</td> </tr> </tbody> </table> </div> </div> </div> <div class="clearfix text-formatted field field--name-field-policydefinitions field--type-text-long field--label-above"> <div class="field__label">Definitions</div> <div class="field__item"><dl> <dt>Pet</dt> <dd>A privately owned animal, vertebrate or invertebrate, kept for ordinary use and/or companionship, and not classified as a Service Animal or a Support Animal.</dd> <dt>Service Animal</dt> <dd>An animal (dog or miniature horse) that is individually trained to do work or perform tasks for the benefit of an individual with a disability. These tasks may include but are not limited to: guiding individuals with impaired vision, alerting individuals who are hearing impaired to intruders or sound, pulling a wheelchair, carrying and/or retrieving dropped items, etc. Other species of animals, whether wild or domestic, trained or untrained, are not Service Animals.</dd> <dt>Support Animal</dt> <dd>A Support Animal, sometimes referred to as an assistance animal or emotional support animal, is an animal that provides emotional support, well-being, or companionship that alleviates or mitigates symptoms of a disability. Unlike Service Animals, Support Animals are (1) not individually trained to perform work or tasks; (2) not limited to dogs and can be other species of animal; (3) when approved in University housing are generally not permitted in other indoor public areas, private offices, classrooms, labs, etc.; and (4) only permitted on campus with prior approval from the campus disability services office.</dd> <dt>Therapy Animal</dt> <dd>An animal, ordinarily a dog, (but can be cats and other species) that has been obedience trained and screened for its ability to interact favorably with humans and other animals. The primary purpose of a therapy animal is to provide affection and comfort to people in hospitals, retirement homes, nursing homes, schools, hospices, disaster areas, and other settings.</dd> <dt>University Grounds</dt> <dd>Any land or outdoor spaces owned or leased by the University of Minnesota.</dd> <dt>University Property</dt> <dd>Any land, building, or other real property owned or leased by the University of Minnesota.</dd> </dl> </div> </div> <div class="field field--name-field-committee-review field--type-entity-reference field--label-above"> <div class="field__label">Committee Involvement</div> <div class="field__items"> <div class="field__item"><a href="/taxonomy/term/4" hreflang="en">SCC</a></div> <div class="field__item"><a href="/taxonomy/term/19" hreflang="en">Disabilities Issues</a></div> </div> </div> <div class="field field--name-field-policy-responsible-executi field--type-entity-reference field--label-above"> <div class="field__label">Senior Leader</div> <div class="field__items"> <div class="field__item"><a href="/user/76" hreflang="en">frans</a></div> </div> </div> <div class="field field--name-field-policy-responsible-officer field--type-entity-reference field--label-above"> <div class="field__label">Responsible Officer</div> <div class="field__items"> <div class="field__item"><a href="/user/76" hreflang="en">frans</a></div> </div> </div> <div class="clearfix text-formatted field field--name-field-description field--type-text-long field--label-above"> <div class="field__label">Revision Description for Review/Update Page</div> <div class="field__item"><p><strong>New Policy.</strong></p> <ol> <li>Clarifies which kinds of animals can be on campus and in buildings.</li> <li>Outlines the requirements around service and assistance animals, and by and large sets in place a ban on domestic pets in all university facilities.&nbsp;</li> <li>Ensures compliance with the law, but also protects university property as well as creates a safe place for those who live and work here.</li> </ol> </div> </div> <div class="clearfix text-formatted field field--name-field-policyresponsibilities field--type-text-long field--label-above"> <div class="field__label">Responsibilities</div> <div class="field__item"><dl> <dt>Animal Handler / Owner</dt> <dd>Comply with all provisions of this policy. Maintain control of their animal and ensure safety of others at all times.</dd> <dt>Campus Disability Services Office</dt> <dd>Define and maintain process for approval of Support Animals. Process requests for Support Animals in university housing. Serve as a resource for individuals and supervisors with questions about application of this policy with regard to Service Animals.</dd> <dt>Campus Housing Office</dt> <dd>Facilitate approved requests for Support Animals.</dd> <dt>Campus/City Police or Safety Officials</dt> <dd>Respond to complaints about stray or noncompliant animals. On the Duluth, Morris, and Twin Cities campuses, Police refers to the University of Minnesota Police Department. On the Crookston and Rochester campuses, Police refers to the local/city police department.</dd> <dt>Campus Student Conduct Office</dt> <dd>Adjudicate reported violations of this policy by students.</dd> <dt>College of Veterinary Medicine</dt> <dd>Maintain collegiate policy and procedure for animals in the workplace.</dd> <dt>Institutional Animal Care and Use Committee (IACUC)</dt> <dd>Administer Board of Regents policy regulating research, teaching, display, and service activities involving animals when conducted by, or on the behalf of, university faculty, staff, or students or when using university facilities or equipment.</dd> <dt>PAWS Program</dt> <dd>Notify supervisors of faculty and staff who have animals that have been certified by the program as participants.</dd> <dt>Supervisors</dt> <dd>Respond to violations of this policy by employees within their unit. Ask noncompliant animal handlers to leave university buildings or public transportation. Address repeat offenders through the employee performance process.</dd> </dl> </div> </div> <div class="clearfix text-formatted field field--name-field-policyrelatedinformation field--type-text-long field--label-above"> <div class="field__label">Related Information</div> <div class="field__item"><ul> <li>Board of Regents Policy: <a href="https://regents.umn.edu/sites/regents.umn.edu/files/2019-09/policy_animal_care_and_use.pdf"><em>Animal Care and Use</em></a></li> <li><a href="https://research.umn.edu/units/iacuc/policies-guidelines/animal-use-guidelines-exceptions">IACUC Animal Use Guidelines and Exceptions</a></li> </ul> </div> </div> <div class="clearfix text-formatted field field--name-field-policyhistory field--type-text-long field--label-above"> <div class="field__label">History</div> <div class="field__item"><dl> <dt>Effective</dt> <dd>January 2020 - <ol> <li>Clarifies which kinds of animals can be on campus and in buildings.</li> <li>Outlines the requirements around service and assistance animals, and by and large sets in place a ban on domestic pets in all university facilities.</li> <li>Ensures compliance with the law, but also protects university property as well as creates a safe place for those who live and work here.</li> </ol> </dd> </dl> </div> </div> <div class="field field--name-field-date-comp-review field--type-datetime field--label-above"> <div class="field__label">Date Comp Review</div> <div class="field__items"> <div class="field__item"><time datetime="2020-01-02T12:00:00Z" class="datetime">Thu, 01/02/2020 - 12:00</time> </div> </div> </div> <div class="field field--name-field-date-comp-review-due field--type-datetime field--label-above"> <div class="field__label">Date Comp Review Due</div> <div class="field__item"><time datetime="2024-01-02T12:00:00Z" class="datetime">Tue, 01/02/2024 - 12:00</time> </div> </div> <div class="field field--name-field-senate-involvement field--type-list-string field--label-above"> <div class="field__label">Senate Involvement</div> <div class="field__items"> <div class="field__item">Senate Action Necessary?</div> </div> </div> <div class="field field--name-field-d7-nid field--type-integer field--label-above"> <div class="field__label">D7 NID</div> <div class="field__item">14601</div> </div> <div class="field field--name-field-d7-vid field--type-integer field--label-above"> <div class="field__label">D7 VID</div> <div class="field__item">270326</div> </div> <div class="field field--name-field-date-comp-review-stamp field--type-timestamp field--label-above"> <div class="field__label">Date of Comprehensive Review - Time Stamp</div> <div class="field__item">Thu, 01/02/2020 - 00:00</div> </div> <div class="field field--name-field-review-interval field--type-list-string field--label-above"> <div class="field__label">Review Interval</div> <div class="field__item">4 years</div> </div> Mon, 10 Jun 2019 13:49:00 +0000 young041 1938 at https://policy.umn.edu Background Checks and Verifications https://policy.umn.edu/hr/backgroundverification <span class="field field--name-title field--type-string field--label-hidden">Background Checks and Verifications</span> <span class="field field--name-uid field--type-entity-reference field--label-hidden"><a title="View user profile." href="/user/1" lang="" about="/user/1" typeof="schema:Person" property="schema:name" datatype="" class="username">oitadmin</a></span> <span class="field field--name-created field--type-created field--label-hidden">Fri, 02/27/2015 - 00:00</span> <div class="field field--name-field-category field--type-entity-reference field--label-above"> <div class="field__label">Category</div> <div class="field__items"> <div class="field__item"><a href="/taxonomy/term/80" hreflang="en">Hiring</a></div> </div> </div> <section class="field field--name-field-comments field--type-comment field--label-above comment-wrapper"> <h2 class="title comment-form__title">Add new comment</h2> <drupal-render-placeholder callback="comment.lazy_builders:renderForm" arguments="0=node&amp;1=1732&amp;2=field_comments&amp;3=policy_comment" token="0lEXNB5NR0H-QR5eIH6KWP_MOIb16B6FQS38hdCKYBg"></drupal-render-placeholder> </section> <div class="field field--name-field-owner field--type-entity-reference field--label-above"> <div class="field__label">Owner</div> <div class="field__items"> <div class="field__item"><a href="/user/414" hreflang="en">maryrk</a></div> </div> </div> <div class="field field--name-field-policy-related-procedures field--type-entity-reference field--label-above"> <div class="field__label">Policy Related Procedures</div> <div class="field__items"> <div class="field__item"><a href="/hr/backgroundverification-proc01" hreflang="en">Conducting a Background Check or Verification</a></div> </div> </div> <div class="field field--name-field-urlcategory field--type-list-string field--label-above"> <div class="field__label">urlcategory</div> <div class="field__item">HR</div> </div> <div class="field field--name-field-path-slug field--type-string field--label-above"> <div class="field__label">Path slug</div> <div class="field__item">BACKGROUNDVERIFICATION</div> </div> <div class="field field--name-field-policy-related-appendices field--type-entity-reference field--label-above"> <div class="field__label">Policy Related Appendices</div> <div class="field__items"> <div class="field__item"><a href="/hr/backgroundverification-appa" hreflang="en">Senior and Other High-Level Leader Positions for Background Checks and Verifications</a></div> <div class="field__item"><a href="/hr/backgroundverification-appb" hreflang="en">Positions for Which Background Verification Is Advisable</a></div> <div class="field__item"><a href="/hr/backgroundverification-appf" hreflang="en">Background Check Requirements for Non-Employees</a></div> <div class="field__item"><a href="/hr/backgroundverification-appe" hreflang="en">Summary of Rights Under the Fair Credit Reporting Act</a></div> <div class="field__item"><a href="/hr/backgroundverification-appg" hreflang="en">Types of Background Checks</a></div> </div> </div> <div class="field field--name-field-policy-related-faqs field--type-entity-reference field--label-above"> <div class="field__label">Policy Related FAQs</div> <div class="field__items"> <div class="field__item"><a href="/hr/backgroundverification-faq" hreflang="en">Background Check Program</a></div> </div> </div> <div class="field field--name-field-sme field--type-entity-reference field--label-above"> <div class="field__label">Primary Contact</div> <div class="field__items"> <div class="field__item"><a href="/user/80" hreflang="en">Contact</a></div> </div> </div> <div class="field field--name-field-governing-regents-policies field--type-entity-reference field--label-above"> <div class="field__label">Governing Regents Policies</div> <div class="field__items"> <div class="field__item"><a href="/policy-regents/1023" hreflang="en">Employee Recruitment and Retention</a></div> </div> </div> <div class="clearfix text-formatted field field--name-field-revisiondescription field--type-text-long field--label-above"> <div class="field__label">Revision Description</div> <div class="field__item"><p>6/9/2021 -&nbsp;Corrected Employee Retention Board policy url.</p> </div> </div> <div class="field field--name-field-subtype field--type-list-string field--label-above"> <div class="field__label">SubType</div> <div class="field__item">Administrative Policy</div> </div> <div class="field field--name-field-daterevised field--type-datetime field--label-above"> <div class="field__label">Last Revised</div> <div class="field__item"><time datetime="2018-01-26T12:00:00Z" class="datetime">Fri, 01/26/2018 - 12:00</time> </div> </div> <div class="field field--name-field-dateeffective field--type-datetime field--label-above"> <div class="field__label">Effective Date</div> <div class="field__item"><time datetime="2008-09-01T12:00:00Z" class="datetime">Mon, 09/01/2008 - 12:00</time> </div> </div> <div class="clearfix text-formatted field field--name-field-policystatement field--type-text-long field--label-above"> <div class="field__label">Policy Statement</div> <div class="field__item"><p>Background checks and verifications are used to evaluate individuals’ eligibility to be engaged in certain work by the University on a case-by-case basis. Units are required to initiate background checks at the University for those covered by this policy, and must coordinate with Central Office of Human Resources (OHR) to use the University’s designated vendor. Background checks and verifications must be completed before the first day of work.</p> <h3>Background Checks</h3> <p>Standard background checks through the University’s designated vendor (as defined in Appendix: <em>Background Check and Verification Packages</em>) are required for:</p> <ul> <li>individuals being offered employment in, or being transferred or reassigned to, non-student positions;</li> <li>individuals, including non-employees and student employees, who are assigned duties where checks are legally or contractually required; and</li> <li>individuals, including non-employees and student employees, being engaged by the University encompassing work with minors (see administrative policy <em>Safety of Minors)</em>.</li> </ul> <p>Non-employees are required to complete a successful background check if they will be performing security-sensitive work for the University. Units must obtain confirmation of the successful completion of a background check for the non-employee with the vendor. Refer to appendix: <em>Background Checks for Non-Employees </em>for more information. If not available, then the unit must conduct a background check through the University’s designated vendor prior to the first day of work.</p> <p>Senior leaders and other high-level leader positions (as defined in Appendix: <em>Senior and Other High-Level Leader Positions for Background Checks and Verifications) </em>as well as members of the University of Minnesota Police Department will be subject to more extensive background checks, whether triggered by an employment offer, a transfer, or a reassignment into one of these positions.</p> <p>Individuals who completed a background check at the University with satisfactory results within the last twelve months will not be required to undergo another background check unless the new position or newly-assigned duties require different checks or verifications than those originally conducted.</p> <p>Offers of employment, transfers, and reassignments and assignment of duties are contingent upon completion of background checks and specified verifications with satisfactory results.&nbsp; Accordingly, units must plan and submit background check and verifications requests before employment or assignments occur.</p> <h3>Verifications of Credentials</h3> <p>Individuals, who are being offered employment or reassignment to a position where the assigned work requires certain educational, employment, and licensing credentials, must have their credentials verified.&nbsp; Units are responsible for ensuring that licensures are tracked and demonstrated.</p> <h3>Results Review</h3> <p>Departments are responsible for initiating background checks and verifications through OHR and incur the costs. OHR staff will conduct individualized assessments of background check and credentials verification results taking into consideration important factors such as the nature and severity, time frame, and relevancy of any criminal convictions.</p> </div> </div> <div class="clearfix text-formatted field field--name-field-policyreason field--type-text-long field--label-above"> <div class="field__label">Reason for Policy</div> <div class="field__item"><p>This policy supports Board of Regents Policy: <em><a href="https://regents.umn.edu/sites/regents.umn.edu/files/2019-09/policy-employee_recruitment_and_retention.pdf">Employee Recruitment and Retention</a></em> and provides business processes for Board of Regents Policy: <em><a href="https://regents.umn.edu/sites/regents.umn.edu/files/policies/Safety_of_Minors.pdf" target="">Safety of Minors</a></em>. It furthers important University efforts to provide a safe and secure environment for all University students, employees, and visitors to protect its funds, property, and other assets. Therefore, the University provides this formal process of background checks and verifications (1) to minimize institutional risk, (2) to comply with federal and state regulations that require it for specified positions, and (3) to help responsible hiring authorities make sound hires.</p> </div> </div> <div class="clearfix text-formatted field field--name-field-policycontacts field--type-text-long field--label-above"> <div class="field__label">Contacts</div> <div class="field__item"><div class="tablewrapper"> <table> <thead> <tr> <th scope="col">Subject</th> <th scope="col">Contact</th> <th scope="col">Phone</th> <th scope="col">Email</th> </tr> </thead> <tbody> <tr> <th scope="row">General information or procedural assistance</th> <td>Primary: OHR Program Lead<br /> OHR, AHC or UMD – Human Resources Employment Consultants</td> <td class="nowrap">Refer to directory</td> <td>jobcentr@umn.edu<br /> Refer to directory</td> </tr> <tr> <td>Document processing</td> <td>Office of Human Resources Contact Center</td> <td>612-624-8647 (UOHR)</td> <td>ohr@umn.edu</td> </tr> </tbody> </table> </div> </div> </div> <div class="clearfix text-formatted field field--name-field-policydefinitions field--type-text-long field--label-above"> <div class="field__label">Definitions</div> <div class="field__item"><dl> <dt>Non-Employees</dt> <dd>Individuals performing work on behalf of or in concert with the University, including vendor contractors or consultants working onsite, who are not actively employed by the University.</dd> <dd>&nbsp;</dd> <dt>Student Positions</dt> <dd>Positions that are non-academic student positions (2xxx job classification series); undergraduate academic teaching and research assistant positions); and graduate assistant positions</dd> <dd>&nbsp;</dd> <dt>Other High-Level Leaders</dt> <dd>For purposes of this policy, refer to Appendix: <em><a href="/hr/backgroundverification-appa">Senior and Other High-Level Leader Positions for Background Checks and Verifications</a></em>.</dd> <dt>Senior Leaders</dt> <dd>Individuals specified as senior leaders in Board of Regents Policy: <em>Reservation and Delegation of Authority</em>. For purposes of this policy, refer to Appendix: Senior and Other High-Level Leader Positions for Background Checks and Verifications.</dd> </dl> </div> </div> <div class="field field--name-field-committee-review field--type-entity-reference field--label-above"> <div class="field__label">Committee Involvement</div> <div class="field__items"> <div class="field__item"><a href="/taxonomy/term/4" hreflang="en">SCC</a></div> </div> </div> <div class="field field--name-field-policy-responsible-executi field--type-entity-reference field--label-above"> <div class="field__label">Senior Leader</div> <div class="field__items"> <div class="field__item"><a href="/user/11" hreflang="en">horst009</a></div> </div> </div> <div class="field field--name-field-policy-responsible-officer field--type-entity-reference field--label-above"> <div class="field__label">Responsible Officer</div> <div class="field__items"> <div class="field__item"><a href="/user/11" hreflang="en">horst009</a></div> </div> </div> <div class="clearfix text-formatted field field--name-field-description field--type-text-long field--label-above"> <div class="field__label">Revision Description for Review/Update Page</div> <div class="field__item"><p>Comprehensive Review, Major Revision: 1. Expands requirements for background checks to include individuals who are not employees but are contracted by the University to perform security-sensitive work.<br /> 2. Establishes that the background checks and verifications must be completed before the first day of work.<br /> 3. Eliminates the separate cover sheet for senior leaders to simplify the process.</p> </div> </div> <div class="field field--name-field-ucmcontentid field--type-string field--label-above"> <div class="field__label">UCMContentID</div> <div class="field__item">BACKGROUNDVERIFICATION</div> </div> <div class="clearfix text-formatted field field--name-field-policyresponsibilities field--type-text-long field--label-above"> <div class="field__label">Responsibilities</div> <div class="field__item"><dl> <dt>Hiring Authority/Department</dt> <dd>Identify and communicate about circumstances where legal, contractual or the nature of the work justify conducting background checks and verifications; ensure licensures are tracked and demonstrated where necessary; identify selected applicants and employees and facilitate the exchange of information with them to conduct background checks and verifications; obtain confirmation from vendors of successful completion of a background check for non-employees when required; and hold responsibility for costs of background checks and verifications in their department.</dd> <dt>College/Administrative Unit Human Resources</dt> <dd>Verify with departments that all background checks are completed before the individual’s first day of work; determine whether to require background checks for additional positions, such as students, where the unit could be adversely impacted or where there is undue liability.</dd> <dt>Office of Human Resources</dt> <dd>Advise hiring authorities/departments about circumstances where legal, contractual, or legitimate business needs justify conducting background checks and verifications; ensure postings include appropriate information about background check requirement; and conduct individualized assessment of background check and verification results.</dd> </dl> </div> </div> <div class="clearfix text-formatted field field--name-field-policyrelatedinformation field--type-text-long field--label-above"> <div class="field__label">Related Information</div> <div class="field__item"><ul> <li>Board of Regents Policy: <a href="https://regents.umn.edu/sites/regents.umn.edu/files/2019-09/policy-employee_recruitment_and_retention.pdf"><em>Employee Recruitment and Retention</em></a></li> <li><span id="bor">Board of Regents Policy:</span> <a aria-labelledby="som bor" href="https://regents.umn.edu/sites/regents.umn.edu/files/policies/Safety_of_Minors.pdf" id="som" target=""><em>Safety of Minors</em></a></li> <li><span id="admin">Administrative Policy:</span> <em><a aria-labelledby="admin somadmin" href="/operations/minorsafety" id="somadmin" target="">Safety of Minors</a></em></li> <li>For residential dorm access: <a href="https://www.revisor.leg.state.mn.us/statutes/?id=299C.68">Minn. Stat. § 299C.68</a></li> <li><a href="http://www.nrc.gov/security/byproduct.html">Nuclear Regulatory Commission</a>: <a href="http://www.nrc.gov/security/byproduct.html">http://www.nrc.gov/security/byproduct.html</a></li> <li><a href="https://controller.umn.edu/business-processes/AR10.html">Payment Cards/PCI DSS Standards Compliance</a></li> <li>State Regulation for child care workers: <a href="https://www.revisor.leg.state.mn.us/statutes/?id=299C.62">Minn. Stat. § 299C.62</a></li> <li>Criminal Offenders, Rehabilitation: <a href="https://www.revisor.leg.state.mn.us/statutes/?id=364.01">Minn. Stat. § 364.01 </a></li> </ul> </div> </div> <div class="clearfix text-formatted field field--name-field-policyhistory field--type-text-long field--label-above"> <div class="field__label">History</div> <div class="field__item"><dl> <dt>Amended:</dt> <dd>January 2018 - Comprehensive Review, Major Revision: 1. Expands requirements for background checks to include individuals who are not employees but are contracted by the University to perform security-sensitive work. 2. Establishes that the background checks and verifications must be completed before the first day of work. 3. Eliminates the separate cover sheet for senior leaders to simplify the process.</dd> <dt>Amended:</dt> <dd>June 2013 - Comprehensive Review. This revision creates a consistent system-wide requirement of background checks on all individuals being offered employment in, or being transferred or reassigned to, non-student positions. Checks will also be conducted for individuals, including volunteers, who are involved in work with minors, or where background checks are legally or contractually required.</dd> <dt>Amended:</dt> <dd>October 2012 - Senior leaders and other high-level leaders replaced the term, senior administrator. The classification job codes and titles assigned to each of these new terms are found in the Appendix: <em>Senior and Other High-Level Positions Requiring Background Checks</em>.</dd> <dt>Amended:</dt> <dd>January 2009 - Edits made and language clarified in the policy statement. Administrative unit was added under the Definition section.</dd> <dt>Effective:</dt> <dd>September 2008</dd> <dt>Adopted:</dt> <dd>August 2008 - The Pre-employment Background Verification Program has been in place since March 2006 and has now been formalized in this administrative policy.</dd> </dl> </div> </div> <div class="field field--name-field-date-comp-review field--type-datetime field--label-above"> <div class="field__label">Date Comp Review</div> <div class="field__items"> <div class="field__item"><time datetime="2018-01-26T12:00:00Z" class="datetime">Fri, 01/26/2018 - 12:00</time> </div> </div> </div> <div class="field field--name-field-date-comp-review-due field--type-datetime field--label-above"> <div class="field__label">Date Comp Review Due</div> <div class="field__item"><time datetime="2022-01-26T12:00:00Z" class="datetime">Wed, 01/26/2022 - 12:00</time> </div> </div> <div class="field field--name-field-policy-related-forms field--type-entity-reference field--label-above"> <div class="field__label">Policy Related Forms</div> <div class="field__items"> <div class="field__item"><a href="/Forms/um-1690" hreflang="en">Personal Disclosure Statement</a></div> <div class="field__item"><a href="/Forms/um-1839" hreflang="en">Background Verification Request - Cover Sheet</a></div> <div class="field__item"><a href="/Forms/um-1692" hreflang="en">Background Check Consent</a></div> </div> </div> <div class="field field--name-field-d7-nid field--type-integer field--label-above"> <div class="field__label">D7 NID</div> <div class="field__item">9508</div> </div> <div class="field field--name-field-d7-vid field--type-integer field--label-above"> <div class="field__label">D7 VID</div> <div class="field__item">256406</div> </div> <div class="field field--name-field-date-comp-review-stamp field--type-timestamp field--label-above"> <div class="field__label">Date of Comprehensive Review - Time Stamp</div> <div class="field__item">Fri, 01/26/2018 - 00:00</div> </div> Fri, 27 Feb 2015 06:00:00 +0000 oitadmin 1732 at https://policy.umn.edu https://policy.umn.edu/hr/backgroundverification#comments Brand Policy: Trademarks, Logos, Colors, and Seal https://policy.umn.edu/operations/branding <span class="field field--name-title field--type-string field--label-hidden">Brand Policy: Trademarks, Logos, Colors, and Seal</span> <span class="field field--name-uid field--type-entity-reference field--label-hidden"><a title="View user profile." href="/user/1" lang="" about="/user/1" typeof="schema:Person" property="schema:name" datatype="" class="username">oitadmin</a></span> <span class="field field--name-created field--type-created field--label-hidden">Mon, 11/03/2014 - 00:00</span> <div class="field field--name-field-category field--type-entity-reference field--label-above"> <div class="field__label">Category</div> <div class="field__items"> <div class="field__item"><a href="/taxonomy/term/91" hreflang="en">Miscellaneous</a></div> </div> </div> <section class="field field--name-field-comments field--type-comment field--label-above comment-wrapper"> <h2 class="title comment-form__title">Add new comment</h2> <drupal-render-placeholder callback="comment.lazy_builders:renderForm" arguments="0=node&amp;1=1740&amp;2=field_comments&amp;3=policy_comment" token="-KMXJ6jrcZnhhIgcl1_cMzQ7358SKK6Ccbo4khSX0k4"></drupal-render-placeholder> </section> <div class="field field--name-field-owner field--type-entity-reference field--label-above"> <div class="field__label">Owner</div> <div class="field__items"> <div class="field__item"><a href="/user/88" hreflang="en">aronson</a></div> </div> </div> <div class="field field--name-field-urlcategory field--type-list-string field--label-above"> <div class="field__label">urlcategory</div> <div class="field__item">Operations</div> </div> <div class="field field--name-field-path-slug field--type-string field--label-above"> <div class="field__label">Path slug</div> <div class="field__item">BRANDING</div> </div> <div class="field field--name-field-policy-related-faqs field--type-entity-reference field--label-above"> <div class="field__label">Policy Related FAQs</div> <div class="field__items"> <div class="field__item"><a href="/operations/branding-faq" hreflang="en">Brand Policy: Trademarks, Logos, Colors, and Seal</a></div> </div> </div> <div class="field field--name-field-sme field--type-entity-reference field--label-above"> <div class="field__label">Primary Contact</div> <div class="field__items"> <div class="field__item"><a href="/user/335" hreflang="en">lkj</a></div> </div> </div> <div class="field field--name-field-governing-regents-policies field--type-entity-reference field--label-above"> <div class="field__label">Governing Regents Policies</div> <div class="field__items"> <div class="field__item"><a href="/policy-regents/1032" hreflang="en">Founding Date, Corporate Name and Seal, and University Marks</a></div> </div> </div> <div class="clearfix text-formatted field field--name-field-revisiondescription field--type-text-long field--label-above"> <div class="field__label">Revision Description</div> <div class="field__item"><p>Added some missing text per&nbsp;Laura Johnson.</p> </div> </div> <div class="field field--name-field-subtype field--type-list-string field--label-above"> <div class="field__label">SubType</div> <div class="field__item">Administrative Policy</div> </div> <div class="field field--name-field-daterevised field--type-datetime field--label-above"> <div class="field__label">Last Revised</div> <div class="field__item"><time datetime="2021-05-25T12:00:00Z" class="datetime">Tue, 05/25/2021 - 12:00</time> </div> </div> <div class="field field--name-field-dateeffective field--type-datetime field--label-above"> <div class="field__label">Effective Date</div> <div class="field__item"><time datetime="2009-05-07T12:00:00Z" class="datetime">Thu, 05/07/2009 - 12:00</time> </div> </div> <div class="clearfix text-formatted field field--name-field-policystatement field--type-text-long field--label-above"> <div class="field__label">Policy Statement</div> <div class="field__item"><p>This policy governs the use of all University trademarks (see definition) for any purpose and applies to the entire University system. Consistency in the use of University trademarks strengthens their value and our ability to protect them from unauthorized use. The Office of University Relations should be consulted whenever it is not clear whether a proposed use is permissible.</p> <h3>General</h3> <p>Campuses, colleges, departments and individuals may only use University trademarks in strict accordance with this policy and the graphics requirements on the <a href="https://university-relations.umn.edu/resources/all-resources">Brand website</a>. In general:</p> <ul> <li>No University trademark may be altered or combined with any other mark or</li> <li>A unit may use its name with the University's wordmark only as outlined on the brand</li> <li>The wordmark is required on all official internal and external communications, excluding individual email University colors and branded elements must appear prominently on all official communication and marketing materials. The use of official University letterhead and business cards is required in all matters of official University business.</li> <li>The use of taglines, icons or graphics as logos or in logos for University units is prohib<wbr />ited. All umn.edu websites must use an official web template header and footer.</li> <li>Use of University trademarks in print and electronic materials including email and social media must conform to brand</li> <li>University trademarks may be used on commercial merchandise only by persons and entities licensed by the University’s exclusive licensing agent.</li> <li>All official University content must provide equitable access to people with disabilities.&nbsp;See&nbsp;<a href="/it/webaccess">Accessibility of Information Technology policy&nbsp;</a>.</li> </ul> <h3>Regents of the University of Minnesota Seal [Regents Seal]</h3> <p>The Regents Seal may be used only as authorized in Board of Regents Policy: <a href="https://regents.umn.edu/sites/regents.umn.edu/files/2019-09/policy_founding_date_corporate_name_and_seal_and_university_marks.pdf">Founding Date, Corporate Name and Seal, and University Marks</a>. It is reserved for use on official documents bearing the signature of a regent, the president or a vice president, chancellor, or dean; on official University awards; and in connection with events or facilities that are frequently used by or have a unique connection to the Board of Regents or president. To request use of the seal, contact the Office of University Relations.</p> <h3>University Brand</h3> <p>Driven to Discover is the official brand of the University. All University Units should use Driven to Discover and brand elements available on the Our Brand site.</p> <h3>Use of University Trademarks and Logos</h3> <h4>By University Colleges, Schools, Departments, Campus Life Programs and Other Units</h4> <p>Units are required to use the wordmark and may use the Block M, in connection with official University business. System campuses must use the appropriate wordmark and Block M combination for their campus in connection with official University business and in their official web headers. University units may also use the mascot marks as appropriate in less formal circumstances.</p> <p>Each of the University's units has unique attributes that enrich the University brand. When developing individual marketing programs to highlight their unique attributes, units are encouraged to work with the Office of University Relations to assure the successful integration of such programs with the University brand.</p> <h4>By Student Organizations</h4> <p>Registered Student Organizations (RSO) on the Twin Cities campus are allowed the use of the Registered Student Organization Block M mark or Registered Student Organization Goldy mark. The RSO Block M mark, and RSO Goldy mark may not be altered or combined with other elements or graphics. More information on&nbsp;guidelines&nbsp;and best practices&nbsp;are available on the&nbsp;<a href="https://sua.umn.edu/engage/student-groups/student-group-policies">Student Group Policies</a>&nbsp;page. RSOs on the other system campuses should consult their campus RSO rules to determine applicability.</p> <p>Registered student organizations from any campus may not use any other University trademarks.</p> <p>Campus Life Programs should refer to “By colleges, schools departments, Campus Life Programs, and other units” above for applicable policy.</p> <h4>By Faculty, Staff, and Students</h4> <ul> <li>No individual faculty, staff, student, or group may use any University trademark or the official web template header and footer, or refer to their affiliation with the University, to indicate support or endorsement of anything that is not official University Potential confusion should be dispelled by adding a disclaimer stating that the University is not involved in the subject of the statement. This is also addressed in Board of Regents Policy: <a href="https://regents.umn.edu/sites/regents.umn.edu/files/2019-09/policy_academic_freedom_and_responsibility.pdf">Academic Freedom and Responsibility</a> and Board of Regents Policy: <a href="https://regents.umn.edu/sites/regents.umn.edu/files/2019-09/policy_outside_consulting_and_other_commitments.pdf">Outside Consulting and Other Commitments</a>.</li> <li>Athletics Department staff may conduct summer camps and clinics as such activities are commonly understood.The use of the name of the University or any title which would imply University endorsement or sponsorship (e.g., "Gopher" or "Bulldogs") is specifically prohibited unless the camp or clinic is developed and operated as a University-sponsored program or the camp or clinic is held in a campus facility and the athletics director gives written permission for the use of specific identifying terms. This is addressed in the Administrative Procedure: <a href="/operations/outsideconsulting">Outside Consulting and Other Commitments.</a></li> </ul> <h4>By Persons and/or Entities Outside the University</h4> <p>University trademarks may be used by persons or entities outside the University only pursuant to a license, memorandum of understanding, or sponsorship agreement stating the terms and conditions of such use. All memoranda of understanding and sponsorship agreements are subject to the approval of the Office of General Counsel.</p> <h3>Prohibited Uses of University Trademarks</h3> <h4>No Endorsements.</h4> <p>Neither the name of the University nor any University trademark, including University colors, may be used in any way that states or implies endorsement of a commercial product or service, gives a false impression, is misleading, or could cause confusion regarding the University’s relationship with any person or entity. Statements that the University is a user or purchaser of a product or program are permitted if true. Use of University trademarks are not allowed in third-party communications including vendor websites or other communications aimed at marketing their products or services.</p> <h4>General Prohibition.</h4> <p>Neither the name of the University nor any University trademark may be used in any manner that could adversely affect the University’s image or standing or would for any other reason be inappropriate for a public research university. Such proscribed uses include, but are not limited to, the use of University trademarks in connection with cigarettes or other tobacco products, sexually oriented products or services, religious products, political parties or organizations, gaming or games of chance, and firearms.</p> <h3>Violations</h3> <p>If a violation of this policy is identified, units will be required to work with the Office of University Relations to determine the action needed, which may include redesign of print and/or electronic materials. With respect to all violations of this policy, the University reserves its right to seek appropriate remedies under applicable federal or state law.</p> <h3>Exceptions</h3> <p>Units may submit a request for a special exception to University Relations for consideration.</p> </div> </div> <div class="clearfix text-formatted field field--name-field-policyreason field--type-text-long field--label-above"> <div class="field__label">Reason for Policy</div> <div class="field__item"><p>To implement Board of Regents Policy:&nbsp;<a href="https://regents.umn.edu/sites/regents.umn.edu/files/2019-09/policy_founding_date_corporate_name_and_seal_and_university_marks.pdf"><em>Founding Date, Corporate Name and Seal, and University Marks</em></a>. The University is a complex institution that is known for many things, including excellence in research and scholarship; the advancement of learning; the fostering of creativity; and the further sharing of these things among diverse constituencies through outreach and public service. A key aspect of representing the University's diverse body of work successfully to the larger world is the continued development and maintenance of a consistent visual and brand identity - a consistent use of University trademarks.</p> <p>A consistent use of the University's brand brings together the efforts of all who constitute the University; it unifies and strengthens the University’s reputation; and it distinguishes the University of Minnesota from other institutions of higher learning, enhancing its relationships with all constituencies, public and private.</p> </div> </div> <div class="clearfix text-formatted field field--name-field-policycontacts field--type-text-long field--label-above"> <div class="field__label">Contacts</div> <div class="field__item"><div class="tablewrapper"> <table> <thead> <tr> <th scope="col">Subject</th> <th scope="col">Contact</th> <th scope="col">Phone</th> <th scope="col">Email</th> </tr> </thead> <tbody> <tr> <th scope="row">Primary Contact(s)</th> <td><a href="http://www.umn.edu/lookup?UID=lkj">Laura Johnson</a></td> <td>612-626-3527</td> <td>lkj@umn.edu</td> </tr> <tr> <th scope="row">General Information</th> <td>University Relations</td> <td>612-624-6868</td> <td>brand@umn.edu</td> </tr> </tbody> </table> </div> </div> </div> <div class="clearfix text-formatted field field--name-field-policydefinitions field--type-text-long field--label-above"> <div class="field__label">Definitions</div> <div class="field__item"><dl> <dt>Block M</dt> <dd>The logo that consists of the capital letter "M" in the distinctive graphic design that is unique to the University. See "Block M" on the Our Brand website. Note that the Block M is a graphic design, not a font or a style of type. There are three versions of the block m: solid, single outline, and double outline. Official versions in the approved color combinations are available on the Our Brand website.</dd> <dt>Brand Elements</dt> <dd>The basic components of the University's brand, which include the following: <ul> <li>&nbsp;Block M</li> <li>Driven to Discover and brand elements</li> <li>Mascot marks</li> <li>University colors</li> <li>Wordmark</li> </ul> </dd> <dt>Mascot Mark</dt> <dd>A University mark that features the mascot of one of the system campuses. Official versions of the mascot marks in the approved color combinations are available from the Office of University Relations on each system campus and, for the Twin Cities campus, on the Our Brand website.</dd> <dd>The Mascot Marks are as follows: <ul> <li>Crookston campus: the golden eagle (Regal the Eagle)</li> <li>Duluth campus: the bulldog (Champ the Bulldog)</li> <li>Morris campus: the cougar (Pounce the Cougar)</li> <li>Rochester campus: the raptor (Rockie the Raptor)</li> <li>Twin Cities campus: the gopher (Goldy Gopher; there are two forms, known as "Running Goldy" and "Leaning Goldy.")</li> </ul> </dd> <dt>Official University Business</dt> <dd>Work that supports the University’s mission of teaching, research, and public service including programs and events sponsored by the University and activities conducted in the ordinary and regular course of business of the University.</dd> <dt>Regents Seal</dt> <dd>The corporate seal of the University of Minnesota.</dd> <dt>Sponsorship Agreements</dt> <dd>Agreements documenting the provision of financial or other support for the University and the manner in which it will be publicly acknowledged.</dd> <dt>University Brand</dt> <dd>Driven to Discover and related creative elements. See <a href="https://university-relations.umn.edu/resources/all-resources">Brand website</a> for use guidelines.</dd> <dt>University Colors</dt> <dd>Maroon and gold, in the specifications given on the <a href="https://university-relations.umn.edu/resources/all-resources">Brand site</a>. No similar color, regardless of its specifications, may be used in a way that could cause confusion with a University Trademark.</dd> <dt>University Trademarks</dt> <dd>All words, logos, or symbols used to identify or distinguish goods or services as coming from or being affiliated with the University, whether or not they have been registered with the U.S. Patent and Trademark Office or any other authority. University trademarks include the Regents Seal, Driven to Discover, the wordmark, the block m, and the mascot marks. The term also includes the University colors, though not every use of one or both of those colors constitutes use of a University trademark. Contact the Office of University Relations with any question about the proper use of University trademarks.</dd> <dt>University Unit</dt> <dd>All campuses, colleges, institutes, schools, departments, offices, and centers that are a part of the University.</dd> <dt>Wordmark</dt> <dd>The logo that consists of the words “UNIVERSITY OF MINNESOTA” as a distinctive graphic design that is unique to the University and cannot be replicated in type.</dd> <dt>Unit Wordmark Combination</dt> <dd>A version of the wordmark that includes the name of a college, department, institute, or other University entity and is created as explained on the Our Brand website.</dd> </dl> </div> </div> <div class="field field--name-field-committee-review field--type-entity-reference field--label-above"> <div class="field__label">Committee Involvement</div> <div class="field__items"> <div class="field__item"><a href="/taxonomy/term/4" hreflang="en">SCC</a></div> </div> </div> <div class="field field--name-field-policy-responsible-executi field--type-entity-reference field--label-above"> <div class="field__label">Senior Leader</div> <div class="field__items"> <div class="field__item"><a href="/user/359" hreflang="en">kramerm</a></div> </div> </div> <div class="field field--name-field-policy-responsible-officer field--type-entity-reference field--label-above"> <div class="field__label">Responsible Officer</div> <div class="field__items"> <div class="field__item"><a href="/user/359" hreflang="en">kramerm</a></div> </div> </div> <div class="clearfix text-formatted field field--name-field-description field--type-text-long field--label-above"> <div class="field__label">Revision Description for Review/Update Page</div> <div class="field__item"><p>Comprehensive Review, minor revisions. Updates are focused on adding clarity related to Registered Student Organization use of trademarks, promoting digital accessibility principles, aligning language with the updates to the Outside Consulting and Other Commitments policy, and clarifying language in the “No endorsements” section to address common questions or concerns University Relations has received related to it.</p> </div> </div> <div class="field field--name-field-ucmcontentid field--type-string field--label-above"> <div class="field__label">UCMContentID</div> <div class="field__item">BRANDING</div> </div> <div class="clearfix text-formatted field field--name-field-policyresponsibilities field--type-text-long field--label-above"> <div class="field__label">Responsibilities</div> <div class="field__item"><dl> <dt>Office of University Relations</dt> <dd>Responsible for communicating, interpreting, and enforcing this policy.</dd> <dt>University Communicators</dt> <dd>Responsible for knowing and understanding this policy and complying with it in all communication and marketing materials, print or electronic.</dd> <dt>Office of the General Counsel</dt> <dd>Responsible for reviewing and acting on memoranda of understanding and sponsorship agreements, and communicating with University Relations when such documents include marketing or branding considerations.</dd> </dl> </div> </div> <div class="clearfix text-formatted field field--name-field-policyrelatedinformation field--type-text-long field--label-above"> <div class="field__label">Related Information</div> <div class="field__item"><h3>Related Policies</h3> <ul> <li>Board of Regents Policy: <a href="https://regents.umn.edu/sites/regents.umn.edu/files/policies/Academic_Freedom.pdf"><em>Academic Freedom &amp; Responsibility</em></a></li> <li>Board of Regents Policy:<a href="https://regents.umn.edu/sites/regents.umn.edu/files/policies/Associated_Organizations.pdf"><em>Associated Organizations</em></a></li> <li>Board of Regents Policy:<a href="https://regents.umn.edu/sites/regents.umn.edu/files/2019-09/policy_founding_date_corporate_name_and_seal_and_university_marks.pdf"><em>Founding Date, Corporate Name and Seal, and University Marks</em></a></li> <li>Board of Regents Policy:<a href="https://regents.umn.edu/sites/regents.umn.edu/files/policies/Outside_Consulting.pdf"><em>Outside Consulting and Other Commitments</em></a></li> </ul> <h3>Other Related Information</h3> <ul> <li><a href="https://university-relations.umn.edu/resources/frequently-used-resources"><em>Our Brand - How to Convey It</em></a></li> <li><a href="https://university-relations.umn.edu/"><em>Twin Cities - University Relations</em></a></li> <li><a href="http://www3.crk.umn.edu/relations/index.html"><em>Crookston - University Relations</em></a></li> <li><a href="http://www.d.umn.edu/external-affairs/"><em>Duluth - University Marketing and Public Relations</em></a></li> <li><a href="http://www.morris.umn.edu/urelations/"><em>Morris - University Relations</em></a></li> <li><a href="http://r.umn.edu/about-umr/news/communications/"><em>Rochester - Communications and Public Relations</em></a></li> <li><a href="https://university-relations.umn.edu/"><em>Office of University Relations</em></a></li> </ul> </div> </div> <div class="clearfix text-formatted field field--name-field-policyhistory field--type-text-long field--label-above"> <div class="field__label">History</div> <div class="field__item"><dl> <dt>Amended:</dt> <dd>May 2021 - Comprehensive Review, minor revisions. Updates are focused on adding clarity related to Registered Student Organization use of trademarks, promoting digital accessibility principles, aligning language with the updates to the Outside Consulting and Other Commitments policy, and clarifying language in the “No endorsements” section to address common questions or concerns University Relations has received related to it.</dd> <dt>Amended:</dt> <dd>February 2021 - Removed prohibition of alcohol to align with Board of Regents Policy.</dd> <dt>Amended:</dt> <dd>May 2017 - Comprehensive Review, Minor Revision. 1. Clarifies language throughout the policy. 2. Updates senior leader, responsible University office, and Policy owner information.</dd> <dt>Amended:</dt> <dd>December 2015 - Replaced the term "vendor" with "supplier" in Policy Statement and FAQ.</dd> <dt>Amended:</dt> <dd>June 2013 - Minor Revision, Comprehensive Review. Clarified that use of University Trademarks is prohibited on commercial merchandise unless produced through an appropriately licensed vendor. Added reference to email and social media to branding requirements for printed and electronic materials. Clarified when use of the Regents Seal is appropriate. Clarified when University Trademarks may be used by persons or entities outside the University. Contacts, definitions and responsibilities also updated.</dd> <dt>Amended:</dt> <dd>November 2010 - Clarified workmark requirements for mass email. Language now reads: "The Wordmark is required on all official internal and external communications, excluding individual email messages. The Wordmark is required on mass email messages that include a HTML message part.&nbsp;</dd> <dt>Effective:</dt> <dd>May 2009</dd> </dl> </div> </div> <div class="field field--name-field-date-comp-review field--type-datetime field--label-above"> <div class="field__label">Date Comp Review</div> <div class="field__items"> <div class="field__item"><time datetime="2021-05-25T12:00:00Z" class="datetime">Tue, 05/25/2021 - 12:00</time> </div> </div> </div> <div class="field field--name-field-date-comp-review-due field--type-datetime field--label-above"> <div class="field__label">Date Comp Review Due</div> <div class="field__item"><time datetime="2025-05-25T12:00:00Z" class="datetime">Sun, 05/25/2025 - 12:00</time> </div> </div> <div class="field field--name-field-d7-nid field--type-integer field--label-above"> <div class="field__label">D7 NID</div> <div class="field__item">9516</div> </div> <div class="field field--name-field-d7-vid field--type-integer field--label-above"> <div class="field__label">D7 VID</div> <div class="field__item">281951</div> </div> <div class="field field--name-field-date-comp-review-stamp field--type-timestamp field--label-above"> <div class="field__label">Date of Comprehensive Review - Time Stamp</div> <div class="field__item">Tue, 05/25/2021 - 00:00</div> </div> Mon, 03 Nov 2014 06:00:00 +0000 oitadmin 1740 at https://policy.umn.edu