Thank you everyone for suggestions. We already tried all methods but like Jeff said all disable queries are queued and are disabled one by one. It's strange that stop entire production takes less time than disabling only all Services. What we are trying to achieve is drain all data from all Productions and then stop productions but that can only be done when services are disabled.
Hi Andrew
Thanks for your response. We already tried that but it doesn't stop them concurrently therefore it still takes the same amount of time to disable all Services.
Thanks again
HI @Irène Mykhailova
Still do not get any responses to any questions.
Hi
Is the work still ongoing or was completed? ASK DC AI still doesn't work.
Thank you
Was there any Intersystems updates since version 2016 that allows easy conversion of XML to JSON?
Thanks
Hello Jeffrey,
We're currently working on IRIS for Health 20.1 build 197, and we were wondering what fixes or additions went to latest build 199. Intesystems used publish all fixes with each FT build version, is there such list?
Thank you
Yuriy
Very nice feature indeed! Thank you for adding it.
We noticed that SAMPLES DB appears to be missing, was this intentional? Are you planning to add it in the official release?
Also, will there separate notification on build releases with list of fixes?
Thank you
Yuriy
When issues are found, how do we report them to support if our organization has tech support? WRC doesn't seem to list 2019.1 version as one that can be selected when incident is created.
What about Health Connect clients, does IRIS include components that are part of HealthShare Elite?
Thanks
Yury
Good News Indeed!
Sebastian,
What are the actual differences in AP version and standard installation kits if a customer is only licensed for Health Connect portion of it? If there are differences then there should be a separate standard install kit which excludes Patient Index, Active Analytics, and Clinical viewer. Otherwise, what's stopping Health Connect customer from using AP install kit? From what we experience AP version is released earlier than standard.
Yuriy
I have been using this UI since it was first introduced. Great many features and easy to use!
Happy about "Improved performance of production configuration page in management portal." in 16.2.
Brian,
Try this.
ClassMethod getRawHL7Content(pSessionID As %String = "", pTargetName As %String = "") As %String
{
set RawContent= "Message Not Found: Contact Interface Team"
set pID = ""
if (..NotEmpty(pSessionID)) && (..NotEmpty(pTargetName))
{
&sql(
SELECT TOP 1 MessageBodyId INTO :pID
FROM Ens.MessageHeader
WHERE (TargetConfigName=:pTargetName AND SessionId=:pSessionID)
OR (SourceConfigName=:pTargetName AND SessionId=:pSessionID)
)
if SQLCODE '= 0 {
set RawContent = "Message Not Found: Contact Interface Team"
}
else
{
set RawContent = ##class(EnsLib.HL7.Message).%OpenId(pID).OutputToString()
}
}
Quit RawContent
}
Thank you Mark,
Is there literature available on how Cache uses SMT?
Thanks again.
How would this impact performance of Ensemble 2014.1 if SMT 8 is enabled?
The document recommends a range for Max Response Times but certain operating systems like Red Hat do not report Max times instead they only report average times. How do we achieve these recommendations if we can’t compute them in the first place? Are there any third party tools used by InterSystems to measure Max Response Times on Red Hat?
Great Tool!
But running test on two databases sitting on two different storage types reveals something we didn't expect. The DB with less IOPS (reported by the tool) actually performs better with real Ensemble data, especially when searching is involved. Perhaps random reads isn't a good indicator to determine overall DB performance?
Thanks!
I don't know about other users but we heavily rely on Find In Files feature of Studio. It becomes very useful and efficient when we're searching for a common change key in all of our DTL classes. In our experience the search is very reliable and fast