Find

Digest
· Aug 25

欢迎报名参加线上研讨会 | 以医疗AI枢纽构建智能协同生态：InterSystems IRIS AI 组件注册中心

#InterSystems IRIS

在医疗 AI 快速发展的今天，数据孤岛、标准不统一、部署效率低等问题日益凸显，如何打破壁垒、实现 AI 能力的高效整合与落地成为行业关键课题。

8月29日14:00，我们邀请InterSystems高级销售工程师 @Nicky Zhu （祝麟） 举办题为“以医疗 AI 枢纽构建智能协同生态”的线上研讨会，聚焦 “医疗 AI 枢纽” 建设，以 InterSystems IRIS 为核心，深度解析医疗 AI 面临的核心挑战 —— 从开放数据可用性、研究可及性到部署基础设施瓶颈，结合国际电信联盟（ITU）AI 就绪框架，剖析行业痛点。

👉点击报名

您将在此次分享中了解到：

  • 针对 AI 组件注册中心架构的系统介绍：依托多模型数据存储（ relational+object+K/V+doc+vector ）、FHIR 等行业标准协议，实现院内信息能力的一体化整合，通过能力支撑AI应用。
  • 门诊助手实战案例分享：直观展示如何通过 AI 组件注册中心实现执行规划 Agent、上下文感知 Agent 等工具的协同，降低资源整合成本、提升 AI 能力投放效率。
  • 展望医疗 AI 演进趋势：探讨从对话机器人到网络化应用的转型路径，以及 Agent、工具与流程编织的未来方向。

无论您是医疗信息化从业者、AI 技术开发者还是行业决策者，都能在本次研讨会中获取医疗 AI 落地的实战经验、技术架构设计思路与前沿趋势洞察，助力推动医疗 AI 生态的协同创新。我们期待与您的进一步互动。

1. 留言互动

在会议进行过程中，如果您有任何疑问，或者希望与我们进一步讨论，可以在屏幕上方点击“提问”按钮，提交您的问题，我们会在分享结束后整理问题，并通过邮件向您回复。

2. 有奖调研

参会期间，点击屏幕右上角“有奖调研”完成问卷，将有机会获得定制小礼品。

快来加入我们吧٩(๑>◡<๑)۶ 👉点击报名

Discussion
· Aug 25

Summer 2025 with Global Masters

#Global Masters

Summer is coming to an end, and we’re sure you had plenty of highlights! ✨

Maybe you learned something valuable, got yourself a reward on Global Masters, or even joined READY 2025 🎉

Here’s a quick checklist — but you can, of course, share anything else about your summer in the comments. Photos are more than welcome 📸

  • Went to the sea or a lake
  • Hiked/enjoyed nature
  • Traveled somewhere new
  • Attended a concert or festival
  • Watched a movie or series
  • Read a book
  • Earned points and redeemed a reward on Global Masters 🏆
  • Joined READY 2025 🎉
  • Spent time with family or friends

We hope your summer was amazing — can’t wait to see your stories, and photos, if you’d like to share — we start first! 🌟



P.S. Your comment will be awarded with 30 points on Global Masters automatically.

27 new Comments
Discussion (27)14
Log in or sign up to continue
Digest
· Aug 25

Publicações Desenvolvedores InterSystems, Agosto 18 - 24, 2025, Resumo

#Developer Community Official #Digest
Agosto 18 - 24, 2025Week at a GlanceInterSystems Developer Community
Announcement
· Aug 25

Developing with InterSystems Objects and SQL – In Person September 15-19, 2025 / Registration space available

#InterSystems IRIS #InterSystems IRIS for Health

Developing with InterSystems Objects and SQL – In Person September 15-19, 2025

  • This 5-day course teaches programmers how to use the tools and techniques within the InterSystems® development environment.
  • Students develop a database application using object-oriented design, building different types of IRIS classes.
    • They learn how to store and retrieve data using Objects or SQL, and decide which approach is best for different use cases.
    • They write code using ObjectScript, Python, and SQL, with most exercises offering the choice between ObjectScript and Python, and some exercises requiring a specific language.
  • This course is applicable for users of InterSystems IRIS® data platform and InterSystems Caché®
  • Self-Register Here
Discussion (0)1
Log in or sign up to continue
Question
· Aug 25

Catching WorkQueue Errors

#Caché #HealthShare

I'm trying to catch some WorkQueue errors that are happening on 2019 but not on more recent versions.

I'm getting an error when trying to call a class method via a workQueue. It functions properly in 2024.1. When calling the method, it immediately errors. I have logging at the top of the method that never gets set. 

The error being returned by Iris is simply an "ERROR #5039: An error occurred while calling function  s %sc=##class(|"NS"|Path.To.Class).ClassMethod(.%p1,.%p2)"

The parameter counts match and are appropriate for the method.

When I catch the full stack, it's erroring on the WorkQueue compiled routine, somewhere around startWork+233^%WorkQueueMgr. The error stack mentions a few lines, all in startWork. Looking at what, I think is, the associated inc file (occWorkQueue.inc), there's some mention of turning on logging by setting ^%SYS("WQM","EnableWorkLogging"). If that's true, it will set the error being passed in into the ^%ISCLOG global. However, even when I do set ^%SYS("WQM","EnableWorkLogging") to 1, and ^ISCLOG to 4 (or higher), I never see the logs I'd expect to. I know there are logs within the routine that set values and errors to $$$WorkSysLog at levels 2 and 3, so setting ^ISCLOG to 4 should catch those errors. 

How can I view the errors being thrown by the compiled routine? Does the value of "EnableWorkLogging" only matter at some stage I can't set? 

7 new Comments
Discussion (7)3
Log in or sign up to continue