Improve User to Task and QuestionnaireResponse Association

[hhund]

Related Problem

Task resources requested by practitioner users are not associated to the user but the organization the users belongs to. QuestionnaireResponse resources are not assigned to any user or user role.

Describe the Solution You’d Like

• The Task.requester property should be set to a practitioner identifier for non organization users.
• When starting a process a practitioner user will get a 403 error if the user is not configured with the correct practitioner-role, required by the ActivityDefinition. We may want to hide draft Task resource that can not be started from the search result or disable the "Start Process" Button.
• Requested, in-progress, completed and failed Task resources should only be included in search results of practitioner users, if the user is set as Task.requester.
• QuestionnaireResponse resources should be associated with specific practitioner users or practitioner roles. The QuestionnaireResponse.author property may fit our needs. The property could be set by the process to a role or a specific user. Setting a role should only be allowed with status in-progress.