← All work
Case study · Global IT services company · Mar 2020 – Sep 2021

Most stuck claims weren’t system failures. They started with missing details.

My first research, before I had the title. As a Research Analyst supporting a U.S. healthcare clearinghouse, I looked past individual tickets to ask why some customers kept raising them, and found the problem usually began long before the claim.

My roleResearch Analyst
TimelineMar 2020 – Sep 2021
ClientU.S. healthcare clearinghouse
MethodsTicket analysis in R, interviews, thematic mapping
3
Amber Awards for my work on the team
Top tier
Of a 30-person team
6 months
Until I was asked to train new hires
01

The contextClaims stuck between hospitals, insurers and patients

COVID-19 hit just as I started. Inquiries surged. Payments and claims moving between hospitals, insurance companies and patients were getting stuck, and my day-to-day work was claims support: tracing why a claim had stalled across different portal systems, and keeping customers updated.

Solving tickets one by one wasn’t going to reduce them. So I started asking a different question.

The question

Why do some customers raise many tickets, while others never raise one?

02

What I didFrom thousands of tickets to a research report

1Analysed the ticketsCompared customers with many tickets against those with none, in R, and ranked ticket reasons by severity and frequency.
2Interviewed three groupsClearinghouse staff, customers with many and with no tickets over 6 and 12 months, and the business team.
3Mapped the themesFound what connected the business, the clearinghouse and the patients.
4Shared the reportWith senior research analysts and my manager, who took it to the client.
03

What I foundThe ticket was the last step, not the first

Most tickets traced back to errors or gaps in customers’ details, often months before the claim was made.

Two paths that ended in a stuck claim
Missing information at the start
Customer chooses cover without full informationLater develops an illness the plan doesn’t matchClaim is rejected or stallsTicket raised
A life change the system didn’t reflect
Job loss or another change in circumstancesA premium is missed and cover is removedPatient doesn’t know until they claimTicket raised
Missing holidaysHolidays weren’t in the clearinghouse system, so claim status during them was unknown.
Numbers that didn’t matchClaim and bill numbers didn’t always line up between systems.
Conflicting statusesWallet statuses (approved, pending, detained) differed from what hospitals said they had received.
04

What happenedSmall fixes, and a bigger change for me

What it taught me

The frustration I heard in customers’ voices came less from the people and more from unclear information and broken processes. I wanted to fix those at the root, so I took UX research courses and moved into UX research.

Data analysis in RInterviewsThematic analysisRoot-cause analysisReportingTraining and onboarding

Reconstructed from memory. The client and data are anonymised, with no figures beyond what I recall.