Nova postagem

Pesquisar

Resumo
· Mar. 11

Join the InterSystems AI Programming Contest!

Dear Community member,

We're excited to invite you to participate in the 🏆 InterSystems AI Programming Contest 🏆


 

Task: develop any solution on InterSystems IRIS, InterSystems IRIS for Health, or IRIS Cloud SQL that uses generative AI.

Duration: March 17 - April 6, 2025

Prize pool: $12,000  + a chance to be invited to the Global Summit 2025!

>> Full contest details here.

We're looking forward to your entries 😉

Artigo
· Mar. 11 1min de leitura

Swagger API for FHIR in InterSystems IRIS For Health

Hi colleagues!

Often, while developing a frontend app or any other communication vs REST API, it is worth having a Swagger UI - a test UI for the REST API that follows Open API 2.0 spec. Usually, it is quite a handful as it lets have quick manual tests vs REST API and its responses and the data inside.

Recently I've introduced the Swagger support to the InterSystems IRIS FHIR template for FHIR R4 API:

How to get it working.

Make sure you have docker installed.

Clone the repository:

git clone git@github.com:intersystems-community/iris-fhir-template.git

and start:

docker compose up -d

Once everything is built up open swagger at:

http://localhost:32783/swagger-ui/index.html

Or if you pull it at VS Code, you can open via InterSystems menu:

To get it tested for example proceed to Patient entry and request for the patient id=3:

Hope you like it! 

Comments, feedback, Pull requests are most appreciated!

Discussão (0)1
Entre ou crie uma conta para continuar
Artigo
· Mar. 11 1min de leitura

API Swagger pour FHIR dans InterSystems IRIS For Health

Bonjour collègues !

Lors du développement d'une application front-end ou de toute autre communication avec l'API REST, il est souvent judicieux d'utiliser une Swagger UI, une interface de test pour l'API REST conforme à la spécification Open API 2.0. Elle est généralement très pratique, car elle permet d'effectuer des tests manuels rapides avec l'API REST, ses réponses et les données qu'elle contient.

J'ai récemment intégré la prise en charge de Swagger dans InterSystems IRIS FHIR template pour l'API FHIR R4 :

Comment le faire fonctionner.

Assurez-vous d'avoir installé Docker.

Clonez le dépôt :

git clone git@github.com:intersystems-community/iris-fhir-template.git

et commencez :

docker compose up -d

Une fois que tout est construit, ouvrez Swagger à :

http://localhost:32783/swagger-ui/index.html

Ou si vous le récupérez dans VS Code, vous pouvez l'ouvrir via le menu InterSystems :

Pour le faire tester, par exemple, passez à la saisie du patient et demandez l'identifiant du patient = 3 :

J'espère que cela vous plaira !

Vos commentaires, retours et requêtes pull sont les bienvenus !

Discussão (0)1
Entre ou crie uma conta para continuar
Artigo
· Mar. 11 2min de leitura

Best Structure to Make a Priority Queue In Objectscript

Intro

In the process of trying to get more familiar with Objectscript I decided to try to build a general priority queue since I wasn't able to find an implementation anywhere. My though process for implementing this followed this general path.

Discussão (0)1
Entre ou crie uma conta para continuar
Pergunta
· Mar. 11

git-source-control questions

Hi

I'm trying to assess whether git-source-control will work for our development environment.  I've watched some videos and read the documentation and read some posts and I'm still unsure whether it works with multiple developers using a shared remote development environment (i.e. namespace).  This [Video] Let InterSystems IRIS Do the Work: Git Source Control & Linting says that you can have multiple developers and says it's "Package Manager-aware (supporting multiple repos in one namespace)" whereas  this post on the git-source-control github Remote development and multiple users · Issue #613 · intersystems/git-source-control
appears to say you can't.  Which is it? 

Also does it support .js and .css files?  I've been trying to replicate the git-source-control demo in this video: [Video] Selecting The Right Source Control Strategy for Your Team on my local instance with my own project which contains .csp, .js, .css and .png files and they weren't exporting originally, so I added the ",*.js,*.css,*.png" code to the SoureControl.Git.Utils class


ClassMethod BaselineExport(pCommitMessage = "", pPushToRemote = "") As %Status
{
    set sc = $$$OK
    try {
        write !, "Exporting items..."
        set rs = ##class(%Library.RoutineMgr).StudioOpenDialogFunc(
            "*.mac,*.int,*.inc,*.cls,*.csp,*.js,*.css,*.png" // Spec

and they export now, but still don't import. 

2 Comments
Discussão (2)3
Entre ou crie uma conta para continuar