Nova postagem

検索

Artigo
· Maio 21 1min de leitura

CCR Client Tools UI Upgrade

#CCR #Outro

We're excited to announce the first-ever UI update for CCR Client Tools. The Client Tools UI has been upgraded to match the modern CCR UI, aiming to create a more seamless experience across both applications. The color scheme, fonts, and style elements have all been updated accordingly in the new UI:

All functionality has been preserved through the update, and the new changes are fully compatible with all major browsers, VSCode, and the legacy Studio IDE. For the best experience we recommend using VSCode or any modern browser, but Studio is still supported and will also reflect the new UI changes:

There are no functional changes to the application in this UI update, so users will be able to continue using Client Tools as usual with the added benefit of a more seamless CCR-Client Tools experience. Please let us know of any issues or questions about the new UI, user feedback is welcome! 

1 Comment
Discussão (1)2
Entre ou crie uma conta para continuar
Anúncio
· Maio 21

[Video] Streamlining Electronic Prior Authorizations with FHIR

#FHIR #Vídeo #InterSystems IRIS for Health

Hey Community!

We're happy to share the next video in the "Code to Care" series on our InterSystems Developers YouTube:

⏯  Streamlining Electronic Prior Authorizations with FHIR

In this episode of the Code to Care video series, explore how FHIR-based technology is transforming the cumbersome prior authorization process in healthcare. Learn how their innovative SMART on FHIR app streamlines payer-provider communication, reduces administrative burden, and ultimately improves the patient experience. Discover how the collaboration leverages InterSystems technology to simplify and standardize this critical interaction, helping providers navigate complex payer requirements in real-time - all from within their EHR.

Presenters:
🗣 @Don Woodlock, Head of Global Healthcare Solutions, InterSystems
🗣 Jay Nakashima, President, eHealth Exchange, Board Member

Enjoy watching, and subscribe for more videos! 👍

Discussão (0)1
Entre ou crie uma conta para continuar
Artigo
· Maio 21 2min de leitura
Open Exchange

ISCLauncher - Get immediate access to InterSystems knowledge and support records!

#Outro

For 15 over years I have been playing with ways to speed up the way I use InterSystems systems and technology via AutoHotkey scripting.  As a power keyboard user (I avoid my mouse when possible) I found it very helpful to set up hotkeys to get to my most frequently accessed systems and research utilities as quickly as possible.  While I have used this approach for many years, this is the first time that I am introducing my approach and a customer-facing hotkey script to the D.C. and OEx...

ISCLauncher is a hotkey program based on AutoHotKey (Windows scripting language) which provides quick access a number of useful InterSystems resources and online systems (Windows OS only). Use it to quickly access the following InterSystems resources:

To try it out for yourself, use the "Download' button on the ISCLauncher Open Exchange listing, which will pull down a Zip file from which you can extract the contents.  Run the ISCLauncher.exe and you will see the following in your Windows SysTray:

To pull up the Help screen so you can see all of the things that it can do, once you are running ISCLauncher, press [Ctrl]+[Windows]+[?]:

 

The power of ISCLauncher is that it can turn plain text into a hyperlink.  E.g. If you have an ID from a WRC, iService or CCR record in an email, chat or notes, simply highlighting the record ID and using the appropriate hotkey will allow you to just directly to that record.  See a demo for a CCR lookup below ([Ctrl]+[Windows]+[c]):

To access a record even faster, use ISC Uber-Key ( [Ctrl]+[Windows]+[Space] ) to try to automatically determine the record type and navigate immediately there (credit to @Chad Severtson for the original ISC Uber-Key code from years ago!).

In addition to WRC, iService and CCR records - do quick searches against things like InterSystems Documentation ([Ctrl]+[Windows]+[b]
) or the Developer Community ([Ctrl]+[Windows]+[d]):

Make this tool even more powerful by adding your own hotkeys for things that you frequently type or open on your desktop.  For some inspiration, here is my personal launcher which I have tuned over the years:

Have ideas how to make this more powerful?  Add comments below.  Also, once this is in GitHub you can feel free to create PRs with your suggestions.  

1 Comment
Discussão (1)2
Entre ou crie uma conta para continuar
InterSystems Oficial
· Maio 21

