Skip to main content
This release links orders to the note they were placed from, flags confidential notes, reports, and orders, and adds the date a clinical form was administered. All three are non-breaking changes under Change Management: columns are added and no existing column changes.

​
Schema Changes

​
Release Highlights

Orders linked to the note they were placed from An order placed from inside a visit note or a non-visit note, such as a phone note, now carries that note’s id. This connects orders to the visit they came from: the visit type, the diagnoses on the note, and whether the order was placed during a visit or between visits. Both columns are empty for an order created outside a note. See Ordering medical tests for your patients for how orders are placed in the chart. Working with these columns
  • Filter med_order.origin = 'rx' to count prescriptions placed outside a note. Rows with origin = 'surescripts' are imported medication history and never carry a note.
  • Count orders in misc_orders with count(distinct id). The table has one row per order for each test and diagnosis code on it.
Example queries are in Visit Notes. Confidential notes, reports, and orders confidential is true when a note, report, or order is marked confidential in the chart, and confidential_marked_by_user_id names the user who marked it. confidential_marked_by_user_id is empty when the document is not confidential. See Managing confidential records for how records are marked. This counts confidential visit notes by month, leaving out deleted notes:
When a clinical form was administered screening_date is when a form such as a PHQ-9 was administered. creation_time is when it was saved in Elation. Use screening_date to report when a screening happened, and creation_time to audit when it was documented. screening_date defaults to when the clinician opened the form, or when the patient submitted it for a patient form, so it is usually a little earlier than creation_time: minutes for forms filled out in the chart, sometimes days for patient forms. That gap on its own does not mean the form was backdated. Clinicians can also change the date, including after the form is saved. See Structured Questionnaires for the forms in the chart. clinical_form_collection has one row per question on a form, so every row of a form carries the same screening_date. The new columns are described in the Hosted Database schema. If you have any questions about this topic please reach out to Elation Support Portal with the subject line HDB - <your_question>