What are rules for Coding vs. CodeableConcept?

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Unresolved

      Some elements use Coding and some use CodeableConcept and it's not clear why the choices made were made - why is 'text' allowed for outcome but not type? Why are translations allowed for subtype but not type? (If repetitions are distinct concepts but not translations, why are translations not allowed?) In general, any place we're mandating data that isn't purely structural, we should support translations to allow retention of the original data. Even if the core standard doesn't mandate standardized codes, implementationg guides may and translations will be needed. If you want to prohibit text, consider using CodeableConcept with an invariant prohibiting text or at least mandating coding.

      (Comment 22 - imported by: Ron G. Parker)

            Assignee:
            Unassigned
            Reporter:
            Lloyd McKenzie
            Lloyd McKenzie, Ron Parker
            Watchers:
            2 Start watching this issue

              Created:
              Updated: