Medical Neighbor Project July 15, 2014 Design Team Meeting Record of Learning Project Purpose: Improve referral infrastructure across the medical neighborhood in Greater Columbus Meeting Objectives Provide clarity on the purpose of the Medical Neighborhood Project and the role of the design team. Introduce examples of infrastructure functionality and terminology. Identify the critical components of shared infrastructure for local organizations. Meeting Participants Steve Albanese, Maryhaven Parminder Bajwa, MD, Columbus Neighborhood Health Center Stephanie Baker, Clintonville-Beechwold Community Resource Center David Ciccone, United Way of Central Ohio Neal Edgar, Mental Health America of Franklin County John Gregory, LifeCare Alliance Sherry Inskeep, AIDS Resource Center Ohio Nadia Kasvin, US Together Framing & Purpose
Coordinated by:
Tricia Kincaid, OhioHealth Heather McCormick, LifeCare Alliance Marty Miller, Heart of Ohio Family Health Centers Colleen O’Brien, The Ohio State University Wexner Medical Center Greg Sawchyn, MD, OhioHealth Dana Vallangeon, MD, Lower Lights Christian Health Center Matthew Yannie, United Way of Central Ohio Allan Zaenger, Charitable Pharmacy of Central Ohio
Small Group Work Session After an introduction on the project purpose and framing the opportunity to improve, participants worked in small groups to identify key software functionality needed for shared infrastructure to be successful. Discussion Question: What are the top five pieces of functionality that could be required for successful infrastructure on day one? Functionality Description Small Group Responses Reporting Generate utilization/grant reports. xxxxx Service Eligibility Identify what services patient/client is eligible for. xxxxx Capacity Tracking Ability to identify which organizations/providers have capacity. xxxx Current Services Tracks what services the patient/client is currently receiving. xxx Customized Forms Customize client intake forms to fit the needs of each organization. xxx Limit Client Data Ability to limit access to specific shared client data xx Case Management Develop individualized care plans and set wellness goals x Documents Attach documents to shared client data x Mapping Show location of services on a map. x Record Merge System prompts user to merge shared client data. x Reminders Reminder to follow up with patient/client after referral x Client Photo Ability to add client photo to shared patient data Family Grouping Group patients/clients into families. Medications Ability to track patient/client medications. Messaging Ability to send and receive messages from patients/clients. Patient Portal Provides patients with a portal to access system. Small Group Reflections Ability to broadcast your organization’s capacity to other organizations. Capacity tracking is crucial to assist the expanded Medicaid population in navigating the healthcare system Client consent will need to be addressed. Clients will need to give the organization permission to share their information through this infrastructure. EMR integration would be very nice. Probably not feasible at this time. Important that the infrastructure is device/platform agnostic. Medications can be extremely difficult to track. Maintaining/establishing that database would be very difficult. Next Steps Learning from today will be used to narrow available cloud-based, shared client data referral infrastructure to the top two that fit the needs of the Greater Columbus community.
Scheduled 2014 Meeting Dates and Tentative Topics (All dates from 8:30 – 10:00 AM @ United Way of Central Ohio, Room 300) Aug 19
Sept 16
Demonstrations with top two vendors
Oct 21 Infrastructure selection process
Nov 18
Dec 16
Planning for potential pilot