查找

公告
· 一月 21

[Video] Containers & Kubernetes - Proper Use and Lessons Learned

#容器化 #Global Summit 2024 #Kubernetes #视频 #Summit

Hey Community,

Enjoy the new video on InterSystems Developers YouTube:

⏯ Containers & Kubernetes - Proper Use and Lessons Learned @ Global Summit 2024

When does it make sense to use containers? How about Kubernetes? Join us to learn about the proper use of containers and lessons learned with Kubernetes deployments, and pitfalls to avoid.

Presenters: 
🗣 @Mark Bolinsky, Principal Technology Architect, InterSystems
🗣 @Ariel Glikman, Sales Engineer, InterSystems
🗣 @Bob Kuszewski, Product Manager, Developer Experience, InterSystems
🗣 @Kai Zou, Manager of Release Engineering, InterSystems  

Learning has never been this easy - tune in and subscribe to stay inspired! 👍

讨论 (0)1
登录或注册以继续
公告
· 一月 21

Top InterSystems Developer Community Authors of 2024

#开发者社区官方

Hey Developers,

It's time to announce the Top InterSystems Developer Community Authors of 2024 🎉

We are pleased to reward the most active contributors across all regional DC sites (EN, ES, PT, JP, CN, and FR):

  • Breakthrough of the Year
  • Top Best-Selling Authors
  • Top Experts
  • Top Opinion Leaders

Let's look at the DC Wall of Fame 2024 and greet everyone with big applause! 👏

Badge's Name Winners DC Winners InterSystems
 
Nomination: Breakthrough of the Year
Breakthrough of 2024

  

@john.smith4237

@Meenakshi Muthu

@Eyal Levin

@Alin Soare

@Veerraju Grandhi

@Takao Otokita

@Maxim Gorshkov

@Nicole Sun

@Brad Nissenbaum

@Shuheng Liu
 
Nomination: InterSystems Best-selling Author
1st place: 
Gold Best-Selling Author

  

@Muhammad Waseem

@Luis Angel Pérez Ramos
2nd place: 
Silver Best-Selling Author

  

@Robert Cemper

@Megumi Kakechi
3rd place: 
Bronze Best-Selling Author

  

@Iryna Mykhailova

@Hiroshi Sato
Best-Selling Author

  

@Heloisa Paiva

@Pierre LaFay

@David Hockenbroch

@姚 鑫

@sween

@Kurro Lopez

@Yuri Marx

@Mihoko Iijima

@Alberto Fuentes

@Sylvain Guilbaud

@Guillaume Rongier

@Toshihiko Minamoto

@Ricardo Paiva

@Danusa Calixto
 
Nomination: InterSystems Expert
1st place: 
Gold Expert

  

@Enrico Parisi

@Luis Angel Pérez Ramos
2nd place: 
SilverExpert

  

@Robert Cemper

@Alexander Koblov
3rd place: 
Bronze Expert

  

@Jeffrey Drumm

@Brett Saviano
DC Expert

  

@Julius Kavay 

 @John Murray

@David Hockenbroch

@Ashok Kumar T

@Robert Barbiaux

@Stephen Canzano

@Yaron Munz

@Eduard Lebedyuk 

@Ben Spead 

@Timo Lindenschmid 

@Guillaume Rongier 

@Timothy Leavitt 

@Sylvain Guilbaud 

@Tani Frankel  
 
Nomination: InterSystems Opinion Leader
1st place: 
Gold Opinion Leader

  

@Robert Cemper

@Luis Angel Pérez Ramos
2nd place: 
Silver Opinion Leader

  

@Iryna Mykhailova

@Sylvain Guilbaud
3rd place: 
Bronze Opinion Leader

  

@Enrico Parisi

@Guillaume Rongier
DC Opinion Leader

  

@Muhammad Waseem

@Pierre LaFay

@Heloisa Paiva

@Kurro Lopez

@David Hockenbroch

@John Murray

@Yuri Marx

@Julio Esquerdo

@Ben Spead

@Timothy Leavitt

@Danusa Calixto

@Eduard Lebedyuk

@Evgeny Shvarov

@Mihoko Iijima

@Hiroshi Sato

 

This list is a good reason to start following some of the great authors of the Developer Community ;)

BIG APPLAUSE TO OUR WINNERS!

Congratulations to all of you, and thank you for your great contributions to the InterSystems Developer Community in 2024! 

15 Comments
讨论 (15)7
登录或注册以继续
问题
· 一月 21

In Studio is there a way to access the code that flags whether a project has unsaved changes? (is there a property that controls the "star" on unsaved projects?)

#Studio #Caché #HealthShare #InterSystems IRIS #InterSystems IRIS for Health

I'm working on some code that would benefit from being able to see whether or not a project file has been saved in Studio.

I can see when I make changes, that the project name has an asterisk added to it:

In searching for it, however, I haven't been able to find any methods or calls to access the property/check that controls that asterisk.

