XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Highest
    • Shorthand (FHIR)
    • 0.12.0 [deprecated]
    • FHIR Infrastructure
    • Language Reference
    • 3.3.5
    • Hide

      Closely allied to FHIR-27265, but not quite a duplicate. In the other issue, the pro and con arguments are laid out, and the proposed resolution is to accept both "|" and "or" in References. That resolution will resolve this issue.

      The decision was to change "|" to "or".

      Show
      Closely allied to FHIR-27265 , but not quite a duplicate. In the other issue, the pro and con arguments are laid out, and the proposed resolution is to accept both "|" and "or" in References. That resolution will resolve this issue. The decision was to change "|" to "or".
    • Moesel/Rhodes 11-0-1
    • Enhancement
    • Non-compatible

      Why use a diffent representation here? Other parts in the spec use and and or as keywords, shouldn’t we do the same here?

      Existing Wording:

      Note: The vertical bar within references represents logical ‘or’.

            Assignee:
            Unassigned
            Reporter:
            Bas van den Heuvel
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: