Coordination of Benefits Check

Submit a coordination of benefits (COB) check in JSON format

POST/coordination-of-benefits

Coordination of benefits (COB) checks help you determine whether patients are covered by multiple health plans, whether coverage overlap requires coordination of benefits, and each payer's responsibility for payment (primacy).

  1. Call this endpoint with a JSON payload. Each check must be for a Stedi-supported payer with which the patient has coverage. Visit the Payer Network for a complete list of supported payers.
  2. Stedi searches a national database containing 245+ million patient coverage records from 45+ health plans, ASOs, TPAs, and others, including participation from the vast majority of national commercial health plans. Data is updated weekly to ensure accuracy.
  3. The endpoint returns information about the patient's active health plans, the responsibility sequence number for each payer if available (such as primary or secondary), and whether coordination of benefits is required.

Visit Coordination of benefits checks for a full how-to guide.

Authorizationstringrequiredheader

A Stedi API Key for authentication.

Body

application/json
dependentobject

A dependent for which you want to check coordination of benefits.

  • An individual qualifies as a dependent when they are listed as a dependent on the subscriber's insurance plan AND the payer cannot uniquely identify them through information outside the subscriber's policy. For example, if the dependent has their own member ID number, you should identify them in the subscriber object instead.
  • The demographic information you provide must patch the payer's data exactly. For example, if the payer has the dependent's name as Jonathan Doe, a COB request for Jon Doe will fail because the name doesn't match the payer's records.
Show attributes
dependent.dateOfBirthstringrequired

The dependent's date of birth.

  • Pattern: ^\d{4}-(0[1-9]|1[0-2])-(0[1-9]|[12]\d|3[01])$
dependent.firstNamestringrequired

The dependent's first name.

  • Required string length: 1 - 35
dependent.lastNamestringrequired

The dependent's last name.

  • Required string length: 1 - 60

The dependent's Social Security Number (SSN).

  • Pattern: ^\d{9}$
encounterobjectrequired

Information about the encounter.

  • You can submit COB checks with the 30 service type code for Health Benefit Plan Coverage. This is the broadest service type code that covers all medical services and subtypes included in the patient’s health plan.
  • The service dates you provide must be within the past 2 years. COB checks don't support requests with dates outside of this range.
  • Don't send service dates that are in the future. Future service dates typically result in errors from the payer.
  • If you don't specify a service date (either a single day or a range of dates), Stedi defaults to using the current date.
Show attributes

The beginning date of service. If you include this value, you must also include the endDateOfService.

  • Pattern: ^\d{4}-(0[1-9]|1[0-2])-(0[1-9]|[12]\d|3[01])$

The date of service of the encounter.

  • Pattern: ^\d{4}-(0[1-9]|1[0-2])-(0[1-9]|[12]\d|3[01])$

The end date of service. If you include this value, you must also include the beginningDateOfService.

  • Pattern: ^\d{4}-(0[1-9]|1[0-2])-(0[1-9]|[12]\d|3[01])$

The service type code for the encounter. If not provided, the default value is 30.

Possible values
30
providerobjectrequired

An object containing information about the entity requesting the COB check. This may be an individual practitioner, a medical group, a hospital, or another type of healthcare provider. You must provide the organizationName (if the entity is an organization) or firstName and lastName (if the provider is an individual). You must also provide the provider's National Provider Identifier (npi).

Show attributes

The provider's first name. This property is required if the provider is an individual.

  • Required string length: 1 - 35

The provider's last name. This property is required if the provider is an individual.

  • Required string length: 1 - 60
provider.npistringrequired

The provider's National Provider Identifier (NPI).

  • Pattern: ^\d{10}$

The provider's business name.

  • Required string length: 1 - 60
subscriberobjectrequired

The primary policyholder for the insurance plan or a dependent with a unique member ID. If a dependent has a unique member ID, include their information here and leave dependent empty.

The demographic information you provide must match the payer's data exactly. For example, if the payer has the subscriber's name as Jonathan Doe, a COB request for Jon Doe will fail because the name doesn't match the payer's records. Also note that:

  • Any prefix on the member's card is considered part of the memberID used for the search.
  • Mismatches in the memberId are one of the most common causes of Member Not Found errors. We strongly recommend first performing an Eligibility Check and using the memberId in the response to populate your COB check.
  • We recommend including the ssn property in addition to the memberId if possible. This allows Stedi to do an additional search for the patient when the memberId doesn't return a match.
  • Stedi can identify coverage overlap for the same payer if the member ID differs between the two coverages.
Show attributes

