XML files are reported to be valid, but converter says 'Validation errors exist'. about qpp-conversion-tool HOT 6 CLOSED

My work email is [email protected].
Thanks...

from qpp-conversion-tool.

Also, I found a number of lines in each xml file (almost 950 in each one), that had an ending comment
tag ('-->') without a space after the end of the comment, like '.-->', or ''.
The file editor I use, CrimsonEditor v4.7, shows the next line or group of lines as part of the comment,
and I thought that would affect the parsing for the xml....

from qpp-conversion-tool.

the line above: like '.-->' or ''. should read:
like '.--> or
.....(CodeSystem: ConfidentialityCode 2.16.840.1.113883.5.25 STATIC) (CONF:711246).-->
the last example is from line 45 in both files.

from qpp-conversion-tool.

I think that I found the issue, but not sure.
The MIPS files I've been given have:
<!-- QRDA Category III Report (QRDA III) --> <templateId root="2.16.840.1.113883.10.20.27.1.1" extension="2016-09-01"/> <!-- QRDA Category III Report - CMS EP --> <templateId root="2.16.840.1.113883.10.20.27.1.2" extension="2016-11-01"/>
The valid QRDA file Converter uses for tests has:
<templateId root="2.16.840.1.113883.10.20.27.1.1" extension="2017-06-01"/> <templateId root="2.16.840.1.113883.10.20.27.1.2" extension="2017-07-01"/>
So it appears the test files I've been given are 2016 format, not 2017 or 2018.
I'm checking into whether we can produce 2018-format files from our data.

from qpp-conversion-tool.

@thomasclifford any update on this?

from qpp-conversion-tool.

Closed due to no update.

from qpp-conversion-tool.