We do not believe this is only for test data management.  Functionality like this is widely used in production.  We will define the following capabilities: From Q6 discussion at WGM: Plan is to define: DELETE /:type/:id/_history - remove all versions of the resource except the current version (which if the resource has been deleted, will be an empty placeholder) DELETE /:type/:id/_history/:vid - remove the specified version of the resource.  It is an error to remove the 'current' version.  (Must first perform a regular delete, and can then delete the non-current version.  If the desire is to roll-back to a previous version, use a PUT to "roll forward" instead.) Same status codes as for the original DELETE operation Will define the `delete-history` and `delete-history-version` to correspond to these POST /Patient/:id/$purge – get rid of all current + historical data for a whole Patient compartment POST /Group/:id/$purge – get rid of all current + historical data for all Patient compartments of all group members These $purge operations are suitable for async behavior. Will include a link to both of these operations on the http page in the Delete section.