Leap Day has no impact on CA eHealth, related CA products

Document created by natma01 Employee on Jan 13, 2016Last modified by SamCreek on Dec 17, 2016
Version 2Show Document
  • View in full screen mode

 

Hello, eHealth Community,

 

Just wanted to drop a note to confirm that you should not expect any problems on or around February 29, 2016 related to the 2016 Leap Day. During the most recent Leap Day in 2012, we were not alerted to any problems with CA eHealth performance, functionality or reporting that related back to the Leap Day.

 

Brief History of Leap Day

Leap Days are needed to keep our calendar in alignment with the Earth's revolutions around the Sun. Adding a Leap Day at the end of February every four years has become a routine way to reconcile our current-day twelve-month annual Gregorian Calendar with the Earth's slowing revolutions.


Technical Statement 

There is no need for eHealth Administrators or Users to be concerned with the 2016 Leap Day, which will happen on Monday, February 29, 2016. The impact is that eHealth Users and Admins will notice 29 days worth of data for February, instead of the usual 28, and should not experience any problems with CA eHealth performance, functionality or reporting that related to the Leap Day.

 

 

More Info

For more information, please visit http://www.timeanddate.com/date/leapyear.html

 

 

-Margaret, Sr Product Manager, Enterprise Management

Attachments

    Outcomes