Options you could explore
=========================
1) If *everything* is in EST timezone, then perhaps set the database timezone to that and partition ORDER_DATE storing it as TIMESTAMP WITH LOCAL TIMEZONE.
2) Store everything as UTC, and partition on that. It is possible to get *some* performance degradation for queries right at the partition boundary, but you could minimize that by partitioning with an hour offset as well. For example,
SQL> select timestamp '2020-01-01 05:00:00 UTC' d1,
2 timestamp '2020-01-01 05:00:00 UTC' at time zone 'EST' d2
3 from dual;
D1 D2
-------------------------------------------------- -------------------------------------
01-JAN-20 05.00.00.000000000 AM UTC 01-JAN-20 12.00.00.000000000 AM EST
So I could use "values less than ( timestamp '2020-01-01 05:00:00')" and store all my timestamps as UTC. Queries from midnight to midnight in EST will not span boundaries.
I generally prefer all my timestamps to be stored in UTC - it's the one thing that won't change, unlike other zones where daylight saving switchovers etc all make things more complicated.