Thursday, April 23, 2026

AI Didn’t Know the Law. It Made the Path Visible.

How I finally appealed a denied insurance claim

Kate (now 21!) had dental surgery on 12/01/2025, a 4-5 hour procedure.

I don’t pay much attention to insurance stuff because it’s overwhelming. Before I joined my current company, it was also genuinely hard and expensive. Every day I’m grateful for my employer's coverage and, by extension, the generosity that makes it possible.

Kate has had 3–4 major dental surgeries over the last couple of years. She doesn’t technically qualify as “hillbilly” yet. Her dentist says that’s eight or fewer teeth. 😆

Kate also requires general anesthesia. 

Dental surgery is not cheap, which means I know the exact limits of our dental coverage: $2,500 per year. Her most recent surgery came in just north of five figures. Thankfully, Kate has Medicaid as secondary insurance. Less thankfully, her dentist, who is excellent, no longer accepts Medicaid. 

About a month later, another bill arrived. This one was for anesthesia. It was roughly half the cost of the surgery itself. Sigh. 

I called the anesthesiologist’s office and learned they didn’t have Kate’s current insurance information. I gave it to them and asked them to resubmit the claim. They did. Denied. Denial code: 001. 

This is classified as dental work, so medical does not cover anesthesia. I think. 001 isn’t super descriptive, it says:

We denied this service. Your benefits don't cover this kind of care. You can check your plan documents or go to the Benefits section of our website for a searchable list of what's covered.

Not super descriptive. AI (Gemini CLI) to the rescue. I downloaded the EOB and asked Gemini to scan it. It did and came back the above so I asked if it there were any other reasons possible?

While the document itself doesn't provide a specific medical rationale beyond the generic reason code 001 ("Your benefits don't cover this kind of care"), we can infer a highly likely explanation based on Kate's profile and typical insurance practices. Given that Kate's diagnosis is Developmentally Disabled, the most common scenario for an automatic denial like this is:

The Underlying Procedure was Dental: It is very common for special needs individuals to require general anesthesia for routine dental work that a neurotypical patient might do awake. Because routine dental care is generally excluded from medical plans, the automated claims system will automatically deny the associated anesthesia as "not covered care," even though the anesthesia itself is medically necessary due to her disability.

“Kate’s profile.” That’s a reference to other AI work I’ve been doing trying to make my life just a bit easier handling all the bureaucracy surrounding her (Guardianship, SSI, etc). My next prompt was, “How do I appeal?”

This is where it gets super fun and unexpected. With that other context, “Kate’s Profile,” Gemini’s first response was:

I will research Florida's specific legal requirements for anesthesia coverage for individuals with developmental disabilities and provide the exact steps to file the appeal with the insurance provider.

It came back with this:

✦ To appeal this denial, you need to challenge the automated determination that the care is "not covered." Because Kate has a developmental disability, Florida law likely requires them to cover the anesthesia and facility charges, even if the underlying procedure (like dental work) is not normally covered. 

The Strategy: Use Florida Law
Florida law mandates that health insurance policies must cover general anesthesia and associated hospital/facility charges for dental procedures if the patient meets specific criteria. Since Kate is over age 8, your appeal will rely on:

Statute: Fla. Stat. § 627.65755

The Argument: Kate has a developmental disability (as noted in her profile.json) that creates a "significant or undue medical risk" if dental or minor medical treatment were performed without general anesthesia in a controlled environment.

This isn’t an example of AI “knowing the law.” It’s an example of AI making a path visible that was previously opaque enough to stop me from trying. 

This is the second time in as many weeks that it has helped me overcome a bureaucratic hurdle that usually stops me from pursuing a thing. The last time, it helped me transfer Kate’s Conservator Payee (SSI) from my mom to myself. My mom handled it previously because I would not engage with that labyrinthine system. She’s retired. It took her 10 months. I’m ridiculously grateful and lucky. 

If you’re looking for ways to utilize AI, here’s another. 

*Editor's Note

I posted this internally a few weeks back. I'm slowing making my way back out into public waters. 

Saturday, April 18, 2026

It's Been a Minute...

 

Hi.

It's been a while. 

Not sure if this is a one-off or not, but I'm going to give it another go. I miss writing (publicly).

Like, this is super awkward. "What do I say?"

"How are you?"

"Things are good."

"How are you?"






Tuesday, August 23, 2016

Real World SQL and PL/SQL: Advice from the Experts



Because my hero is Cary Millsap, I'm going to do what he did and publish my foreword Preface. All joking aside, I consider myself incredibly fortunate to have been included in this project. I learned...a lot, by simply trying to find the author's mistakes (and there were not many). There was a lot more work than I expected, as well. (Technical) Editing is lot easier than writing, to be sure.

Brendan Tierney and Heli Helskyaho approached me in March 2015 about being an author on this book, along with Arup Nanda and Alex Nuijten. Soon after, we picked up Martin Widlake. To say that I was honored to be asked would be a gross understatement. Rather quickly though, I realized that I did not have the mental energy to devote to the project and didn’t want to put the other authors at risk. Still wanting to be part of the book, I suggested that I be the Technical Editor and they graciously accepted my new role.

This is my first official role as Technical Editor, but I’ve been doing it for years through work; checking my work, checking others work, etc. Having a touch of Obsessive Compulsive Disorder (OCD) helps greatly.

