Professional and Institutional Claims: Operational Differences
Professional and institutional claims represent different billing structures. Professional claims commonly use CMS-1500 or 837P conventions; institutional claims commonly use UB-04 or 837I conventions with facility-oriented data such as bill types, revenue codes, and statement periods. The applicable instructions control each claim.
Updated 2 min read
On this page
Key takeaways
- Professional and institutional claims are distinct data and operating structures.
- Shared controls do not mean identical field or correction rules.
- Claim-type decisions should be supported and routed to qualified owners when unclear.
What it controls
Professional and institutional claims represent different billing structures. Professional claims commonly use CMS-1500 or 837P conventions; institutional claims commonly use UB-04 or 837I conventions with facility-oriented data such as bill types, revenue codes, and statement periods. The applicable instructions control each claim.
Routing both claim classes through identical edits, work queues, or correction procedures can remove required data or apply the wrong assumptions. Systems and teams should preserve the claim type from source through submission and follow-up.
Design the work
Document which entities, services, settings, and billing arrangements create each claim type. Map the source systems and qualified owners for provider roles, dates, diagnoses, procedures, revenue codes, bill types, occurrence or value information, and other applicable data.
Keep shared controls—source traceability, completeness, duplicate prevention, release authority, submission proof—while tailoring validation and correction paths to the actual transaction and payer instructions.
Minimum controls
- Claim-type determination based on approved billing arrangements and instructions.
- Separate validation rules for professional and institutional structures.
- Qualified routing for coding and claim-type questions.
- Claim-type-specific batch, acknowledgment, correction, and retention procedures.
Keep claim-specific information in the approved system
Put it into practice
Determine the claim class
Use the billing entity, service, setting, and applicable program or payer requirements.Apply the correct data contract
Validate the fields, relationships, codes, and transaction required for that class.Preserve the path
Retain claim type through acknowledgments, corrections, remittance, denial, and reporting.
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
Is place of service enough to choose claim type?
No. Billing entity, service, setting, enrollment, program, contractual, and transaction requirements can all matter.
Can one organization submit both claim types?
Yes, when its services and billing arrangements require them; each path still needs appropriate systems, rules, and controls.
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