RE: This is a big assumption. How will data consumers communicate data requirements? In addition, how will data producers know which data collection operations (i.e., quality measures) they will be subject to? There is existing text : "Note that implementing this scenario requires that the Producer system understand the data requirements for the measure in order to provide the data. As with the Submit Data operation, the implementation can either manually determine the relevant data using the measure definition, or the implementation can use the Data Requirements operation to determine relevant data." Will move the above referenced section into the Collect Data section introduction for up front context that the producer knows this in order to respond to the $collect-data operation. THIS has been preapplied here: ~output/datax.html#collect-data ( note that text regarding incremental updates is still under revision and out of scope for this tracker ) The other question: "How will this (data requirements) be communicated back to the physician?Da Vinci Guiding Principles stipulate that responders (i.e., producers) have the ability to review and approve the content prior to release." Data is captured from provider entered data in clinical workflow and EHRs use this information to support the implementation. The intent it to reduce provider burden my automating these interactions, therefore there is no intention to communicate the data requirements back to the provider. The ability to review and approve the content prior to release is more appropriately addressed during the measure authoring that during the collection.