The documentation for http://build.fhir.org/communicationrequest-definitions.html#CommunicationRequest.payload says:

> Text, attachment(s), or resource(s) to be communicated to the recipient.

... but the example shows a "payload" with a CodeableConcept whose text says:

> "Please provide the accident report and any associated pictures to support your Claim# DEF5647."

i.e. the example payload seems to be a message for the "sender", not for the "recipient".

It's not just an issue with the example, I think – there's some blurry conceptualization here. It's possible that "payload" needs to be refactored instead of asking it to do double-duty.