Sounds like you are learning about what many of us preach, “avoid using bulkcopy”.
If you want to do “wam bam thank you mam” and then leave someone behind unsatisfied perhaps it makes sense, but not if you are going to hang around.
This is especialy true when converting a message from one version of HL7 to another.
Bulkcopy only copies the items that have identical paths.
If you are using bulkcopy and look at the field pathing in the IDE Xlate coming in and the field pathing in the IDE xlate going out and see they are not identical, then don’t expect bulkcopy to map them.
Thanks to Jim kosloskey and some experience of my own I don’t readily embrace using bulkcopy anymore, so I would copy every field I want to come across individually.
For me this typically adds an extra 2 days of work but I believe I get it back later on for more reasons than the one we are talking about.
It also gives you good practice with doing iterations since you are likely to have repeating groups and segments.
If you do decide to use bulkcopy then one way to trick bulkcopy is to modify one of the HL7 variants until the pathing matches.
In some cases this might even require editing the variant file with a text editor because the IDE might be too smart to let you do just anything.
A long time ago I used this approach to convert HL7 2.3 messages to HL7 2.2 for older systems.
With my current experience I would definitely not use that approach in favor of the field by field copy.
I understand their is a pathcopy which might be another alternative but I’ve never used pathcopy.
Russ Ross
RussRoss318@gmail.com