Existing Wording: There may be cases where the CQL provided by a payer was unable to locate information on a patient that is present in the EHR system. This may be due to the information existing in unstructured notes where it is not able to be easily retrieved by CQL, or it may be in a location that the CQL did not expect. To reduce the burden on the users of the application, DTR provides a mechanism for the user to attest that the information exists in the patient's record, without specifying the exact value or location of the information.

Comment:

Is there a mechanism needed that specifies the information is present but privacy restricted? In such a case follow up may be required but is out of the hands of the individual completing the workflow at the time. Depending on the nature of the information it might not be apppropirate to stop the workflow.

Summary:

CQL and privacy restricted information workflow