Appointment Availability1

Appointment Reminders3

Appointment Types2

Appointments5

Charges6

Deltas1

Drugs3

Encounter Types1

Encounters4

Extended Patient Details1

Facilities1

Health Maintenance2

Inventory4

Partner Applications3

Patient Allergies1

Patient Charges3

Patient Documents5

Patient Emails1

Patient Facilities/Specialists7

Patient Free-Text Notes4

Patient Health Maintenance2

Patient Images5

Patient Invoices2

Patient Lab Results1

Patient Orders2

Patient Past Medical History1

Patient Portal4

Patient Prescriptions5

Patient Subscriptions2

Patient Supplements4

Patient Tags3

Patient Vaccines1

Patient Vitals8

Patients6

Questionnaires3

Secure Messages2

Supplements5

Tags4

Tasks4

Users3

Vitals3

Patients

Create a new patient

Data: property-value key-pairs, including nested objects for address and insurance information (match the structure from the GET API call)

Notes: At a minimum, you must provide a first name, last name, date of birth (preferred format is YYYY-MM-DD), and sex (must be M, F, or ?)

post/patients

Request

Base URL: https://clinic-subdomain.md-hq.com/api/v1
URL: https://clinic-subdomain.md-hq.com/api/v1/patients
Auth: HTTP basic

Request body

first_namestring required

last_namestring required

dobstring required

YYYY-MM-DD

sexstring required

must be 'M', 'F', or '?'

inactivestring

Sets the patient status. Accepts the following values:

Value	Result
"prospective" or "-1"	Prospective patient
"0", empty, or omitted	Active patient (default)
"inactive" or "1"	Inactive patient
"deceased" or "dead" or "2"	Deceased patient

Important — GET response behavior:

When reading patient data via GET, the inactive field is cast to a boolean rather than returning the original value. This means:

Stored status	inactive in GET	patient_status_description in GET
Prospective (-1)	true	"prospective"
Active (0)	false	"active"
Inactive (1)	true	"inactive"
Deceased (2)	true	"deceased"

Because inactive returns true for prospective, inactive, and deceased patients alike, you must use the patient_status_description field to determine the actual status. This is a known legacy serialization issue where the create/update and read representations differ.

Response

Successful response

Changes

No recorded changes to this operation across all 1 revision of this API.