Claim edit: Discharge hour on non-final institutional claims
Claims
Stedi now rejects 837I institutional claims that include a discharge hour but use a claim frequency code that indicates the patient has not been discharged.
How the edit works
In institutional claims, the discharge hour tells the payer when the patient left the facility.
Discharge hour
Claim type | JSON API field | X12 element |
837I institutional |
|
Institutional claims also include a claim frequency code that tells the payer where the claim falls in a patient's billing cycle.
Claim frequency code
Claim type | JSON API field | X12 element |
837I institutional |
|
Some claim frequency codes, such as 2 (Interim – First Claim), indicate the patient is still receiving care and has not yet been discharged. Claims with these frequency codes are called non-final claims.
A discharge hour should not be included on non-final claims. If it is, the payer may reject the claim.
This edit catches the issue before the claim reaches the payer. It prevents payer rejections, which are slower 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.
The error message references the claim’s bill type. This is a combination of the claim’s facility type code and claim frequency code.
For example, bill type 112 indicates facility type 11 (Hospital inpatient – general) with frequency code 2 (Interim – First Claim).
{ "errors": [ { "code": "33", "description": "Invalid Discharge Date/hour. Discharge information should not be present for the submitted bill type 112. These fields are only used for final inpatient claims. Correct and resubmit.", "followupAction": "Please Correct and Resubmit" } ] }
{ "errors": [ { "code": "33", "description": "Invalid Discharge Date/hour. Discharge information should not be present for the submitted bill type 112. These fields are only used for final inpatient claims. Correct and resubmit.", "followupAction": "Please Correct and Resubmit" } ] }
{ "errors": [ { "code": "33", "description": "Invalid Discharge Date/hour. Discharge information should not be present for the submitted bill type 112. These fields are only used for final inpatient claims. 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, entity identifier code, and error message:
STC*A7>190*20260407*U*500.0********Invalid Discharge Date/hour. Discharge information should not be present for the submitted bill type 112. These fields are only used for final inpatient claims. Correct and resubmit
STC*A7>190*20260407*U*500.0********Invalid Discharge Date/hour. Discharge information should not be present for the submitted bill type 112. These fields are only used for final inpatient claims. Correct and resubmit
STC*A7>190*20260407*U*500.0********Invalid Discharge Date/hour. Discharge information should not be present for the submitted bill type 112. These fields are only used for final inpatient claims. Correct and resubmit
Stedi now rejects 837I institutional claims that include a discharge hour but use a claim frequency code that indicates the patient has not been discharged.
How the edit works
In institutional claims, the discharge hour tells the payer when the patient left the facility.
Discharge hour
Claim type | JSON API field | X12 element |
837I institutional |
|
Institutional claims also include a claim frequency code that tells the payer where the claim falls in a patient's billing cycle.
Claim frequency code
Claim type | JSON API field | X12 element |
837I institutional |
|
Some claim frequency codes, such as 2 (Interim – First Claim), indicate the patient is still receiving care and has not yet been discharged. Claims with these frequency codes are called non-final claims.
A discharge hour should not be included on non-final claims. If it is, the payer may reject the claim.
This edit catches the issue before the claim reaches the payer. It prevents payer rejections, which are slower 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.
The error message references the claim’s bill type. This is a combination of the claim’s facility type code and claim frequency code.
For example, bill type 112 indicates facility type 11 (Hospital inpatient – general) with frequency code 2 (Interim – First Claim).
{ "errors": [ { "code": "33", "description": "Invalid Discharge Date/hour. Discharge information should not be present for the submitted bill type 112. These fields are only used for final inpatient claims. 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, entity identifier code, and error message:
STC*A7>190*20260407*U*500.0********Invalid Discharge Date/hour. Discharge information should not be present for the submitted bill type 112. These fields are only used for final inpatient claims. 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.
