DOCSLIB.ORG

SEAL Encryption Software

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
SEAL Encryption Software Attachment 9 Adult and Pediatric HIV/AIDS Confidential Case Reports for National HIV/AIDS Surveillance OMB No. 0920-0573 Technical Guidance for HIV/AIDS Surveillance Programs Volume III: Security and Confidentiality Guidelines. Centers for Disease Control and Prevention; 2006. 1 Technical Guidance for HIV/AIDS Surveillance Programs Volume III: Security and Confidentiality Guidelines DEPARTMENT OF HEALTH AND HUMAN SERVICES Centers for Disease Control and Prevention HIV/AIDS Surveillance Guidelines — Security and Confidentiality All material contained in this document is in the public domain and may be used and reprinted without permission; citation of the source is, however, appreciated. Suggested Citation Centers for Disease Control and Prevention and Council of State and Territorial Epidemiologists. Technical Guidance for HIV/AIDS Surveillance Programs, Volume III: Security and Confidentiality Guidelines. Atlanta, Georgia: Centers for Disease Control and Prevention; 2006. The document is available at http://www.cdc.gov/hiv/surveillance.htm. ii January 2006 HIV/AIDS Surveillance Guidelines — Security and Confidentiality Contents — Security and Confidentiality Introduction ........................................................................................................ 1-1 Existing Protections............................................................................................ 1-1 Purpose of Guidelines........................................................................................ 1-2 Policies............................................................................................................... 1-5 Scope............................................................................................................. 1-2 Requirements and Standards ........................................................................ 1-3 Guiding Principles.......................................................................................... 1-4 Responsibilities .................................................................................................. 1-9 Training .............................................................................................................1-11 Physical Security...............................................................................................1-11 Data Security.................................................................................................... 1-13 Data Movement ........................................................................................... 1-14 Sending Data to CDC .................................................................................. 1-17 Transferring Data between Sites ................................................................. 1-18 Local Access................................................................................................ 1-18 Central, Decentral, and Remote Access...................................................... 1-22 Security Breaches............................................................................................ 1-23 Laptops and Portable Devices ......................................................................... 1-24 Removable and External Storage Devices....................................................... 1-26 Attachment A.................................................................................................... 1-27 Attachment B.................................................................................................... 1-33 Attachment C ................................................................................................... 1-39 Attachment D ................................................................................................... 1-41 Attachment E.................................................................................................... 1-43 Attachment F.................................................................................................... 1-51 Attachment G ................................................................................................... 1-69 Attachment H ................................................................................................... 1-81 January 2006 iii HIV/AIDS Surveillance Guidelines — Security and Confidentiality Notes ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ iv January 2006 HIV/AIDS Surveillance Guidelines — Security and Confidentiality Contributors This document, Technical Guidance for HIV/AIDS Surveillance Programs, was developed by the HIV Incidence and Case Surveillance Branch of the Division of HIV/AIDS Prevention, National Center for HIV, STD, and TB Prevention, Centers for Disease Control and Prevention in collaboration with the Council of State and Territorial Epidemiologists. The CDC/CSTE Advisory Committee provided oversight and leadership throughout the entire process. Workgroup contributors consisted of state and local health department representatives. Irene Hall, CDC, and Eve Mokotoff, CSTE, led the development. Members of the CDC/CSTE Advisory Committee CDC: Pamela Gruduah, Irene Hall, Martha Miller CSTE: Gordon Bunch, California; Dena Ellison, Virginia; Jim Kent, Washington; Eve Mokotoff, Michigan; Stanley See, Texas Chairs of Workgroups, CDC Michael Campsmith, Data Analysis and Dissemination Sam Costa, Security and Confidentiality Irene Hall, Data Quality Laurie Kamimoto, Electronic Reporting Lata Kumar, Data Dictionary Martha Miller, Overview Kathleen McDavid, HIV Risk Factor Ascertainment Ruby Phelps, Case Residency Assignment Richard Selik, Death Ascertainment Richard Selik, Record Linkage Suzanne Whitmore, Perinatal and Pediatric Case Surveillance CDC Contributors Lori Armstrong, Mi Chen, Betsey Dunaway, John Gerstle, Kate Glynn, Irene Hall, Felicia Hardnett, David Hurst, Jennie Johnston, Danielle Kahn, Tebitha Kajese, Laurie Kamimoto, Kevin Lyday, Martha Miller, Andy Mitsch, Michelle Pan, Richard Selik, Amanda Smith, Damien Suggs, Patricia Sweeney, Kimberly Todd, Will Wheeler, Suzanne Whitmore, Irum Zaidi. State and Local Health Department Contributors and Reviewers Alabama: Anthony Merriweather, Danna Strickland; California-Los Angeles: Gordon Bunch, Mi Suk Harlan, Virginia Hu, Ann Nakamura; California-San Francisco: Ling Hsu, Maree Kay Parisi, Sandra Schwarcz; District of Columbia: Gail Hansen, Kompan Ngamsnga; Florida: Becky Grigg, Lorene Maddox; Illinois-Chicago: Margarita Reina; Indiana: Jerry Burkman; Iowa: Randy Mayer; Louisiana: Joseph Foxhood, Greg Gaines, William Robinson, Debbie Wendell, Amy Zapata; Massachusetts: Maria Regina Barros; January 2006 v HIV/AIDS Surveillance Guidelines — Security and Confidentiality Michigan: Elizabeth Hamilton, Nilsa Mack, Eve Mokotoff, Yolande Moore; Minnesota: Luisa Pessoa-Brandao, Tracy Sides; New Hampshire: Chris Adamski; New Jersey: Wogayehu Afework, Linda Dimasi, Abdel Ibrahim, John Ryan; New York City: Melissa Pfeiffer, Judy Sackoff; New York State: Alexa Bontempo, Kathleen Brousseau, Donna Glebatis; Ohio: Sandhya Ramachandran; Oklahoma: Mark Turner; Pennsylvania: Bonnie Krampe, Ming Wei; South Carolina: Dana Giurgiutiu; Texas: Thomas Barnabas, Dianna Highberg, Roy Reyna, Stanley See, Jan Veenstra; Virginia: Dena Ellison; Washington: Maria Courogen; Washington-Seattle & King County: Amy Bauer, Jim Kent; Wisconsin: Loujean Steenberg. vi January 2006 HIV/AIDS Surveillance Guidelines — Security and Confidentiality HIV/AIDS Surveillance Guidelines — Security and Confidentiality Introduction This document supersedes the October 1998 version of “Guidelines for HIV/AIDS Surveillance, Appendix C: Security and Confidentiality.” It reflects CDC's recommendation as best practices for protecting HIV/AIDS surveillance data and information. It details program requirements and security recommendations. These requirements, recommendations, and practices are based on discussions with HIV/AIDS surveillance coordinators, CDC’s Divisions of STD Prevention and TB Elimination, and security and computer staff in other Centers and Offices within CDC, and on reviews by state and local surveillance programs. This document requires each cooperative agreement grantee to designate an Overall Responsible Party (ORP). The ORP will have the responsibility for the security of the surveillance system (including processes, data, information, software, and hardware) and may have liability for any breach of confidentiality. The ORP should be a high-ranking public health official. This official should have the authority to make decisions about surveillance operations that may affect programs outside of HIV/AIDS
Load more

