Remove analytics until future release following implementer feedback (#382)

In the absence of analytics, also expand upon the value of the suggestion UUID.

Author: isaacvetter

docs/specification/1.0.md

@@ -373,19 +373,9 @@ Each **Suggestion** is described by the following attributes.
 Field | Optionality | Type | Description
 ----- | ----- | ----- | --------
 `label` | REQUIRED | *string* | Human-readable label to display for this suggestion (e.g. the EHR might render this as the text on a button tied to this suggestion).
-`uuid` | OPTIONAL | *string* | Unique identifier for this suggestion. For details see [Suggestion Tracking Analytics](#suggestion-tracking-analytics)
+`uuid` | OPTIONAL | *string* | Unique identifier, used for auditing and logging suggestions.
 `actions` | OPTIONAL | *array* | Array of objects, each defining a suggested action. Within a suggestion, all actions are logically AND'd together, such that a user selecting a suggestion selects all of the actions within it.
 
-##### Suggestion Tracking Analytics
-
-Whenever a user clicks a displayed label (e.g., button) from a "suggestion" card, the EHR uses the
-suggestion `uuid` to notify the CDS Service's analytics endpoint via a `POST`
-with an empty body:
-
-    `POST {baseUrl}/cds-services/{serviceId}/analytics/{uuid}`
-
-If a suggestion has no `uuid`, the EHR does not send a notification.
-
 ##### Action
 
 Each **Action** is described by the following attributes.