That's an ambitious plan for sure! I also recommend the demos&drinks event, you can learn a lot of stuff you don't even have an idea you wanted to know about before you see it :) . See you there!

1) Download and install docker

2) Run this code in terminal

docker run --rm --name iris-demo -d -p 9090:52773 -e IRIS_USERNAME=demo -e IRIS_PASSWORD=demo intersystemsdc/irishealth-community:latest

3) Open browser at http://localhost:9090/csp/sys/UtilHome.csp and use VSCode to connect to the same host/port

Regarding SQL Server setup, you'll have to ask on SQL Server forum

I'm with Tim on this one, it's OK to create something like https://sergeinator.com for fun and giggles or use is as a prototyping tool instead of MS Paint, but I would not let this code anywhere near production.

Great article Tim! I think another area where AI can help a lot and which is usually overlooked in IRIS development is an automated testing

Looks like the error is on a back-end, the Java code you are calling is not configured properly. Try running it from the terminal.

Great stuff James, can't wait to see it in production!

Hi Stephen, this is a valid approach however you will lose information about problematic calls such as json can't be parsed or API key in headers is wrong. I prefer to actually save the http call in full as http generic message and then call a process or operation with transformation to the proper message format, as Alex demonstrated in his third example. You can still call operation manually if you want, passing the parsed message. 

Is there a list of changes? Release notes document looks very empty

https://docs.intersystems.com/iris20251/csp/docbook/DocBook.UI.Page.cls?...

Congratulations to all winners, it was difficult to vote this time, so many great applications and samples!

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