PUT
/
public
/
v1
/
patient-plans
/
curl --request PUT \
  --url https://api.silnahealth.com/public/v1/patient-plans/ \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "member_number": "<string>",
  "group_number": null,
  "start_date": null,
  "end_date": null,
  "payor_entity_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "insurance_type": null,
  "source_id": "<string>",
  "patient_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "plan_order_number": 123,
  "insurance_card_file_id": null,
  "insurance_card_back_file_id": null,
  "conflict_behavior": "REPLACE",
  "deduplication_strategy": "MEMBER_NUMBER"
}'
{
  "patient_plan_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a"
}

The default behavior of this API has destructive properties! If you have an existing primary plan for a patient and you create a new primary plan for the same patient, the existing primary plan will be deleted/archived and all in progress benefits check and prior authorizations will be withdrawn! If you want to protect against this behavior, we recommend setting conflict_behavior=RAISE_ERROR.

​
Behavior Overview

This API has two flows: update and create. We trigger the update flow if we find a plan for the input patient with a matching source_id or we determine the requested plan to be a duplicate. Else we trigger the create flow. Since all fields are immutable on the patient plan record except for the source_id, we will only update the source_id field in the case when we determine the patient plan to be a duplicate. This means that in the case of source_id match, this API will make no updates and will just return the found patient plan.

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
Request schema for updating a patient plan

Request schema for updating a patient plan

Response

200
application/json
Response schema for creating a patient plan

Response schema for creating a patient plan

PUT
/
public
/
v1
/
patient-plans
/
curl --request PUT \
  --url https://api.silnahealth.com/public/v1/patient-plans/ \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "member_number": "<string>",
  "group_number": null,
  "start_date": null,
  "end_date": null,
  "payor_entity_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "insurance_type": null,
  "source_id": "<string>",
  "patient_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "plan_order_number": 123,
  "insurance_card_file_id": null,
  "insurance_card_back_file_id": null,
  "conflict_behavior": "REPLACE",
  "deduplication_strategy": "MEMBER_NUMBER"
}'
{
  "patient_plan_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a"
}

The default behavior of this API has destructive properties! If you have an existing primary plan for a patient and you create a new primary plan for the same patient, the existing primary plan will be deleted/archived and all in progress benefits check and prior authorizations will be withdrawn! If you want to protect against this behavior, we recommend setting conflict_behavior=RAISE_ERROR.

​
Behavior Overview

This API has two flows: update and create. We trigger the update flow if we find a plan for the input patient with a matching source_id or we determine the requested plan to be a duplicate. Else we trigger the create flow. Since all fields are immutable on the patient plan record except for the source_id, we will only update the source_id field in the case when we determine the patient plan to be a duplicate. This means that in the case of source_id match, this API will make no updates and will just return the found patient plan.

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
Request schema for updating a patient plan

Request schema for updating a patient plan

Response

200
application/json
Response schema for creating a patient plan

Response schema for creating a patient plan