We make good care better
Event Registration - The American Balint Society
Credentialed Leaders' Weekend: Edge Cases
11/8/2024 - 11/9/2024
9:30 AM - 4:30 PM PST

Registration ends on 10/25/2024

Event Description
Course Description: This two-day zoom course qualifies for maintenance of credentialing - satisfying the three-year requirement with this single activity. In addition, 11 hours of APA CE and/or 9 hours of AAFP CME certificates are available. It will begin and end with discussion and feature six Balint groups with intensive-style debriefing after each. Leaders will be assigned for the first Balint Group and all leaders thereafter will be volunteers. We will break out into as many 8-12 person groups as we have registrants for.


Background: ‘Edge case’ is a term that is part of software engineering and mathematics. Its definition in Wikipedia is interspersed below. We are using it as a metaphor to help us imagine what makes our work what it is: What are its limits? Can we define our boundaries? This is not just a matter of appropriate cases to present. We are using the word “case” here to apply more broadly than that.
“An edge case is a problem or situation that occurs only at an extreme (maximum or minimum) operating parameter. For example, a stereo speaker might noticeably distort audio when played at maximum volume, even in the absence of any other extreme setting or condition. “
We are often asked whether someone/a relationship will be too extreme for our work: I am not clinically active; may I attend an intensive? I am a supervisor, but not a clinician; may I present my supervisee relationships? What are your answers? What makes someone/something appropriate (or inappropriate) for Balint work?
“An edge case can be expected or unexpected. In engineering, the process of planning for and gracefully addressing edge cases can be a significant task, and yet this task may be overlooked or underestimated.”
We may stumble on an ‘edge case’ situation when somebody behaves in a way that hampers the group process or when something wholly new to us comes up in a group. What are our tools for handling such unexpected ‘edge cases’?
“Non-trivial edge cases can result in the failure of an object that is being engineered. They may not have been foreseen during the design phase, and they may not have been thought possible during normal use of the object. For this reason, attempts to formalize good engineering standards often include information about edge cases.”
Can we begin to describe ‘edge cases’, i.e. situations beyond the ordinary that may work well enough using our normal processes and situations beyond the ordinary that will not?

Cancellation Policy: Cancellations received by February 14th will be eligible for refunds of minus $50 for administrative costs.