Loading...

XML

Word

Printable

JSON

Specification:

Shorthand (FHIR)
Raised in Version:

0.12.0 [deprecated]
Work Group:

FHIR Infrastructure
Related URL:
http://hl7.org/fhir/uv/shorthand/2020May/reference.html#reference-type-restriction-rules
Related Page(s):

Language Reference
Related Section(s):
3.3.5
Grouping:
- Block-Vote-4
Resolution Description:

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".
Resolution Vote:
Moesel/Rhodes 11-0-1
Change Category:
Enhancement
Change Impact:
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?

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

is voted on by

BALLOT-12455 Affirmative - Bas van den Heuvel : 2020-May-SHORTHAND R1 STU