What Early Release is
When a change to the Hosted Database is ready but is still inside its notice period, or is waiting on a scheduled release date, Elation can build a copy of the affected table with the change already applied and share it into your Hosted Database in theearly_release schema. The GA table is untouched, so nothing you have in production changes.
That gives you two things:
- Early access. If you are waiting on a new table or column to unblock work on your side, you can start querying it now instead of at the GA date.
- A place to test. Every change is fully validated by Elation before it reaches Early Release, so the channel is not where a change gets its first exercise. It is there so you can confirm the change lands cleanly in your environment: point a test run at the Early Release table and see your own pipelines and queries handle it before the change reaches the table they read today.
Currently in Early Release
The table below lists every change available in the ER channel today, with its GA date where one has been set. A blank GA date means the date has not been fixed yet. Select change notes on a row to read what is changing and what to check on your side.Where to find it
The ER tables are in theearly_release schema of your Hosted Database, alongside your existing GA tables. The same users and roles that read your GA tables can read them.
If the schema is not visible to a user who can read your GA tables, contact the Elation Support Portal with the subject line HDB - Early Release access.
Working with Early Release data
- Query the
early_releaseschema. Each pending change is published there under the same table name as GA — for exampleearly_release.med_orderalongsidemed_order. Point test queries and validation runs at the ER schema explicitly; a schema swap is enough to evaluate a change without rewriting table names in every query. - Do not run production reporting off it. The channel exists for validation and early adoption work. A change in ER can still be adjusted before GA.
- Expect only the affected tables. ER adds a table per pending change, not a duplicate of your Hosted Database.
- Column order can differ. ER tables are built on a parallel pipeline, so ordinal position may not match GA even when a column’s name and type are the same. Named selects are unaffected; positional exports or loads that rely on GA column order are not.
Change notes
Patient forms
Queryearly_release.patient_form and the six tables below. Seven new tables report on the patient forms a practice sends and the patients who fill them in: which forms a patient was sent, whether each is complete, and how long completion took. They are a non-breaking change under Change Management: additions, which carry no notice period, so no query you run today is affected. No GA date is set yet.
Working with these tables
- History starts at 2024-07-11. Forms created before then and not edited since may be missing, as may submissions made before then and not changed since. Left join
patient_formfor a form’s name, so rows whose form is missing are kept. - Deleted ad-hoc requests are mostly unanswered ones. Filtering on
patient_form_request.deletion_timetherefore drops most of the forms that went unanswered, which understates a response rate. To count every form that was sent, keep deleted requests. - Required forms reflect today’s setup. Keep
patient_form_appointment_typerows wheredeletion_timeis null for an appointment type’s current forms. When a form was added isn’t recorded, so the forms a past appointment required come from how its type is set up today. - Form names are the current name. A renamed form shows its new name on earlier requests and submissions too.
- A submitted form may have no submission row.
patient_form_request_form.patient_form_submission_idcan point to a submission that is not in your Hosted Database, usually because the form predates 2024-07-11. Left joinpatient_form_submission. - Count submissions from
patient_form_submission. Rows inreportwithreport_type = 'PatientForm'are not a count of submitted forms; some have no submission behind them. - Appointment forms emails are per appointment, not per form. Which forms an email listed, and who sent it, are not recorded.
- “Opened” is per request, and request links don’t expire.
viewed_atapplies to a whole ad-hoc request rather than to each form on it, and appointment forms have no opened signal at all. The nearest states to expired are overdue and deleted. - No question or answer content. These tables carry form metadata and status only, never the questions on a form or patients’ answers.
Appointment time changes
Queryearly_release.appointment_time_change. A new table that records every time an appointment’s scheduled time was set or changed, one row per change: when an appointment was rescheduled, the time it moved from and to, and who moved it. It is a non-breaking change under Change Management: an addition, which carries no notice period, so no query you run today is affected. No GA date is set yet.
Working with this table
- The first row is the booking. The row where
old_appt_timeis null records the time set when the appointment was booked. Every other row is a reschedule fromold_appt_timetonew_appt_time, so to count reschedules, keep rows whereold_appt_timeis not null. - Read an appointment’s history in order. Filter on
appointment_idand sort bymodified_time. The appointment’s current time isappointment.appt_time. - Appointment times and change times use different time zones.
old_appt_timeandnew_appt_timeare in your practice’s time zone, likeappointment.appt_time.modified_timeis in Pacific Time. Convert one before comparing them, for example to measure how far ahead of the appointment a reschedule was made. - Rows are never changed or removed, including when the appointment is later deleted. To leave out deleted appointments, join
appointmentand filter on itsdeletion_time. - Some changes are made by Elation system users. Changes made through an integration rather than by a person are recorded against an Elation system user, which may not appear in
user. Left joinuserso these rows are kept. - Only the scheduled time is recorded. Changes to an appointment’s duration, provider, type or status are not.
Frequently Asked Questions
Does Early Release cost extra?
No. It is included with your Hosted Database.Is Early Release data real, and is it current?
Yes to both. It is your own data, not synthetic or sample data, and it is subject to the same access controls as the rest of your Hosted Database. ER tables are built on the same refresh cadence as your GA tables, so the only difference between the two is the pending change itself.What happens on the GA date?
The change lands in your GA table as described in its release notes, and the ER table is retired. If you built test queries against theearly_release schema, repoint them at the GA schema.
Related Articles
If you have any questions about this topic please reach out to Elation Support Portal with the subject line HDB - <your_question>