Comment:

Note that these reasonable assumptions about application architecture: "The DTR application may send information back to the host it was launched from to save application state. As mentioned in the previous section, the services and formats used to communicate state information are outside the scope of this implementation guide." contradicts the earlier statement that: "If the resulting information is to be sent to a third party (e.g. payer). The DTR / SMART on FHIR App should include a step requiring the provider to grant permission to send along the information gathered in the form before sending. However this should be configurable on a site or provider basis."

Summary:

Two sentences are contradicting each other.

Actual links and text:

http://hl7.org/fhir/us/davinci-dtr/2019Sep/use_case.html

If the resulting information is to be sent to a third party (e.g. payer). The DTR / SMART on FHIR App should include a step requiring the provider to grant permission to send along the information gathered in the form before sending. However this should be configurable on a site or provider basis.

http://hl7.org/fhir/us/davinci-dtr/2019Sep/specification__behaviors__persisting_application_state.html

The DTR application may send information back to the host it was launched from to save application state. As mentioned in the previous section, the services and formats used to communicate state information are outside the scope of this implementation guide.