Skip to main content
POST
/
public
/
v1
/
patients
Create Patient
curl --request POST \
  --url https://api.silnahealth.com/public/v1/patients/ \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "first_name": "<string>",
  "last_name": "<string>",
  "date_of_birth": "2023-12-25",
  "patient_specialties": [
    "PHYSICAL_THERAPY"
  ],
  "status": "INTAKE",
  "provider_service_location_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "provider_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "source_id": null,
  "address_line_1": null,
  "address_line_2": null,
  "city": null,
  "state": null,
  "zip_code": null
}
'
{
  "patient_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a"
}

​
Patient Creation Walkthrough

  1. Get the provider that you want to create a patient for through the Get Providers API.
  2. Get the service location where the patient receives services through the Get Service Locations API.
  3. Use this endpoint to create a patient with the provider and service location information. We recommend including the EHR ID if you have one available as this will help identify the patient as it is represented in your system.

​
Creation with Place Of Service and Diagnosis Codes

After you create a patient, you can add place of service codes and diagnosis codes by using our Place Of Service and Diagnosis APIs. For Place Of Service, you would do the following:
  1. Get the Place Of Services configured for your provider service location by making a request through the Get Provider Places of Service API .
  2. With the returned place of services, you can then make a POST request to Create Patient Place of Service API with the patient_id of the patient you just created and a provider_place_of_service_id that you got from the Get Service Locations API.
To add a diagnosis to a patient, you would make a POST request to the Create Patient Diagnosis API with the patient_id and a diagnosis code. Please refer to here for a list of ICD-10 diagnosis codes that you can use.

Authorizations

​
Authorization
string
header
required

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

Body

application/json
Patient Create Request Schema

Patient Create Request Schema

​
first_name
string
required

Patient's first name

​
last_name
string
required

Patient's last name

​
date_of_birth
string<date>
required

Patient's date of birth

​
patient_specialties
enum<string>[]
required

Patient's specialties. A patient can have multiple

Available options:
PHYSICAL_THERAPY,
ABA_THERAPY,
SPEECH_THERAPY,
OCCUPATIONAL_THERAPY,
PSYCHOLOGICAL_TESTING,
HOME_HEALTH_CARE,
HOSPICE,
CARDIAC_REHABILITATION,
INTENSIVE_CARDIAC_REHABILITATION,
MENTAL_HEALTH,
PRINCIPAL_ILLNESS_NAVIGATION,
PRINCIPAL_CARE_MANAGEMENT,
ADVANCED_PRIMARY_CARE_MODELS,
PREVENTATIVE_HEALTH,
PARTIAL_HOSPITALIZATION_PROGRAM,
INTENSIVE_OUTPATIENT_PROGRAM,
INTERVENTIONAL_RADIOLOGY,
VASCULAR_SURGERY,
INTERVENTIONAL_CARDIOLOGY,
ORTHOPEDICS,
CHIROPRACTIC,
GYNECOLOGY,
LONG_TERM_CARE,
NUTRITIONAL_COUNSELING
​
status
enum<string>
required

Patient's status

Available options:
INTAKE,
ACTIVE,
DISCHARGED,
ON_HOLD
​
provider_service_location_id
string<uuid>
required

Provider Service Location ID (where the patient receives service)

​
provider_id
string<uuid>
required
​
source_id
string | null

Patient's EHR ID (or other unique identifier) that you have in your system

​
address_line_1
string | null

Patient's street address

Maximum string length: 255
​
address_line_2
string | null

Patient's apartment, suite, unit, etc.

Maximum string length: 255
​
city
string | null

Patient's city

Maximum string length: 255
​
state
string | null

Patient's state

Maximum string length: 255
​
zip_code
string | null

Patient's zip code

Response

Patient Create Response Schema

Patient Create Response Schema

​
patient_id
string<uuid>
required