Validation Endpoint Issue

When the /validation endpoint encounters issues in the claim evaluation, it will list in the response.

```json
{
    "status": "EDITS",
    "controlNumber": "000000001",
    "tradingPartnerServiceId": "9496",
    "claimReference": {
        "correlationId": "201117R999898~53196482361992277",
        "submitterId": "009998999898",
        "customerClaimNumber": "000000001",
        "patientControlNumber": "12345",
        "timeOfResponse": "2020-11-17T17:46:02.792-06:00",
        "claimType": "INS"
        "formatVersion": "5010"
    },
    "errors": [
        {
            "field": "01",
            "value": "1",
            "description": "The Type of Admission is required and must be valid.\n\nLOOP 2300 CL101",
            "location": "2300 CL1"
        },
        {
            "field": "claimInformation.otherSubscriberInformation.IndividualRelationshipCode",
            "description": "Allowed Values are: '01' Spouse, '18' Self, '19' Child, '20' Employee, '21' Unknown, '39' Organ Donor, '40' Cadaver Donor, '53' Life Partner, 'G8' Other Relationship"
        }
    ]
}
```

Some error listings will also show the EDI loop and element in which the error occurred. Most error listings will also show the EDI loop and element in which the error occurred. The example here shows that the admissionTypeCode in Loop 2300, Element CL101, has an incorrect value and must contain one of the values specified in the correction text. For more information, see Error types in Professional claims.

✍️ In the sandbox request, using value: test00005 (lower case and not uppercase), for
fieldName: patientControlNumber returns a EDITS canned response.

Updated 3 months ago