justin-fyfe
commented
7 years ago I have not experienced that behavior before however if there is a bug it is most likely in EDFormatter.Parse on DT R1 parser. Unfortunately I don’t have the cycles to investigate for the next few weeks..
On the formatter, are there any IResultDetails reported in the parse result?
Cheers -Justin
Sent from my Windows 10 phone
From: William Setterbergmailto:notifications@github.com Sent: August 26, 2017 19:03 To: MohawkMEDIC/everestmailto:everest@noreply.github.com Cc: Subscribedmailto:subscribed@noreply.github.com Subject: [MohawkMEDIC/everest] Issues with parsing component.section.text with paragraph xml element (#4)
When Everest parses certain medical section narratives within
Specifically, it seems that Everest trips on the paragraph elements. I've attached a screenshot at a breakpoint showing the issue.
[sc1]https://user-images.githubusercontent.com/13972006/29742944-a54eb978-8a4d-11e7-8333-02cbdf14a739.png
A potential workaround that I've thought of is simply modifying the document to replace
before having Everest parse it, but I don't see why the framework fails on this relatively simple XML. Could it have something to do with the HL7v3 namespace being applied or not applied to the paragraph elements?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/MohawkMEDIC/everest/issues/4, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AHqoJwrVagbOgnnJln77GVz58E0fRsGWks5scEHegaJpZM4PDiNR.
settwi
When Everest parses certain medical section narratives within
<text></text>, which are valid xml, it silently fails. For example, this section, taken from a NextGen example CDA r2:Specifically, it seems that Everest trips on the
paragraphelements. I've attached a screenshot at a breakpoint showing the issue.A potential workaround that I've thought of is simply modifying the document to replace
<paragraph>and</paragraph>with<br/>before having Everest parse it, but I don't see why the framework fails on this relatively simple XML. Could it have something to do with the HL7v3 namespace being applied or not applied to theparagraphelements?