There have been many examples of users who have run into issues with the validation rules in Order Entry that require all Drug Orders with careSetting = 'OUTPATIENT' to have non-null quantity, quantityUnits, and numRefills specified.
The typical suggested workaround is for these users to build custom application handling that hides these fields and sets them all to "0". This indicates clearly that there are use cases in which this validation should be loosened, and users / implementations should be able to opt out of it if desired. The suggestion is also difficult due to the additional validation that non-null quantity (eg. 0) requires a non-null quantityUnits (which must refer to a valid concept, and this concept must exist within a defined concept set, and this must be configured in a global property). So it's a lot to ask and not a great situation.
This ticket is to change the validation as follows:
- Add a new global property: "drugOrder.requireOutpatientQuantity" which defaults to true (for backwards-compatibility)
- Modify the DrugOrderValidator.validateFieldsForOutpatientCareSettingType method to skip validation if the value of the above global property = false.
See slack conversation:
See talk thread:
FYI - I will have a need to backport this into the 2.3.x line, in addition to master