Existing Wording: Each entry SHALL contain a transaction, and, if the entry.transaction.methodis a PUT or a POST, a resource. The entry SHALL contain the resource state at the conclusion of the operation.

Proposed Wording: The entry SHALL contain the resource state of when the resource version was created.

Comment:

Servers may version resources outside of interactions which occur via the FHIR methods, and may track these updates as versions of resources. To support that b ehaviour, transaction should not be a required element in the history response.