My question is whether anyone out there knows if that is accessible and if so then how can it be accessed.

I'd like to add a check in my code that enforces that the project file must be saved prior to proceeding with the intended action. (alerting in case the asterisk is present, e.g. the project hasn't been saved)

 

2 Comments
讨论 (2)2
登录或注册以继续
问题
· 一月 21

file process workflow in healthcare cloud

#Health Connect

Hello,

We are doing the hl7 integration migration from cloverleaf to InterSystems Healthshare.  so I have an application has workflow like below, and I am seeking the suggestion of the workflow in InterSystems HealthConnect cloud version.

The current application has workflow like this.

1. local server has Cron job every night to create about 10 files with specific name and next day's timestamp in file name with a dummy word in it and the files located in local cloverleaf server. pretty much 1 facility per file, file name has facility name and timestamp in it.

2. next day when we have lab reports in Epic, and the message will flow to cloverleaf server and write the messages(with transformation) in the related facility file that is generated in step 1, when the day is done, we have full day's messages in the file in cloverleaf server, it is same server as step 1

3. in another sftp server, we have Cron job, that comes next early morning every day to pick up the files in step 2 , call a tcl script to do data manipulation(remove duplication) and add foot and header etc. and then send the files to another destination sever for vendor process.

so my question is, now in InterSystems we have cloud server so we do not have local machine to store the file any more, so what's the recommended workflow here?  for step 1, I assume I need to use a service to produce the file and put on a ftp server , intersysetm says we can do a S3 storage but it is not built yet.  for step 2, since we have no local server, is it possible to map a S3 storage as a local server so I can write the file, or I need to pull the file down and write and sftp it back for every message? for step 3, I assume I need to sftp down the file, use vss code to write a related script to manipulate the data and then sftp the file back to the cloud storage?  would my assumption work this way?

Thank you in advance!

讨论 (0)1
登录或注册以继续
InterSystems 官方
· 一月 21

Alerte : données non valides introduites dans la base de données et les fichiers journaux avec des opérations $LIST spécifiques

#日志 #ObjectScript #InterSystems IRIS #文档 #Health Connect #HealthShare #InterSystems IRIS for Health #InterSystems 官方 #TrakCare

InterSystems a corrigé un défaut qui provoque l'introduction d'enregistrements de base de données et de journaux non valides lors de l'utilisation d'une syntaxe $LIST spécifique. La probabilité de rencontrer ce défaut est très faible, mais les impacts opérationnels peuvent être importants.

Produits concernés

  • Plateforme de données InterSystems IRIS® : versions 2023.3, 2024.1.0, 2024.1.1, 2024.1.2, 2024.2, 2024.3
  • InterSystems IRIS® for Health : versions 2023.3, 2024.1.0, 2024.1.1, 2024.1.2, 2024.2, 2024.3
  • HealthShare® Health Connect : versions 2023.3.0, 2024.1, 2024.1.1, 2024.1.2, 2024.2, 2024.3
  • HealthShare® Unified Care Record and Suite : version 2024.2
  • Toutes les offres basées sur les produits ci-dessus

Le problème concerne uniquement les installations Unicode.

Le problème survient lors de l'ajout d'un nouvel élément à une liste dans un nœud global à l'aide de la syntaxe suivante :

SET $LIST(<global reference>, *+1) = value

Lorsque la liste résultant de cet appel dépasse la longueur de chaîne maximale, le comportement correct consiste à renvoyer une erreur <MAXSTRING>. C'est ce qui se produisait avant la version 2023.3 d'InterSystems IRIS, InterSystems IRIS for Health et Health Connect. Dans la version 2023.3 et les versions ultérieures, la valeur non valide est enregistrée dans la base de données au lieu de générer une erreur <MAXSTRING>.

Toute tentative ultérieure de référencement du nœud global génère une erreur <MAXSTRING>.

La mise à jour globale génère également un enregistrement de journal (en supposant que les mises à jour de ce nœud global soient normalement journalisées). Toute opération qui tente d'appliquer l'enregistrement de journal résultant, y compris la récupération au démarrage, la restauration du journal et les opérations de mise en miroir, échouera avec une erreur <MAXSTRING> et arrêtera le traitement ultérieur du fichier journal.

Si vous constatez les conséquences de ce défaut, contactez le Worldwide Response Center (WRC) pour obtenir de l'aide.

La correction de ce défaut est identifiée comme DP-437169. Elle sera incluse dans toutes les versions futures à partir d'InterSystems IRIS, InterSystems IRIS for Health et Health Connect 2024.1.3 et 2025.1.0. Elle est également disponible via une distribution ad hoc. La correction sera incluse dans HealthShare Unified Care Record version 2025.1 et dans la suite de produits dès leur sortie, mais ne sera pas incluse dans les versions de maintenance des versions précédentes. Si vous avez des questions concernant cette alerte, veuillez contacter le Worldwide Response Center.

讨论 (0)0
登录或注册以继续