1. Development of a Public Health Communication Portal PH Access Susan Mottice and Jon Reid

2. Epi Communication Need  Need for intra-program communication tool  Issue Tracker  Asynchronous application built 2004 on external server  Works well, high user acceptance  Costly for use outside of program ($6K annually for 200 users)  Original intention to be phased out for UNIS  UNIS  Asynchronous application built 2005 on internal server  Non-intuitive interface, slow user acceptance  Closed source, cost prohibitive to restructure sufficiently to meet Epi communication needs

3. Epi Application Developed  Goals to develop application similar to Issue Tracker with:  High user acceptance  Low cost (internal server)  Expandability to LHD’s  Need a secured location to host this application

4. Public Health Communication Need  SPHERE exercise action items  Better internal communications  Better communications with partners (“External communication needed significant improvement”)  Consider adding asynchronous communication techniques  Over-reliance on time-consuming synchronous communications - conference calls/videoconferencing  COE  Better external communication with clinicians  Asynchronous communication within PH  Clinicians have to learn many website and many passwords to access UDOH programs such as Medicaid, Vital Records, USIIS, Epi, Preparedness, etc.

5. Public health in Utah lacks an Public health in Utah lacks an  Accepted  Secured  Low-cost  Asynchronous communication infrastructure

6. Public Health Infrastructure Development  PH Access  Secured  Open Source  Internal Server  Asynchronous  Application Driven  Website that  Permits internal and external customers to easily access UDOH applications from ONE website using ONE password

7. Related applications grouped for ease of management, access and use Upcoming activities:  Epidemiology  UT-NEDSS (done)  Issue Tracker (done)  IBIS – query module (done)  Electronic Lab Reporting interface  EpiCenter  RODS  Secured email (done)  Survey creator  Project management/ collaboration tool  Preparedness  Volunteer Registry  Web-EOC  City Watch  COOP software  Code Red Tracker  Clinicians  Web-based Reporting (printable CMR)  Germ Watch  Infectious disease listserver  Emergency notifications

8. Marketing  PH Access  Users:  “It’s your way into public health”  Remember one website and one password  Asynchronous, secured interaction with public health  Added value  Developers:  Application developers retain control over their applications and users  Increase acceptance with users