go to post David Reche · Dec 2, 2019 Hello @Pasi Leino We are very sure that probably we will again at https://jonthebeach.com/ this time will be from May 13th to 15th of course in Málaga Please be on tune. We will be talking about this in the coming months Regards
go to post David Reche · Jul 17, 2019 Review the cconsole.log and check if there is any problem with the license, also you can check Application errors log
go to post David Reche · Jul 16, 2019 Great initiative !! We did a webinar for spanish speakers some days ago and the feedback was very good.Also the title sounds very interesting !!Congrats
go to post David Reche · Jul 5, 2019 Yes, could be, however personally I don't like business metrics too much for this type of things. Because you are making the query every "N" seconds. If you want to show the SQL result in a DS dashboard, from my POV is more useful to make a simple KPI executing the SQL:https://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=D2MODADV_ch_kpiIn this case the query is made only when the DS is show.
go to post David Reche · Jul 5, 2019 Well, there are only 2 tables related with that queries:Ens.MessageHeader(https://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=EMONITOR_concepts#EMONITOR_concepts_msgs)EnsLib.HL7.Messages (https://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=EHL72_tools#EHL72_tools_classes)Any Ensemble Message has a header object or record (Ens.MessageHeader) the Message Body related with this Header can be any persistent object. Then you have to check MessageBodyClassName property to check if the body is a EnsLib.HL7.Message, then you can link the Header and Body using MessageBodyId property.I hope this helps.Ens.MessageHeader
go to post David Reche · Jul 5, 2019 Do you want to explore the content of the HL7 Messages using SQL? Or only meta Data like document type, date etc? In case you want more data from HL7 body using SQL I recommend to use a HL7 Search table
go to post David Reche · Jun 22, 2019 Good, but if you create a new Database the problem still being the same. The only easy thing you can do is to enable interoperability for the namespace USER:To create another database and enabling interoperability throws the same problem (exceeds databases license limit).So, because IRIS CE is mainly thought for development and not for production I think a best practice is to enable interoperability USER by default.Thanks
go to post David Reche · Jun 22, 2019 In any case from my point of view this number or user databases limit for CE Edition is not well explained (specially to new people):This the list of "user" databases (or not system databases) in the list of databases:Into the red circle are 5 user databases. So in this case you can't create any more databases with IRIS CE license.But the license counts ENSLIB as "user database" and is not true. This Database is needed to enable interoperability to any database. According to IRIS documentation:ENSLIB — This is a read-only database contains additional code needed for InterSystems IRIS Interoperability features, specifically the ability to create productions, which integrate separate software systems. If you create a namespace that is interoperability-enabled, that namespace has access to the code in this database.So keep in mind that the practical number of user databases for CE is 4.
go to post David Reche · Jun 13, 2019 I think the link for download is wrong. The right one is https://wrc.intersystems.com/wrc/coDistGen.csp. Right @Andreas Dieckow ?
