Case study - Health ops · Search & data mapping
A two-week investigation, answered on the call
When a member asks "is this procedure covered?", the answer starts with a five-digit CPT code - and nobody could get from that code to a coverage answer without leaving the tool they were in. I designed a CPT search, a code landing page, and the admin layer that keeps the mapping honest, replacing a four-tool manual lookup that generated over half a million tasks a year.
Overview
01
Context
Half a million tasks a year, resting on a number the tools didn't recognise.
The claims & benefits team fields member calls and processes roughly 500,000 tasks a year. A large share of them exist for one reason: the CPT or HCPCS code on a claim - the standard code describing a procedure - doesn't map to anything a health assistant can see while the member is on the phone.
Neither the health-assistant platform nor the internal benefits admin platform had any concept of a CPT code. It was just a number sitting on a claim. Connecting it to "what does this member's plan actually cover" was entirely human work.
The data already existed. The entry point didn't.
02
The problem
No path from a CPT code to a coverage answer inside the tools people already use - so a lookup became a two-week task.
Health assistants left the platform mid-call to cross-reference external sources. Whatever they couldn't resolve on contact became a task for the ops team. Members waited.
03
Constraints
Discovery
04
Research
18 months of task data, 40 million claims, and an afternoon watching the actual process.
Where the volume actually sits
Starting from a warehouse pull - task data from January 2024 to June 2025, and every 2025 claim. Setting aside generic follow-ups, which are 42.4% of tasks and no signal on their own, claims tasks were the largest single category at 12.34%: bigger than outreach, rising-risk care or case management.
Four steps to answer one question
Shadowing the claims & benefits team through a real CPT-related task exposed the chain behind every answer.
- 01Look the code up in an external CPT reference tool
- 02Search the web for plain-language context
- 03Cross-check the relevant medical policy document
- 04Translate all of it into an answer about this member's benefit
The finding that made the project possible
Across roughly 40 million claims, the 1,500 most common CPT codes accounted for about 80% of all volume. The whole code set never needed mapping - a focused map of the highest-frequency codes covers the large majority of real member questions. I built a proof-of-concept mapping of the top 1,000 codes against the current benefit set, using Claude for the first pass, for a human to verify before anything shipped.
1,500 codescover~80% of 40M claims
05
Synthesis
Two opportunities, two different kinds of answer.
Claims tasks exist because nothing connects a claim to its benefit
Make that connection automatically and a large share of claims tasks never need to be created - scoped at up to a 40% reduction.
Benefits tasks exist because a code can't be looked up in place
Making CPT codes searchable, with results scoped to the member's plan, was scoped at up to 50%. The ceiling is lower on purpose: some questions genuinely need a human to read medical policy, and that step doesn't disappear.
Don't build new intelligence - remove the need to leave the tool.
Design
06
Directions considered
07
Iteration & collaboration
Designed with engineering, ops SMEs and content team.
The mapping model changed shape mid-design
The starting assumption was close to one code, one benefit. Research showed codes routinely serve several benefits depending on diagnosis context - so the schema and the UI both moved to many-to-many: a code page listing many services, a service page listing many codes, rather than forcing a false relationship. Getting that structural call right early is what made both the search results and the admin tool coherent later.
Review designed in, not bolted on
Because the first-pass mapping is machine-generated, the admin surface treats verification as a primary job: ops SMEs and content review and refine definitions, usage guidance, and service links before anything becomes member-facing.
Who owned what
Engineering owned the schema changes needed to store the mapping. Ops SMEs and content wrote and validated the plain-language definitions. Product sequenced the phases. I designed and connected the three surfaces so none of them required leaving the platform.
08
Validation
Against real volume, not a small sample.
The prioritisation was checked directly against roughly 40 million 2025 claims and confirmed to cover about 80% of volume. A working proof-of-concept map of the 1,000 most common codes was built and spot-checked before Phase 1 was scoped.
Ongoing validation is structural rather than a one-off study: every machine-suggested mapping passes SME and content review inside the admin tool before a health assistant or a member ever sees it.
Solution
09
Search, where people already are
Typing a code, a keyword or a synonym into the existing platform search returns everything relevant in one list - the code's own overview page, the healthcare services that use it, virtual categories, and benefit programs. No guessing which system holds the answer.
10
The code page - coverage at a glance
The highest-value screen in the project.
Searching a code lands on a page listing every related service as a card, each taggedcoverage available, restrictions apply, or we are missing information - alongside the code's plain-language definition, clinical usage notes, and links out for anything needing a deeper check. It turns "is this covered" from an investigation into a glance.
- Coverage available
- Restrictions apply
- We are missing information
11
The same link, read backwards
Every service detail page now shows its related CPT codes inline, with a count and a link through to the full list - each code in plain language. The loop closes from either direction.
12
The admin layer that keeps it true
None of this works without someone maintaining it.
A new codes library in the benefits admin platform: a searchable, filterable table of every mapped code, its type, and how many services it's assigned to - plus a per-code editor for definition, description, usage guidance and service links. This is where the machine-generated first pass gets verified before it reaches anyone.
Impact
Outcomes & impact
Phase 1 was in delivery and Phase 2 scoped but not started, so these are the numbers the work was scoped against rather than measured in-market results.
14
How we'd know it worked
Chosen to survive changing customer and call volume.
15
Reflection
16