Jon Reid, MBA, Susan Mottice, PhD, Theron Jeppson, MEd, Richard Kurzban, Wu Xu, PhD Developing an...
-
Upload
helen-hall -
Category
Documents
-
view
212 -
download
0
Transcript of Jon Reid, MBA, Susan Mottice, PhD, Theron Jeppson, MEd, Richard Kurzban, Wu Xu, PhD Developing an...
Jon Reid, MBA, Susan Mottice, PhD, Theron Jeppson, MEd, Richard
Kurzban, Wu Xu, PhD
Developing an Open Source Developing an Open Source Asynchronous Communication Asynchronous Communication Framework for Public HealthFramework for Public Health
- PHAccess- PHAccess
2
AgendaAgenda
• Problems with communication in Public Health
• Need for an Open Source Framework• Solution – PHAccess• Next Steps
3
Problems with CommunicationProblems with Communication
• 2007 SPHERE action items:– Better internal communications– Better communications with partners– Consider adding asynchronous communication
techniques
• Synchronous communication too costly and time consuming
4
Communication SurveyCommunication Survey
• Conducted Dec 2008 – Jan 2009 – The value of sharing information– Identifying barriers that exist that may
prevent them from receiving/sharing information
– Satisfaction levels with current communication processes
– Preferred communication methods for the receiving/sharing of information
5
Survey Results (n=52)Survey Results (n=52)
Preferred method of communication
23%
61%
12%
2%
2%
Secure Web-Site
Phone Call
Fax
Video Conference
67% 33%
Preference for staying informed on routine communicable disease issues
Own Time Personal Interaction
6
Need for Open Source FrameworkNeed for Open Source Framework
• Length of time to develop and implement software
• Most software applications have redundant code (Authentication, UI)
• Hard to build user base• High cost of implementation• Users don’t want another username
and password
7
Solution - PHAccessSolution - PHAccess
• Secured Web-Site• Able to host secure applications• Portal to public health information• Allows secure asynchronous
communication within public health and external users
• Single sign-on using the Utah Master Directory
• Gives autonomy to users (Web 2.0)
8
PHAccess DevelopmentPHAccess Development
• Collaboration of Public Health Workers, Clinicians, IT, Informaticists
• Used modified Agile/RAD methodology
• Built using Open Source tools and resources
• Released to local and state public health and clinical workers
9
Open Source Tools UsedOpen Source Tools Used
• Linux (SUSE)• Apache 2.0• PHP v. 4.4.9• MYSQL v. 4• TinyMCE• YUI Tools 2.5• PHPMailer
10
PHAccess Building BlocksPHAccess Building Blocks
Utah Master Directory
Application Level Security User Level Security
Auditing Logs
Custom Applications Core Applications
Web Services Secure Messaging File Library
Shared Calendaring Project WikiElectronic Messaging
11
Application TypesApplication Types
• Core Applications– Messaging– Calendar– Contacts– Wiki– File Library– User Management– Project
Management
• Secure Applications– Issue Tracker– UT-NEDSS– Newborn Screening– Clinical Apps– ELR
12
PHAccess Application FrameworkPHAccess Application Framework
Authentication User Interface
Utah Master Directory
Group Membership
Application Security
File Repository
HL7 Messaging
Application Data
Common Menu
Seamless Integration
Functions and Classes
Custom Application
Data Interfaces
Authorization
13
PHAccess Application FrameworkPHAccess Application Framework
Authentication User Interface
Utah Master Directory
Group Membership
Application Security
File Repository
HL7 Messaging
Application Data
Common Menu
Seamless Integration
Functions and Classes
Custom Application
Data Interfaces
Authorization
19
PHAccess Application FrameworkPHAccess Application Framework
Authentication User Interface
Utah Master Directory
Group Membership
Application Security
File Repository
HL7 Messaging
Application Data
Common Menu
Seamless Integration
Functions and Classes
Custom Application
Data Interfaces
Authorization
20
Example of Data Interfaces
HL7
PHAccess
Lab LIMS Database
Secure PHI Database
Authorized User
Lab Result Application
Lab Results/Information Stored
ELR
Internet
21
Case StudyCase Study
• Needed to transmit lab test results to Epi through a secure method
• Easy to manage user rights through PHAccess application manager
• Fast turn around time• Allows users to create custom
queries
22
PHAccess Application FrameworkPHAccess Application Framework
Authentication User Interface
Utah Master Directory
Group Membership
Application Security
File Repository
HL7 Messaging
Application Data
Common Menu
Seamless Integration
Functions and Classes
Custom Application
Data Interfaces
Authorization
23
User Interface
• Common Interface– Shared Menu, layout
• Seamless Integration– Hosted or external application– Portal of applications
• Functions/Classes– Auditing, File storage/retrieval– Secure Messaging
25
Secure Message ProcessSecure Message Process
Send email to external email
address
Email Contains PHI?
Store secure email in
PHAccess
Send email to recipient with link to secure email
Recipient logs into PHAccess using UMD
credentials
Sender Creates Email
No
Yes
26
Case Study
• PHAccess messaging used during H1N1 outbreak
• Easy group creation and management
• Send secure and insecure messages• Clinical Infection Preventionists (IP)
sending reports to state and local departments
• Reduces number of faxes and increase turn-around-time
28
Next StepsNext Steps
• Increase Clinical User Base– ELR– Clinical Web-Based Reporting (CMR)
• Roll out PHAccess to other agencies– EMS/Preparedness– LHD/Environmental Reporting
• Develop Open Source Community– COP– Facilitate Adoption
29
For More InformationFor More Information
• Office of Public Health Informatics– http://health.utah.gov/phi/phaccess
• PHAccess Demo/Code– http://
www.rockymountaincoe.org/phaccess
• Contact– Jon Reid – [email protected]