🚨 TS-11 - Unexpected scenarios

Description

See if software in test can handle scenarios that passed validations whereas they should not.
Inspired by IMEC own set of test : https://wiki.ivlab.ilabt.imec.be/display/VLMS/EVS_Scenarios_S11_Validation_Fails

EVSREF	Description
100	Weekday is used when frequency is a multiple of days.
101	Daynumber is bigger than the frequency.
102	Date is used when frequency is a multiple of weeks.
103	Regimen with both weekdays and nothing (startdate will be used).
104	No frequency is specified and weekday is used.
105	Daynumber is used when frequency is a multiple of months.
106	The 'day' part in the date field of the regimen is higher than 28 when frequency is a multiple of months.
107	Weekday is used when frequency is a multiple of years.
108	The 'day' part in the date field of the regimen is higher than 28 when frequency is a multiple of years.
109	Daynumber in the regimen is higher than the multiple of weeks frequency.
110	Medication is suspended without an endmoment.
111	Temporality is missing.
112	Length of the instructionforpatient field is longer than 340 characters.
113	Medication in the treatment suspension differs from the corresponding medicationscheme element.
114	Quantity contains a value that is bigger than 4 digits.
115	More than five treatment suspensions.
117	Endmoment and duration are used together.
119	Duration contains the value 0.
120	Quantity is less than or equal to 0.
121	Quantity contains a value with trailing zeros.
126	Invalid CNK / INNCLUSTER code.

When looking to the patient medication scheme, all these criterias must be fulfilled :

The software should not crash for any medication following these unexpected scenarios
The software should follow a "best effort" strategy. In other words, display what the software can.
The software could warn professional users, so they can fix medication lines later (Invalid CNK, ...)