1. Approval of January Meeting Minutes
2. Announcements
3. HIPAA (Health Information Portability and Accountability Act) Regulations
4. Joint Meeting with the Academic Computing Coordinating Council (AC4)

Excused: John Meyer and Dave Shelby.

Absent: Earlene Ford.

Staff to the Council: Debbie Lauriano, Bob Loessberg-Zahl, Randy Moory, and Babette Schmitt.

1. Approval of January Meeting Minutes

   Chair Robert Smiley asked the Council for any comments regarding the minutes from the January meeting. Council asked that the minutes clarify when Vice Provostis framework proposal would be available. Chair Smiley advised the Council that Vice Provost Bruno would provide this information. The minutes were approved as submitted.

    
   

2. Announcements

   Chair Robert Smiley provided the Council with an overview of the January 22, 2001, Information Technology Policies Board (ITPB) meeting. Minutes from the ITPB meeting are available at http://itpb.ucdavis.edu/meetings/01_22_01.html. He advised the Council that AC4 Chair, Richard Plant, suggested a joint meeting with AdC3 to discuss the future of MyUCDavis. He also spoke about the proposal by Information and Educational Technology (IET) to have Pacific Bell provide its VPOP service and outsource the modem pool. Council asked whether such outsourcing would impact IET staffing levels. The reply was that the proposal affects only equipment, not staffing levels.

   Vice Provost Bruno announced he would present the proposal for a new UC Davis information and educational technology planning framework at the next AdC3 meeting (on March 5). He also identified the projects that are in pilot status and require consideration in the budget review process. These include:

   • Document Management System
   • Data Warehouse
   • E-recruitment
   • DaFIS DOCS
   • Portal Access to information on grants and contracts (Plant Project)
   • My UCDavis

   In addition to these projects, Vice Provost Bruno also identified the five advanced technology projects that he has initiated within Information and Educational Technology. These short-term projects will result in reports, but the implementation of projects generated from these reports could require budget allocations and discussion at future AdC3 meetings. The advanced technology projects focus on the following important middleware issues:

   • Enterprise Directory Services
   • Window 2000
   • Wireless Networking
   • Mobile Computing Authentication
   • Incident Response

   (See the Advanced Technology Projects page for project descriptions and status reports.)

   Council had several questions about the possible impact of these projects on the biennial budget process, the administrative support planning process, and the implementation of the New Business Architecture recommendations. Council decided the appropriate course of action was to implement the procedure identified in the UC Davis Administrative Computing Plan: working closely with their oversight committees, the Project Leaders should develop an annual report of their administrative systems. At a minimum, the reports should include the following:

   • A budget report, with current costs and a three-year projection of administrative computing expenses, and
   • A brief analysis of the administrative computing project in the context of the New Business Architecture and the UC Davis enterprise portal. Whenever applicable, the analysis should address anticipated impacts on other systems, the campus infrastructure, and users.

   The Project Leaders should submit their reports through their vice chancellors for review by Vice Provost Bruno and Director Loessberg-Zahl. Following IET's technical review and Resource Management and Planning's resource assessment, Council will develop its recommendations of priorities.

   Council identified the need for administrative system owners to cover both short-term (12-18 months) and long-term (3-4 years) needs and projections for this review process.

    
   

3. HIPAA (Health Information Portability and Accountability Act) Regulations

   Rob Drewniak, a Principal in the Arthur Anderson Healthcare Business Consulting Unit, gave the Council an overview of the requirements and content of the regulations implementing HIPAA (Kennedy Kassebaum Act). Rob emphasized the need to involve Campus legal counsel in all questions about the implementation of HIPAA regulations. The PowerPoint slide presentation is posted on the AdC3 Web site.

   Robert Ono, the campus' Security Coordinator, advised the Council that the UC Davis Medical Center has established a contract for a review of its practices, data, and procedures affected by HIPAA. The main campus could extend that contract to review its own activities.

   Council asked several questions regarding the applicability of HIPAA to certain campus programs. The replies focused on the need for Campus legal counsel to be involved to insure compliance. Council also asked about coordination at the UCOP level. Council was advised that such coordination has been occurring with the compliance officers associated with the medical schools. However, there is no joint, university-wide program to address HIPAA compliance

    
   

4. Joint Meeting with the Academic Computing Coordinating Council (AC4)

   Mary Jo Anderson, AdC3 representative on AC4, reported that the Academic Computing Coordinating Council has requested a joint meeting with AdC3 to address the possible continuation of the MyUCDavis project. MyUCDavis is currently a pilot funded with Instructional Technology Funds (ITF). AC4 identified several areas to expand the functionality of MyUCDavis (for more information see the January AC4 minutes). There is considerable interest in new features for faculty, including the ability to check the status of a research grant application. These features have possible overlap with New Business Architecture services. AC4 supports the campuswide implementation of MyUCDavis. IET would provide technical infrastructure support for the portal and various campus units would contribute content.

   Council agreed to hold a joint meeting with AC4. Council asked that the joint meeting be used to consider whether or not the technology applied in the pilot is appropriate for full implementation. Council also wants the issue of a single campus portal to be considered so the needs of the major campus constituent groups (faculty, students, and staff) can be met.

   The Council moved to set up the joint meeting. Chair Smiley requested staff to contact AC4 Chair Plant and organize the joint meeting.