DiagnosticOrder currently does not have timing attributes. From the workflow discussions it is becoming very clear that the Task timing information (.when) is intended to focus on the timing of the task (e.g., new, suspend, etc.), which may or may not coincide with the timing on the associated nnnRequest. Other request resources have such request specific timing attributes (one or more depending on the resource), while DiagnosticOrder has nothing yet.

We suggest to propose when.code and when.schedule and through discussion determine whether there are use cases that may need more.