All testing was done with the pre-built Database App Development VM provided by OTN/Oracle which made things easy. Configuration for testing was simple with the instructions provided in those chapters that required it.

One of my biggest challenges was the multi-tenant architecture of Oracle 12c. I haven’t done DBA type work in a few years, so trying to figure out if I should be doing something in the root container (CDB) or the pluggable database (PDB) was fun. Other than that though, the instructions provided by the authors were pretty easy to follow.

Design (data modeling, Edition Based Redefinition, VPD), Security (Redaction/Masking, Encryption/Hashing), Coding (Reg Ex, PL/SQL, SQL), Instrumentation, and “Reporting” or turning that raw data into actionable information (Data Mining, Oracle R, Predictive Queries). These topics are covered in detail throughout this book. Everything a developer would need to build an application from scratch.

Probably my favorite part of this endeavor is that I was forced to do more than simply see if it works. Typically when reading a book, or blog entry, I’ll grab the technical solution and move on often skipping the Why, When, and Where. How, to me, is relatively easy. I read AskTom daily for many years, it was my way of taking a break without getting in trouble. At first, it was to see how particular solutions were solved, occasionally using it for my own problems. After a year or two, I wanted to understand the Why of doing it a certain way and would look for those responses where Tom provided insight into his approach.

That’s what I got reviewing this book. I was allowed into their minds, to not only see How they solved technical problems, but Why. This is invaluable for developer’s and DBAs. Most of us can figure out How to solve specific technical issues, but to reach that next level we need to understand the Why, When and Where. This book provides that.

Thursday, July 9, 2015

Kscope15 - It's a Wrap, Part II

Another fantastic Kscope in the can.

This was my final year in an official capacity which was a lot more difficult to deal with than I had anticipated. Here's my record of service:
  • 2010 (2011, Long Beach) - I was on the database abstract review committee run by Lewis Cunningham. I ended up volunteering to help put together the Sunday Symposium and with the help of Dominic Delmolino, Cary Millsap and Kris Rice, I felt I did a pretty decent job.
  • 2011 (2012, San Antonio) - Database track lead. I believe this is the year that Oracle started running the Sunday Symposiums. Kris again led the charge with some input from those other two from the year before, i.e. DevOps oriented
  • 2012 (2013, New Orleans) Content co-chair for the traditional stuff (Database, APEX, ADF), Interview Monkey (Tom Kyte OMFG!), OOW/ODTUG Coordinator, etc.
  • 2013 (2014, Seattle) Content co-chair for the traditional stuff (Database, APEX, ADF), Interview Monkey, OOW/ODTUG Coordinator, etc.
  • 2014 (2015, Hollywood, FL) Content co-chair for the traditional stuff (Database, APEX, ADF)

This has been a wonderful time for me both professionally and, more importantly to me, personally. Obviously I had a big voice in the direction of content. Also and maybe hard to believe, I actually presented for the first time. Slotted against Mr. Kyte. I reminded everyone of that too. Multiple times. It seemed to go well though. Only a few made fun of me.

I was constantly recruiting too. "Did you submit an abstract?" "No, why not?" and I'd go into my own personal diatribe (ignoring my own lack of presenting) into why they should present. Sarah Craynon Zumbrum summed it up pretty well in a recent article.

But it was the connections I made, the people I met, the stories I shared (#ampm, #cupcakeshirt, etc), and the friends that I made, that's what has had the most impact on me. Kscope is unique in that way because of it's size...at Collaborate or OOW, you'll be lucky to see someone more than once or twice, at Kscope you're running into everyone constantly.

How could I forget? #tadasforkate! This year was even more special. For those that don't know, Katezilla is my profoundly delayed but equally profoundly happy 10 y/o daughter. Just prior to the conference her physical therapist taught her "tada!" and Kate would hold her hands up high in the air and everyone around would yell, Tada! I got this crazy idea to ask others to do it and I would film it. Thirty or forty videos and hundreds of participants later...



So a gigantic thank you to everyone who made this possible for me.
Here's a short list of those that had a direct impact on me...
  • Lewis Cunningham - he asked me to be a reviewer which started all of this off.
  • Mike Riley - can't really say enough about Mike. After turning me away a long time ago (jerk), he was probably my biggest supporter over the years. (Remind me next year to you tell you about "The Hug."). Mike, and his family, are very dear to me.
  • Monty Latiolais (rhymes with Frito Lay I would tell myself) - How can you not love this guy?
  • Natalie Delemar - Co-chair for EPM/BI and then boss as Conference Chair.
  • Opal Alapat - Co-chair for EPM/BI and one of my favorite humans ever invented. I aspire to be more organized, assertive, and bad-ass like Opal.
That list is by no means exhaustive. It doesn't even include staff at YCC, like Crystal Walton, Lauren Prezby and everyone else there. Nor does it include the very long list of Very Special People I've met. I consider myself very fortunate and incredibly grateful.

What's the future hold?
I have no idea. My people are in talks with Helen J. Sander's people to do one or more presentations next year, so there's that. Speaking of which...it's in Chicago. Abstract submissions start soon, I hope you plan on submitting. If you're not ready to submit, I hope you take try to take part in shaping the content by finding one of about 10 abstract review committees. Who knows where they may lead you?

Finally, here's the It's a Wrap video from Kscope15 (see Helen's story there). Here's Kscope16's site. Go sign up.