1. Will add a section to CRD under 4.3 and following 4.3.5 called "Deferring Tasks" worded as follows: CRD clients SHOULD support deferring card actions, allowing the information on a card activity to be reviewed by and/or performed by the current user or someone else at a later point.  If a CRD service feels that the ability to defer a card action is important and (a) the system receiving the card does not have a native mechanism to defer a card action and (b) the system does have the ability to accept 'create Task' actions, the CRD service MAY provide an alternate 'deferred' action that allows the card action to be performed later. CRD clients that do not provide native support for deferring cards SHOULD support accepting Task create actions. If using the 'Task' mechanism, the action will display an appropriate message about deferring the action (e.g. launching the SMART app) and will cause the creation of a Task within the CRD client. This Task will have an owner of the current user and will comply with the [CRD Card Task] profile.  Once created, deferred action Tasks might be re-assigned, scheduled and otherwise managed as normal Tasks.  How EHRs manage Task work queues is outside the scope of this specification. In addition, where no other deferral capabilities exist, a user can 'effectively' defer a DTR task by launching the DTR application, then saving and closing the app - which will save the current DTR session for later resumption by manually invoking the DTR application and selecting and resuming the in-progress session.  The user could also add a note to the in-progress order that DTR work requires completion. 2. Will define a CRD Card Task profile with a unique code indicating "deferred CRD action".  The Task, if necessary, will have contained resources for the action to be performed.  All elements within a CDS Hook action will be mapped within the profile, defining coded inputs as necessary.