277CA Report
Retrieve a 277CA claim acknowledgment in JSON format
/change/medicalnetwork/reports/v2/{transactionId}/277The 277CA claim acknowledgment indicates whether a claim was accepted or rejected and (if relevant) the reasons for rejection. This endpoint retrieves processed 277CA transactions from Stedi.
- Call this endpoint with the
transactionIdof the 277CA you want to retrieve. You can retrieve the transaction ID through webhooks or through Stedi's API. Learn more - The endpoint returns the 277CA in JSON format.
- Visit 277CA claim status details to learn which parts of the 277CA contain claim status information.
- Visit Correlate 277CA to learn how to match 277CAs to the original claim.
A Stedi API Key for authentication.
Path Parameters
A unique identifier for the processed 277 transaction within Stedi. This ID is included in the transaction processed event, which you can receive automatically through Stedi webhooks. You can also retrieve it through the Poll Transactions endpoint or from the transaction's details page within the Stedi portal.
Response
ConvertReport277 200 response
Metadata that helps Stedi track and debug the response.
Show attributes
Whether this is a test or production ERA.
An identifier for the most recent sender of the ERA. This is usually not the original sender, so this value is unlikely to be a payer ID. When Stedi processes and delivers ERAs through the clearinghouse, this value is always STEDI.
Not currently used.
The Stedi transaction identifier.
The payer's 277 response.
Array item
The control number the payer provided in the claim status response. This is used to identify the transaction.
Information about the payer (or intermediary clearinghouse) and the claim status transactions included in the response.
Array item
The payer's Centers for Medicare and Medicaid Services Plan ID. This is specifically for Health Plan ID (HPID) or Other Entity Identifier (OEID), both of which are no longer mandated for use.
Claim status details.
Array item
More detailed status information. This includes information about the patient, provider, and services rendered.
Array item
Patient information and the status of claims related to the patient. You can use the claims.claimStatus.referencedTransactionTraceNumber in this object to correlate the 277CA with the original claim.
Some payers batch acknowledgments for multiple claims into a single 277CA. In these cases, the 277CA will contain multiple patientClaimStatusDetails objects, each with its own referencedTransactionTraceNumber for the corresponding claim.
Array item
Status information for the claim or service line.
Array item
Status information for the claim. This object includes the referencedTransactionTraceNumber you can use to correlate the 277CA with the original claim.
Show attributes
The bill type identification.
The starting date of the service.
- Pattern:
^\d{4}(0[1-9]|1[0-2])(0[1-9]|[12]\d|3[01])$
The date of the service.
- Pattern:
^\d{4}(0[1-9]|1[0-2])(0[1-9]|[12]\d|3[01])$
The ending date of the service.
- Pattern:
^\d{4}(0[1-9]|1[0-2])(0[1-9]|[12]\d|3[01])$
The identifier the clearinghouse assigned to the original claim.
Claim status information.
Array item
This is the date of denial or approval for the claim. This date may or may not be the same as the issue date of the check, EFT, or non-payment remittance. Some payers can provide this date before they issue the remittance.
- Pattern:
^\d{4}(0[1-9]|1[0-2])(0[1-9]|[12]\d|3[01])$
The total amount of the claim payment, expressed as a decimal. This may be zero if no payment is being made. Some payers can provide the adjudicated payment amount before they issue the remittance.
Array item
A code indicating the entity that is responsible for the claim.
0336404171The description of the entityIdentifierCode.
DependentEmployerReceiverSubmitterAttending PhysicianCode indicating the status category of the statusCode property. Visit 277CA code lists for a complete list.
A0A1A2A3A4Description of the healthCareClaimStatusCategoryCode property. Visit 277CA code lists for a complete list.
A National Council for Prescription Drug Programs (NCPDP) reject code.
A code indicating the status.
01236This is the check issue or EFT funds available date. This could be a non-payment remittance date, if available.
- Pattern:
^\d{4}(0[1-9]|1[0-2])(0[1-9]|[12]\d|3[01])$
This is the check or EFT Trace Number. This could also be a non-payment remittance advice Trace Number (835 or paper), if available.
The effective date of the status information.
- Pattern:
^\d{4}(0[1-9]|1[0-2])(0[1-9]|[12]\d|3[01])$
Additional free-form information about the claim status.
The total amount of charges in the original claim, expressed as a decimal. This may differ from the total charges submitted due to claims processing instructions, such as claim splitting. Note that some HMO encounters supply zero as the amount of original charges.
The patient control number provided in the original claim. You can use this value to correlate the payer's response with the original claim.
The Pharmacy Prescription Number.
The patient control number provided in the original claim. You can use this value to correlate the payer's response with the original claim.
The payer's unique identifier for the claim.
The voucher identifier. Some payers assign voucher identifiers to a group of claims as part of the payment process prior to payment being issued.
Information about specific services within a claim. This object is only included in the 277CA when the claim is rejected because of errors with the service line information provided.
Array item
The starting date of the service.
- Pattern:
^\d{4}(0[1-9]|1[0-2])(0[1-9]|[12]\d|3[01])$
The ending date of the service.
- Pattern:
^\d{4}(0[1-9]|1[0-2])(0[1-9]|[12]\d|3[01])$
A unique identifier for the service line that matches the providerControlNumber submitted in the original claim. You can use this value to correlate the payer's response with specific service lines from the original claim.
Information about the service provided.
Show attributes
The amount paid for the service, expressed as a decimal.
The submitted service charge, expressed as a decimal.
The identifying code for the product or service.
Identifies special circumstances related to the performance of the service.
The National Uniform Billing Committee Revenue Code.
The code identifying the source of the procedureCode.
ADERHCHPIVThe description of the serviceIdQualifierCode.
American Dental Association CodesJurisdiction Specific Procedure and Supply CodesHealth Care Financing Administration Common Procedural Coding System (HCPCS) CodesHealth Insurance Prospective Payment System (HIPPS) Skilled Nursing Facility Rate CodeHome Infusion EDI Coalition (HIEC) Product/Service CodeThe number of units of service that were submitted, expressed as a decimal.
The status of the specific service line.
Array item
The date the status information is effective.
The status of the service.
Array item
A code indicating the entity that is responsible for the service line.
0336404171The description of the entityIdentifierCode.
DependentEmployerReceiverSubmitterAttending PhysicianCode indicating the status category of the statusCode property. Visit 277CA code lists for a complete list.
A0A1A2A3A4Description of the healthCareClaimStatusCategoryCode property. Visit 277CA code lists for a complete list.
A National Council for Prescription Drug Programs (NCPDP) reject code.
A code indicating the status.
01236The date of the service.
- Pattern:
^\d{4}(0[1-9]|1[0-2])(0[1-9]|[12]\d|3[01])$
Information about a dependent who received services related to the claim.
Show attributes
The first name of the dependent. Can be up to 35 characters.
The last name of the dependent. Can be up to 60 characters.
The middle name or initial of the dependent. Can be up to 25 characters.
The suffix of the dependent, such as Jr or III. Can be up to 10 characters.
Information about the primary policy holder for the health plan.
Show attributes
The subscriber's employer identification number. This may be used in conjunction with a worker's compensation claim.
The first name of the subscriber. Can be up to 35 characters.
The last name of the subscriber. Can be up to 60 characters.
The subscriber's member ID for their health plan.
The middle name or initial of the subscriber. Can be up to 25 characters.
The subscriber's business name. Applicable when an employer submitted a worker's compensation claim, or other situations when an employer is the subscriber.
Deprecated; do not use.
The suffix of the subscriber, such as Jr or III. Can be up to 10 characters.
An identifier for claims related to this provider.
Information about the service provider.
Show attributes
The provider's first name, when the provider is an individual. Can be up to 35 characters.
The provider's last name, when the provider is an individual. Can be up to 60 characters.
The provider's middle name or initial, when the provider is an individual. Can be up to 25 characters.
The provider's National Provider Identifier.
- Pattern:
^\d{10}$
The provider's business name. Can be up to 60 characters.
The provider's service provider number.
The provider's name suffix, when the provider is an individual. Can be up to 10 characters.
The provider's tax identification number.
Status information for claims related to the provider.
Array item
The status of claims related to this provider.
Array item
Code indicating the entity that the status is related to.
364041AYPRThe description of the entityIdentifierCode.
EmployerReceiverSubmitterClearinghousePayerCode indicating the status category of the statusCode property. Visit 277CA code lists for a complete list.
A0A1A2A3A4Description of the healthCareClaimStatusCategoryCode property. Visit 277CA code lists for a complete list.
Code indicating the status.
01236The description of the statusCode.
The date the status information is effective.
The payer's unique identifier for the claim.
Information about the provider receiving the claim status details.
Show attributes
The provider's Electronic Transmitter Identification Number.
The provider's first name. Can be up to 35 characters.
The provider's last name. Can be up to 60 characters.
The provider's middle name or initial. Can be up to 25 characters.
The provider's business name. Can be up to 60 characters.
Overall status information for the claim.
Array item
The status of the entire claim.
Array item
Code indicating the entity that the status is related to.
364041AYPRThe description of the entityIdentifierCode.
EmployerReceiverSubmitterClearinghousePayerCode indicating the status category of the statusCode property. Visit 277CA code lists for a complete list.
A0A1A2A3A4Description of the healthCareClaimStatusCategoryCode property. Visit 277CA code lists for a complete list.
Code indicating the status.
01236The description of the statusCode.
The date the claim status information is effective.
- Pattern:
^\d{4}(0[1-9]|1[0-2])(0[1-9]|[12]\d|3[01])$
Code identifying the type of organization.
AYPRThe human-readable description of the entity identifier code.
ClearinghousePayerThe payer's Electronic Transmitter Identification Number.
The payer's Federal Taxpayer Identification Number.
- Pattern:
^\d{9}$
The payer or intermediary clearinghouse's business name.
The payer's business contact information.
Show attributes
Each contact will have a single property set, except for phone with extension.
Array item
The Electronic Data Interchange Access Number.
The email address.
The fax number.
The telephone number including the area code (if applicable). Phone numbers are formatted as AAABBBCCCC, where AAA represents the area code, BBB represents the telephone number prefix, and CCCC represents the telephone number. Phone numbers are provided without separators, such as dashes or parentheses. For example, 5551123345 for 555-112-3345.
The telephone extension, if applicable.
The name of the contact person or entity.
The payer's unique identifier.
A number the payer assigns to the transaction to identify it within their system.
The date the payer created the transaction.
- Pattern:
^\d{4}(0[1-9]|1[0-2])(0[1-9]|[12]\d|3[01])$
The time the payer created the transaction, expressed in 24-hour clock time. May be formatted as HHMM, HHMMSS, HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99).
- Pattern:
^([01]\d|2[0-3])[0-5]\d$|^([01]\d|2[0-3])[0-5]\d[0-5]\d$|^([01]\d|2[0-3])[0-5]\d[0-5]\d\d$|^([01]\d|2[0-3])[0-5]\d[0-5]\d\d\d$
curl --request GET \
--url "https://healthcare.us.stedi.com/2024-04-01/change/medicalnetwork/reports/v2/{transactionId}/277" \
--header "Authorization: <api_key>"fetch("https://healthcare.us.stedi.com/2024-04-01/change/medicalnetwork/reports/v2/{transactionId}/277", {
headers: {
"Authorization": "<api_key>"
}
})package main
import (
"fmt"
"net/http"
"io/ioutil"
)
func main() {
url := "https://healthcare.us.stedi.com/2024-04-01/change/medicalnetwork/reports/v2/{transactionId}/277"
req, _ := http.NewRequest("GET", url, nil)
req.Header.Add("Authorization", "<api_key>")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := ioutil.ReadAll(res.Body)
fmt.Println(res)
fmt.Println(string(body))
}import requests
url = "https://healthcare.us.stedi.com/2024-04-01/change/medicalnetwork/reports/v2/{transactionId}/277"
response = requests.request("GET", url, headers = {
"Authorization": "<api_key>"
})
print(response.text)import java.net.URI;
import java.net.http.HttpClient;
import java.net.http.HttpRequest;
import java.net.http.HttpResponse;
import java.net.http.HttpResponse.BodyHandlers;
import java.time.Duration;
HttpClient client = HttpClient.newBuilder()
.connectTimeout(Duration.ofSeconds(10))
.build();
HttpRequest.Builder requestBuilder = HttpRequest.newBuilder()
.uri(URI.create("https://healthcare.us.stedi.com/2024-04-01/change/medicalnetwork/reports/v2/{transactionId}/277"))
.header("Authorization", "<api_key>")
.GET()
.build();
try {
HttpResponse<String> response = client.send(requestBuilder.build(), BodyHandlers.ofString());
System.out.println("Status code: " + response.statusCode());
System.out.println("Response body: " + response.body());
} catch (Exception e) {
e.printStackTrace();
}{
"meta": {
"transactionId": "71716ec5-0e96-462f-bb77-869941bb27ab"
},
"transactions": [
{
"controlNumber": "1001",
"payers": [
{
"claimStatusTransactions": [
{
"claimStatusDetails": [
{
"patientClaimStatusDetails": [
{
"claims": [
{
"claimStatus": {
"claimServiceBeginDate": "20240101",
"claimServiceEndDate": "20240101",
"clearinghouseTraceNumber": "01J1SNT1FQC8ABWD44MAMBDYKA",
"informationClaimStatuses": [
{
"informationStatuses": [
{
"healthCareClaimStatusCategoryCode": "A1",
"healthCareClaimStatusCategoryCodeValue": "Acknowledgement/Receipt - The claim/encounter has been received. This does not mean that the claim has been accepted for adjudication.",
"statusCode": "20",
"statusCodeValue": "Accepted for processing."
}
],
"statusInformationEffectiveDate": "20240702",
"totalClaimChargeAmount": "109.20"
}
],
"patientAccountNumber": "11122233",
"referencedTransactionTraceNumber": "11122233"
}
}
],
"subscriber": {
"firstName": "JOHN",
"lastName": "ANON",
"memberId": "U7777788888"
}
}
],
"providerOFServiceInformationTraceIdentifier": "0",
"serviceProvider": {
"npi": "1235600834",
"organizationName": "THERAPY ASSOCIATES"
}
}
],
"claimTransactionBatchNumber": "01J1SNRJ0FP4ZE6EFWM4G4XB3N",
"provider": {
"etin": "1235600834",
"organizationName": "TEST DATA HEALTH SERVICES, INC."
},
"providerClaimStatuses": [
{
"providerStatuses": [
{
"healthCareClaimStatusCategoryCode": "A1",
"healthCareClaimStatusCategoryCodeValue": "Acknowledgement/Receipt - The claim/encounter has been received. This does not mean that the claim has been accepted for adjudication.",
"statusCode": "20",
"statusCodeValue": "Accepted for processing."
}
],
"statusInformationEffectiveDate": "20240702"
}
]
}
],
"organizationName": "STEDI INC"
}
],
"referenceIdentification": "1511096803",
"transactionSetCreationDate": "20240702",
"transactionSetCreationTime": "0815"
}
]
}{
"code": "string",
"message": "string"
}{
"code": "string",
"message": "string"
}{
"code": "string",
"message": "string"
}{
"code": "string",
"message": "string"
}{
"code": "string",
"message": "string"
}{
"code": "string",
"message": "string"
}{
"code": "string",
"message": "string"
}