Handling errors

Guide to handling errors.

GraphQL Errors

GraphQL Error Docs

• Malformed payloads
• Authentication errors
• Tuuthfairy server error

{
	"errors": [{
		"message": "AUTHENTICATION_ERROR",
		"locations": [{
			"line": 2,
			"column": 3
		}],
		"path": [ "eligibility" ],
		"extensions": {
			"code": "INTERNAL_SERVER_ERROR"	
			}
		}
	],
	"data": null
}

User Errors

User or input errors are usually found in mutations. Generally this is a validation input error that prevented the request from being made. The the field attribute will describe which is the offending field and a description of how to fix in the message field.

{
  "data": {
    "requestEligiblity": {
	    "result": null,
	    "userErrors": [{
		    "type": "invalid_request",
			"field": "payerId",
			"message": "Field must not be empty"
	    }]
    }
  }
}

Request Errors

A valid input was received, but the payer system replied with an error.

{
	"data": {
		"eligibility": {
			"id": "unique-id",
			"requestStatus": [{
				"message": "patient_member_dob_error",
				"source": "edi",
				"status": "error"
			}],
			"plan": null
		}
	}
}

Patient Input Errors

• patient_member_name_error - Generic payer error, but could mean that the patients name has changed (ex. Married/hyphenated names or special characters like apostrophes). Salutations and suffixes should be omitted.
• patient_member_dob_error - Most common case is when only a dependent is sent without the subscriber. Subscriber information is required for dependent requests.
• patient_member_group_number_error - Invalid group number. We recommend not sending the group number for eligibility requests, as it's often a source of error or out dated.
• patient_member_id_duplicate_error - Occasionally payers have older plans still in their systems, and requires more specificity to pull the plan. We'd recommend retrying with the group number to be sent. This error is not common.
• patient_not_found_error - Generic catch all, and likely means the patient does not belong to this payer, or patient information is invalid.

Provider input errors

• provider_npi_error - Valid 10 digit NPI is required. We validate NPI's against the NPPES registery
• provider_name_error - Payers rarely complain about the provider name.
• provider_not_authorized_error - Payer requires provider to be registered.

Payer server issues

• payer_not_supported_error - Tuuthfairy doesn't currently support the payerId that was requested. Please contact tuuthfairy support.
• payer_unable_to_respond_error - Generic error from the payer system. You'll see this message when payers have scheduled maintenance or are throttling requests. Retry the request at a later time.
• payer_unknown_error - Payer system produced a system error or timed out. Retry the request at a later time.