HL7 Accelerator v3?

We have not even shipped Version 2.0 of the HL7 Accelerator for BizTalk that Tom is already thinking ahead and posting a wish list for v3.

Some of the issues he outlines are already addressed in v1.3, others will in v2:

  • 1.1, this is addressed in v1.3 and v2.0 by a flag you need to set on the party trading with you.
  • 2, this is going to be alleviated by including the Schema Generation tool in v2.0 of the Accelerator.
  • 6.1, integration with the HL7 MWB (link might be accessible to HL7 members only) is possible by customizing the Schema Generation tool to accept input from MWB instead of the HL7 message definitions database.

So, what would you like to see in the HL7 Accelerator v3?

BTW, yes, I'm back from vacation and I have a lot of news to share over the next week or two, keep checking back 🙂

Comments (2)

  1. simonchester says:

    One of the biggest issues I have faced in the past is the way ACKs are generated. When a message is received the pipeline converts the message to XML. If this fails for any reason, an ACK is generated. All good. But the ACK is not sent to the MessageBox until the pipeline completes. If the pipeline fails, it never gets there. Now this is annoying as it means we can’t put a map on the pipeline. If the HL7 message is not converted to XML the map fails, takes out the pipeline and the ACK is not sent.

    The result is that conversion maps have to be placed in an orchestration which seriously increases the number of assets in the solution.

    So my BIG wish would be to change it so the ACK is written immediately to the MessageBox.


Skip to main content