The subscriber's date of birth.

  • Pattern: ^\d{4}-(0[1-9]|1[0-2])-(0[1-9]|[12]\d|3[01])$
subscriber.firstNamestringrequired

The patient's first name.

  • Required string length: 1 - 35
subscriber.lastNamestringrequired

The patient's last name.

  • Required string length: 1 - 60

The member ID for the subscriber's insurance policy.

You must provide at least one of the memberId or ssn properties in the request. However, we recommend including both if possible. This allows Stedi to do an additional search for patient information when the memberId doesn't return a match.

  • Pattern: ^[A-Za-z0-9-]+$
  • Required string length: 1 - 80

The subscriber's Social Security Number (SSN).

You must provide at least one of the memberId or ssn properties in the request. However, we recommend including both if possible. This allows Stedi to do an additional search for patient information when the memberId doesn't return a match.

  • Pattern: ^\d{9}$

This is the Payer ID. Visit the Payer Network for a complete list of supported payers for COB checks. - Each check must be for a participating health plan for which the patient has coverage. For example, if the patient has coverage from Cigna and UnitedHealthcare, a COB check to Aetna will return an error. - Medicare and Medicare Advantage plans aren't supported. If you submit a COB check for a Medicare or Medicare Advantage plan, the request will fail with an AAA = 75 error (Subscriber/Insured Not Found). - Ensure that you're sending the request to the correct payer entity. For example, Blue Cross Blue Shield (BCBS) has multiple entities that operate in different states. If you send a request to the wrong entity, the request will fail with an AAA = 75 error (Subscriber/Insured Not Found).

  • Required string length: 1 - 80

Response

application/json

CoordinationOfBenefits 200 response

benefitsInformationarray<object>

Information about the patient's healthcare benefits, including:

  • Active coverage with the health plan identified in the COB request
  • Coverage overlap (if it exists) with one or more payers
  • Payer primacy details (if Stedi was able to determine)
  • Benefits details, such as coverage dates and service types
Array item

Dates associated with the benefits. All properties may either be expressed as a single date. Dates listed only apply to the benefitsInformation object in which this benefitsDateInformation is provided.

Show attributes

Date or date range used for coordination of benefits instance.

The end of the coverage overlap. Included when Stedi finds an instance of coverage overlap.

The start of the coverage overlap Included when Stedi finds an instance of coverage overlap.

Coverage start date. If multiple coverage start dates exist due to different start dates on various coverage/service types, this date applies to the medical coverage.

Contains either information about another payer with which the patient has coverage or information about the subscriber associated with the additional health plan.

For example, if you submit a COB check for a dependent to Cigna and Stedi finds additional coverage through Aetna, the benefitsRelatedEntity would include subscriber details for the Aetna plan.

Array item

The entity's first name, when the entity is a subscriber.

Code identifying the type of benefitsInformation.entityIdentificationValue. This can be either MI - Member ID or PI - Payer ID.

Possible values
MI
PI

The identification number for the entity, qualified by the code in entityIdentification. The ID returned in this property is proprietary to our COB check product, so you can't use it as the Payer ID for eligibility checks or other API requests to Stedi. It likely doesn't match the Payer IDs listed in the Payer Network.

Identifies the type of entity. This can either be a type of payer or the subscriber associated with the COB coverage.

Note that Stedi uses Payer either when there is no COB instance or when Stedi is unable to determine primacy.

Possible values
Insured or Subscriber
Payer
Primary Payer
Secondary Payer
Tertiary Payer

The entity's last name, when the entity is a subscriber.

The entity's middle name or initial, when the entity is a subscriber.

The payer's business name, when the entity is a payer.

The COB benefits information code.

Stedi returns entries with benefitsInformation.code = 1 for every active coverage type for each health plan.

Stedi returns entries with benefitsInformation.code = R when overlapping coverage exists within the date of service provided in the COB check.

Possible values
1
6
R
V

The name of the benefit information code.

Possible values
Active Coverage
Inactive
Other or Additional Payor
Cannot Process

Code identifying the type of services.

The full names of the service type codes.

Information about the primary policyholder for the insurance plan related to this benefitsInformation instance.

Show attributes

The subscriber's date of birth.

  • Pattern: ^\d{4}-(0[1-9]|1[0-2])-(0[1-9]|[12]\d|3[01])$

An overview of the COB response. It indicates whether there is a coverage overlap, whether that overlap creates a coordination of benefits instance, and whether Stedi was able to identify payer primacy (when a COB instance exists).

Show attributes

If set to true, the COB response contains benefits overlap. A benefits overlap indicates that the patient has active coverage from two or more payers for the same service type code, including the subtypes of medical coverage.

