PharmaLedger-IMI / eco-iot-pmed-workspace

UC6-UC7-UC9 ECO-IoT-PMED
MIT License
2 stars 6 forks source link

Visits from optional consent file should hold the same Visits as the mandatory consent. #461

Closed Mastaleru closed 1 year ago

Mastaleru commented 2 years ago

This is a business demand. However let's add a validation on the optional consent, that the visits&procedures header(visits, date/time windows) are the same with mandatory consents visits

Desouler commented 2 years ago

Committed

Mastaleru commented 2 years ago

when versioning an optional consent with a valid file image

Desouler commented 1 year ago

Committed

Mastaleru commented 1 year ago

@Desouler I am not able to update the visits from the mandatory consent with a new visit file that holds different visits. The restriction should apply only to optional consents

Desouler commented 1 year ago

Committed

Mastaleru commented 1 year ago

Reopened with the following issue for visits&procedures consent:

  1. I created the mandatory consent with a visit file VFM1.
  2. I updated the mandatory consent with another visit file VFM2.
  3. I want to create an optional consent with visit file VFO2 that matches VFM2 visits => it does not let me to do so (visit file validation constraints )
  4. Instead it let me to create the optional consent with VFO1 that matches the obsolete version VFM1 visits,.
Desouler commented 1 year ago

Committed

Mastaleru commented 1 year ago

all good now