The Task pattern includes a recommendation for a .relevantHistory element. This should be explained on the Provenance page, and could include reference to a profile on Provenance that is also provided by Task/Request pattern for relevantHistory.

Lloyd: Yes, it means it's not relevant in the view of the person who updated the resource. The purpose of relevant history is to give a view of key events such as creation, suspension, release, dispense, etc. Some of the Provenances pointed to might not even have a focus of the referencing resource (e.g. the dispense example). Minor edits, transformations, etc. wouldn't be shown. The purpose is to do the same as v2 messages that show "status history" where 'status' is interpreted fairly broadly. relevantHistory will never include the most recent change - as that provenance record won't exist yet when you make the update.

See chat https://chat.fhir.org/#narrow/stream/179256-Orders-and.20Observation.20WG/topic/relevantHistory