Request Flow

The /determinations endpoint follows a synchronous pattern.

sequenceDiagram
participant Y as You
participant M as MyndAuth

rect rgba(0, 0, 255, .1)
Note right of Y: Request review of prior authorization
Y->>M: POST /determinations
M->>Y: 200 OK [FHIR Resource Bundle in body]
end

The /authorizations endpoint follows an asynchronous pattern. When a request is submitted MyndAuth will return a Content-Location header where the results of the request can be accessed.

sequenceDiagram
    participant Y as You
    participant M as MyndAuth

rect rgba(0, 0, 255, .1)
Note right of Y: Create a work request
Y->>M: POST /authorizations
M->>Y: 202 Accepted - `Content-Location: /v1/authorizations/fe98f349-743e-4163-ba4e-e1e48c379b4b`
end

rect rgba(0, 0, 255, .1)
loop Poll for results 
Y->>M: GET /v1/authorizations/fe98f349-743e-4163-ba4e-e1e48c379b4b
Note left of M: Work not yet complete
M->>Y: 202 Accepted
end
end

rect rgba(0, 0, 255, .1)
Note left of M: Work complete!
Y->>M: GET /v1/authorizations/fe98f349-743e-4163-ba4e-e1e48c379b4b
M->>Y: 200 OK [FHIR Resource Bundle in body]
end

When polling for results you MUST implement the following backoff policy:

1. For 60 minutes after the initial POST you MUST NOT poll more often than ONCE every 5 minutes.
2. After 60 minutes and up to 24 hours after the initial POST you MUST NOT poll more often than once every 60 minutes.
3. 24 hours after the initial POST poll every 4 hours.
4. You SHOULD poll at least once every 8 hours until a 200 status code is returned.

Excessive GET requests may result the rate limiting of your API access!