Claim edit: Invalid diagnosis-related group code format
Claims
Stedi now rejects 837I institutional claims with a diagnosis-related group (DRG) code that isn't three or four numeric digits.
Diagnosis-related group codes
In institutional claims, a diagnosis-related group (DRG) code groups inpatient hospital stays into categories expected to consume similar resources. DRG 470 covers inpatient hip or knee replacements without complications.
Payers use DRG codes to determine fixed reimbursement rates under DRG-based contracts with providers. Medicare inpatient hospital reimbursement is the most common use case, though Medicaid and some commercial plans use different DRG systems. DRG codes are only required if the provider's payer contract uses DRG reimbursement.
Diagnosis-related group code (DRG)
Claim type | JSON API field | X12 element |
837I institutional |
|
|
How the edit works
X12 standards require all valid DRG codes to be three or four numeric digits. If a claim’s DRG code is a different length or contains a non-numeric character, the payer may reject the claim.
This edit catches the issue before the claim reaches the payer. It prevents payer rejections, which take longer to resolve and delay payment for the provider.
Rejection errors
If you submit a claim using Stedi's Claim Submission API endpoints and the claim fails the edit, you'll get back an error response in real time. The response includes details in the errors array:
{ "errors": [ { "code": "33", "description": "Invalid Diagnosis Related Group (DRG) code. When entered, the DRG code must be three or four numerics and a valid code. The submitted code, 47A, is invalid. Correct and resubmit.", "followupAction": "Please Correct and Resubmit" } ] }
{ "errors": [ { "code": "33", "description": "Invalid Diagnosis Related Group (DRG) code. When entered, the DRG code must be three or four numerics and a valid code. The submitted code, 47A, is invalid. Correct and resubmit.", "followupAction": "Please Correct and Resubmit" } ] }
{ "errors": [ { "code": "33", "description": "Invalid Diagnosis Related Group (DRG) code. When entered, the DRG code must be three or four numerics and a valid code. The submitted code, 47A, is invalid. Correct and resubmit.", "followupAction": "Please Correct and Resubmit" } ] }
If you submit a claim using SFTP and the claim fails the edit, Stedi will reject the claim with a 277CA claim acknowledgment. The acknowledgment will include a related claim status category code, claim status code, and error message:
STC*A7>256*[DATE]*U*[AMOUNT]********Invalid Diagnosis Related Group (DRG) code. When entered, the DRG code must be three or four numerics and a valid code. The submitted code, 47A, is invalid. Correct and resubmit
STC*A7>256*[DATE]*U*[AMOUNT]********Invalid Diagnosis Related Group (DRG) code. When entered, the DRG code must be three or four numerics and a valid code. The submitted code, 47A, is invalid. Correct and resubmit
STC*A7>256*[DATE]*U*[AMOUNT]********Invalid Diagnosis Related Group (DRG) code. When entered, the DRG code must be three or four numerics and a valid code. The submitted code, 47A, is invalid. Correct and resubmit
Stedi now rejects 837I institutional claims with a diagnosis-related group (DRG) code that isn't three or four numeric digits.
Diagnosis-related group codes
In institutional claims, a diagnosis-related group (DRG) code groups inpatient hospital stays into categories expected to consume similar resources. DRG 470 covers inpatient hip or knee replacements without complications.
Payers use DRG codes to determine fixed reimbursement rates under DRG-based contracts with providers. Medicare inpatient hospital reimbursement is the most common use case, though Medicaid and some commercial plans use different DRG systems. DRG codes are only required if the provider's payer contract uses DRG reimbursement.
Diagnosis-related group code (DRG)
Claim type | JSON API field | X12 element |
837I institutional |
|
|
How the edit works
X12 standards require all valid DRG codes to be three or four numeric digits. If a claim’s DRG code is a different length or contains a non-numeric character, the payer may reject the claim.
This edit catches the issue before the claim reaches the payer. It prevents payer rejections, which take longer to resolve and delay payment for the provider.
Rejection errors
If you submit a claim using Stedi's Claim Submission API endpoints and the claim fails the edit, you'll get back an error response in real time. The response includes details in the errors array:
{ "errors": [ { "code": "33", "description": "Invalid Diagnosis Related Group (DRG) code. When entered, the DRG code must be three or four numerics and a valid code. The submitted code, 47A, is invalid. Correct and resubmit.", "followupAction": "Please Correct and Resubmit" } ] }
If you submit a claim using SFTP and the claim fails the edit, Stedi will reject the claim with a 277CA claim acknowledgment. The acknowledgment will include a related claim status category code, claim status code, and error message:
STC*A7>256*[DATE]*U*[AMOUNT]********Invalid Diagnosis Related Group (DRG) code. When entered, the DRG code must be three or four numerics and a valid code. The submitted code, 47A, is invalid. Correct and resubmit
Get started with Stedi
Get started with Stedi
Automate healthcare transactions with developer-friendly APIs that support thousands of payers. Contact us to learn more and speak to the team.
Get updates on what’s new at Stedi
Get updates on what’s new at Stedi
Get updates on what’s new at Stedi
Product
Developers
Resources
Backed by
Stedi and the S design mark are registered trademarks of Stedi, Inc. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.
Product
Developers
Resources
Get updates on what’s new at Stedi
Backed by
Stedi and the S design mark are registered trademarks of Stedi, Inc. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.
Product
Developers
Resources
Backed by
Stedi and the S design mark are registered trademarks of Stedi, Inc. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.
