I work in a hospital & I am working on a database to keep track of the monthly comings & goings of our medical students & residents, as well as a lot of demographic data. I am designing the database so that it can be shared by the various clinical departments and the Education department. The problem is that the Education department starts updating their information in the early spring in prparation for the July 1 "New Year". This means updating all the residents in the database...PGY-1 to PGY-2, PGY-4 to PGY-5 (PGY = Post-Graduate Year...PGY-1 is a 1st-year resident), graduation, etc. However, the clinical services will be using the same database to generate monthly schedules that are dependant on having the current status. Therin lies the problem....Education must update the data WAY in advance, to get it out to others who will need it to prepare, while current data is still needed until early June by the clinical services.
I thought of creating a temporary copy that one goup or the other could use, but there is a secondary table used by the clinical services to update the rotations. They will not complete this until early June. Meanwhile, Education continues to update their future data (preparing for July 1) All spring and into June also.
How can I easily acommodate both users? Is there a way to delay updates until a particular date?
I thought of creating a temporary copy that one goup or the other could use, but there is a secondary table used by the clinical services to update the rotations. They will not complete this until early June. Meanwhile, Education continues to update their future data (preparing for July 1) All spring and into June also.
How can I easily acommodate both users? Is there a way to delay updates until a particular date?
