I understand it is consistent with ITIL policy to pre-denfine a “Standard” change (like Cloverleaf table move, Communication parameter change, etc) that allows you to streamline the Change Management process. That was a huge productivity booster for our team.
So we have 3 levels of change at our large multi-hospital organization, and they seem to be working well. The first is the normal change process, which we meet once a week, and larger Cloverleaf changes need to be done off hours, but smaller ones can be done as long as we get buy in from the affected user community. There are what is called standard changes, things that are low risk, and have no outage. Table changes fall into this category as well as global monitor changes, etc. Finally there is Emergency changes, which are needed to fix an ongoing production issue, read we’re already down, fix it now.
Hope this helps and good luck on your change adventure,
.
.