New claim edit: Missing admission source code
Dec 12, 2025
Stedi now rejects 837I institutional claims that are missing a required admission source code.
In an institutional claim, the admission source code tells you where the patient came from, such as the emergency room (ER), a doctor’s referral, or another facility.
Most institutional claims require this code. Without it, the payer can’t adjudicate the claim. The one exception is non-patient lab services, where no patient is present.
If the code is missing when required, the payer may reject the claim, which can cause payment delays.
This edit – the industry’s term for an automated validation rule – catches the issue before the claim reaches the payer.
When this edit applies
An institutional claim will fail this edit in the following cases:
JSON API
If you’re using Stedi’s JSON institutional claim submission API endpoint, the edit fails if:The
admissionSourceCodefield is missing or empty.
ANDThe
placeOfServiceCodefield does not contain14(Non-Patient Laboratory).
Raw X12
If you’re using raw X12, the edit fails if:
Rejection errors
If you submit a claim that fails the edit using Stedi’s institutional claim submission API endpoints, you’ll get back an error message in real time. If you’re using the JSON API endpoint, the response includes error details in the errors array:
{ "errors": [ { "code": "33", "description": "Missing admission source code. This code is required on all institutional claims with the exception of non-patient laboratory claims (Type of Bill 014x). Correct and resubmit.", "followupAction": "Please Correct and Resubmit" } ] }
If you submit a claim that fails the edit using SFTP, Stedi will reject the claim with a 277CA claim acknowledgment. The acknowledgment will contain a related claim status category code, claim status code, and error message. You can use the error message to correct and resubmit the claim.
Stedi now rejects 837I institutional claims that are missing a required admission source code.
In an institutional claim, the admission source code tells you where the patient came from, such as the emergency room (ER), a doctor’s referral, or another facility.
Most institutional claims require this code. Without it, the payer can’t adjudicate the claim. The one exception is non-patient lab services, where no patient is present.
If the code is missing when required, the payer may reject the claim, which can cause payment delays.
This edit – the industry’s term for an automated validation rule – catches the issue before the claim reaches the payer.
When this edit applies
An institutional claim will fail this edit in the following cases:
JSON API
If you’re using Stedi’s JSON institutional claim submission API endpoint, the edit fails if:The
admissionSourceCodefield is missing or empty.
ANDThe
placeOfServiceCodefield does not contain14(Non-Patient Laboratory).
Raw X12
If you’re using raw X12, the edit fails if:
Rejection errors
If you submit a claim that fails the edit using Stedi’s institutional claim submission API endpoints, you’ll get back an error message in real time. If you’re using the JSON API endpoint, the response includes error details in the errors array:
{ "errors": [ { "code": "33", "description": "Missing admission source code. This code is required on all institutional claims with the exception of non-patient laboratory claims (Type of Bill 014x). Correct and resubmit.", "followupAction": "Please Correct and Resubmit" } ] }
If you submit a claim that fails the edit using SFTP, Stedi will reject the claim with a 277CA claim acknowledgment. The acknowledgment will contain a related claim status category code, claim status code, and error message. You can use the error message to correct and resubmit the claim.
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
Developers
Resources
Get updates on what’s new at Stedi
Backed by
Stedi is a registered trademark 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.
Developers
Resources
Get updates on what’s new at Stedi
Backed by
Stedi is a registered trademark 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.
Get updates on what’s new at Stedi
Backed by
Stedi is a registered trademark 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.