Stream: IG creation
Topic: new error for text.status in latest ig-publisher
Eric Haas (Aug 04 2020 at 18:54):
this error in validator with the latest version of the publisher just popped up...
Encounter.text.div error Resource has provided narrative, but the narrative indicates that it is generated - remove the narrative or fix it up
This presupposes that only the ig publisher can generate the narrative content which is not my understanding of the meaning of generated. And what does "fix it up mean?"
Lloyd McKenzie (Aug 04 2020 at 19:01):
Agree w/ @Eric Haas. It's completely possible to have a 'generated' narrative that represents narrative that could have been generated, but wasn't generated by the publisher. At most, this should be a suppressible warning that could be suppressed if the author has confirmed that the provided narrative is computably generatable from the discrete content
Yan Heras (Aug 04 2020 at 19:05):
Will publisher be updated to remove this error?
Lloyd McKenzie (Aug 04 2020 at 19:15):
@Grahame Grieve
Grahame Grieve (Aug 04 2020 at 21:07):
no this will not be removed. What this is saying is that the input resource has a narrative that claims it is auto-generated, but is not. Either remove the words 'generated narrative' from your narrative, or let it be generated
Eric Haas (Aug 04 2020 at 23:21):
so just remove the this? and keep the status='generated' ?
Grahame Grieve (Aug 04 2020 at 23:27):
right. keep the status as generated, and change the heading to something like "DiagnosticReport".
but you should try taking it out and seeing what the current publisher generates, because I just put some effort into DiagnosticReport and I think it's way better now
Eric Haas (Aug 05 2020 at 03:31):
OK that was temporary fix and will try again. I thought error was about the status.
Maybe the error could be more specific like: " The Narrative text indicates that is...."
Sarah Gaunt (Dec 02 2020 at 04:19):
Agree with fixing that error up - just spend 20 mins trying to figure out how to fix.
Sarah Gaunt (Dec 02 2020 at 04:21):
And, fyi, this is in a PlanDefinition and I'm not using the generated narrative (I was up until just now) because all of a sudden it is creating links that are erroring.
Grahame Grieve (Dec 02 2020 at 04:39):
it shouldn't. what is the error?
Sarah Gaunt (Dec 02 2020 at 04:40):
I'll remove the text element on my next commit and let you know. Will take 20 mins to run though
Grahame Grieve (Dec 02 2020 at 04:41):
I'm off to give blood. Won't be looking at messages again until about 10pm
Sarah Gaunt (Dec 02 2020 at 04:42):
Was going to say - trying to NOT make more work for you so you can hang out with Tali! Thus the narrative "fix".
Sarah Gaunt (Dec 02 2020 at 04:58):
@Grahame Grieve this is error:
PlanDefinition-plandefinition-us-public-health-example.html#/html/body/div/div/div/div/div/div/p/a at Line 190, column 94 error The link 'http://hl7.org/fhir/us/ecr/PlanDefinition/plandefinition-us-public-health-example' for "http://hl7.org/fhir/us/ecr/PlanDefinition/plandefinition-us-public-health-example" cannot be resolved
Will leave it in there until tomorrow so you can see it. I'll put my hack fix back tomorrow if you don't get a chance.
Grahame Grieve (Dec 02 2020 at 20:30):
@Sarah Gaunt where did you leave this?
Sarah Gaunt (Dec 02 2020 at 20:38):
I left it broken. It was happening on a couple of other instances also - can't remember off the top of my head which ones.
PlanDefinition-plandefinition-us-public-health-example.html#/html/body/div/div/div/div/div/div/p/a at Line 190, column 94 error The link 'http://hl7.org/fhir/us/ecr/PlanDefinition/plandefinition-us-public-health-example' for "http://hl7.org/fhir/us/ecr/PlanDefinition/plandefinition-us-public-health-example" cannot be resolved
http://build.fhir.org/ig/HL7/case-reporting/branches/master/qa.html#internal
Grahame Grieve (Dec 02 2020 at 21:22):
fixed next release
Sarah Gaunt (Dec 02 2020 at 22:31):
Thanks!
Sarah Gaunt (Dec 03 2020 at 21:51):
So I think there has been a new IG Publisher release and this is still broken...
Grahame Grieve (Dec 03 2020 at 21:57):
no the release failed. Should be soon
Grahame Grieve (Dec 04 2020 at 01:49):
now try
Sarah Gaunt (Dec 10 2020 at 00:42):
This is still failing: http://build.fhir.org/ig/HL7/case-reporting/branches/master/qa.html#internal
Sarah Gaunt (Dec 16 2020 at 03:05):
Also seems to be failing here: https://build.fhir.org/ig/HL7/HAI-LTCF/branches/master/qa.html#internal with the same narrative generation issue.
Grahame Grieve (Dec 16 2020 at 06:27):
still fails in case reporting because you're supplying the broken narrative directly
Grahame Grieve (Dec 16 2020 at 06:50):
the HAI ones will be fixed next release
Sarah Gaunt (Dec 16 2020 at 08:10):
Oh ok. I guess I tried to fix it by not auto generating and then forgot. Will fix...
And thanks for fixing the HAI ones @Grahame Grieve !!
John Moehrke (Apr 19 2021 at 19:15):
wish this error was either a warning that could be suppressed or explained better. I have pulled in some core resource examples to my IG as samples, but they fail because the core build has generated the narrative. I don't want to change them, because they are right out of core FHIR.
Grahame Grieve (Apr 19 2021 at 23:12):
what's an example?
John Moehrke (Apr 20 2021 at 11:33):
for example, I am writing an IG for an organizational use of core vital-signs. They further refine vital-signs. I want to have in my IG a few of the core vital-signs as proof that the refinements do not break from what is considered core vital-signs.
Grahame Grieve (Apr 20 2021 at 21:07):
how do I reproduce this is what I was asking
Last updated: Apr 12 2022 at 19:14 UTC
