Stream: committers
Topic: text narrative combined generated and hand edited
John Moehrke (Jun 04 2020 at 20:07):
I would like to include in the examples resources that have hand written narrative but also like the auto generated that comes from the build. Is there a way to ask the build to use some .text narrative and also generate the typical generated narrative?
Jose Costa Teixeira (Jun 04 2020 at 20:43):
how would that work?
concatenate both generated text and manually entered text in text.narrative?
what would be the status of the narrative? generated or additional (because it seems to include both)
John Moehrke (Jun 04 2020 at 21:01):
I was invisioning the .text element text would be used, followed by the generated... but I really don't know. I am MORE wondering if this already exists
John Moehrke (Jun 04 2020 at 21:03):
the alternative is to do a build having it be generated, copy that manually; and from that point forward use the original generation... which means that if anything ever moves around or improvements in generation ever happen that they would never work for that example. I can do this, but it seems draconian.
Jose Costa Teixeira (Jun 04 2020 at 21:18):
I don't know - .text is 0..1, and both Narrative and DomainResource are Normative..
John Moehrke (Jun 04 2020 at 21:20):
I was asking if the build had a trick.. not if it was core to FHIR
Jose Costa Teixeira (Jun 04 2020 at 21:20):
IIRC, I think that once you have some .text the build does not touch it.
Jose Costa Teixeira (Jun 04 2020 at 21:21):
I don't think the narrative accepts a starting text or something like that.
John Moehrke (Jun 04 2020 at 21:29):
that is my experience
John Moehrke (Jun 04 2020 at 21:29):
hence the ask
Grahame Grieve (Jun 05 2020 at 02:12):
no this is binary at the moment - the build either generates the narrative or leaves it alone
Lloyd McKenzie (Jun 05 2020 at 03:24):
We could possibly add a publisher flag that would throw the generated narrative into an extension. It would either need to be an escaped string or base64-encoded though because we don't allow XHTML content as an extension value.
Lloyd McKenzie (Jun 05 2020 at 03:25):
Once that was done, the publisher could theoretically spit out a second fragment that a template could render in a separate tab or something. Not a small amount of effort to make happen overall...
John Moehrke (Jun 05 2020 at 12:17):
I am fine with the answer I just didn't want to do a bunch of handcrafting when I could have just turned on a switch.
John Moehrke (Jun 05 2020 at 17:12):
maybe a feature request could be -- given how the examples all have a "See also the XML, JSON, or Turtle format". could we have another link added with the auto-generated view of the content that ignores the .text element?
Lloyd McKenzie (Jun 05 2020 at 17:15):
We could, but it would be redundant if that was the source for the 'official' narrative.
John Moehrke (Jun 05 2020 at 17:16):
yup. but that case could be detected
John Moehrke (Jun 05 2020 at 17:16):
not really strongly caring for this.
Last updated: Apr 12 2022 at 19:14 UTC
