jeremy chapman

I've built a custom pipeline component which can manipulate the encoding
characters found in msh field 2. It has the ability to add missing ones
(some of our 3rd party sending apps don't send all 4 encoding characters,
but some receiving ones require them), change existing ones, and encode any
special characters found in text to retain message validity.

My problem is, I put my component in a send pipeline before the the BTAHL7
assembler component, but if my component changes the ^ (sub component
character) to a ! for example, BTAHL7 2.x assember still uses the ^
character. My component only updates the MSH and body part streams, so I'm
guessing there's something in the context that I need to change as well.
What would that be, and how would I do it?