Can we add 'final' to VERSION.lifecycle_state?
The use case is that in some circumstances a version need to become immutable and any change should be forbidden. Imagine a care plan that was already 'inform-consented' - it should not be allowed to be changed in any way, neither logically deleted (unless perhaps some administrative reasons). In contrast, by current version of specifications, a 'complete' version can be still changed or logically-deleted (which is valid behavior also).
A similar use case we have with 'draft'. Current specification supports 'incomplete' but that has a slightly different meaning. A 'draft' document can be complete and is in an 'awaiting' for an event (attestation) from which point may become 'complete' or 'final'.
Implementing these change will require 2 new codes in terminology and some adjustments in common_im.pdf. Perhaps a new change_type is also required.