We have been investigating how to activate a Server to Generate Tokens and an associated Resource Server to Validate the Token. This step, actually we have found out with the invaluable support of @Alberto Fuentes from Intersystems.
We have a handful of cases where we get reflex orders in an interface that contain multiple OBR segments. These are rare but when we get them, they are causing errors in down stream systems because we are unintentionally excluding OBR segments.
Questions:
At the DTL level - is it possible to iterate over this segment WITHOUT altering the underlying schema? If so what would that look like?
First thank you for your time in reading and answering our question.
We have been reading, inquiring, researching about how to make multiple dispatches from 1 Process of type "DICOM.BP.QueryProcess" to several target Operations.
We need some help to further develop this use case, and some advice 🧭, examples or recommendations
Thank you for taking the time to read and answer this question.
We need to find out how to display an EnsLib.DICOM.Document using LOGINFO, in the traces.
We have tried to use:
set writer=##class(%XML.Writer).%New()
set status=writer.OutputToString()
set status=writer.RootObject(..DocumentFromService)
set xml= writer.GetXMLString()
$$$LOGINFO("..DocumentFromService en xml: "_xml)
First of all, thank you very much in advance for reading and responding.
Also, thank you for any support, because it is a relief, support, contribution, help to have people with more understanding, knowledge and practice, reading, and thinking this doubt.
There is the following need:
Two 2 circuits are available:
1st DICOM Circuit of "Studio" ( Classic Service ).
How would you recommend us to filter in the message viewer to find inside a property called "mensaje" of type " %XML.GlobalCharacterStream" which is inside a class called" Mensajes.Request.Laboratorio.peticionER7Request", the text "24642"?
I'm experiencing a recurrent problem that I haven't found the way to solve, so I'm coming here with the hope somebody can give me a new approach.
To make it short: we are creating categories on-demand to be able to place the maximum numbers of workers in memory, avoiding the limits established by system categories. But from time to time, one of this creation fails and system is no able to start the queue. The error we are getting is:
I've created a custom class that extends to the standard HS.Message.PatientSearchRequest. Inside the custom class i just want to pass the data as input only.
But i am getting ERROR #6277: Type attribute, s01:AcoPatientSearchRequest, does not specify valid type for XML input tag: pRequest (ending at line 5 character 171) </error>
I tried adding Parameter XMLIGNOREINVALIDTAG = 1; and
Hey everyone as you may know I am a beginner and I am kindly asking for some assistance in a problem I have been solving. The problem is that I am calling a user defined function within a procedure called occupiedseatsAdj and the compiler comes up with this error.
Hello, first of all thanks for your time reading this question,
We would need some help, we would need to delete a %GlobalBinaryStream which is a variable called "pOutput" which is being sent from a REST Service to POSTMAN
I have a requirement to delete the Ensemble interfaces , as per User request. I would like to write a routine for that and once I execute, it should remove the interface components through code. Could you please provide code samples for the following actions ?
Deleting an individual rule from a rule class
Deleting a class from Ensemble
Deleting a Host (Service/Operation/Process) from the Production.
I have a requirement to update the Ensemble Host Settings Programmatically. Mainly the "AlertOnError,QueueCountAlert,QueueWaitAlert,InactivityTimeout" settings.
I used Ens_Config.Item (persistent) class to get the settings (list object) and then update it. But for some of the Business Host's, I dont see the above settings in the table, but present in Settings of that particular Host in Ensemble Management Portal. So my logic is not working.