Stream: terminology
Topic: Naming System Title
Peter Jordan (Mar 07 2019 at 01:35):
Should the NamingSystem Resource have a title element, for a human-friendly name, as found in the ValueSet, CodeSystem and ConceptMap resources - or would that be 'overkill'?
Lloyd McKenzie (Mar 07 2019 at 02:20):
Do you have a specific use-case?
Peter Jordan (Mar 07 2019 at 05:53):
So we might take the human-friendly name from the resource instance itself and place that on a page such as https://standards.digital.health.nz/id/nhi. Given that those other terminology resources already have a title element, is this an omission by design or by accident?
Lloyd McKenzie (Mar 07 2019 at 06:02):
As I look at the resource, it seems sort of a no-brainer to add it actually. The only question is whether it should be 'title' or 'label' - i.e. the preferred label for the thing the namespace represents - what you should show on the screen when you have an identifier with that system (or a code with that system if displaying the system actually matters)
Peter Jordan (Mar 07 2019 at 06:18):
'Title' would be consistent with the corresponding element in the ValueSet, CodeSystem and ConceptMap resources. If starting from scratch, 'label' is probably a better name for an element that holds a human-friendly name - but it's too late to change ValueSet & CodeSystem, so my vote would be for consistency.
Lloyd McKenzie (Mar 07 2019 at 15:04):
The reason I proposed a different name is that the purpose is slightly different. Title is the human-friendly name for the resource instance. NamingSystem.label would be the human-friendly name for the identifier that has the system.
Rob Hausam (Mar 07 2019 at 15:40):
Lloyd may have a point there. NamingSystem is a bit different in that respect.
Michael Lawley (Mar 08 2019 at 12:02):
So title in a CodeSystem resource for SNOMED CT is the human-friendly name of the resource itself (not the particular SNOMED CT instance)?
Grahame Grieve (Mar 14 2019 at 07:09):
yes
Last updated: Apr 12 2022 at 19:14 UTC