The classification for the benefits that have been discovered in the COB response. Stedi returns one of the following values: - CobInstanceExistsPrimacyDetermined: COB Instance Exists and Primacy was determined - CobInstanceExistsPrimacyUndetermined: COB Instance Exists and Primacy was NOT determined - CoverageOverlapNoBenefitOverlap: Coverage Overlap detected with no Benefit Overlap - CoverageOverlapExistsNotSubjectToCob: Coverage Overlap exists and is not subject to COB - MemberFoundNoCob: Member found, no COB found

If set to true, the COB response contains a coverage overlap, meaning that the patient has active coverage with two or more payers during the service date submitted in the COB request. - Coverage overlap can be for coverages from the same payer if the member ID is different between the two coverages. - A coverage overlap is necessary for a COB instance to exist. - A coverage overlap can exist without there being a COB instance if either of the two coverages is not subject to COB for any reason.

If set to true, the COB response contains at least one coordination of benefits instance.

If set to true, Stedi was able to determine the primary payer for the patient. If Stedi was unable to determine the primary payer, you must contact the payers directly to determine primacy.

dependentobject

Information about the dependent listed in the original COB request.

Show attributes
dependent.aaaErrorsarray<object>

When a COB request fails, the response contains one or more AAA errors that specify the reasons for the rejection and any recommended follow-up actions.

Array item

The error code. Visit Eligibility troubleshooting for a complete list of all possible error codes and descriptions.

Payers may sometimes return other non-compliant values.

Possible values
04
15
33
35
41

The error description.

The error type, AAA.

Allowed actions you can take, based on the rejection reason code. For example Please Correct and Resubmit.

Payers may sometimes return other non-compliant values.

Possible values
Please Correct and Resubmit
Resubmission Not Allowed
Please Resubmit Original Transaction
Resubmission Allowed
Do Not Resubmit; Inquiry Initiated to a Third Party

The location of the error within the original X12 EDI response.

Information to help you correct the error.

The dependent's address.

Show attributes

The first line of the address.

  • Required string length: 1 - 55

The second line of the address.

  • Required string length: 1 - 55

The city.

  • Required string length: 2 - 30

The two-letter country code from Part 1 of ISO 3166.

  • Required string length: 2

The country subdivision code from Part 2 of ISO 3166.

  • Required string length: 1 - 3

The United States or Canadian postal code, excluding punctuation and blanks.

  • Required string length: 5 - 9

The US state or Canadian province code with unknown option. For example, TN for Tennessee or NB for New Brunswick.

Payers may sometimes return other non-compliant values.

Possible values
NL
PE
NS
NB
QC

The number assigned to each family member born with the same birth date, such as twins or triplets. Indicates the birth order when there are multiple births associated with the provided birth date.

The dependent's date of birth.

  • Pattern: ^\d{4}-(0[1-9]|1[0-2])-(0[1-9]|[12]\d|3[01])$

The dependent's first name.

Code indicating the dependent's gender. Can be F - Female, M - Male, or U - Unknown.

Possible values
M
F
U

The group number associated with the subscriber's insurance policy.

The dependent's last name.

The member ID for the subscriber's insurance policy.

The dependent's middle name or initial.

The name of the relationToSubscriberCode. For example, Child when the code is 19.

Possible values
Spouse
Child
Employee
Unknown
Organ Donor

For the dependent, this can be 01 - Spouse, 19 - Child, 20 Employee, 21 - Unknown, 39 - Organ Donor, 40 - Cadaver Donor, 53 - Life Partner, or G8 - Other Relationship.

Possible values
01
19
20
21
39

The dependent's Social Security Number (SSN).

  • Pattern: ^\d{9}$
errorsarray<object>

If the COB request fails, the COB response contains one or more AAA errors that specify the reasons for the rejection and any recommended follow-up actions.

Array item

The error code. Visit Eligibility troubleshooting for a complete list of all possible error codes and descriptions.

Payers may sometimes return other non-compliant values.

Possible values
04
15
33
35
41

The error description.

The error type, AAA.

Allowed actions you can take, based on the rejection reason code. For example Please Correct and Resubmit.

Payers may sometimes return other non-compliant values.

Possible values
Please Correct and Resubmit
Resubmission Not Allowed
Please Resubmit Original Transaction
Resubmission Allowed
Do Not Resubmit; Inquiry Initiated to a Third Party

The location of the error within the original X12 EDI response.

Information to help you correct the error.

metaobject

Metadata about the response. Stedi uses this data for tracking and troubleshooting.

