Hi Dzung,

not having the XSD you are referring to at hand, I can only guess that the Rapid Prototyper is not yet perfect. We will have a look at that later on.

But that's no real problem as you can easily change the generated template by moving all child nodes of the second ADT_A02 one level up (drag&drop) and deleting the second ADT_A02 node (press delete-key).

The most convenient method, however, is to use a predefined template from our template library. You will find a template library for every HL7 version in the download section:



Download the corresponding zip file, extract it into a folder and import the template you need into your project:



I hope that helps,
Ortwin

Dear Ortwin,

I would like to thank for your reply. Tomorrow I will attach here the .xsd I used to generate the Saddle template. I use the HL7 xsd version 2.6. I hope it can help you if it is really a bug of RapidPrototyper.

Best Regards,
Dzung

Dear Ortwin,

Please find xsd file I used to generate ADT_A02 Saddle template in attached file.

Best Regards,
Dzung

Thanks Dzung but I can't find the attachment.

It's probably because we changed the way you add attachments. After you uploaded it, it appears underneath your post and you have to click "insert" to insert it into your post.

regards,
Ortwin

Dear Ortwin,

Please find xsd file as attachment file.
test.zip

Hi Dzung,

I just saw, I still owe you an answer regarding this issue:

We checked our xsd analyzer and it works correctly. The reason for the additional level of ADT_A02 is because an xml schema always describes an xml-structure. For an xml-structure the main tag - in this case ADT_A02 is part of the actual message. Thus this is correct as the root node is always the template name and not part of the actual message.

However, in this case HL7 "abuses" the xml-schema for describing a message format, which is not xml but in delimited format and therefore the second instance of ADT_A02 is not needed. This means either manual refinement after the template has been generated or using a template from our HL7 template libraries (as you did already).

regards,
Ortwin