The only purpose of Provenance is to capture how a particular record came to be in its current state. Therefore, the only activities that are relevant are those that result in the creation, modification or removal of data. The set of activities relevant for Provenance are a subset of the activities relevant for AuditEvent. Codes for activity thus need to be codes that convey "what occurred". Statuses like "incomplete", "in progress", "normal", etc. have no place here. Nor do actions like "read" or "execute" which do not result in any change to the data. Obligation policies also make no sense. How is "encrypt at rest" (described as an obligation) a type of action that can be captured as a Provenance record? Those codes that are present and deal with types of changes that can occur express themselves in v3 terms, not FHIR terms (e.g. "nullify" rather than "mark as entered-in-error"). This value set is largely unuseable as defined and should be completely re-designed to reflect "what sorts of actions can happen to FHIR resources, documents and other EHR record artifacts that change their content?"