Question:
What does remote_chgid represent in the Claim.MD API, and how should it be formatted?
Answer:
remote_chgid Overview
The remote_chgid (charge ID) is a value you supply in your JSON claim submission to uniquely identify each service line (procedure code). Claim.MD passes this value through unchanged to the payer, and when the payer adjudicates the claim and returns an ERA (835), the payment details are typically reported at the charge line level and include the same remote_chgid value.
Why remote_chgid Matters for ERA Processing
This is especially important during ERA processing, because payers may split or combine charge lines as part of adjudication, which can alter how the original CPT codes appear in the response. By returning the original remote_chgid, the payer provides a reliable way to match payment details back to the originating service line, even when the adjudicated structure differs from the submitted claim.
Formatting Recommendations
Because remote_chgid is transmitted directly to and echoed back from the payer, it should be formatted carefully. We recommend using strictly alphanumeric characters (letters and numbers only). Special characters are discouraged, as some payers do not handle them consistently.
We also recommend limiting remote_chgid to 12 characters or fewer. Some payers may truncate longer values in ERA responses, which can complicate payment reconciliation.
Best Practice Summary
When remote_chgid values are short, alphanumeric, and unique per charge line, they provide a consistent and reliable mechanism for matching ERA payment details to the original submitted services.
Please see these links for further reference:
https://docs.claim.md/docs/how-are-deductibles-represented-in-eligibility-benefit-results
200 OK → result → elig → benefit
remote_chgid (charge ID) is a value you supply in your JSON claim submission to uniquely identify each service line (procedure code). Claim.MD passes this value through unchanged to the payer, and when the payer adjudicates the claim and returns an ERA (835), the payment details are typically reported at the charge line level and include the same remote_chgid value.This is especially important during ERA processing, because payers may split or combine charge lines as part of adjudication, which can alter how the original CPT codes appear in the response. By returning the original remote_chgid, the payer provides a reliable way to match payment details back to the originating service line, even when the adjudicated structure differs from the submitted claim.Because remote_chgid is transmitted directly to and echoed back from the payer, it should be formatted carefully. We recommend using strictly alphanumeric characters (letters and numbers only). Special characters are discouraged, as some payers do not handle them consistently.We also recommend limiting remote_chgid to 12 characters or fewer. Some payers may truncate longer values in ERA responses, which can complicate payment reconciliation.When remote_chgid values are short, alphanumeric, and unique per charge line, they provide a consistent and reliable mechanism for matching ERA payment details to the original submitted services.remote_chgid (charge ID) is a value you supply in your JSON claim submission to uniquely identify each service line (procedure code). Claim.MD passes this value through unchanged to the payer, and when the payer adjudicates the claim and returns an ERA (835), the payment details are typically reported at the charge line level and include the same remote_chgid value.This is especially important during ERA processing, because payers may split or combine charge lines as part of adjudication, which can alter how the original CPT codes appear in the response. By returning the original remote_chgid, the payer provides a reliable way to match payment details back to the originating service line, even when the adjudicated structure differs from the submitted claim.Because remote_chgid is transmitted directly to and echoed back from the payer, it should be formatted carefully. We recommend using strictly alphanumeric characters (letters and numbers only). Special characters are discouraged, as some payers do not handle them consistently.We also recommend limiting remote_chgid to 12 characters or fewer. Some payers may truncate longer values in ERA responses, which can complicate payment reconciliation.When remote_chgid values are short, alphanumeric, and unique per charge line, they provide a consistent and reliable mechanism for matching ERA payment details to the original submitted services.