When data is being shared from a provider organization to a payer organization, there's a need to ensure that payers are only asking for (and receiving) information they have a legitimate need to know.  In some cases, that verification/filtering process can be automated and standard query/subscription/etc. mechanisms can be used to support data access.  However, in other cases, the determination cannot be made in an automated way.  In the current world, clinicians and administrative staff handle the determination of relevance in deciding what information to fill into forms or include as attachments for data that is 'pushed' to the payer.  However, as we shift the model to support 'pull', there are still situations where a human needs to be involved.  The CommunicationRequest workflow was intended to support that need. We are likely changing from CommuniationRequest to Task for this purpose, but will ensure that the documentation more clearly expresses the circumstances in which this row is necessary - and also note that is in the best interest of provider and payer organizations to come to agreements that maximize the amount of data that can be shared automatically to minimize imposition on provider staff and also to minimize delays to the flow of information.