Tea Buzz



Client Spotlight: Community Health Network

Posted February 20, 2018

At Tea Leaves Health, we focus on helping our clients with their strategies, and we love learning more about the people we serve. We frequently feature clients here in our Client Spotlight, so you can learn more about the physician engagement initiatives happening across the country. This month we’re featuring Lyn Reed from Community Health Network. The responses stated here are solely Lyn’s and are not representative of the Community Health Network organization as a whole.

  1. Tell us your title, what organization you work for, a quick description of your role and a little bit about yourself. 

I’m Lyn Reed, Manager of Physician Liaison Services at Community Health Network in Indianapolis, Indiana. Our team of five supports five Hospitals and over 220 sites of service throughout central Indiana. As a seasoned Physician Liaison with over 13 years of experience in the field, I have worked with providers in academic, children’s and community hospital settings. Prior to working as a Physician Liaison, I worked in the managed care insurance industry for over 14 years with organizations in New Jersey, Ohio, Michigan, Washington and Indiana. I am a graduate of Thomas Edison University in Trenton, NJ and a former American Association of Physician Liaisons Board Member (2010-2016).

  1. What would you say is your department’s biggest challenge, and what are you doing to overcome that? 

I think that the diversity of the physician liaison role is a blessing and a curse at the same time. It can be challenging to manage the multiple expectations and communications that are required for team success. We need to be focused and purposeful in the work that we do. Use of a PRM system helps us stay on target and track the work that we do so that we can report our impact back to leadership.

  1. When and why did your organization decide to implement the Physicianology™ solution?

Our organization decided to implement Physicianology in the fall of 2012. At the time, the contact with our existing PRM vendor was expiring and we needed a solution that integrated patient and provider solutions in one package.