InterSystems Platforms Update Q2-2025

#InterSystems IRIS #InterSystems IRIS for Health #InterSystems Oficial

We have a big update this quarter. 

  • RHEL 10 was released yesterday, read on for what that means for you
  • 2025.3 will use OpenSSL 3 across all operating systems SUSE 15 sp6 will be the minimum OS for orgs using SUSE
  • The minimum CPU standards are going up in 2025.3
  • Older Windows Server operating systems will no longer be supported in 2025.3

If you’re new to these updates, welcome!  This update aims to share recent changes as well as our best current knowledge on upcoming changes, but predicting the future is tricky business and this shouldn’t be considered a committed roadmap. 

InterSystems IRIS Production Operating Systems and CPU Architectures

Minimum Supported CPU Architecture

In 2024, InterSystems introduced a minimum supported CPU architecture for all Intel- & AMD-based servers that allows us to take advantage of new CPU instructions to create faster versions of InterSystems IRIS.  InterSystems IRIS 2025.3 will update that list to require the x86-64-v3 microarchitecture level, which requires the AVX, AVX2, BMI, and BMI2 instructions.

  • For users with Intel-based systems, this means that Skylake and up will be required while Hasell/Broadwell will not be supported.
  • For users with AMD-based systems, this means that Excavator and up will be required while Piledriver & Steamroller will not be supported.

Are you wondering if your CPU will still be supported?  We published a handy article on how to look up your CPU’s microarchitecture in 2023.

 

Red Hat Enterprise Linux

  • Upcoming Changes
    • RHEL 10 - Red Hat released RHEL 10 on May 20th.  We’ve been testing on the latest beta of RHEL 10 on InterSystems IRIS 2025.1.
      • InterSystems IRIS 2025.1 support – We anticipate officially adding support for RHEL 10 in about a month.  That’s assuming the GA version of RHEL 10 doesn’t introduce any significant problems, of course.
      • Moving forward – once we have support for RHEL 10 in InterSystems IRIS, we will stop supporting RHEL 8 on moving forward versions of InterSystems IRIS.  This likely means that InterSystems IRIS 2025.2 will just support RHEL 9 & 10.
  • Previous Updates
    • RHEL 9.5 has undergone minor OS certification without incident.
  • Further reading: RHEL Release Page

Ubuntu

  • Current Update
    • Ubuntu 24.04.2 has just been released and minor OS certification has begun.
  • Further Reading: Ubuntu Releases Page

SUSE Linux

  • Upcoming Changes
    • InterSystems IRIS 2025.3+ will require SUSE Linux Enterprise Server 15 SP6 or greater – SLES 15 sp6 has given us the option to use OpenSSL 3 and, to provide you with the most secure platform possible, we’re going to change InterSystems IRIS to start taking advantage of it.
    • In preparation for moving to OpenSSL 3 in IRIS 2025.3, there will be no IRIS 2025.2 for SUSE.

Further Reading: SUSE lifecycle

Oracle Linux

  • Upcoming Changes
    • We’re expecting Oracle Linux 10 to be released around the same time as RHEL 10.  Since we support Oracle Linux via the IRIS RHEL kit, we’re expecting Oracle Linux 10 support at the same time as RHEL 10 support is released.
  • Further Reading: Oracle Linux Support Policy

Microsoft Windows

  • Recent Changes
    • Windows Server 2025 is now supported in InterSystems IRIS 2025.1 and up.
  • Upcoming Changes
    • InterSystems IRIS 2025.3+ will no longer support Windows Server 2016 & 2019.
    • Microsoft has pushed back the anticipated release date for Windows 12 to the fall of 2025.  We’ll start the process of supporting the new OS after it’s been released.
  • Further Reading: Microsoft Lifecycle

