• Item:operations-top-levelMoreItem:operations-workItem:greenhopper_issue...Item:operations-archiveItem:operations-attach...Item:operations-votesw...Item:operations-subtasksItem:devstatus-cta-listItem:operations-operat...Item:operations-deleteItem:operations-manual...
  • Resolved - No Change
  • AdminItem:operations-fieldsItem:operations-admin-...
  • Item:operations-restore
Item:jira.issue.tools ExportXMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Considered - Question answered
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Terminology Infrastructure
    • Terminologies
      Terminologies - Concept Maps
      Terminologies - Systems
      Terminologies - v2 [deprecated]
      Terminologies - v3 [deprecated]
      Terminologies - Valuesets
    • 1. 1.14.0
    • Hide

      <p>yes there is a version</p>

      Show
      <p>yes there is a version</p>
    • Rob Hausam / Grahame Grieve : 8-0-0
    • Clarification

      Existing Wording
      Is there the ability to include an optional "version" parameter in the pair composed of "system" and "code" to manage cases where specifying a code system version in necessary - for example, where a terminology may have reused a code or significantly changed the meaning of a code between version of a code system?

      Comments
      Throughout this specification, coded values are always treated as a pair composed of "system" and "code", where the system is a URL that identifies the code system that defines the codes.

      Grahame's Comments
      yes there is also a version

      Disposition
      Considered - Question Answered

      Disposition Comment
      version is available as part of the Coding data type, but is optional

            Panel: location:atl.jira.view.issue.left.context

              Assignee:
              Unassigned
              Reporter:
              Russell Hamm
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Panel: location:atl.jira.view.issue.right.context