Existing Wording: 4.4.4 Requesting Additional Information from the User

When the execution of Clinical Quality Language (CQL) is unable to obtain the required data, it is necessary to prompt the user for input.

Comment:

Please explain how this will not be a horribly inconvenient burden. Many payer systems will be banging on the clinician's EMR day and night - seven days a week. Every time a null pops up, some sort of out of channel message will have to be generated to the clinician. We can be certain that almost all of the time that this prompt gets generated it will not be convenient for the clinician to respond. Are clinicians going to be faced with a new task queue in the corner of their screen that grows throughout the day? (And at night and on weekends?) For each data request, the clinician will have to open that patient's record and review it prior to providing the "missing" data. The birth of a new burdensome imposition. Find another way.

Summary:

Please explain how this will not be a horribly inconvenient burden.