Medical Neighbor Project September 16, 2014 Design Team Meeting Record of Learning Project Purpose: Improve referral infrastructure across the medical neighborhood in Greater Columbus Meeting Objectives Introduce examples of infrastructure functionality and terminology. Introduction to the functionality of cloud-based, shared client data infrastructure: Apricot Meeting Participants Stephanie Baker, Clintonville-Beechwold Community Resource Center David Ciccone, United Way of Central Ohio Neal Edgar, Mental Health America of Franklin County Mariellyn Grace, The Charitable Pharmacy of Central Ohio John Gregory, LifeCare Alliance Isi Ikharebha, Physicians CareConnection Sherry Inskeep, AIDS Resource Center Ohio Tricia Kincaid, OhioHealth
Loraine Maguire, The OhioHealth Group Heather McCormick, LifeCare Alliance Colleen O’Brien, The Ohio State University Wexner Medical Center Christine Patella, The Breathing Association Lauren Paluta, United Way of Central Ohio Greg Sawchyn, MD, OhioHealth Dana Vallangeon, MD, Lower Lights Christian Health Center Greg Whisman, MD, The Medical Group of Ohio Matthew Yannie, United Way of Central Ohio
Framing & Purpose
Critical functionality of shared infrastructure identified by design team during July meeting.
Coordinated by: Introduction
to the
functionality of cloud-based, shared client data infrastructure: Apricot After a brief framing of the session’s purpose, participants were taken through a product demonstration for Apricot. Additional information can be found here: http://www.communitytech.net/solutions/apricot Key observations from Apricot demonstration:
Clients are able to access public web forms to request appointments with agencies. Customized referral forms based on the needs of individual organizations. o Ability to include a case note for the referral via a secure portal. o Provides the ability to attach documents and pictures to each referral. Currently are working with a group of domestic violence agencies to create a portal that offers capacity tracking. Each organization would spend time with the vendor to create a customized process that aligns with current workflows. Process typically takes 30 – 90 days. Offers a platform that can be highly customized based on the needs of the participating organizations. Offers a wide array of reporting capabilities. Product could be set up to be managed by a single entity, or controlled by each participating organization. Provides organizations with the opportunity to set limits on what employees are able to view. o Able to limit agency permissions for individual clients so that sensitive data is not shared with unintended organizations.
Design team reflections: Apricot seems to be more focused on individual organizations managing their data, and ClientTrack dealt more with the referral process between organizations. Felt it was helpful to have a representative from ClientTrack in the room vs a presenter over the phone. Would be helpful to have each vendor provide an example of how their process works in the same scenario. Next Steps During the next meeting the design team will be introduced to an referral product offered by OHIP. Beginning in November meeting participants will select potential infrastructure through a collaborative process, and plan for next steps.
Scheduled 2014 Meeting Dates and Tentative Topics (All dates from 8:30 – 10:00 AM @ United Way of Central Ohio, Room 300) Oct 21
November and Beyond
Demonstration with OHIP (Ohio Health Information Partnership)
Infrastructure selection process and planning for potential pilot