go to post Glenda Anaya · Dec 5, 2019 Hi, How do I get the count of OBX segments in BPL, so I can split the message and send one line (OBX.5 value - mapping) at the time to the CSV file? I used a Integer var context.OBXNumber with request.GetValueAt("ORCgrp().OBXgrp(*)") While context.OBXCounter<context.OBXNumber, but it is not getting me the count. Thanks
go to post Glenda Anaya · Dec 5, 2019 Thank you for replying, The layout is identical, the CSV file will have a record with more or less lines referring to one patient/order depending of how many OBX segments we have in the message (report). OK.. I will try the BPL/DTL to split each line OBX and send it to the CSV file. Output .csv file: Order 123|Patient 1| line 1 report OBX... Order 123|Patient 1| line 2 report OBX . . Order 123|Patient 1| line n report OBX Order 235|Patient 1| line 1 report OBX . . Order 235|Patient 1| line n report OBX Order 199|Patient 2| line 1 report OBX . . Order 199|Patient 2| line n report OBX Thanks
go to post Glenda Anaya · Dec 5, 2019 Hi Jeffrey, Could you please tell me how can I configure a field in the record map to create a line for each OBX segment, each line is going to repeat the OrderNumber (ORC field) and PatientID (PID field). Do I need to create a complex record map? or use BPL that will iterate on each OBX segment? Thanks Glenda
go to post Glenda Anaya · Jun 15, 2016 Hello,We got the same error when we updated Ensemble to 2015.2.3, even though we already had Java 7 installed.Connection failed.JDBC Gateway failed to start: ERROR #5001: There were errors returned when trying to start the Java GatewayReturn: Exception in thread "main"java.lang.UnsupportedClassVersionError: JVMCFRE003 bad major version; class=com/intersys/gateway/JavaGateway, offset=6 ...The problem was that the JAVA Home Directory in the SMP was still pointing to wrong directory Java 6. We just changed it to right directory 71_64 , started the Gateway and everything is OK.
go to post Glenda Anaya · Jun 15, 2016 Than you Richard for letting us know about that routine to debug connection issues, I was not aware.The issue was resolved just by changing the settings; since PEM certificate already had all the CA certificates concatenated, we did not have to enter the clients credentials, once this was changed we got a SSL connection succeeded message. Regards,
go to post Glenda Anaya · Jun 9, 2016 I just wanted to know if anybody here had the same issue, before open a support case/ticket. Thank you Aaron, I will do that.