FHIR Chat · Preventing narrative generation · IG creation

Stream: IG creation

Topic: Preventing narrative generation


view this post on Zulip Lloyd McKenzie (Nov 08 2020 at 17:28):

I have a profile for de-identified Coverage that prohibits narrative from being present (maxOccur=0). However, the IG Publisher auto-generates narrative for all resources, resulting in an instance that's not valid against the profile. I want narrative to be generated for most of my examples, but not this particular one. How do I keep narrative from being generated for specific instances?

view this post on Zulip Lloyd McKenzie (Nov 08 2020 at 17:28):

(@Grahame Grieve )

view this post on Zulip Grahame Grieve (Nov 10 2020 at 20:26):

don't know.

view this post on Zulip Jose Costa Teixeira (Nov 11 2020 at 09:12):

Can't narrative.status=empty be used for that?

view this post on Zulip Lloyd McKenzie (Dec 01 2020 at 15:40):

That would still create a 'text' element. And the 'text' element is prohibited. We don't want it present, regardless of status.

@Grahame Grieve, thoughts on how to fix this?

view this post on Zulip Grahame Grieve (Dec 01 2020 at 20:42):

well, I can think of the following options, but I'm not doing any of them this week:

  • put a parameter in the IG to say not to generate narrative for particular resources
  • put an extension on the resource to say not to generate narrative
  • put text element in and put an extension on it to say remove it

view this post on Zulip Lloyd McKenzie (Dec 01 2020 at 23:08):

I can live with any of those, though with the second option, the generation process would need to strip the extension.


Last updated: Apr 12 2022 at 19:14 UTC