Hi @Alex Woodhead there is no "preview" container on the https://containers.intersystems.com site any more, only "latest-preview" - was this released? If so which build?

Thanks!

=Sergei

Hi @Evgeny Shvarov 
You need to use port 52773 with localhost in Docker. It's relative to the container not to your host.

I just tried this with intersystemsdc/irishealth-community:latest image above, works fine.

Looks like a typo, this one works: https://iris-fhirfy.demo.community.intersystems.com/csp/fhirfy/index.html

Ciao Henry, this URL doesn't open for me can you double check?

Yes but you can have one top-level 'manually created' one and have individual ones based on separate OpenAPI files

Well you gave me two so I should have one spare wish :)

Make iris:latest-cd just iris:latest, this way we can just skip the "latest" bit altogether and just use iris without any tag at all.

Hi Bob,

That's good news and I like new names much more than old ones. I hope old tags for old releases will still be available?

A couple of entries from my container tagging wishlist (one can dream, you know)

- provide :latest tag for all containers, but especially for community ones, which will just pull the latest working release without having to rebuild dockerfiles every year when license expires

- provide 2023.1.x tag which will follow the latest minor version

Hi Ben,

I believe here is about hmf gateway of TrakCare

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

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.

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.

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

Looks like it doesn't work with single file kits https://docs.intersystems.com/iris20222/csp/docbook/DocBook.UI.Page.cls?...

Have some fun,
And delete one,
65535 lines of code in the project!

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:

You can also try to ask WRC privately if above option is not suitable for any reason.

David's answer is not quite correct because one can't use $translate to search for groups of symbols (like two quotes next to each other), this is what $replace function is for. $translate always search for an individual character.

$translate(str,"""","")

https://docs.intersystems.com/iris20212/csp/docbook/Doc.View.cls?KEY=RCO...