Find

Article

Ricardo Paiva · Jun 28, 2024 9m read

Integrar aplicaciones frontend de React con servicios backend como la base de datos IRIS a través de APIs REST puede ser una forma poderosa de construir aplicaciones web robustas. Sin embargo, un obstáculo común que los desarrolladores suelen encontrar es el problema de Cross-Origin Resource Sharing (CORS), que puede impedir que el frontend acceda a los recursos en el backend debido a restricciones de seguridad impuestas por los navegadores web. En este artículo, exploraremos cómo abordar los problemas de CORS al integrar aplicaciones web de React con servicios backend de IRIS.

Discussion (0)1

Announcement

Irène Mykhailova · Jun 28, 2024

#Docker #Video #InterSystems IRIS

Salut la Communauté!

Profitez de regarder la nouvelle vidéo sur la chaîne Youtube d'InterSystems France.

📺 Obtenez InterSystems IRIS depuis le Docker Store

Apprendrez à accéder à la liste InterSystems IRIS sur le Docker Store et à extraire une image Community Edition.

Cette vidéo est doublée grâce à Bard, l'intelligence artificielle de Google.

N'oubliez pas à partager vos réflexions et impressions dans des commentaires après avoir regardé cette vidéo !

Discussion (0)1

Article

Hiroshi Sato · Jun 27, 2024 1m read

#Security #Tips & Tricks #InterSystems IRIS #Caché #Ensemble #InterSystems IRIS for Health

InterSystems FAQ rubric

You can use the List query of the %SYS.Audit to output audit logs programmatically.

The sample code is as follows:

 Set statement=##class(%SQL.Statement).%New()  
 Set status=statement.%PrepareClassQuery("%SYS.Audit","List")
 Set rs=statement.%Execute()  
 Set tab = $char(9)
 While rs.%Next() {    
   Write rs.%Get("TimeStamp")_tab_rs.%Get("Event")_tab_rs.%Get("Username"),!      
 }

Discussion (0)1

Question

Scott Roth · Jun 27, 2024

#Business Process (BPL) #DTL #FHIR #HL7 #JSON #HealthShare #InterSystems IRIS for Health #Health Connect

IRIS for UNIX (Red Hat Enterprise Linux 8 for x86-64) 2024.1 (Build 267_2U) Tue Apr 30 2024 16:06:39 EDT [HealthConnect:7.2.0-1.r1]

I have a use case where Epic is sending an A60 Allergy transaction is set at the Patient level, but we have a system called VIBE which needs the ADT at an Encounter level instead. Currently we store ADT information in a MS SQL database for years, and we are querying it to get the latest Account Number to insert into the ADT^A60 for VIBE.

This MS SQL Visit Database was built over 20 years ago and is quite cumbersome to keep maintaining. I would like us to move away from using this MS SQL Database, and query Epic directly.

One idea is to use Epic's FHIR repository to query and get the most resent Account Number to pass into the HL7 message.

Using the FHIR Demo model to test the functionality to connect to Epic's FHIR repository. I am sending a request through HS.FHIRServer.Interop.HTTPOperation. Just recently I figured out the magic chant to get the Response back from Epic, however I am not sure what to do next.

How do I take the Quick Stream ID from JSON and put it into the FHIR Bundle Class Structure that I can pass back into the HL7 message via in a DTL?

2 Comments

Discussion (2)2

Discussion

Robert Barbiaux · Jun 27, 2024

#InterSystems IRIS for Health

When using VS Code client-side editing in combination with a file-based revision control system such as git, I find activities such as branch switching and moving/renaming classes and packages a bit tedious, since you to maintain the connected namespace in sync manually.

I am not aware of a built-in way to do this with VS Code Extension. Just added an idea to the portal that is about adding some kind of mechanism to do this automatically, please do not hesitate to comment, amend and vote for idea DPI-I-608 😊

Discussion (0)1

Creación de una aplicación web React simple con backend IRIS: resolución de CORS

[Vidéo] Obtenez InterSystems IRIS depuis le Docker Store

How to output audit logs programmatically (by user or event)

InterSystems FAQ rubric

How to interpret FHIR.Interop.Response into Patient FHIR Bundle to use to enhance HL7 message

VS Code client-side editing and class/package changes