TECH TALKS WITH GRACE

TECH TALKS WITH GRACE

Download on the App Store

TECH TALKS WITH GRACE episodes

  • Tech Talks with Grace — E19: Using Claims Data in Mass Torts (If I Had Claims Data During RoundUp, We All Would Have Made More Money)

     Using Claims Data in Mass Torts: Know What You Have Before You Keep Spending

    **Cases cost money before they ever make money. Advertising, intake, medical records, and staff time all add up—but how much are you spending before you understand what you actually have?**

    In Episode 19 of **Tech Talks with Grace**, Grace sits down with **Derek Cole, PharmD, Senior Clinical Consultant at Milliman IntelliScript**, to discuss how medical and prescription claims data can help mass tort teams make better-informed decisions about case evaluation, record retrieval, and where to focus their resources.

    Drawing on her experience working on Roundup cases, Grace asks the operational questions law firms face every day: What should we look for? What might we miss? What do we tell our team to do next? And when information is missing, what does that actually mean?

    Derek brings a clinical pharmacist’s perspective to those questions. He explains how claims data can reveal relevant diagnoses, prescription fills, treatments, providers, and facilities—and how those details can create an evidence trail for more targeted medical-record requests.

    The conversation also addresses the limits. Claims data is not a complete medical record. A test being ordered does not necessarily reveal its result. A diagnosis code may identify a broader condition without establishing the specific subtype a legal team needs to verify. And a “no hit” does not, by itself, establish fraud or prove that someone was never treated.

    **The central takeaway: claims data is not simply more information to review. Used thoughtfully, it can help teams decide where to put their next hour and their next dollar.**

    ### Inside the conversation

    **Derek’s clinical background and personal connection to mass torts**  

    Derek discusses his experience in hospital pharmacy and healthcare consulting before moving into his current work with claims data. He also shares his connection to Southeast Ohio and the C8 contamination associated with DuPont’s Washington Works facility—a personal experience that gives his work in this space added meaning.

    **What claims data actually contains**  

    Derek explains the medical and prescription information generated through reimbursement processes. Prescription data can include the medication, dose, quantity, and days supplied. Medical claims can identify why someone was seen through diagnosis codes and what services were performed through procedure codes.

    **Why “speed and structure” matter**  

    The discussion explores how structured code sets can help teams identify relevant information without beginning with hundreds of pages of unstructured records. Derek also discusses authorization requirements and how claims information can support a more focused approach to record retrieval.

    **What the data can—and cannot—tell you about testing**  

    Using breast cancer and BRCA testing as examples, Grace and Derek distinguish between evidence that testing occurred and the underlying results that may still require medical-record verification. The practical value is often knowing which provider or facility to contact next.

    **The Roundup example: clinical context changes what you find**  

    Grace reflects on the time and expense involved in understanding a Roundup case inventory. Derek explains how diagnosis and treatment information could help identify relevant signals—and why looking only for a familiar disease name can miss important codes.

    In one NHL code-group example, Derek describes **more than 500 relevant diagnosis codes, with only about 20 explicitly stating non-Hodgkin lymphoma**. The example illustrates why clinical interpretation matters when building criteria and reviewing claims information.

    **What to tell your team to do next**  

    Derek outlines two practical uses: identify diagnoses and treatments relevant to the condition being investigated, and identify the providers and facilities that hold the records needed for follow-up. The goal is a specific next task, not another broad search.

    **ION versus NAION: recognizing the limits of specificity**  

    The conversation turns to ischemic optic neuropathy and the distinction between ION and non-arteritic ischemic optic neuropathy, or NAION. Derek explains how claims data may identify a diagnosis and the treating ophthalmologist while leaving details that still need to be confirmed in the medical records.

    **Hit rates, missing information, and fraud concerns**  

    Grace and Derek discuss what returned data can indicate and when patterns warrant closer review. Importantly, they emphasize that missing information should not be treated as an automatic conclusion about a person or a claim. Coverage gaps, incomplete information, and the way healthcare services are documented all matter.

    **Guided discovery—not a substitute for verification**  

    The episode closes on a practical principle: use the available evidence to guide due diligence, target record requests, and allocate resources more deliberately. Claims data can help point the way, but it does not eliminate the need to verify case-specific facts.

    ### Who this episode is for

    Mass tort attorneys, law firm owners and operators, intake leaders, case managers, medical-record retrieval teams, and legal technology professionals looking for a clearer understanding of how claims data fits into case development.

    ### Featured guest

    **Derek Cole, PharmD**  

    Senior Clinical Consultant, Milliman IntelliScript

    ### Keep the conversation going

    Where does your team lose the most time: identifying providers, retrieving medical records, or confirming whether the information supports the case?

    Connect with Grace and Derek Cole on LinkedIn, and follow **Tech Talks with Grace** for more conversations about technology, legal operations, and better-informed decision-making.

    *This episode is an educational discussion, not case-specific medical or legal advice. Claims data should be interpreted in context and does not replace medical-record verification or appropriate due diligence.*

    23 min
  • Tech Talks with Grace — E18: Delivery Systems (Build a Delivery Workflow That Works Every Time)

    Intake gets clients in the door. Marketing fills the pipeline. But delivery is where your firm proves whether it actually deserves to grow.


    Most law firms don’t have a delivery system. They have great people and strong intentions—but delivery still relies on memory, individual judgment, heroics, and constant manual intervention. Delivery works… until it doesn’t.

    In Episode 18 (Pillar 7 — Delivery Systems & Client Experience), Grace explains how to build a delivery system that works every time—not because people are perfect, but because the system is.

    In this episode:
    • Why delivery is the most fragile part of a law firm (humans + time + external dependencies + high‑emotion clients)
    • The 3 failure patterns: delivery depends on who has the case; work happens but no one can see it; clients experience gaps as trust erosion
    • The 3 non‑negotiables: non‑negotiable steps, workflow structure (what’s next / who owns it / by when), and reduced variability with defined exception handling
    • A case example (Litify): improving delivery by enforcing sequence, standardizing tasks, and making status updates non‑optional

    Actionable takeaways:
    1) List your delivery steps for one case type (as it actually happens)
    2) Identify one variable step where outcomes change based on who’s handling it
    3) Standardize one step, one handoff, and one client communication moment—and make it non‑negotiable in the system

    Next: Episode 19 — Mapping delivery workflows visually so you can see where work moves, stalls, or breaks.

    Show Notes / Keywords: law firm delivery system, legal operations, delivery workflows, case workflow, client experience, client communication, status updates, visibility, handoffs, task ownership, deadlines, standardization, exception handling, workflow design, process improvement, SmartAdvocate, Litify, CasePeer, Filevine

    16 min
  • Tech Talks with Grace — E17: CRM Stages (Design Stages That Match Real Workflow)

    “New.” “Active.” “Pending.” “In Progress.” “Waiting.”


    If your stages sound like that—and no one can explain what actually changed—your CRM stages aren’t running the work. They’re just labeling it. And when stages don’t reflect real movement, cases stall silently, handoffs get messy, and your team stops trusting the system.

    In Episode 17 of Tech Talks with Grace (Pillar 6 — CRM Excellence & Client Journey Management), Grace breaks down how to design CRM stages that match your real workflow (not your software defaults), including how to handle the dual-system reality many firms live in (Lead Docket + SmartAdvocate, HubSpot + Litify, CasePeer, etc.).

    In this episode:
    • Why default CRM stages fail law firms (they describe categories, not progress)
    • The two failure modes: everything sits in one stage, or each role uses stages differently
    • The dual-system reality—and the key rule: you can have two systems, but not two sources of truth at the same time
    • What a CRM stage is (observable change, handoff point, decision boundary, communication trigger) and what it is not
    • The 5 requirements of a usable stage: sequential, observable, action-driven, aligned across systems, and simple enough to be trusted
    • Case study: the “everything is Active” firm—and how stage redesign restored visibility and control

    Actionable takeaways:
    1) Write down the real workflow (as it actually happens)
    2) Compare your workflow to your CRM stages (does work truly change?)
    3) Remove or rename one misaligned stage to reflect reality

    Next: Episode 18 — Defining stage rules (because stages without rules still rely on memory).

    Show Notes / Keywords: law firm CRM stages, CRM stage design, case management workflow, legal operations, client journey management, pipeline stages, workflow stages, stage definitions, handoffs, ownership, client communication triggers, source of truth, dual systems, Lead Docket, SmartAdvocate, Litify, CasePeer, Filevine, process improvement, operational visibility

    12 min
  • Tech Talks with Grace — E16: CRM Excellence (Make Your CRM the Operational Heart of the Firm)

    Most law firms don’t actually run the business from their CRM.

    They store contacts there, log notes there, and pull reports occasionally.
    But the real work lives in email threads, inboxes, Teams messages, and memory.

    When that happens, the CRM stops being the system of record. It becomes a filing cabinet—and everything downstream breaks quietly: cases stall, follow‑ups slip, clients get confused, and leadership loses visibility.

    In Episode 16 (Pillar 6 — CRM Excellence & Client Journey Management), Grace breaks down what it actually means for the CRM (case management) to be the operational heart of your firm—and the five foundations that make it work at scale.

    In this episode:
    • Why law firms struggle with CRMs (long lifecycles, emotional client journeys, handoffs, compliance constraints)
    • The 3 predictable failure modes: CRMs become optional, historical (not operational), and untrusted
    • Case Study #1 (Redwood Legal Group): “compliant but chaotic” when stages reflect categories instead of movement
    • The 5 non‑negotiables of a CRM that actually runs the journey: aligned stages, consistent fields, predictable follow‑up, ownership that shifts, and clean data that ages well
    • Case Study #2 (IronGate Injury Law): high volume + outdated stages = visibility collapse (and how redesign reduced stress)

    Actionable takeaways (do this this week):
    1) Review your CRM stages: what changed, who owns next, what the client expects
    2) Standardize one decision-driving field (make it structured + required)
    3) Tighten one follow‑up rule (what must happen, by when, triggered by what CRM event)

    Next: Episode 17 — Designing CRM stages that actually match how work happens (not software defaults).

    Show Notes / Keywords: law firm CRM, case management software, legal operations, CRM excellence, client journey management, workflow stages, pipeline stages, stage design, required fields, structured data, data quality, data governance, follow-up rules, client communication, ownership, handoffs, visibility, SmartAdvocate, Litify, CasePeer, Filevine, process improvement

    17 min
  • Tech Talks with Grace — E15: Measuring Intake Performance (4 Metrics That Improve Law Firm Intake)

    Most law firms know intake is important. Fewer can say—clearly—whether intake is getting better over time.


    In Episode 15 of Tech Talks with Grace (Pillar 5 Capstone: Intake Excellence), we focus on measuring intake performance without turning your firm into a reporting nightmare. This isn’t tactical-heavy or dashboard-obsessed—it’s about tracking a few signals that stabilize the system and reduce tension inside the firm.

    The 4 intake metrics that matter (law firms):
    • Response time (time to first human response—look for patterns, not averages)
    • Qualification rate (intake clarity—are you screening consistently?)
    • Conversion rate (of qualified leads—where does confidence break?)
    • Follow‑up consistency (do confirmations, reminders, and next steps happen on time?)

    Actionable takeaways:
    1) Track time to first response
    2) Review qualification + conversion together
    3) Choose one improvement, then measure again

    Next: Pillar 6 — CRM Excellence.

    10 min
  • Tech Talks with Grace — E14: Why Tools Fail (The Intake Misalignment Problem)

    Most teams don’t have a “tool problem.” They have a misalignment problem.


    When your intake form collects one set of information, your calendar asks for another, your CRM stores it differently, and your team communicates in a fifth place… your system can’t hold. That’s when you get duplicate entry, missing details, broken handoffs, and “we’ll fix it later” chaos.

    In Episode 14 of Tech Talks with Grace (Pillar 5 — Intake Excellence & First Touch Systems), Grace breaks down why tools fail in real businesses—and how to align your first-touch stack so intake becomes fast, clean, and reliable.

    In this episode:
    • Why tools fail: misalignment between systems, fields, and ownership
    • A real-world example: Harrison & Cole
    • The 4 core intake tools to align: forms, scheduling, CRM/case management, communication
    • Where duplicate entry really comes from (and how to eliminate it at the source)

    Actionable takeaways:
    1) Pick your “source of truth” for intake data
    2) Standardize the fields that must match across tools
    3) Remove one duplicate entry step this week (even if everything else stays the same)

    Next: Measuring intake performance and tightening the workflow over time.

    13 min
  • Tech Talks with Grace — E13: Intake Workflows (Design a Clear Intake Process Your Team Can Follow)

    Fixing intake isn’t just about collecting the right information—it’s about designing a repeatable workflow your team can execute without improvising.


    In Episode 13 (Pillar 5 — Intake Excellence & First Touch Systems), Grace breaks down how to build a clear, consistent intake workflow that protects your delivery timeline, improves client experience, and makes automation reliable.

    In this episode:
    • The difference between an intake form and an intake workflow
    • How to define one “canonical” intake path (so requests don’t enter 5 different ways)
    • How to set an “Intake Complete” definition (what must be true before work begins)
    • Where intake usually breaks: ownership, delays, missing fields, and unclear next steps
    • How to route intake to the right team/tool without creating extra admin work

    Do this today:
    1) Choose ONE intake entry point you want to standardize first
    2) Write your “Intake Complete” checklist (3–7 required items)
    3) Assign one owner + one response-time target (so momentum is protected)

    Next: How to measure and improve intake performance (response time, completion rate, rework).

    10 min
  • Tech Talks with Grace — E12: Intake Excellence (Why Intake Determines Momentum + Client Experience)

    Most businesses think they have a delivery problem—when what they really have is an intake problem.


    Intake is the first moment information enters your system. It determines how fast work moves, how clear your team feels, how reliable your automations become, and how confident clients feel before you even start delivering.

    In Episode 12 (Pillar 5 — Intake Excellence & First Touch Systems), Grace explains why intake is the most important system in your business—and how weak intake creates invisible delays, rework, and broken handoffs downstream.

    In this episode:
    • Why momentum starts before delivery (intake = the gatekeeper)
    • How intake shapes client experience and internal clarity
    • A real-world case study: the agency that couldn’t scale until intake was fixed
    • Why you can’t automate around bad intake (structure comes first)

    Do this today (3 quick wins):
    1) List your intake steps (every form, call, email, and handoff)
    2) Identify one delay point where work pauses waiting for info
    3) Standardize one field (make it required; reduce free text)

    Next: Designing clear, consistent intake workflows your team can follow—and your systems can trust.

    10 min
  • Tech Talks with Grace - E11: Real-World AI Use Cases (What Works + Why It Fails Without Clean Data)

    Pillar 4 — Real‑World Use Cases & Strategic Application

    AI doesn’t fail because it’s “not smart enough.” It fails because your data and workflows aren’t ready.


    In Episode 11, Grace shares real-world AI use cases and mini case studies to show what actually works in business—especially when your data is structured, consistent, and stored in the right “source of truth.” You’ll also learn the common failure points that make AI outputs unreliable.

    In this episode:
    • Real examples of AI + automation in operations (what works vs what breaks)
    • Why structured data improves outcomes (and why messy data creates chaos faster)
    • The fastest way to pick one workflow to improve for ROI

    Do this today:
    1) Pick one slow/repetitive/error-prone workflow (your ROI target)
    2) Pull 10 recent records and look for missing fields, inconsistencies, duplicates, and free-text chaos
    3) Choose one system as the source of truth and make one enforcement change (required field, dropdown, naming rule)

    This episode is designed to show (not tell) how AI actually works in real businesses when the data is structured—and why it fails when it isn’t.


    Take the free 3‑minute diagnostic at GrowClarity.io.

    Show Notes / Keywords: real world AI use cases, AI case studies, AI in business, business automation, workflow automation, operations, structured data, data integrity, data quality, source of truth, CRM data, process improvement, automation failures, AI implementation, AI strategy, operational excellence

    Pillar 4 Wrap‑Up

    You now understand how data integrity impacts real‑world automation.

    15 min
  • Tech Talks with Grace - E10: History Log (Make Progress Visible & Stop Starting Over)

    If progress feels invisible, you’ll keep feeling stuck—even when you’re improving.


    In Episode 10, Grace breaks down the History Log: a lightweight tracking system that gives your business memory. You’ll learn what to log, how to review it after each quarterly reset, and how to spot trends that reveal your real bottleneck—so you stop repeating the same fixes and start compounding improvements.

    In this episode:
    • What a History Log is (and isn’t) so it stays simple
    • The 5 fields to track: what changed, when, why, owner, impact
    • How to identify patterns and choose one improvement for the next quarter

    Do this after your next reset:
    1) Create a History Log (doc or spreadsheet) with 5 columns: Date/Quarter, System, Change, Owner, Impact
    2) Review the last quarter and highlight anything that shows up 2+ times
    3) Pick ONE improvement + ONE proof metric (duplicates/week, handoff errors/week, response time)

    Next: Real-world examples—seeing these systems in action.

    Take the free 3‑minute diagnostic at GrowClarity.io.

    Show Notes / Keywords: history log, progress tracking, quarterly review, business systems, operations, process improvement, operational excellence, continuous improvement, system audit, workflow audit, metrics, founder operations, planning cadence, automation readiness, business clarity

    15 min

About TECH TALKS WITH GRACE

From the publisher's feed

Demystifying technology in business. Technology broken down into its components and explained.