AIX

  • Upcoming Changes
    • IBM is rolling out new Power 11 hardware this summer.  We anticipate running the new hardware through the paces over the course of the late summer and early fall.  Look for a full update on our findings in the Q4 newsletter.
  • Previous Changes
    • IRIS 2024.3 and up only support OpenSSL 3. NOTE:  This means that 2024.2 is the last version of IRIS that has both OpenSSL 1 and OpenSSL 3 kits.  In IRIS 2023.3, 2024.1, & 2024.2, we provided two separate IRIS kits – one that supports OpenSSL 1 and one that supports OpenSSL 3.  Given the importance of OpenSSL 3 for overall system security, we’ve heard from many of you that you’ve already moved to OpenSSL 3.
  • Further Reading: AIX Lifecycle

Containers

  • Previous Updates
    • We changed the container base image from Ubuntu 22.04 to Ubuntu 24.04 with IRIS 2024.2
    • We’re considering changes to the default IRIS container to, by default, have internal traffic (ECP, Mirroring, etc) on a different port from potentially externally facing traffic (ODBC, JDBC, etc).  If you have needs in this area, please reach out and let me know.

 

InterSystems IRIS Development Operating Systems and CPU Architectures

MacOS

  • Recent Changes
    • IRIS 2025.1 adds support for MacOS 15 on both ARM- and Intel-based systems.

InterSystems Components

  • Upcoming Releases
    • InterSystems API Manager 3.10 will be released soon.
    • InterSystems Kubernetes Operator 3.8 will be released in the coming weeks as well.

Caché & Ensemble Production Operating Systems and CPU Architectures

  • Previous Updates
    • A reminder that the final Caché & Ensemble maintenance releases are scheduled for Q1-2027, which is coming up sooner than you think.  See  Jeff’s excellent community article for more info.

InterSystems Supported Platforms Documentation

The InterSystems Supported Platforms documentation is the definitive source information on supported technologies.

 

… and that’s all folks.  Again, if there’s something more that you’d like to know about, please let us know.

3 Comments
Discussão (3)2
Entre ou crie uma conta para continuar
Artigo
· Maio 21 2min de leitura

Usando %System.Monitor.LineByLine com %SYS.MONLBL para analisar seu código

#InterSystems IRIS

Tenho certeza de que a maioria de vocês está familiarizada com a utilidade %SYS.MONLBL, que é crucial ao analisar gargalos de desempenho de código. Ela permite que você selecione várias rotinas que deseja monitorar em tempo de execução e também especifique qual(is) processo(s) você quer observar. MAS, e se você não souber exatamente qual processo executaria seu código? Isso é verdade para muitos aplicativos baseados na web (CSP/REST) hoje. Você quer minimizar a utilização de recursos em seu sistema de produção que precisa de análise. Então, que tal fazer uma pequena alteração?

1. Defina um arquivo INC com estas macros:

#define START(%level) try { ##continue 
s zzroutine=$p($view(-1,-3),"^",6) ##continue 
if ##class(%Monitor.System.LineByLine).IsActive(zzroutine)=0 { ##continue $$$ThrowOnError(##class(%Monitor.System.LineByLine).Start($lfs(zzroutine),$lfs(##class(%Monitor.System.LineByLine).GetMetrics(%level)),$lb($job))) ##continue } ##continue 
h 1 ##continue 
} catch (e) { ##continue
 d BACK^%ETN ##continue 
} 

#define PAUSE s sc=##class(%Monitor.System.LineByLine).Pause()

Na sua classe ou rotina, identifique um local que você deseja monitorar e insira estas duas macros para iniciar a coleta de dados e pausar a coleta, como neste exemplo:

$$$START(2)   // use 1 or 2 here

// code of your application here

$$$PAUSE

Sempre que você executar este código (método de uma classe ou rotina), ele tentará iniciar o %SYS.MONLBL para essa classe ou rotina e processo específicos.

Uma vez que seu código tenha terminado, você pode simplesmente ir ao terminal no namespace onde sua aplicação é executada e chamar d ^%SYS.MONLBL. Como a macro START iniciou o monitor, ele ainda estará em execução e você poderá facilmente coletar seus dados de desempenho, opcionalmente junto com o código-fonte. Não se esqueça de parar o monitor depois de coletar seus dados!

Se você precisar coletar dados para mais rotinas, pode facilmente modificar a macro START para permitir a entrada manual de uma lista de rotinas para análise.

Espero que você ache esta pequena alteração útil!

Discussão (0)1
Entre ou crie uma conta para continuar