Recommended publications
  • ¿Qué Es El Software Libre?
    ¿Qué es el software libre? Prof. Virginia Álvarez ¿Qué es el software libre? Con software libre nos referimos a la libertad de los usuarios para ejecutar, copiar, distribuir, estudiar, cambiar y mejorar el software. Nos referimos especialmente a cuatro clases de libertad para los usuarios de software: ¿Qué es el software libre? ● "libertad 0", ejecutar el programa con cualquier propósito (privado, educativo, público, comercial, militar, etc.) ● "libertad 1", estudiar y modificar el programa (para lo cual es necesario poder acceder al código fuente) ● "libertad 2", copiar el programa de manera que se pueda ayudar al vecino o a cualquiera ● "libertad 3", Mejorar el programa y publicar las mejoras Pero… ¿qué es el código fuente? ¿qué es el código fuente? ¿Qué es el software libre? La ambigüedad de “free” El término original en inglés para ‘programas libres’ es free software. Sin embargo, en inglés el término free además de ‘libre’ significa ‘gratis’, lo que genera gran confusión. Por ello a menudo en inglés se toman prestadas palabras españolas y se habla de ‘libre software’, en contraposición a ‘gratis software’, al igual que nosotros tomamos prestada la palabra software. Terminología a tener en cuenta… Terminología – Software Libre El Open Source es una organización que se encarga de fomentar el uso de sistemas de código abierto, concepto significativamente diferente del de Software Libre. Un sistema de código abierto no necesariamente tiene que estar regido bajo la Licencia Pública General, sino que puede estar regido por alguna de las tantas licencias de la Iniciativa Open Source (www.opensource.org). Uno de los fundadores de esta iniciativa es Eric Raymond, famoso hacker del mundo de GNU/Linux.
    [Show full text]
  • Introducción Definiendo Algunos Malvare
    Computación / enfermería /UNPA Software malintencionado e infeccioso Introducción Los virus informáticos son un tipo de programa malicioso (malware). El término virus informático suele aplicarse de forma incorrecta para referirse a todos los tipos de malware, incluidos los virus verdaderos1. Por lo que en la actualidad sería más correcto mejor usar el término MALWARE en el momento de referirse a cualquier código malicioso (parásito/infección). Malware - malicious software - software malicioso - también llamado badware, código maligno, o software malintencionado. Es un tipo de software que tiene como objetivo infiltrarse o dañar una computadora o sistema de información sin el consentimiento de su propietario. El software se considera malware en función de los efectos que provoque en un computador. En sí, el término malware es muy utilizado por profesionales de la informática para referirse a una variedad de software hostil, intrusivo o molesto. Debe aclararse que Malware no es lo mismo que software defectuoso (este último contiene bugs2 peligrosos, pero no de forma intencionada). En el mundo de los Malware encontramos nombres como Virus, Troyanos(Trojans), Gusanos (Worm), y Spywares, pero también ha habido una evolución de como los conocíamos, surgiendo nuevos integrantes como Rootkits (la mayor parte), ladrones de los Troyanos Bancarios, secuestradores de PCs (Botnets), "Falsos Antivirus" (Rogues), FakeAVs, Keyloggers, Ransomwares, Adware intrusivo, Hijackers, Bootkits, Scareware, Crimeware y otros software malicioso e indeseable que no dejarán de salir. Si se trata de clasificar, los Malware podría tenerse los siguientes grandes grupos: el Malware infeccioso, el Malware oculto y el Malware para obtener beneficios. El Malware infeccioso incluye a los virus y gusanos.
    [Show full text]
  • Information Technology Survey Report
    Information Technology Survey Report For the Turning Point National Excellence Collaborative for Information Technology January 2003 Michael Burke W. Douglas Evans American Institutes for Research Funding for this research has been obtained from the Robert Wood Johnson Foundation Information Technology Survey Report Introduction The year 2001 was a watershed year for public health. Due to the tragic terrorist attacks of September 11th and the subsequent anthrax attacks through the U.S. Postal Service, the public has an increased focus on public health and has recognized the need for effective and efficient functioning at national and local levels. Even before the events of 2001, however, information technology and its key role in the nation’s public health infrastructure were receiving national attention. Healthy People 2010 devotes much of Chapter 23, Public Health Infrastructure, to information systems, data collection, and data management. Healthy People 2000 also placed a great deal of emphasis on data and surveillance, but did not specifically focus on the infrastructure requirements underpinning its objectives. Public health departments, like most government offices, have tended to lag behind industry in adopting the most current technology. Financial constraints, limited technical expertise, and the independent and sometimes territorial nature of local and State health departments have limited health department adoption of new technology. This independence may have resulted in less information and resource sharing and therefore a duplication of efforts and lack of synergy in developing and implementing public health software technology. Further impacting information technology use in health departments is a perceived shortage of specialized products. This limited number of software applications specifically designed for public health is the result of a lack of 1 Information Technology Survey Report content expertise and perceptions of a limited market on the part of software developers.
    [Show full text]
  • STATE of CONNECTICUT INFORMATION and TELECOMMUNICATIONS STRATEGIC PLAN for FISCAL YEAR 2021 September 15, 2020
    State of Connecticut IT Strategic Plan for Fiscal Year 2021 STATE OF CONNECTICUT INFORMATION AND TELECOMMUNICATIONS STRATEGIC PLAN FOR FISCAL YEAR 2021 September 15, 2020 Pursuant to C.G.S. § 4d-7 as amended by P.A. 14-202, this plan provides an overview of State agency efforts to improve government efficiency through the use of technology. This plan reflects enterprise and agency efforts and includes special attention to eGovernment initiatives to put more government services online. Prepared by: Chief Information Officer Mark Raymond Department of Administrative Services Bureau of Enterprise Systems and Technology (860) 622-2419 [email protected] Page 1 of 174 State of Connecticut IT Strategic Plan for Fiscal Year 2021 Contents FY 2021 Information Technology Strategy .................................................................................. 4 Statement of Vision for Technology ......................................................................................................... 4 Background ............................................................................................................................................... 4 Current Technology Assessment .............................................................................................................. 5 FY 2021 Strategy ....................................................................................................................................... 8 Statutory Basis .......................................................................................................................................
    [Show full text]
  • Enisa Threat Landscape for 5G Networks
    ` ENISA THREAT LANDSCAPE FOR 5G NETWORKS Threat assessment for the fifth generation of mobile telecommunications networks (5G) NOVEMBER 2019 0 ENISA THREAT LANDSCAPE FOR 5G NETWORKS 5G TL | 1.0 | External | NOVEMBER 2019 ABOUT ENISA The European Union Agency for Cybersecurity (ENISA) has been working to make Europe cyber secure since 2004. ENISA works with the EU, its member states, the private sector and Europe’s citizens to develop advice and recommendations on good practice in information security. It assists EU member states in implementing relevant EU legislation and works to improve the resilience of Europe’s critical information infrastructure and networks. ENISA seeks to enhance existing expertise in EU member states by supporting the development of cross- border communities committed to improving network and information security throughout the EU. Since 2019, it has been drawing up cybersecurity certification schemes. More information about ENISA and its work can be found at www.enisa.europa.eu. EDITORS Marco Lourenço, Louis Marinos, ENISA CONTACT For contacting the authors please use [email protected] For media enquiries about this paper, please use [email protected]. ACKNOWLEDGEMENTS We would like to thank the members of the 5G Threat Analysis Expert Group, Ioannis Askoxylakis, Pascal Bisson, Jean-Philippe Wary, Panagiotis Papadimitratos and Jorge Cuellar for supporting the ENISA team in information collection, knowledge transfer in the subject matter and revision of interim drafts of this report. LEGAL NOTICE Notice must be taken that this publication represents the views and interpretations of ENISA, unless stated otherwise. This publication should not be construed to be a legal action of ENISA or the ENISA bodies unless adopted pursuant to the Regulation (EU) No 2019/881.
    [Show full text]
  • National HIV Behavioral Surveillance Among Men Who Have Sex With
    National HIV Behavioral Surveillance System: Heterosexuals at Increased Risk of HIV (NHBS-HET2) Model Surveillance Protocol Behavioral Surveillance Team NCHHSTP/DHAP-SE/BCSB Version: February 5, 2010 ACKNOWLEDGEMENTS These national protocol guidelines for NHBS-HET2 were written by staff of the Behavioral Surveillance Team, Behavioral and Clinical Surveillance Branch (BCSB), Division of HIV/AIDS Prevention—Surveillance and Epidemiology, National Center for HIV, Viral Hepatitis, STD, and TB Prevention, Centers for Disease Control and Prevention. Prepared by employees of the federal government as part of their official duties, the national HIV behavioral surveillance guidelines is part of the public domain and is not copyright protected under Title 17 of the United States Copyright Code. These protocol guidelines may be copied and shared with others without CDC approval. CONTACTS For inquires about this protocol or the National HIV Behavioral Surveillance System (NHBS), contact the following CDC staff: Protocol Paul Denning, MD Epidemiologist Centers for Disease Control and Prevention 1600 Clifton Rd, Mailstop E-46 Atlanta, Georgia 30333. Telephone: 404.639.2963; E-mail: [email protected] Teresa Jacobs Finlayson, PhD MPH Epidemiologist Centers for Disease Control and Prevention 1600 Clifton Rd, Mailstop E-46 Atlanta, Georgia 30333. Telephone: 404.639.2083; E-mail: [email protected] Isa J. W. Miles, ScD MS Behavioral Scientist Centers for Disease Control and Prevention 1600 Clifton Rd, Mailstop E-46 Atlanta, Georgia 30333. Telephone: 404.639.6304; E-mail: [email protected] NHBS General Inquiries Elizabeth A. DiNenno, PhD Team Leader (Acting), Behavioral Surveillance Centers for Disease Control and Prevention 1600 Clifton Rd, Mailstop E-46 Atlanta, Georgia 30333.
    [Show full text]
  • Computación / Enfermería /UNPA Compilador: Bertha López Azamar
    Computación / enfermería /UNPA Algunos términos relacionados con los tipos de licencias de software: Abandonware: Abandon = abandonado, ware=software. Software abandonado. Un producto de software, por lo general videojuegos, que ya no son comercializados por sus fabricantes o ya no poseen derechos de copyright generalmente por tratarse de programas antiguos.Existen cientos de sitios dedicados a coleccionar este tipo de programas especialmente con fines nostálgicos. Por lo general se exceden en la definición de abandonware y ponen a disposición juegos y programas antiguos que aún tienen derechos de copyright. Adware -Advertising-Supported software - Programa Apoyado con Propaganda: se trata de programas creados para mostrarnos publicidad. Los Adwares se dedican a mostrarnos publicidades en los programas que estos vienen incluidos por medios de banners en estos, pero ya los más peligrosos nos van a abrir ventanitas pop-ups por todas partes, van a agregar direcciones en los favoritos del IE y van a instalarnos barras de herramientas con el único objetivo de que naveguemos siempre dentro de sus redes de publicidad. (Algunos programas que incluyen Adwares: Alexa, MyWebSearch, FlashGet, Cydoors, Gator, GoHit, Webhancer, Lop, Hotbar, eZula, KaZaa, Aureate / Radiate, RealPlayer, Zango, C2Media, CID, Messenger Plus) Beerware (Beer = cerveza, ware = software). Es un término de licencia de software otorgado bajo términos muy libres. Provee al usuario final el derecho a un programa particular, si el usuario considera el software útil, se le exhorta a comprarle al autor una cerveza "para devolver el favor". Es un término en broma utilizado para designar aquellas aplicaciones que pueden ser compradas si se le compra una cerveza a su autor (o, en otra variante, se bebe una cerveza en nombre de este).
    [Show full text]
  • Automated Malware Analysis Report for KIX32.EXE
    ID: 111362 Sample Name: KIX32.EXE Cookbook: default.jbs Time: 10:11:50 Date: 19/02/2019 Version: 25.0.0 Tiger's Eye Table of Contents Table of Contents 2 Analysis Report KIX32.EXE 4 Overview 4 General Information 4 Detection 4 Confidence 4 Classification 5 Analysis Advice 5 Mitre Att&ck Matrix 6 Signature Overview 6 Spreading: 6 Key, Mouse, Clipboard, Microphone and Screen Capturing: 6 Spam, unwanted Advertisements and Ransom Demands: 6 System Summary: 6 Data Obfuscation: 7 Persistence and Installation Behavior: 7 Hooking and other Techniques for Hiding and Protection: 7 Malware Analysis System Evasion: 7 Anti Debugging: 7 HIPS / PFW / Operating System Protection Evasion: 7 Language, Device and Operating System Detection: 7 Remote Access Functionality: 7 Behavior Graph 7 Simulations 8 Behavior and APIs 8 Antivirus Detection 8 Initial Sample 8 Dropped Files 8 Unpacked PE Files 8 Domains 8 URLs 8 Yara Overview 9 Initial Sample 9 PCAP (Network Traffic) 9 Dropped Files 9 Memory Dumps 9 Unpacked PEs 9 Joe Sandbox View / Context 9 IPs 9 Domains 9 ASN 9 JA3 Fingerprints 9 Dropped Files 9 Screenshots 9 Thumbnails 9 Startup 10 Created / dropped Files 10 Domains and IPs 11 Contacted Domains 11 Contacted IPs 11 Static File Info 11 General 11 File Icon 11 Static PE Info 11 General 11 Entrypoint Preview 12 Rich Headers 12 Data Directories 12 Sections 13 Copyright Joe Security LLC 2019 Page 2 of 16 Resources 13 Imports 13 Version Infos 14 Possible Origin 14 Network Behavior 14 Code Manipulations 14 Statistics 14 Behavior 14 System Behavior 15 Analysis
    [Show full text]
  • Introduction to Free Software, February 2008
    Free Software Jesús M. González-Barahona Joaquín Seoane Pascual Gregorio Robles PID_00148386 GNUFDL • PID_00148386 Free Software Copyright © 2010, FUOC. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License" GNUFDL • PID_00148386 Free Software Index 1. Introduction........................................................................................ 9 1.1. The concept of software freedom.................................................. 9 1.1.1. Definition ....................................................................... 10 1.1.2. Related terms ................................................................. 11 1.2. Motivations ................................................................................. 12 1.3. The consequences of the freedom of software ........................... 12 1.3.1. For the end user ............................................................ 13 1.3.2. For the public administration ....................................... 14 1.3.3. For the developer ........................................................... 14 1.3.4. For the integrator .......................................................... 15 1.3.5. For service and maintenance providers ......................... 15 1.4. Summary ....................................................................................
    [Show full text]
  • …It's Full of Scripts
    KiXtart 2010 1 KiXtart 20 10 (version 4.51) …It’s full of scripts... Contents Introduction 3 What’s New 3 KiXtart: Do You Care? 6 System Requirements 10 System Requirements 11 KiXtart 2010 Files 11 Installing KiXtart 11 To install KiXtart on the network 12 To install KiXtart on a client 12 Required files for Windows NT/2000/XP Clients 12 Required files for Windows 9x Clients 12 Uninstalling KiXtart 12 Updating from previous versions 12 Running KiXtart 13 Running KiXtart from a Batch File 14 Pre-tokenizing scripts 15 Locating Files 16 Troubleshooting KiXtart 16 Introduction 16 Common issues 16 Debug mode 18 Miscellaneous… 18 KiXtart and the console 18 COM automation in KiXtart 2010 19 Group-membership information. 21 General Syntax Rules 23 Block Commenting 23 Dynamic Program Variables 24 Expressions 27 KiXtart Command Reference 31 2 KiXtart 2010 KiXtart Function Reference 53 KiXtart Macro Reference 113 APPENDIX A: KiXtart on Windows 9x 117 Thunking and the KiXtart RPC Service 117 Choosing Where to Install the KiXtart RPC Service 117 To install the KiXtart RPC service 119 Updating the KiXtart RPC service 119 Starting the KiXtart RPC Service 120 Known Problems of KiXtart on Windows 9x 120 The ‘MAP ROOT’ issue. 121 Running KiXtart with Lmscript Emulation 122 APPENDIX B: Error handling 124 Where to find more information 125 Acknowledgements 126 About KiXtart 127 Disclaimer and distribution information. 127 KiXtart 2010 3 Introduction KiXtart is a logon script processor and enhanced batch scripting language for computers running Windows Vista, Windows Server 2003, Windows XP, Windows 2000, Windows NT or Windows 9x in a Windows Networking environment.
    [Show full text]
  • IT Assessment and Strategic Plan
    CHICAGO 2021 IT Strategic Plan Our Vision Vision Executive Summary Goals & Key Initiatives Additional Information About the IT Strategic Plan Implementation Roadmaps The 2021 IT Strategic Plan upholds the City’s technology vision to fuel inclusion, engagement and innovation from an inside-out perspective. While the City has made great progress towards achieving this technology Initiative Details vision, the City’s modernization efforts continue to be hindered by paper-based processes, aging legacy systems, and a dwindling IT workforce. This plan is focused on the set of initiatives needed to strengthen the City’s core capabilities with the end result of equitable, responsive technology services for all Chicagoans. 1 CHICAGO 2021 IT Strategic Plan Executive Summary Vision The City of Chicago has high ambitions for technology, viewing it as a key enabler to fuel inclusion, employee and resident engagement, innovation, and opportunities to improve the quality of life for all Chicagoans. Over the past year, City staff has leveraged technology to live up to these ambitions by: ExecutiveExecutive SummarySummary ▪ Rapidly pivoting to remote work (within 3 days). ▪ Expanding online/digital options for government services (e.g., applications for outdoor dining permits, affordable housing Goals & Key Initiatives applications, permit submissions, etc.). ▪ Mobilizing census outreach to underserved communities through WiFi equipped vans & iPads. ▪ Facilitating more equitable services through an improved translation web experience and continued expansion of its modern, robust CHI 311 platform that enables Chicagoans to request City services. The City also continues to make progress in improving data accessibility and transparency, and building a more sustainable Additional Information infrastructure, including: ▪ Publishing 742 datasets on the open data portal comprising business licenses, crime, food inspections, environmental data, etc.
    [Show full text]
  • Academic Catalog & Student Handbook 2019-2020
    UNIVERSITY CATALOG & STUDENT HANDBOOK 2019-2020 University Catalog & Student Handbook 2019-2020 Kansas City University of Medicine and Biosciences This catalog and student handbook is an official bulletin of Kansas City University of Medicine and Biosciences (KCU) and is intended to provide general information. The document contains policies, regulations, procedures and fees effective July 1, 2019. The University reserves the right to make changes at any time to reflect current board policies, administrative regulations and procedures, amendments by state law and fee changes. Information provided in this document is subject to change without notice and does not constitute a contract between KCU and a student or an applicant for admission. The institution is not responsible for any misrepresentation or provisions that may arise as a result of errors in preparation. Students are responsible for observing any policies or regulations contained herein or in the online policy library; therefore, they must read this document carefully. This document does not contain all institutional rules, regulations or policies for which students are responsible. Other University sources discuss expectations for and policies applicable to students: the Clinical Education (CE) Clerkship Guidelines and the University’s Intranet- based policy library. The current electronic copies of these publications, as well as other University policies, can be obtained at the University’s intranet-based policy library. Note: Printed versions may not be current; the electronic
    [Show full text]