Embedded Files
Our Community
Our Community
Locally owned and nationally grown. Each Public Health Authority (PHA) who is a member of the consortium owns their own instance of each application. The Consortium is a gathering place for these users to come together and collaborate for continuous improvement of the open-source suite. 19 Public Health Authorities are currently active in the Consortium; 9 active contributors and 10 others at different stages of investigation and implementation. We also have affiliate members including professional public health partners, foundations, vendors, and others.
Our Approach
Our Approach
The consortium model is the secret sauce of PHAST. Centered on collaboration and customization, the growth potential is limitless. Each participating jurisdiction has their own tailored instance with unlimited access to an ever improving foundation.
In an era where the most valuable commodity in public health is cost savings and sustainability, the Public Health Applied Surveillance Tools (PHAST) Consortium provides an innovative solution; an open source disease surveillance software suite designed and governed by public health for public health.
Affiliate Contributing Organization
Affiliate Contributing Organization
These organizations are not public health authorities and do not have a live implementation of any of the applications in the suite. They are vendors, foundations, private companies, professional public health organization, and other partners. They attend meetings and can make contributions to the consortium.
Community Member Organization
Community Member Organization
Organizations that do not participate at the level of a contributor but have access to the code repository and the consortium documentation. These organizations are typically investigating or interested in the products offered by the consortium. They attend meetings but do not contribute code.
Contributing Organization
Contributing Organization
Contributing organizations must be a public health authority. An organization must sign the Contributor License Agreement in order to be a contributor. They have an active instance of at least one application or are implementing one. They contribute code, documentation, and other training materials.
Meet with us
Annual Meeting
Attendees: representatives from consortium members including community member, contributors, and non-implementing contributors
Purpose: three day peer-to-peer conference
Frequency: annually in September
User Collaboration and Learning
User Collaboration and Learning
Attendees: All consortium members, vendors, and investigating entities
Purpose: peer-to-peer collaboration and learning, troubleshooting, Q&A, idea generation, and coordination
Frequency: weekly on Wednesday at 2:00 pm Mountain Time
Technical
Attendees: code contributors, data scientists, informaticists, programmers, etc. from all consortium members, vendors, and investigating entities
Purpose: peer-to-peer technical collaboration and learning, troubleshooting, Q&A, idea generation, and coordination
Frequency: bi-weekly on Monday at 9:30 am Mountain Time
Managers Meeting
Attendees: Release managers and product managers; public health representatives from each contributor jurisdiction with full authority to represent the jurisdiction in decision making process
Purpose: focus on coordinating technical and strategic aspects of feature releases. Review, vote, and make final decisions on system changes.
Frequency: bi-weekly on Monday (off weeks of technical meeting) at 1:00 pm Mountain Time
Voting Meeting
Attendees: Product Managers only; public health representatives from each contributor jurisdiction with full authority to represent the jurisdiction in decision making process
Purpose: Voting session to finalize decisions for the consortium
Frequency: Once a month on the last Wednesday of the month
Work Groups
Attendees: any consortium members, vendors, and investigating entity members interested in the specific work group topic area
Purpose: address specific issues, learning opportunities, functions, or feature of any of the products in the software suite
Frequency: ad hoc; meet as deemed necessary by work group co-chairs and agreed upon by work group membership
Looking for a one on one? Email us at
PHASTconsortium@gmail.com
Page updated
Google Sites
Report abuse