1. Will add a new section under 4.3.4.2 (card types) called "Pre-emptive prior authorization" with the following language. One result of invoking a CRD service may be that, based on the patient, their type of coverage and other information available in the patient's record queried by the CRD service, is that the service determines that - not only is prior authorization necessary for the intervention being ordered, but that the ordered intervention meets prior authorization requirements.  In such a case, the CRD service may return a card with two alternate suggestions - store the prior authorization in computable or add the prior authorization as an annotation to the order.  The first will be handled through a 'create' action that stores a ClaimResponse instance complying with the HRex [unsolicited authorization]  profile together with an 'update' to the order or appointment instance that triggered the CDS Hook invocation to modify the record adding the ClaimResponse as a 'supportingInfo' element - establishing a linkage between the order and the prior authorization. The second suggestion will function exactly as per the 'annotate' card, with the annotation covering all relevant information needed for the prior authorization (billing codes, modifiers, authorized quantity, authorized amounts, time period, authorization number, etc.  Support for this  second suggestion type is included as part of the mandatory support required for 'Annotate' suggestions. [and will include a full example of a card having both types of suggestions] Will also update the description