XML Invalid document structure

Clovertech Forums Read Only Archives Cloverleaf Cloverleaf XML Invalid document structure

  • Creator
    Topic
  • #54015
    BobbyD
    Participant

      Schema compiled with default options. Passes with XMLSpy.  Everything looks ok.  I can get it to iterate on address (I have value echo out), but then it fails right on the first row.

      Any help would be appreciated.

      TIA!

    Viewing 1 reply thread
    • Author
      Replies
      • #79876
        Robert Kersemakers
        Participant

          Hi Bobby,

          I have had a look at your files and all works as expected, although I had to test some things to find out what is going on.

          CancerReport.xsd can be compiled and then Sample.xml can be tested against the CancerReport.xsd: no problem.

          Then I tried your translation. As I don’t have the outbound format (another xml format named CDAv0), I used CancerReport as outbound format. And look: I got almost the same error as you did:

          Code:

          Please Wait ……
          Command Issued: hcixlttest -d 1 -f eof xmltranstest.xlt /hci/qdx5.7/integrator/testberichten/Sample.xml
          Command output:

           — in value:  {1122 Main Street}
           — in value:  {4807 89th Ave N}
          MESSAGE 1
          [0:TEST] Message encode warnings: Fatal Error generated during parsing. – Invalid document structure – Line 1, Col 40
          Output validation errors: Fatal Error generated during parsing. – Invalid document structure – Line 1, Col 40
          [0:TEST] Fatal Error generated during parsing. – Invalid document structure – Line 1, Col 44

          Then I changed the output format into HL7 2.4 and ran the test again:

          Code:

          Please Wait ……
          Command Issued: hcixlttest -a  -d 1 -f eof xmltranstest.xlt /hci/qdx5.7/integrator/testberichten/Sample.xml
          Command output:

           — in value:  {1122 Main Street}
           — in value:  {4807 89th Ave N}
          MESSAGE 1
          0(0).MSH(0)  :  >|^~&|||||||ADT||P|2.4|||||||||||4807 89th Ave N<

          That works without errors!

          Conclusion: the output format is not correct. Which is understandable: in the output format (CancerReport in my case, but CDAv0 will be the same) all required fields must be filled. As long as this is not the case, you will keep getting these errors.

          So continue with your translation until you have filled out at least all required fields. Then you shouldn’t get any errors.

          Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands

        • #79877
          BobbyD
          Participant

            This was sitting with me and I had a tickle in my brain it may be the output schema.  After reading your findings and performing the same steps to confirm for my setup, I had the same failsuccess.  Thank you very much for taking the time to review this.  I am trying to use a CDA R2 schema.  I found there was one in “client/formats/xml” on our box, but I get the same error.  I’ll start a new thread about CDA.  Thanks again!

        Viewing 1 reply thread
        • The forum ‘Cloverleaf’ is closed to new topics and replies.