A common scenario in FHIR is going to be the following:

• A resource gets created and manipulated multiple times.
  - A provenance resource is created on the source system for both the initial create and each subsequent manipulation
  - The "current" version of the record is then transferred to a second system. That second system wants both the record and the Provenances associated with that record so that it knows what the history of the record is (relevant for merging/aggregating data that's propagated through multiple sources, etc.)
  - The second system can't realistically query the historical versions of the record from the source system, nor does it want to recreate the historical versions in its own system.

What guidance can we provide to implementers on managing the historical Provenance of a record when porting records across systems. In principle, that's one of the primary values that Provenance provides, but I haven't seen us give any guidance on how to actually make it work in practice.