FHIR Chat · Naming systems · shorthand

Stream: shorthand

Topic: Naming systems


view this post on Zulip Etienne Cantineau (Apr 28 2020 at 07:04):

A few things about naming systems:

  • What's the way to add a naming system in shorthand? I tried as an Instance, but it is added in examples (normal for an instance i guess) while it was added in terminology before, am i using the good way or there was a change in the publisher layout?
  • I have a contact name and telecom but in the generated narrative the contact is still empty.
  • My contact is overwritten by the IG to use the infos from the contact (me) in the ImplementationGuide file

view this post on Zulip Nick Freiter (Apr 28 2020 at 12:23):

You can add a NamingSystem that won't be treated as an example by doing the following:

Instance: MyNamingSystem
InstanceOf: NamingSystem
Usage: #definition

By specifying the Usage as #definition, you tell SUSHI to treat this Instance as a definition of some Resource, not as an example of one. This should fix the issue with adding the NamingSystem to examples.

As for the bottom two issues, I observed the same thing when I tested it out, but I'm not sure what we can do about that on the SUSHI side. The generation of narratives is controlled by the IG Publisher, and the overwriting of the contact seems to be a decision the IG Publisher is making.

view this post on Zulip Etienne Cantineau (Apr 28 2020 at 12:48):

Thank you, it fixed well. I'll report the two issues in IG creation stream.

view this post on Zulip Lloyd McKenzie (Apr 28 2020 at 13:55):

Shouldn't NamingSystem default to being a definition?

view this post on Zulip Nick Freiter (Apr 28 2020 at 14:33):

Currently every Instance defaults to being an example, if no Usage is specified. Our reasoning was that the most common use case we are seeing of Instances is as examples, so we wanted to make that the default. That doesn't mean we are against smarter defaulting though. It does seem fair that we could default Instances of terminology resources to definition, not example. It makes the defaulting behavior more complex to document, but probably easier to work with for users that only ever use the default, and don't specify a Usage.


Last updated: Apr 12 2022 at 19:14 UTC