General Locking Scenarios:

  Existing:
		1436165 The service will return a 409 error if the charted view is currently locked by a different personnel provided in the request.
		1436164 The service will succeed if the charted view is currently locked by the same personnel provided in the request or is able to be locked.
		1436168 The service will lock the charted view with the personnel id provided in the request when the call is successful.
		1436167 The service will lock a charted view for a time span of 10 minutes.
		1436169 The service will update the lock status of the charted view to "locked" when locking the charted view is successful.
		1436170 The service will update the lock status of the charted view to "unlocked" when the charted view is successfully uncharted.

  To deprecate:
		1436171 The service will only lock charted views that have the ability to be locked based on the type of charted view provided in the request.

  New:
   	1. The service will lock the view if the charted view source is MPC or IC.
		2. The service will not lock the view if the charted view source is ML or STATIC.

Locking Scenarios specific to unchart charted view service:
  Existing:
		1436162 The service will create a lock for the charted view and unchart the charted view when a current lock does not exist.
		1436172 The service will release the lock for the charted view when uncharting the view is successful.
		1436174 The service will release the lock, and will not unchart the charted view if the unchart documentation privilege is set to no.
		1436175 The service will release the lock, and will not unchart the charted view if the version of the charted view is invalid.
		1436177 The service will release the lock, and will not unchart the charted view if the relationship provided is invalid.