Show attributes

The type of data in the request. Stedi uses production to identify transactions processed in our live clearinghouse environment.

The value provided in the submitterTransactionIdentifier property in the original COB request.

A unique ID Stedi assigns to the COB request.

payerobject

Information about the payer listed in the COB request.

Show attributes

The payer's name, such as CIGNA.

The tradingPartnerServiceId (Payer ID) you used to identify the payer in the COB request.

Dates associated with the patient's health plan coverage. This information is used to determine their eligibility for benefits.

  • The provided dates apply to every every benefit within the patient's health plan unless specifically noted within a benefitsInformation.benefitsDateInformation object.
  • If the payer sends back date(s) that are different for the subscriber and dependents, Stedi includes only the dates for the dependent in this object and omits the subscriber's date(s). Dependents can have different coverage dates than the subscriber due to qualifying life events, such as starting a new job or passing the age limit for coverage through their parent's plan.
Show attributes

When the patient's health plan coverage begins.

  • Pattern: ^\d{4}-(0[1-9]|1[0-2])-(0[1-9]|[12]\d|3[01])$

When the patient's health plan coverage ends.

  • Pattern: ^\d{4}-(0[1-9]|1[0-2])-(0[1-9]|[12]\d|3[01])$
providerobject

Information about the entity that submitted the original coordination of benefits request. This may be an individual practitioner, a medical group, a hospital, or another type of healthcare provider. This object will always include the provider's NPI.

Show attributes
provider.aaaErrorsarray<object>

When a COB request fails, the response contains one or more AAA errors that specify the reasons for the rejection and any recommended follow-up actions.

Array item

The error code. Visit Eligibility troubleshooting for a complete list of all possible error codes and descriptions.

Payers may sometimes return other non-compliant values.

Possible values
04
15
33
35
41

The error description.

The error type, AAA.

Allowed actions you can take, based on the rejection reason code. For example Please Correct and Resubmit.

Payers may sometimes return other non-compliant values.

Possible values
Please Correct and Resubmit
Resubmission Not Allowed
Please Resubmit Original Transaction
Resubmission Allowed
Do Not Resubmit; Inquiry Initiated to a Third Party

The location of the error within the original X12 EDI response.

Information to help you correct the error.

The provider's National Provider Identifier (NPI).

  • Pattern: ^\d{10}$

The provider's first name. This applies to providers that are an individual.

The provider's last name. This applies to providers that are an individual.

The provider's organization name.

Information about the primary policyholder for the insurance plan listed in the COB request.

Show attributes

When a payer rejects your request, the response contains one or more AAA errors that specify the reasons for the rejection and any recommended follow-up actions.

Array item

The error code. Visit Eligibility troubleshooting for a complete list of all possible error codes and descriptions.

Payers may sometimes return other non-compliant values.

Possible values
04
15
33
35
41

The error description.

The error type, AAA.

Allowed actions you can take, based on the rejection reason code. For example Please Correct and Resubmit.

Payers may sometimes return other non-compliant values.

Possible values
Please Correct and Resubmit
Resubmission Not Allowed
Please Resubmit Original Transaction
Resubmission Allowed
Do Not Resubmit; Inquiry Initiated to a Third Party

The location of the error within the original X12 EDI response.

Information to help you correct the error.

The subscriber's address.

Show attributes

The first line of the address.

  • Required string length: 1 - 55

The second line of the address.

  • Required string length: 1 - 55

The city.

  • Required string length: 2 - 30

The two-letter country code from Part 1 of ISO 3166.

  • Required string length: 2

The country subdivision code from Part 2 of ISO 3166.

  • Required string length: 1 - 3

The United States or Canadian postal code, excluding punctuation and blanks.

  • Required string length: 5 - 9

The US state or Canadian province code with unknown option. For example, TN for Tennessee or NB for New Brunswick.

Payers may sometimes return other non-compliant values.

Possible values
NL
PE
NS
NB
QC

The number assigned to each family member born with the same birth date, such as twins or triplets. Indicates the birth order when there are multiple births associated with the provided birth date.

The subscriber's date of birth.

  • Pattern: ^\d{4}-(0[1-9]|1[0-2])-(0[1-9]|[12]\d|3[01])$

The subscriber's first name.

Code indicating the subscriber's gender. Can be F- Female, M - Male, or U - Unknown.

Possible values
M
F
U

The group number associated with the subscriber's insurance policy.

The subscriber's last name.

The member ID for the subscriber's insurance policy.

The subscriber's middle name or initial.

The subscriber's Social Security Number (SSN).

  • Pattern: ^\d{9}$