A 35,000-page medical record is now an ordinary case file, and somewhere inside it is the 5 percent that actually matters. In this episode, Dr. Brian Woodruff talks with Dr. Saurabh Gupta, an interventional cardiologist, chief of cardiology at St. Charles Health System, professor of medicine at Washington State University, and founder and CEO of Cormetrix, the company behind Verix AI.
Dr. Gupta explains how EHRs built for billing turned into “note bloat,” what he learned facing roughly 300,000 pages of records a month as vice chair of the Oregon Medical Board, and why he thinks not using AI record tools may soon be considered below the standard of practice for an expert witness. He walks through what AI can reliably do with medical records today, from pulling up the actual EKG instead of 12,000 mentions of one, to plotting trends across encounters, flagging missing records, and mapping everyone who touched the patient. He is also clear about where it stops: standard of care, which depends on venue, context, and the expert’s judgment.
The conversation also covers billing pressure building on both the plaintiff and defense sides, why generic AI tools struggle with bias and hallucinations on large records, what “domain-specific” really means, and how Verix AI links every fact to its source page and refuses to cite anything outside the record. Plus the mother-and-baby records problem that caught an entire engineering team off guard.
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