User bio
I've been Software Engineer and Java Developer for 20 years with 15 years working for the HealthCare sector.
Madrid
Member since Jun 13, 2022
Posts:
Replies:
Why don't you modify your query to execute just one massive SQL? An update with the select in the where.
I guess that you are using a Enslib.HL7.Service that uses EnsLib.File.InboundAdapter as Adapter. The problem is that the name of the file is not a property of Enslib.HL7.Message class, so you have to follow these steps:
- Create your own service that extends to Enslib.HL7.Service.
- Overwritte OnProcessInput process to get the name of the readed stream:
Set tFileName=pInput.Attributes("Filename") set sessionID = $$$JobSessionId set ^GlobalName("Session", sessionID) = tFileName do ##super() - From DTL use code to get the global that you created before getting the ID session from Enslib.HL7.Message and assign it to MSH property:
-
Set globalValue = $GET(^GlobalName("Session", sessionID)) - And finally assign globalValue variable to the MSH propery (using SET from the DTL):
target.{MSH.PropertyName} = globalValue
Open Exchange applications:
Certifications & Credly badges:





Global Masters badges:







Followers:
Following:
But a batch update will be more real time than a loop and multiple updates.