"stage" is a poor name - 2016-09 core #344

XMLWordPrintableJSON

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

      As per 12052 (duplicate)

      Change "stage" to:

      "intent": 1..1 code (proposal | plan | order)

      Add the following usage note:

      When resources map to this element, they are free to define as many codes is necessary to cover their space and will map to "proposal, plan or order". Can have multiple codes that map to one of these. E.g. "original order", "encoded order", "reflex order" would all map to "order". Expectation is that the set of codes is mutually exclusive or a strict all-encompassing hierarchy.

      Show
      As per 12052 (duplicate) Change "stage" to: "intent": 1..1 code (proposal | plan | order) Add the following usage note: When resources map to this element, they are free to define as many codes is necessary to cover their space and will map to "proposal, plan or order". Can have multiple codes that map to one of these. E.g. "original order", "encoded order", "reflex order" would all map to "order". Expectation is that the set of codes is mutually exclusive or a strict all-encompassing hierarchy.
    • Bryn Rhodes/Hans Buitendijk: 38-0-3
    • Clarification
    • Non-compatible
    • DSTU2

      Comment:

      DiagnosticRequest.stage = "Whether the request is a proposal, plan, an original order or a reflex order"

      The concept "stage" is a semantic misfit for the definition

      Given the definition and the code value, it should be renamed to DiagnosticRequest.type

      Summary:

      "stage" is a poor name

            Assignee:
            Unassigned
            Reporter:
            Stephen Chu
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: