#GitHub

2 Followers · 83 Posts

GitHub is the largest web service for hosting IT projects and their joint development. This web service is based on the Git version-control system - a distributed version-control system for tracking changes in source code during software development.

Learn more.

Join the InterSystems Developer Community on GitHub.

New
Article Thomas Mazur · Jun 22 2m read

I am going to share some of the things I find very useful about VS Code, after many years developing in Studio.

The first and obvious thing to me is the fact that it does not crash in the middle of development when it disconnects from the network for any reason, forcing you to restart Studio and deal with the risk of losing valuable code. I also find VS Code a lot quicker than Studio, and the user interface far better with so many ways to customise it to your liking.

In France we use farm animal names for our dev and test environments.

5
1 109
New
Article Mainza Kangombe · Jun 12 6m read

1. The End of "Pay-and-Chase": A New Era of Payment Integrity

For decades, healthcare payers have been trapped in a reactive cycle known as "pay-and-chase." Traditional payment integrity relies on retrospective audits—reviewing claims months after disbursement to claw back overpayments. This inefficiency costs the industry billions in unrecovered fraud, waste, and abuse.

ClaimAuditAI introduces a fundamental paradigm shift by moving the audit to the point of submission.

1
0 29
New
Article Johannes Heikkonen · Jun 11 1m read

Hi everyone, 

I created a short demo and reference repository showing how to configure Auth0 as an OAuth provider for an InterSystems IRIS FHIR server, and how to call protected FHIR resources from a Python Flask application. 

The links below include a video walkthrough and a github repo with the sample application used in the video 

Links 

Video walkthrough

GitHub repository: https://github.com/MarshyKid/iris-fhir-oauth-demo

0
1 53
Question Hamras T · Jun 1

Hi all,

I'm working on a DICOM router in InterSystems IRIS, based on the workshop-iris-dicom-interop (https://github.com/intersystems-ib/workshop-iris-dicom-interop) example on GitHub. I'm using EnsLib.DICOM.Process to route incoming images to different PACS destinations, where the target system is decided at runtime via a database lookup.

I've run into two issues I'd love some guidance on:

1. Dynamically changing the destination without disrupting transactions

Right now, if I want to send to a new PACS target, I'd need to add a new Business Operation and call

1
0 46