Changes and deployments

A clinical application release needs a maintenance window. The change manager records the affected service, risk, scheduled start and end, and rollback plan. The advisory reviewer records a decision and reason. An approved change enters implementation, while a service deployment outcome and change rollback checks remain available for review. A deferred change remains available for the next decision.

The advisory review belongs to a Change and records a reviewer, decision and reason. Match the service deployment to the planned change by service, window and version during review. Rollback checks retain expected and actual results against the Change.

• Plan. The Clinical Change Manager records risk, maintenance window, service and rollback plan on the Change.
• Review. The Change Advisory Reviewer records Approve, Reject or Defer with a reason on the advisory review.
• Observe. The manager checks the service deployment status and records rollback check results against the Change.

A pending review is not approval. A deployment marked Pending or Deploying is not a verified healthy outcome. Keep the observed result separate from the planned window.

Agree who can record the advisory decision and which evidence the reviewer needs for a high-risk change. Identify the deployment source and how its service and version will be matched to the scheduled Change. Set the rollback checkpoints before the window opens.

Rehearse a deferred decision and a failed deployment. The team should preserve the review reason and actual check result. An implementation status should follow an approving decision, not merely the creation of a review row.

Use a planned application release. Compare the service, risk, scheduled start and end, and rollback plan with the advisory review. Have the reviewer record a decision and reason. If approved, follow the service deployment from Pending through its observed outcome.

Review a rollback check against the same Change. The manager should explain whether the actual result matched the expected result and whether the Change can be marked Verified or rolled back. A failed observation should remain visible rather than be replaced by the plan.

A deferred advisory decision calls for another review of the plan and window. A rejected decision ends that proposed path. For an approved change, the manager compares the planned service with the deployment’s service and checks the actual rollback results before marking the change Verified. Retain the reviewer’s reason beside the decision.

• Clinical Changes In Review — Review the filtered records and choose the next action.
• Clinical Change Schedule — Open related records before the handoff.

Follow the related process.