Stream: terminology
Topic: LinkType
Brian Kaney (Mar 26 2019 at 14:13):
Hi folks -- As patient is normative in R4, is this valueset also normative (https://www.hl7.org/fhir/valueset-link-type.html)? The spelling of the codes and displays are inconsistent...
Lloyd McKenzie (Mar 26 2019 at 15:28):
You can see the normative status at the top of the value set, and yes this one's normative. We can change display names for normative items, but there's no reason to do so here. It's fine (and expected) for the codes and display names to not be identical. Codes are generally lower-case with no spaces for ease of computation. Display names are normally title-case with spaces for human-readability.
Brian Kaney (Mar 26 2019 at 18:11):
Is see. I was more noticing "replaced-by" code is "Replaced-by" display (dash in the code makes sense, but not so much in the display) and then we have "seealso" (no dash in the code, which seems inconsistent compared to this and other similar value sets).
Lloyd McKenzie (Mar 26 2019 at 18:27):
The fact the codes are inconsistent in formatting isn't great, but too late to change. We can certainly improve the consistency/readability of the display names. Feel free to submit a change request.
Brian Kaney (May 02 2019 at 18:38):
This pattern of inconsistency also manifests elsewhere, such as the search parameters. One example is the differences in R4 and STU3 for DocumentReference... securitylabel in 3 becomes security-label in 4. However relatesto didn't change. And a new search parameter in 4 is spelled contenttype. Perhaps we should say if we prefer using hyphens (or not) and work toward that consistency?
Last updated: Apr 12 2022 at 19:14 UTC
