
March 14, 2022
As we head into spring, and with the easing of COVID, team members, physicians and leaders are feeling the growing optimism of a brighter future and continuing TriHealth's journey from Good to Great!
We never lost our passion for making TriHealth the place where team members want to work, physicians want to practice, and the community chooses to receive healthcare. And we never lost sight of investing in each and every team member…and we aren't stopping now.
Between Monday, March 14, and Friday, March 25, you have the opportunity to tell us how we are doing by participating in the 2022 TriHealth Engagement Pulse Survey. In less than five minutes, you can help us continue to make progress on the feedback you gave in August 2021—where we've improved and where we need to continue to focus our efforts.
We Are Making It Easy to Share Your Feedback!
On Monday, March 14, you can access the survey multiple ways:
- Perceptyx, our survey partner, will send a personalized link to the brief, confidential survey to your TriHealth email.
- If you don't access the survey using your personalized link, you can also access the survey by texting 2022PULSE to 22333.
- Don’t want to wait? Click the link to log in to the 2022 TriHealth Engagement Pulse Survey site using your TriHealth employee ID or your Physician/APC NPI number. The link works best if opened in Google Chrome, Microsoft Edge or Safari.
As with every engagement survey, your individual responses remain confidential.
You shared what matters most to you in the comprehensive August 2021 TriHealth Engagement & Safety Survey. This brief Pulse survey allows us to hear from you so we can support you best as we bounce back from multiple COVID surges and get back to business.
Thank you for participating in this quick, convenient survey—working together to remain One Team, TriHealth Strong.
Error rendering this component, check logs for details.
Error rendering this component, check logs for details.