Create Authorization Line Access
Create a new authorization line access record.
The access record data is specified in the body of the request. The data is a JSON object conforming to the DI file specification for access records. All field names must be lowercase.
If there is an existing data match for the new access record, the record is not created. When the call is accepted it returns an operations URL that the requesting client uses to track the status of the request.
The lookup keys for the authorization record to update are included in the query parameters, authnumber and authlinenumber.
Sample Request Format
Required key fields are highlighted.
POST [base URL]/authorization/line/access?authnumber=[authnumber]&authlinenumber=[authlinenumber]
{
“idtype”: “”,
“providerid”: “”,
“role”: “”
}
Sample Response Format
HTTP/1.1 202 Accepted
Operation-Location: [base URL]/operation/[operationId]
Update
Authorization Line Access
Update an authorization line access record.
This is a sparse update; only fields being changed need to be included.
The lookup keys for the authorization line access record to update are included in the query parameters, authnumber, authlinenumber, idtype, and providerid.
Sample Request Format
PATCH
[base URL]/authorization/line/access?authnumber=[authnumber]&authlinenumber=[authlinenumber]&idtype=[idtype]&providerid=[providerid]
{
“role”: “”
}
Sample Response Format
HTTP/1.1 202 Accepted
Operation-Location: [base URL]/operation/[operationId]
Delete Authorization Line Access
Delete an authorization line access record.
The lookup keys for the authorization line access record to delete are included in the query parameters, authnumber, authlinenumber, idtype, and providerid.
Sample Request Format
DELETE
[base URL]/authorization/line/access?authnumber=[authnumber]&authlinenumber=[authlinenumber]&idtype=[idtype]&providerid=[providerid]
Sample Response Format
HTTP/1.1 202 Accepted
Operation-Location: [base URL]/operation/[operationId]