The Data Elements That Make a Professional Claim
A professional claim combines submitter and receiver information, patient and subscriber data, billing and rendering provider identifiers, service facility, diagnoses, claim-level references, and line-level services, dates, codes, modifiers, units, and charges. Requirements depend on the transaction, payer, service, and circumstances.
Updated 2 min read
On this page
Key takeaways
- Professional claim data comes from multiple governed sources.
- Situational data should be present only when the applicable condition is true.
- Claim-level and line-level relationships are as important as individual field formats.
What it controls
A professional claim combines submitter and receiver information, patient and subscriber data, billing and rendering provider identifiers, service facility, diagnoses, claim-level references, and line-level services, dates, codes, modifiers, units, and charges. Requirements depend on the transaction, payer, service, and circumstances.
The claim is not a flat list of fields. Relationships between subscriber and patient, provider roles, diagnosis pointers, claim and line data, and situational segments determine whether the payer can identify and adjudicate what was submitted.
Design the work
Group data by operational source and owner: registration, eligibility, provider master, encounter, documentation, coding, authorization, charge entry, and payer configuration. This makes an edit actionable because the team knows which source should be corrected.
Distinguish always-required, situational, payer-specific, and not-applicable data using current official and payer instructions. Do not populate a field with guessed or default information merely to satisfy a format check.
Minimum controls
- Source ownership for each material claim data group.
- Current transaction, code-set, form, and payer instruction versions.
- Relationship validation between claim-level and line-level information.
- Audit history for corrections and submitted claim versions.
Keep claim-specific information in the approved system
Put it into practice
Map each data group
Identify its approved source, owner, format, and applicable condition.Assemble relationships
Connect patient, subscriber, providers, diagnoses, services, and references correctly.Validate the claim version
Confirm required and situational data before release and preserve what was sent.
Review and improve
Review the control on a fixed cadence and after a material policy, payer, system, staffing, or workflow change. Compare the current process with its documented design, sample the evidence it produces, and record exceptions separately from completed routine work. A control that exists only in a policy but leaves no observable evidence cannot be evaluated reliably.
Use findings to change the upstream process, not merely to clear the current queue. Assign one owner, one next action, and one follow-up date. Preserve the definition and baseline used for the review so a later result can be compared without changing the measurement after the fact.
Frequently asked questions
Does the CMS-1500 show every 837P data element?
No. The paper form and electronic transaction overlap but are not identical representations, and electronic transactions can carry structures not visible on the form.
Which payer rule should be followed?
Use applicable official requirements, the payer’s current instructions and companion guide, and contractual or program rules for the claim circumstances.
Operational terms
Authoritative sources
- Medicare Claims Processing Manual (opens in a new tab)
Centers for Medicare & Medicaid Services
- Medicare Billing: CMS-1500 and 837P (opens in a new tab)
Centers for Medicare & Medicaid Services