go to post Sergei Shutov · Mar 15 You can also just use incoming XML as a steam and extract data you need using parser into a custom defined ensemble message, if you only need parts of the incoming data
go to post Sergei Shutov · Mar 15 Hi Phillip, In TrakCare, interoperability is controlled by TrakCare Health Messaging Framework (HMF). Each Interface has to go through HMF Gateway, which is an IRIS Production, and then all those are getting routed through HMF Router which is a separate IRIS production. Please have a look at HMF documentation for more details. A lot of this code is auto-generated so you need to understand what needs to be configured in TrakCare and what needs to be configured in Production.
go to post Sergei Shutov · Mar 15 Well first of all there is a first-class support for FHIR data in IRIS for Health and I would definitely recommend to use it instead of rolling out your own class-based solution. See documentation here https://docs.intersystems.com/irisforhealth20221/csp/docbook/Doc.View.cl... If you want to work with projections, given that even basic data fields in FHIR are quite complex https://www.hl7.org/fhir/datatypes.html#primitive you'll need to define separate embedded classes for each data type; it doesn't have to be a separate class for each field.
go to post Sergei Shutov · Dec 18, 2022 That's an old programmers drinking song https://www.barrypopik.com/index.php/new_york_city/entry/99_little_bugs/ No idea how to actually fix this, just being silly
go to post Sergei Shutov · Dec 14, 2022 Looks like it doesn't work with single file kits https://docs.intersystems.com/iris20222/csp/docbook/DocBook.UI.Page.cls?...
go to post Sergei Shutov · Dec 13, 2022 Have some fun,And delete one,65535 lines of code in the project!
go to post Sergei Shutov · Sep 7, 2022 There are few reasons superserver API is not publicly documented, one of them is to prevent an easy discoverability of outdated instances outside firewalls by hackers. You can use Atelier API with relatively recent Cache/IRIS, which answers on Web server port and has support for authentication and will return version of Cache/IRIS it's running on, for example: http://localhost:57772/api/atelier/ You can also try to ask WRC privately if above option is not suitable for any reason.
go to post Sergei Shutov · Aug 29, 2022 SAM was built as a "gateway" to proper custom Prometheus/Grafana setup for cases when you only need to monitor IRIS. If you are building more complex solution, with non-InterSystems sources, I would recommend to set up Prometheus separately from SAM and just add SAM monitoring endpoints there.
go to post Sergei Shutov · Jul 28, 2022 Hi Michael, You should have one top-level dispatch class which will dispatch individual API calls to separate endpoint classes. <!-- teapots --> <Map Prefix="/teapots" Forward="REST.Teapots"/> <!-- kettles --> <Map Prefix="/kettles" Forward="REST.Kettles"/>