# Claim edit: Missing first name

> Stedi now rejects 837P professional, 837D dental, and 837I institutional claims that include a person entity with no first name.

Published Apr 13, 2026

Product: Claim edits

Stedi now rejects [837P professional](https://www.stedi.com/docs/healthcare/submit-professional-claims), [837D dental](https://www.stedi.com/docs/healthcare/submit-dental-claims), and [837I institutional](https://www.stedi.com/docs/healthcare/submit-institutional-claims) claims that include a person entity with no first name.

## How the edit works

In a claim, each entity, such as the billing provider or subscriber, is identified as either a person or a non-person using an entity type qualifier.

When an entity is a person, a first name is required. If the first name is missing, the payer may reject the claim.

This [edit](https://www.stedi.com/docs/healthcare/claim-edits-and-repairs#edits) catches the issue before the claim reaches the payer. It prevents payer rejections, which are slower and delay payment for the provider.

## How entity type qualifiers are specified

If you use Stedi's [JSON Claim Submission API endpoints](https://www.stedi.com/docs/healthcare/intro-to-claim-submission#api-claim-submission), Stedi sometimes infers the entity type qualifier. For example, if you provide a [`firstName`](https://www.stedi.com/docs/healthcare/api-reference/post-healthcare-claims#body.billing.firstName) and [`lastName`](https://www.stedi.com/docs/healthcare/api-reference/post-healthcare-claims#body.billing.lastName) for the [`billing`](https://www.stedi.com/docs/healthcare/api-reference/post-healthcare-claims#body.billing) provider in a [JSON 837P Professional Claims API request](https://www.stedi.com/docs/healthcare/api-reference/post-healthcare-claims), the entity is treated as a person. If you provide an `organizationName`, the entity is treated as an organization. Other entities, such as [`otherPayerBillingProvider`](https://www.stedi.com/docs/healthcare/api-reference/post-healthcare-claims#body.claimInformation.otherSubscriberInformation.otherPayerBillingProvider), have an explicit [`entityTypeQualifier`](https://www.stedi.com/docs/healthcare/api-reference/post-healthcare-claims#body.claimInformation.otherSubscriberInformation.otherPayerBillingProvider.entityTypeQualifier) field.

If you use X12, you set the entity type qualifier directly in `NM1-02` (Entity Type Qualifier), where `1` indicates a person and `2` indicates a non-person entity.

## Rejection errors

If you submit a claim using Stedi's [Claim Submission API endpoints](https://www.stedi.com/docs/healthcare/intro-to-claim-submission#api-claim-submission) and the claim fails the edit, you'll get back an error response in real time. The response includes details in the `errors` array.

```jsonc
{
  "errors": [
    {
      "code": "33",
      "description": "Missing First Name. When the Billing Provider entity is a person, as identified by the entity type qualifier 1, the entity first name is required. Correct and resubmit.",
      "followupAction": "Please Correct and Resubmit"
    }
  ]
}
```

If you submit a claim using [SFTP](https://www.stedi.com/docs/healthcare/submit-claims-sftp-connection) and the claim fails the edit, Stedi will reject the claim with a [277CA claim acknowledgment](https://www.stedi.com/docs/healthcare/claim-responses-overview#277ca-claim-acknowledgment). The acknowledgment will include a related [claim status category code](https://x12.org/codes/claim-status-category-codes), [claim status code](https://x12.org/codes/claim-status-codes), entity identifier code, and error message.

```jsx
STC*A6>505>85*[DATE]*U*[AMOUNT]********Missing First Name. When the Billing Provider entity is a person, as identified by the entity type qualifier 1, the entity first name is required. Correct and resubmit.~
```