OHDSI Home | Forums | Wiki | Github

Vocab Request - Additional Type Concepts for Claims Provenance

Hello all, this is my first time requesting vocab modifications (but it does tie back to some previous forum conversations, linked below), so I apologize if I’m missed anything, posted in the wrong place, etc. Please see below and advise on next steps.

My goal:

  • Annotate records with provenance showing that they are from a particular claim type and include the “open”/“closed” adjudication status. As an example, a specific record may come from a “closed professional claim line” or an “open dental claim line”.

The issue:

  • This is not currently possible in the OMOP schema using standard vocabularies. The standard vocabulary Type Concept provides the ability to delineate claim type (id: 32871 “Professional claim”, id: 32844 “Facility claim”, id: 32816 “Dental claim”, etc.). That same vocabulary also has records for id: 32875 “Payer System” and id:32867 “Primary Provider System” which can roughly translate to “open” pre-adjudicated claims or “closed” adjudicated claims. The trouble is that there aren’t any vocabulary entities that combine this information.

Why is it important to retain this information?

  • Claim type (Professional, Facility, Dental, etc.)
    • Provide researchers with a general understanding of provenance
    • Understanding claim type is critical for researching things like policy interventions, utilization patterns, etc.
  • Adjudication status
    • Post-adjudication (“Closed”) claims are generally viewed as higher quality for most use cases. They represent completed transactions that have been thoroughly reviewed, with any discrepancies resolved.
    • Pre-adjudication (“Open”) claims frequently have more data, but also missing claims and duplicates which affect research findings if not properly understood and managed.

Also, adjudication status is critical for the cost table to work correctly, which is something Vojtech pointed out in the other post.

My Proposal:

I am requesting that OMOP modify their standard type vocabulary to include additional entities that can create a hierarchical relationship grouping by claim adjudication status.

This picks up on an exchange I originally had with several others on the forum, including @Vojtech_Huser . I believe the below captures what Vojtek advised at the end of this post.

Also, for quick reference, here is the existing standard vocab list for aall type concepts with “Claim” in the name is here.

An example of the new members I am requesting is below, with new entities labeled with a *

  • Dental claim

    • Approved dental claim*

    • Rejected dental claim*

    • Pre-adjudicated dental claim*

  • Facility claim

    • Approved facility claim*

    • Rejected facility claim*

    • Pre-adjudicated facility claim*

  • Inpatient claim

    • Approved inpatient claim*

    • Rejected inpatient claim*

    • Pre-adjudicated inpatient claim*

  • Outpatient claim

    • Approved outpatient claim*

    • Rejected outpatient claim*

    • Pre-adjudicated outpatient claim*

  • Pharmacy claim

    • Approved pharmacy claim*

    • Rejected pharmacy claim*

    • Pre-adjudicated pharmacy claim*

  • Professional claim

    • Approved pharmacy claim*

    • Rejected pharmacy claim*

    • Pre-adjudicated pharmacy claim*

The leaf-level new members shown above would also roll up to existing members in a separate hierarchy, shown below:

  • Adjudicated Approved Claims*

    • Approved dental claim *

    • Approved facility claim *

    • Approved inpatient claim *

    • Approved outpatient claim *

    • Approved pharmacy claim *

    • Approved professional claim *

  • Adjudicated Rejected Claims*

    • Rejected dental claim

    • Rejected facility claim *

    • Rejected inpatient claim *

    • Rejected outpatient claim *

    • Rejected pharmacy claim *

    • Rejected professional claim *

  • Pre-Adjudicated Claims*

    • Pre-Adjudicated dental claim *

    • Pre-Adjudicated facility claim *

    • Pre-Adjudicated inpatient claim *

    • Pre-Adjudicated outpatient claim *

    • Pre-Adjudicated professional claim *

    • Pre-Adjudicated pharmacy claim *

3 Likes

Hi @Dan_Angelelli:

By “pre-adjudicated” you probably mean open claims that have been submitted (aka invoices) and the payer hasn’t reacted yet. There are also special pre-adjudication services which scrub claims before they go into the system to give them a better first-pass chance of approval. Or do you mean to get that distinction?

By “pre-adjudication”, I just mean “open claims that have been submitted (aka invoices) and the payer hasn’t reacted yet.”

1 Like

@Dan_Angelelli:

Ok.

Next question. We currently have the following claims: Claim, Dental claim, Facility claim, Inpatient claim, Outpatient claim, Pharmacy claim, Professional claim, Vision claim, Facility claim detail, Facility claim header, Inpatient claim detail, Inpatient claim header, Outpatient claim detail, Outpatient claim header, Professional claim detail, Professional claim header.

According to your idea, we would have to triplicate them, by adding one pre-coordinated concept for each “Open” and “Closed”. That would make it 16*3=48 of them. Do you think that is necessary?

What’s the use case anyway for all of this? Usually, the entire database is either Open or Closed Claim. Why would you query each record?

Addressing the 1st point:

I don’t know that you would need to triplicate all of those. The list you pasted in has the generic “claim” and also the more detailed “claim header” and “claim detail” for each type of claim. I can certainly see the case for consistency and applying the 3-status approach to all of those, but as you said that makes way more concepts.

IMO, it’s a reasonable to apply this logic just to the 7 more generic “claim” concepts ( Dental claim, Facility claim, Inpatient claim, Outpatient claim, Pharmacy claim, Professional claim, Vision claim) and not to the corresponding “header” and “detail” concepts. You also don’t need to apply this to the “Claim” concept - the proposed “Adjudicated Approved Claims”, “Adjudicated Rejected Claims”, and “Pre-Adjudicated Claims” parent-level concepts already address that.

So it would actually be 7*3=21, not 48. (I missed “Vision” in my original post when I listed the claim types).

Addressing the 2nd point:

21 new concepts is still not nothing, so I hear you on needing the use case.
I’m currently transforming data for a large population into OMOP. That data includes a mix of open and closed claims + rejections, primarily from commercial data providers. There are also plans to add more data sources down to road to build a more complete profile of the population.
So I am currently working with a database that is a mix of open and closed claims.

I was hoping the Why is it important to retain this information? section, above, explained the use case but let me know if that isn’t sufficient. I’m an engineer, not a researcher, so I’m trying to accurately represent the use cases from the researchers.

t