Stream: IG creation
Topic: narrative generation issues with autopublisher
Eric Haas (Aug 04 2020 at 19:13):
my local build generates the narrative without issue e.g. :
(Publisher Version: IG Publisher Version: v1.1.7)
but the autobuild generated narrative is all mangled with errors e.g.:
Publisher Version: IG Publisher Version: v1.1.7
Grahame Grieve (Aug 04 2020 at 21:09):
where is this?
Eric Haas (Aug 04 2020 at 23:16):
DEQM CI Build: https://build.fhir.org/ig/HL7/davinci-deqm/qa.html
Grahame Grieve (Aug 05 2020 at 05:01):
ok I fixed the second one - the null error. But I'm not sure what the point of the first one is
Eric Haas (Aug 05 2020 at 05:15):
if you mean the tow screenshots. The first one illustrates the correctly generated narrative locally vs the incorrectly generated narrative via the autobuild in the second screenshot. I thought it odd that local is different than autobuild.
Grahame Grieve (Aug 05 2020 at 05:19):
ok maybe I haven't fixed it then. I can't reproduce it, but I did fix an error that happened while generating
Eric Haas (Aug 05 2020 at 05:20):
I am running again to see if persisting
Eric Haas (Aug 05 2020 at 06:16):
The narrative generation error is persisting and only show up in the QA for the autobuilder although now there is a Exception displayed locally in the Generated Narrative.
Here is an example error:
The link 'Bundle-multiple-indv-mrp-obs-report.html#Encounter_encounter01' for "Generated Summary: id: multiple-indv-mrp-obs-report; type: transaction; timestamp: Jul 8, 2020, 10:17:14 PM" cannot be resolved (valid targets: 52 targets)
Michaela Ziegler (Aug 06 2020 at 08:41):
I get errors that links cannot be resolved, see QA.
The links are generated by the IG publisher (in Generated Narrative) and refer to the wrong resource.
E.g. of Composition: generated link encounter refers to the Bundle.
(I did not have this problem with IG publisher v1.1.6.)
Grahame Grieve (Aug 06 2020 at 08:42):
i think I just fixed that... let me check
Grahame Grieve (Aug 06 2020 at 09:00):
note that You have an invalid document - the composition has no narrative.
Grahame Grieve (Aug 06 2020 at 09:00):
that doesn't fix the problem; I
Grahame Grieve (Aug 06 2020 at 09:00):
I'm still working on it - a problem in the IG publisher
Grahame Grieve (Aug 06 2020 at 12:12):
yes fixed next release
Grahame Grieve (Aug 06 2020 at 12:14):
though note for general authors: there's an unresolved problem here that doesn't arise in Michaela's IG: if you have a resource that refers to another resource, and the other resource is in side a bundle of type "document" (but not other types), then the IG Publisher will generate a link to that resource, but it can't generate the target of the link, since the rendering of a bundle of type document follows the spec, and it's up to the author of the document to include the link or not
Eric Haas (Aug 06 2020 at 18:30):
@GG We are still getting these errors even with the latest IG publisher (IG Publisher Version: v1.1.8). This is an issue for both DEQM v2.0.0 which we are trying to publish and the DEQM ver 2.1.0 which we are trying to publish for ballot.
Eric Haas (Aug 06 2020 at 18:31):
see here: http://build.fhir.org/ig/HL7/davinci-deqm/branches/master/qa.html
David deRoode (Aug 06 2020 at 19:04):
Not sure if these new build errors in Dental are related to narrative generation, but they are now appearing on every html page within the IG
unable to parse character reference ' Background<b class="caret"> </b> </a> <ul class="dropdown-menu"> <li><a href="scope.html">Scope</a></li> <li><a href="dependencies.html">Dependencies</a></li> <li><a href="current_project.html">Current Project</a></li> <li><a href="background.html">Background</a></li> <li><a href="workflows.html">Workflows</a></li> </ul> </li> <li class="dropdown"> <a data-toggle="dropdown" href="#" class="dropdown-toggle">Best Practice Recommendations<b class="caret"> </b> </a> <ul class="dropdown-menu"> <li><a href="best_practice_recommendations.html">Best Practice Recommendations</a></li> <li><a href="proper_use_of_the_dental_findings_section.html">Proper use of the Dental Findings Section</a></li> <li><a href="incorporating_snodent_concepts.html">Incorporating SNODENT Concepts</a></li> <li><a href="planned_procedures_and_encounters_using_cdt_and_snodent.html">Planned Procedures and Encounters using CDT and SNODENT</a></li> <li><a href="dental_images_as_results.html">Dental Images as Results</a></li> <li><a href="reason_for_referral_indications.html">Reason for Referral Indications</a></li> <li><a href="referral_identifiers_in_the_consult_note.html">Referral Identifiers in the Consult Note</a></li> <li><a href="periodontal_findings.html">Periodontal Findings</a></li> </ul> </li> <li class="dropdown"> <a data-toggle="dropdown" href="#" class="dropdown-toggle">Content Inclusion<b class="caret"> </b> </a> <ul class="dropdown-menu"> <li><a href="content_inclusion.html">Content Inclusion</a></li> <li><a href="caries_risk_assessment.html">Caries Risk Assessment</a></li> <li><a href="patient_self-management_goals.html">Patient Self-Management Goals</a></li> </ul> </li> <li><a href="value_set_discrepencies_tbd.html">Value Set Discrepencies (TBD)</a></li> <li class="dropdown"> <a data-toggle="dropdown" href="#" class="dropdown-toggle">Dental Use Case Scenarios<b class="caret"> </b> </a> <ul class="dropdown-menu"> <li><a href="dental_use_case_scenarios.html">Dental Use Case Scenarios</a></li> <li><a href="scenario_1_medical_to_dental_referral.html">Scenario 1 Medical to Dental Referral</a></li> <li><a href="scenario_2_dental_to_medical_consult_note.html">Scenario 2 Dental to Medical Consult Note</a></li> <li><a href="scenario_3_dental_to_dental_endodontist_referral.html">Scenario 3 Dental to Dental (Endodontist) Referral</a></li> <li><a href="scenario_4_dental_endodontist_to_dental_general_dentist_referral_result.html">Scenario 4 Dental (Endodontist) to Dental (General Dentist) Referral Result</a></li> </ul> </li> <li><a href="team.html">Dental Data Exchange Project Team</a></li> <li><a href="acknowlegements.html">Acknowlegements</a></li> <li><a href="appendix_a_imaging_results_example_code.html">Appendix A Imaging Results Example Code</a></li> <li><a href="appendix_b__dentaquest_more_care_referral.html">Appendix B DentaQuest MORE Care Referral</a></li> <li><a href="app._c._dental_treatment_rpt.html">App. C. Dental Treatment Rpt</a></li> <li><a href="appendix_d_value_set_discrepancy_mapping.html">Appendix D Value Set Discrepancy Mapping</a></li> <li><a href="artifacts.html">Artifact Index</a></li> </ul> </div> <!-- /.nav-collapse --> </div> <!-- /.container --> </nav> <!-- /.navbar --> <!-- /HEADER CONTENT --> </div> <!-- /container --> </div> <!-- /segment-navbar --> <!--status-bar--> <div id="segment-breadcrumb" class="segment"> <!-- segment-breadcrumb --> <div class="container"> <!-- container --> <ul class="breadcrumb"> <li><a href='toc.html'><b>Table of Contents</b></a></li><li><b>Acknowlegements</b></li> </ul> </div> <!-- /container --> </div> <!-- /segment-breadcrumb --> <div id="segment-content"> <!-- segment-content --> <div class="container"> <!-- container --> <div class="row"> <div class="inner-wrapper"> <style type="text/css"> h2:before{color:silver'' (last text = ' ' at line 169 column 24
Eric Haas (Aug 06 2020 at 19:07):
(deleted)
Grahame Grieve (Aug 06 2020 at 20:00):
@David deRoode that means you have an error in your source html - using a & directly
Grahame Grieve (Aug 06 2020 at 20:00):
must be &
David deRoode (Aug 06 2020 at 21:14):
Fixed :+1:
Grahame Grieve (Aug 06 2020 at 21:19):
@Eric Haas1.19 is the latest and will fix those errors
Eric Haas (Aug 06 2020 at 21:35):
and adds 30 new errors!!!! Thanks I think.
Grahame Grieve (Aug 06 2020 at 22:21):
right. now it can find the measure, it compares to the measure
Eric Haas (Aug 06 2020 at 22:51):
Yes I figured that out.
Last updated: Apr 12 2022 at 19:14 UTC