go to post Graham Uricchio · Mar 13, 2019 Thank you so much again Jeffrey you have really helped me out.
go to post Graham Uricchio · Mar 12, 2019 I hate to bother you again but I am so close and have 2 more questions. In the <transform> action, I have my DTL set up with the source as the HL7 schema and the target as the Record Map class that I have built. In the activity is that also what goes here:Second question. I have the <call> activity set up to send to the RecordMap file Operation on the production but am having trouble understanding how to build that request. I am guessing that request message class should be my Record Map class but when I go to "build request" the source seems to be HL7 message header fields. It should just be a direct passthrough now?
go to post Graham Uricchio · Mar 12, 2019 Thank you so much. This clears everything up. I really appreciate it
go to post Graham Uricchio · Mar 12, 2019 So I got into and did the course. I wish it was more HL7 oriented. I wondered if maybe you could confirm a few things for me if possible.If I am accepting an HL7 message (request) and want to send to a RecordMapBatch operation is it correct that in my context the request class would be 'EnsLib.HL7.Message' and response class be 'EnsLib.RecordMap.BatchResponse'?Secondly I am used to using the HL7.{SEG:FIELD} notation when building rules. Is this possible within a BPL?How would you build the ASSIGN to set the DG1 count context variable?Thank You,G
go to post Graham Uricchio · Mar 11, 2019 @Jeff.Drumm Thanks for your response. I would love to walk through that course but I get a 404 when I try to start it. I will let someone at InterSystems know
go to post Graham Uricchio · Apr 6, 2017 Thanks Armin. This was the issue. The inbound process was set to 2.3 where we needed to be using 2.5. Appreciate your help.
go to post Graham Uricchio · Apr 4, 2017 There is no error message but I do get a warning saying document is missing (due to the OBX segments not being there)- DocType: 2.5:MDM_T02- DocTypeCategory: 2.5- DocTypeSecondary: MDM_T02- DocTypeName: MDM_T02
go to post Graham Uricchio · Apr 4, 2017 Yep! That mapped the MRN over. Now I just can't seem to get the source OBXs into the OBXgrp() object. This works when I use the test tool but not when I call the DTL from the process and rule. <foreach property='source.{OBX()}' key='k1' ><assign value='source.{OBX(k1)}' property='target.{OBXgrp(k1).OBX}' action='set' /></foreach>