For the service broker solution I am building, I have to embed in the receive pipeline of the two way MLLP send adapter to poll for the next message. The receive pipeline component is supposed to be triggered by the ACK message. What I find is sometimes the ACK simply not being routed back to […]

In the testing scenarios, we are dealing with multiple systems. One frustration for me is, I need to simulate those systems but (to my knowledge) only way to generate the ACK is to use the accelerator pipeline with parties.To use the standard accelerator pipeline component is not an easy thing, the schemas have to be […]

So scenario is from SAP to HL7, using the BATHL assembler in the send side to serialize the HL7 stream to flat file format then relay via MLLP adapter. Lesson leant, To help debugging, I took the BTAHL assembler pipeline component, reflected to be my custom pipeline component. This way, I have a debuggable component […]

The HL7 flat file disassembler use the logic below for body document spec, if party defined, use configured namespace, else use standard HL7 namespace append with #MSH9_1 append with #MSH9_2 append with #MSH12_1 without ‘.’ if MSH12_2 present append it, else append ‘GLO’ if MSH12_3 present append it, else append ‘DEF’ <still not clear> It […]

Problem is if you come up with a custom trigger event within a domain, i.e. ADT_ZZZ, the accelerator requires not only update the MSH schema, but also create the custom schema, i.e. ADT_ZZZ_231_GLO_DEF.xsd. It would be nice if to get rid of this behavior and a single schema handles all custom trigger event within a […]

// if set passthrough to true, then this disassembler is a passthrough componentobject obj2 = inMsg.Context.Read(“PassThru”, “http://HL7Schemas.HeaderPropertySchema”);if ((obj2 != null) && ((bool) obj2))                {                    this.mCalledFirstTime = false;                    this.mMessageList[0] = inMsg;                }                Technorati Tags: BizTalk,HL7 // either individual or batch// determined by HL7DataReaderthis.mType=Individual // source partyMSH3_1, MSH_3_2,MSH_3_3 // ProcessIndividualMessage1) process message headerHL7MessageProcessor wrap documenspec i.e. http://microsoft.com/HealthCare/HL7/2X#MSH_25_GLO_DEFpass […]