Emergency medicine is fast, probabilistic, and unforgiving, and when things go wrong, the legal scrutiny can be intense. In Episode 19 of the Expert Witness Playbook, Dr. Brian Woodruff sits down with Dr. Joshua Feblowitz, an emergency medicine physician, clinical leader, and expert witness based in Maryland, to unpack what makes EM litigation uniquely complex.
Dr. Feblowitz brings an unusual combination of credentials to this conversation: Harvard Medical School, residency at Mass General Brigham, a Master’s in Science Writing from MIT, and two years of growing expert-witness practice. Together, he and Dr. Woodruff cover the probabilistic nature of emergency clinical decision-making, the operational realities juries rarely see, documentation pitfalls that create legal exposure, and what to expect when a deposition focuses less on medicine than on your billing records and website.
They also dig into trends driving EM litigation today, sepsis protocols, stroke timing, troponin sequencing, and close with a candid discussion on where AI fits (and where it doesn’t) in expert witness practice. Whether you’re an emergency physician considering expert work or an experienced expert looking to sharpen your litigation perspective, this episode delivers practical, grounded insight from someone building their practice in real time.
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked