The ProvenanceActivityType definition states that: "This value set contains representative Activity Type codes, which includes codes from the HL7 DocumentCompletion, ActStatus, and DataOperations code system, W3C PROV-DM and PROV-N concepts and display names, several HL7 Lifecycle Event codes for which there are agreed upon definitions, and non-duplicated codes from the HL7 Security and Privacy Ontology Operations codes."

However, the representative codes are very limited and may confuse implementers. For example, there are no links to the LCE codes https://www.hl7.org/fhir/valueset-object-lifecycle-events.html, all of which should be included in this representative value set.

Important v3-DataOperations codes are missing, e.g., execute, perhaps because of the thought that classic RESTful Operations don't include execute. However, the Provenance.activity could be conducted outside of the RESTful paradigm.

There are few activities listed in Act.code http://build.fhir.org/v3/ActCode/cs.html. Even the ObligationPolicy codes are about the requirement to do an act. Perhaps this value set should be removed from Provenance Activity Type value set. Check to see that these required activities are included elsewhere as "activities". E.g., in https://www.hl7.org/fhir/valueset-object-lifecycle-events.html

ActStatus http://terminology.hl7.org/CodeSystem/v3-ActStatus has several that should be added, e.g., completed, held, aborted, nullified, suspended, and obsolete.

All of the DocumentCompletion codes should be included. http://build.fhir.org/v3/DocumentCompletion/cs.html