Can the diagnosticRequest.stage element be removed or reworked to have less overlap with other elements in the resource. - 2016-09 core #280

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU2
    • Orders & Observations
    • DiagnosticRequest (see ServiceRequest) [deprecated]
    • Hide

      See [#12052] .stage renamed to .type

      The decision was made to separate these concepts from status since they are not request statuses but rather categorise how the request is being used.

      Show
      See [#12052] .stage renamed to .type The decision was made to separate these concepts from status since they are not request statuses but rather categorise how the request is being used.
    • Eric Haas/Kathy Walsh: 7-0-2
    • Enhancement

      Comment:

      The stage element is a little confusing, since part of it seems to overlap with status and the other part seems to overlap with the concept of the Observation.related element.

      Could we remove the need for this element by relying on the status element for proposal/plan and introducing a related element for original-order/reflex-order?

      Summary:

      Can the diagnosticRequest.stage element be removed or reworked to have less overlap with other elements in the resource.

            Assignee:
            Unassigned
            Reporter:
            Danielle Friend
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: