Skip to main content

​
Product Enhancements

​
Bug Fixes

​
New Tables (Beta)

The following tables are in beta and may be altered without prior notification. The older vn2_* visit note tables will be removed in a future release.

​
Release Highlights

office_messages: report_id If a report is attached to an office message, report_id now links to the report table. office_messages_recipients: thread removal tracking removed_from_thread (boolean) and removed_at (timestamp) were added to track when recipients are removed from a message thread. appointment: is_blocking The is_blocking flag indicates whether an appointment blocks the provider’s schedule. Defaults to true. med_order: prescription lifecycle and sample tracking
  • supervising_physician_id: the supervising physician for the order
  • fulfillment_state: current state of the prescription: new, failure, error, sent, complete, pending_complete, denied, sending
  • num_samples: populated when the medication is a sample
  • patient_adherence: patient adherence data for the medication
provider_letter: viewed_at Records the timestamp when a provider letter was initially viewed. referral_order: clinical_reason removed The clinical_reason column has been removed. Use the body column instead, which is pulled from the body of the referral. patient_problem: unique key change A bug caused duplicate rows due to incorrect fields being included in the unique key. All unique keys for this table will change as a result of this fix. Customers doing incremental builds will need to account for this. patient_phone: empty string deletions now visible When a phone number was manually removed from a chart, it was previously filtered out. It will now appear as an empty phone number (not as deleted). New Elation Note tables (beta) Six new tables expose structured data from Elation’s custom note blocks. See the entity relationship diagram for details on how these tables relate. Entity relationship diagram showing six beta elation note tables. visit_note links to elation_note, which connects to elation_note_question, elation_note_structured_data, and elation_note_custom_block_snapshot. elation_note_custom_block_snapshot links to elation_note_custom_block (with a self-referencing copied_from_block_id). elation_note_structured_data links to elation_note_question and elation_note_response_option. The versioned_custom_block_id relationship between elation_note_structured_data and elation_note_custom_block_snapshot is highlighted in gold as highly likely to change.
These tables are beta. Schema may change without notice. The vn2_* tables will be removed in a future release.