Field Deprecation Warning
April 1st, 2026 is the last day of support for writing toinsurances field. insurances will become read only on April 2nd, and all writes must go through the new insurance policies endpoints. Please see https://help.elationhealth.com/articles/rest/insurance-api/transitioning-from-patient-endpoints and the FAQ for more details.
Object Definition
Allowed Values
Preventing Duplicate Patients
When you create a patient, Elation checksfirst_name, last_name, dob, and sex against existing patients in the practice. If all four match an existing patient, the request returns a 409 Conflict instead of creating a new chart, to prevent accidental duplicates.
Two different patients can occasionally share all four of these fields. This safeguard can’t be bypassed through the API — if you’ve confirmed the patient you’re creating is not a duplicate of the existing match, create the chart manually in the Elation web UI instead (which allows it), then query or pull the new patient’s profile to retrieve their generated id and use that going forward via the API.
Setting Patient Providers
primary_physician represents the physician providing care to the patient within your practice. This is a required field. This value must match theid of one of the physicians retrieved via the Find Physicians endpoint.
primary_care_provider_npi represents the patient’s primary care provider. This person may be in a different practice. This field is not required.
primary_care_provider is a read-only field that provides the internal Elation id of the collaborator record that is created within your practice to represent your practice’s connection with the patient’s primary care provider.
Working with patients via the API
A patient’smetadata.object_web_link appears as a link in the patient chart. Practice users see it on the patient’s profile, labeled with your application’s vendor name and using metadata.object_id as the link text, while your application is active for the practice. The link opens the URL in a new tab exactly as stored. Include your own patient identifier in the URL so the link opens the matching record in your application. See Metadata for the field format.