What does a life care plan actually contain, and how do the dollar figures get there? In this episode, Dr. Brian Woodruff talks with Dr. Jared H. Griffard, a double board-certified general surgeon and surgical critical care intensivist at UNLV who is also a certified life care planner. A combination so rare that he may be one of the only trauma surgeons in the country doing this work.
Dr. Griffard walks through the anatomy of a life care plan: the medical record chronology, the client interview and examination, projecting future care needs, and how costs are established using national databases like Context4 Healthcare and FAIR Health at the 75th–80th percentile benchmark. He explains the advantage physician life care planners have in standing on their own diagnoses and shares what surprised him most in deposition: that attorneys often spend more time attacking credentials and cost projections than discussing the case itself, and how over-preparing turned that into a win.
Whether you’re an experienced expert or just thinking about your first case, this conversation is packed with practical advice on directories, LinkedIn networking, building attorney relationships, and pushing through the slow early years.
Connect with Dr. Griffard at jhglcp.com or jhg@jhglcp.com.
Subscribe, comment, and reach out. We’d love to hear from you.
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