Create Dependent Coverage
Create a new dependent coverage record.
The coverage data is specified in the body of the request. The data is a JSON object conforming to the DI file specification for coverages. All field names must be lowercase.
If there is an existing data match for the new coverage 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 eligibility record to update are included in the query parameters, memberid, groupnumber, and depmemberid.
Sample Request Format
Required key fields are highlighted.
POST [base URL]/eligibility/dependent/coverage?memberid=[memberid]&groupnumber=[groupnumber]&depmemberid=[depmemberid]
{
}
Sample Response Format
HTTP/1.1 202 Accepted
Operation-Location: [base URL]/operation/[operationId]
Update Dependent Coverage
Update a dependent coverage record.
This is a sparse update; only fields being changed need to be included.
The lookup keys for the coverage record to update are included in the query parameters, memberid, groupnumber, depmemberid, covtypename, and coveffdate.
Sample Request Format
PATCH [base URL]/eligibility/dependent/coverage?memberid=[memberid]&groupnumber=[groupnumber]&depmemberid=[depmemberid]&covtypename=[covtypename]&coveffdate=[coveffdate]
{
}
Sample Response Format
HTTP/1.1 202 Accepted
Operation-Location: [base URL]/operation/[operationId]
Delete Dependent Coverage
Delete a dependent coverage record.
The lookup keys for the coverage record to update are included in the query parameters, memberid, groupnumber, depmemberid, covtypename, and coveffdate.
Sample Request Format
DELETE [base URL]/eligibility/dependent/coverage?memberid=[memberid]&groupnumber=[groupnumber]&depmemberid=[depmemberid]&covtypename=[covtypename]&coveffdate=[coveffdate]
Sample Response Format
HTTP/1.1 202 Accepted
Operation-Location: [base URL]/operation/[operationId]
