UVIS : what went wrong and what we can learn from it
| dc.contributor.author | Wilson, Bennett M. | |
| dc.date.accessioned | 2008-11-10T20:16:04Z | |
| dc.date.available | 2008-11-10T20:16:04Z | |
| dc.date.issued | 2006-05-03 | |
| dc.description.abstract | In order to better understand the current problems we are having with Universal Veterinary Information Software, or UVIS, we must first take a look back and see where UVIS came from. In the late 1990s there was international concern about the impact of Y2K on computer software. Similar to today, our lives are inextricably linked to computers and computer software. The focus was on what all the computer systems were going to do when the date changed from 1999 or rather from '99 to '00? Would nothing happen, or would computers stop working? Would airplanes come crashing out of the sky? Appropriately so, Cornell University College of Veterinary Medicine was also concerned about how Y2K might effect their computers and software. | |
| dc.identifier.uri | https://hdl.handle.net/1813/11611 | |
| dc.language.iso | en_US | en_US |
| dc.relation.ispartofseries | Senior seminar paper | en_US |
| dc.relation.ispartofseries | Seminar SF610.1 2006 W56 | |
| dc.subject | Veterinary medicine -- Data processing | |
| dc.subject | Medical records | |
| dc.title | UVIS : what went wrong and what we can learn from it | en_US |
| dc.type | term paper | en_US |