The table below lists the magic numbers that can be used to trigger various scenarios when performing an easyclaim transactions against the integration server simulator (ISS).
The magic number should be given for the patient member number, unless otherwise stated.
| Magic Number | Description | Result | Extra Info |
|---|---|---|---|
| 202 | An Easyclaim transaction receives 202 in response to the start transaction message | UNSUCCESSFUL |
Accepted
|
| 400 | An Easyclaim transaction receives 400 in response to the start transaction message | UNSUCCESSFUL |
Bad request
|
| 403 | An Easyclaim transaction receives 403 in response to the start transaction message | UNSUCCESSFUL |
Authentication failed
|
| 404 | An Easyclaim transaction receives 404 in response to the start transaction message | UNSUCCESSFUL |
Not found
|
| 409 | An Easyclaim transaction receives 409 in response to the start transaction message | UNSUCCESSFUL |
Conflict
|
| 410 | An Easyclaim transaction receives 410 in response to the start transaction message | UNSUCCESSFUL |
Unknown resource
|
| 500 | An Easyclaim transaction receives 500 in response to the start transaction message | UNSUCCESSFUL |
Server error
|
| 501 | An Easyclaim transaction receives 501 in response to the start transaction message | UNSUCCESSFUL |
Not implemented
|
| 502 | An Easyclaim transaction receives 502 in response to the start transaction message | UNSUCCESSFUL |
Bad gateway
|
| 503 | An Easyclaim transaction receives 503 in response to the start transaction message | UNSUCCESSFUL |
Service unavailable
|
| 504 | An Easyclaim transaction receives 504 in response to the start transaction message | UNSUCCESSFUL |
Gateway timeout
|
| Magic Number | Description | Result | Extra Info |
|---|---|---|---|
| 20200 | An easyclaim transaction is initiated, and progresses, however a HTTP 202 error is received in the response to one of the update requests | UNSUCCESSFUL |
Accepted
|
| 40000 | An easyclaim transaction is initiated, and progresses, however a HTTP 400 error is received in the response to one of the update requests | UNSUCCESSFUL |
Bad request
|
| 40300 | An easyclaim transaction is initiated, and progresses, however a HTTP 403 error is received in the response to one of the update requests | UNSUCCESSFUL |
Authentication failed
|
| 40400 | An easyclaim transaction is initiated, and progresses, however a HTTP 404 error is received in the response to one of the update requests | UNSUCCESSFUL |
Not found
|
| 41000 | An easyclaim transaction is initiated, and progresses, however a HTTP 410 error is received in the response to one of the update requests | UNSUCCESSFUL |
Unknown resource
|
| 50000 | An easyclaim transaction is initiated, and progresses, however a HTTP 500 error is received in the response to one of the update requests | UNSUCCESSFUL |
Server error
|
| 50200 | An easyclaim transaction is initiated, and progresses, however a HTTP 502 error is received in the response to one of the update requests | UNSUCCESSFUL |
Bad gateway
|
| 50300 | An easyclaim transaction is initiated, and progresses, however a HTTP 503 error is received in the response to one of the update requests | UNSUCCESSFUL |
Service unavailable
|
| 50400 | An easyclaim transaction is initiated, and progresses, however a HTTP 504 error is received in the response to one of the update requests | UNSUCCESSFUL |
Gateway timeout
|