Need relationships between Codings - 2016-09 core #50

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU2
    • Modeling & Methodology
    • Datatypes
    • 2.22.0.5 codeable co
    • Hide

      Will look at adding an extension to support this when we have a specific implementation that wants to do this and thus have knowledge about exactly what information is needed. We don't want to define an extension based on theoretical need. (For example, mappings can take multiple codings, original text and possibly companion attributes as part of the translation process. How much of this can/should be exposed?)

      Show
      Will look at adding an extension to support this when we have a specific implementation that wants to do this and thus have knowledge about exactly what information is needed. We don't want to define an extension based on theoretical need. (For example, mappings can take multiple codings, original text and possibly companion attributes as part of the translation process. How much of this can/should be exposed?)
    • Grahame Grieve/Ron Shapiro: 3-0-0
    • Enhancement

      Comment:

      A codeable concept may have many codings.

      This is a valuable feature, but it may be necessary to distinguish kinds of codings.

      Precedence: It would be important to know whether one value is the original and another is a translation. (This may be the intent of "user-selected" but there may be no user-selected value.)

      Precision may also be useful: some codings may be precise representations of the intent; others may be broader.

      I recommend a relationship attribute.

      This may be where to specify values suggested for 'user selected' above.

      Summary:

      Need relationships between Codings

            Assignee:
            Unassigned
            Reporter:
            Jay Lyle
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: