A practical guide to completing Box 6: Patient Relationship to Insured accurately and consistently.

From our workflow: Patient Relationship to Insured may be a small entry, but it affects the rest of the claim. We compare it with the source record and then confirm that the surrounding fields tell the same story.

Show how the patient is related to the insured or subscriber.

The payer does not read Patient Relationship to Insured in isolation. We compare it with the surrounding claim data before deciding the entry is ready.

General rule: Payer-specific instructions, contracts, program manuals, and current coding guidance can add to or override general form guidance. Verify requirements before submission.

Why payers care about this value

For Patient Relationship to Insured, we also check the related patient, insured, provider, diagnosis, and service-line data. A field can pass a format edit and still be inconsistent with the claim around it.

Passing an edit is not the same as filing an accurate claim. For Patient Relationship to Insured, correct the underlying record instead of substituting a value that merely looks acceptable.

How to enter it consistently

  1. Identify the person, organization, date, code, or identifier the field is asking for.
  2. Locate the source document: insurance card, eligibility response, clinical note, authorization, provider enrollment record, fee schedule, or payer remittance.
  3. Enter the value using the form’s structure and the payer’s required format.
  4. Compare it with related fields and service lines for consistency.
  5. Save evidence of the source and the final submitted claim.

Where errors tend to appear

  • Selecting self when a parent is subscriber.
  • Relying on age alone.
  • Conflicting with eligibility.

We do not treat the last paid claim as the source for Patient Relationship to Insured. It may contain information that was valid then and is no longer valid now.

Before the claim leaves your office

  • Use eligibility or enrollment information.
  • Align with Boxes 2 and 4.
  • Resolve custody or dependent questions before claim submission.
  • Compare the completed claim with the clinical and billing record.
  • Confirm the receiving address or electronic route.
  • Keep a secure copy and proof of submission.

What the software should handle

A dependable program can reuse stable records and flag inconsistent entries for Patient Relationship to Insured. It should not silently guess at information that is absent or uncertain.

Apply this in software: For a workflow that keeps claim data reusable and reviewable, see the CMS-1500 paper and electronic filing options. Software can enforce format and consistency, but the source record and payer instructions still control the claim.
Privacy reminder: Use fictional data for training and printer tests. Claims contain protected information and should be stored, transmitted, printed, and destroyed through approved secure processes.

Written and reviewed by

1500Software Development Team

Covers the software, printing, validation, export, and troubleshooting steps described on this page.

1500Software Claims Review Team

Reviews field placement, provider roles, source records, and practical correction steps.

Reviewed July 26, 2026. Always follow the receiving payer’s current instructions and companion guide.

Official references

These are the national sources we use as a starting point. The receiving payer may add more specific instructions.