go to post Jeffrey Drumm · Aug 13, 2021 If you don't care about any unsent/completed/suspended messages, try calling the CleanProduction() method in class Ens.Director: Do ##class(Ens.Director).CleanProduction() This is strongly discouraged for PROD environments ... be forewarned. Would recommend you contact the WRC if you're getting this error in a PROD environment.
go to post Jeffrey Drumm · Aug 13, 2021 Giving them only the %EnsRole_Operator role will prevent them from making configuration changes to the production. And if they aren't assigned the database resource (%DB_<databasename>), they won't be able to start or stop the production either.
go to post Jeffrey Drumm · Aug 9, 2021 If the message text is displayed in black, it's most likely that the message does not conform to the document type selected in the inbound service.
go to post Jeffrey Drumm · Aug 8, 2021 In the %SYS namespace: %SYS>Set ^%SYS("Portal","EnableAutoRefresh")=1 That will reveal the radio buttons that allow you to turn on/off Auto Refresh. Setting that global to 0 actually has the same effect as clicking the Off button, but eliminates the ability to turn it back on via the management console.
go to post Jeffrey Drumm · Jul 28, 2021 There's the Activity Monitor, but I don't know whether it was available for 2017.x. It requires configuration, as it is not enabled by default. It starts gathering activity after configuration, so you won't be able to use it to obtain activity/volume history for messages processed through the production prior to setup.
go to post Jeffrey Drumm · Jul 22, 2021 Building a new message would have been my suggestion had I seen this in time, but you arrived at the same conclusion without my help!
go to post Jeffrey Drumm · Jul 20, 2021 Are these messages all compliant with the doctype structure they're associated with? If yes, why not use the symbolic path that the structure supplies ... i.e. something like MsgOut.GetValueAt("PIDgrpgrp.ORCgrp(n).OBXgrp(n).NTE(n)")?
go to post Jeffrey Drumm · Jul 16, 2021 @Robert C. Cemper has you on the right track, but I'm curious as to whether the vendor of the foreign (i.e. non-HealthShare/HealthConnect) system has provided a specification. Do you need to accommodate Acknowledgement messages for both sending/receiving? Is there some sort of handshake protocol that is used to indicate when it's safe to send, a sort of RTS/CTS-type mechanism? Or is this being designed "on the fly?" If I were designing something like this, I'd go with a web service ... always over the same port, and when you want to send something you'd POST it. When there's nothing to POST, you'd periodically GET to see if anything is waiting. Anything else would most likely be a one-off in healthcare integration.
go to post Jeffrey Drumm · Jul 14, 2021 Are you receiving the A19 message as a response to each ADT message? Or are they being sent asynchronously?
go to post Jeffrey Drumm · Jul 14, 2021 The maximum string length for HL7 fields in Health Connect/IRIS for Health is something like 3.6MB; larger than that, the field itself is represented as a stream. You may want to look into the stream methods for accessing fields for your use case.
go to post Jeffrey Drumm · Jul 13, 2021 The variable obx5 most likely refers to the OBX:5 field of an HL7 message, which is normally used for narrative or image result data in healthcare. \.br\ is a commonly used mechanism for representing line breaks in formatted text data. Why they're included in a base64 string/stream is a mystery, but I've seen stranger.
go to post Jeffrey Drumm · Jul 10, 2021 Or how about this (again, with thanks to @Stuart Strickland)? N(i,s) f j=1:1:$l(i) s c=$e(i,j),o=$g(o)_$s(",.!?"[c:c,c?1a:$e(" ",j>1)_$ZCVT(c,"U")_$p(s,7,$a(c)#32),1:"") q o 114 characters Who needs the Nato alphabet in the code when you can pass it as a parameter? (I'll stop now, I know I'm getting silly)
go to post Jeffrey Drumm · Jul 10, 2021 One additional modification to @Stuart.Strickland8116's most amazing attempt: N(i) f j=1:1:$l(i) s c=$e(i,j),o=$g(o)_$s(",.!?"[c:c,c?1a:$e(" ",j>1)_$ZCVT(c,"U")_$p("lfa77harlie7elta7cho7oxtrot777ndia7777ike7ovember7scar777omeo777niform7777ankee",7,$a(c)#32),1:"") q o 180 192 characters, assuming Unix line endings and a ridiculously limited use case that still solves the problem EDIT: Added 12 characters to add fix for capitalized output ...
go to post Jeffrey Drumm · Jul 10, 2021 While true, that's a rabbit hole that will generally be quite unrewarding as you continue down through the language/abstraction layers to the underlying machine code. "Code golf" in my experience has never been about the size of the final executable ... it's all about how little you have to write to solve the problem.
go to post Jeffrey Drumm · Jul 9, 2021 While not actually competing in this exercise, I would suggest that both of you could shorten your comma-delimited list by 26 characters with the realization that the first character of each entry is already supplied by the input string
go to post Jeffrey Drumm · Jul 6, 2021 The <transform> action seems to hide the return value of the call to the DTLName.Transform() method, but you should be able to call it in a code action and obtain it: Set xform=##class(My.DTL.Class).%New() Set tSC = xform.Transform(SrcMsg, .TgtMsg) If there's been an error, tSC should tell you what it is ...
go to post Jeffrey Drumm · Jul 6, 2021 I haven't actually tried this, but I suspect it's as simple as creating a message of type Ens.AlertRequest, populating it, and <call>ing Ens.Alert asynchronously in the <catchall>. Or maybe insert an <alert> action?
go to post Jeffrey Drumm · Jul 1, 2021 Hi @Eduard Lebedyuk, I recently implemented this mechanism for handling ad-hoc message selection queries to the Google Health HL7v2 Store, and wanted to share a modification needed to satisfy the customer. Their concern was that the service name was hard-coded in the dispatch class, and that they would have to touch the code if they used the class with a differently named service. To resolve that, I added a TargetConfigName property to the otherwise empty proxy service along with a SETTINGS parameter to reveal it through the configuration panel and allow the user to configure it. I then modified the methods in the dispatch class to expect the service name in the URL "launch" argument and interrogate the production for the specified service's TargetConfigName value. As always, thank you for the informative articles and answers!
go to post Jeffrey Drumm · Jun 27, 2021 Would it be possible to provide a little more detail? Are you referring to the Ensemble/HealthConnect message store, the HealthShare UCR, or the TrakCare EHR?
go to post Jeffrey Drumm · Jun 25, 2021 The tools for doing this will vary by platform, but a utility called qpdf supports your needs for most modern Unix/Linux variants. You would call it from ObjectScript using the $ZF(-100) function.
