In the EHR
Vitals are recorded in a patient’s chart as part of a note. One collection holds the readings taken at a single point in time — height, weight, blood pressure, heart rate, respiratory rate, temperature, oxygen saturation, head circumference, and pain — together with a BMI. Providers enter them in the vitals section of a visit note, or on a non-visit note when recording readings from outside records. See Adding historical vitals.Working with vitals via the API
Four behaviors to know before you build against this object. A create without a note creates one. APOST that omits both visit_note and non_visit_note opens a new visit note in the patient’s chart and attaches the vitals to it. Send visit_note or non_visit_note when the readings belong on a note that already exists.
A visit note carries one collection. A POST naming a visit_note that already has vitals responds 409 with a redirect field holding the id of the existing collection. Update that collection to add readings to the note.
An empty array clears a reading. A PATCH that sets a reading to [], such as "weight": [], removes that reading and leaves the collection on its note, and bmi keeps its value when height or weight is cleared. Clear readings this way when the note stays in the chart, and send a corrected bmi alongside a cleared height or weight.
Deleting a note removes the vitals on it. A collection is deleted through its note: deleting a visit note or a non-visit note removes that note’s vitals and sets the collection’s deleted_date to the time of the delete. Delete the note when both the note and its vitals should be removed.