We're updating the issue view to help you get more done. 

When generating the list of available fields to push, filter out any fields associated with consents that have not been granted at the previous step

Description

After the user checks applicable consents in the first "Push" screen and moves on to the next step, they currently can select what patient data to push from a list of all fields supported by both the local and remote server, regardless whether they have consent for submitting some types of data. Instead, the fields associated with consents that have not been granted should not be displayed, i.e. made unavailable for pushing.

Change:

  • The consentsModule widget to allow retrieving the list of fields that were not consented

  • PushPatient#pushCallBack to send to ExportPreferences via the enabledFields parameter the list of fields enabled on the remote server excluding those associated with consents for which the checkbox was not checked on this screen.

Environment

Status

Assignee

Veronika Koltunova

Reporter

Marta Girdea