Contract properly belongs to the Event pattern. The current definition of the Contract resource seems to attempt to track activities related/leading to the Contract activation within the contract itself. This seems to be conflating multiple concept that are in discord with the general Request/Event/Definition patterns.

The Workflow FHIR-I group would like to discuss the intent of the Contract resource, and how it can work with other resources like Task to manage the associated life-cycle of the contract.