@Sean Brady - welcome to the D.C.!  Great question and you should get a lot of help here.

First, definitely watch the video linked by @Oliver Wilms in the earlier response.  It will help you understand how the InterSystems-based healthcare platforms tend to work best with the embedded source control paradigm due to how changes are made in the Management Portal and not just in VS Code.  

As you try to get Git set up, can you please confirm that you using the Embedded Git package?  https://community.intersystems.com/tags/embedded-git

You said you are having issues working with Git - could you please provide more details?

If you haven't, you should review the Branching Strategy doc on GitHub for Embedded Git (https://github.com/intersystems/git-source-control/blob/main/docs/hcc.md#general).  While it is in the HealthConnect Cloud section, @Pravin Barton has assured me it is generally applicable.

While you are working towards getting a proper Git-based progression in place, you can use Deployment Manager in the Portal (but you should stop using this once you have Embedded Git working).  This is the easiest way to grab things in bulk and move them between environments.  

Please note that HealthShare Registries are not yet covered by Source Control / Change Control hooks, so you will need to move those by hand or via custom scripting.  Those will come later this year - see the Global Summit presentation on the topic here: https://www.intersystems.com/change-control-for-healthshare-intersystems/

Hopefully this is enough to get you rolling.  Let us know what questions you may have!
 

I was talking to someone about the VS Code Workspace enhancement and I don't have a local instance to check.  Can anyone provide a screenshot or more detail on where to find this new feature? (I didn't notice it in the GitHub release notes either)

this is very helpful video ;)

Thanks for the callout!  @Sean Brady - welcome to the D.C.!  This would be the right place for you to start.  

I believe the API were first included in 2016.2 but there were issues so 2017.1 or later is recommended.

To connect to 2016.1, your only option is to use InterSystems Studio.  If you don't have access, reach out to a support who can supply you with a kit.

FYI .... This material was presented at Global Summit, and the recording can be found (for now) here:

https://www.intersystems.com/creating-an-intersystems-iris-cross-functio...

I assume that eventually it will be moved to the InterSystems YouTube channel as well.

very creative!!

@Oliver(Take2IT).Wilms - current versions of IRIS do not include IPM out of the gate.  You can side load it very easily - see https://community.intersystems.com/post/install-zpm-one-line.

At some point in the future, IRIS should include IPM.  

Really glad you found this to be helpful!!

@Laurel James (GJS)  - my pleasure.  Glad you enjoyed the presentation :)

Bravo to those who participated and especially to those who completed!!

This is a *really* useful utility and I want to make sure people have this on their radar.  @Matthew Giesmann / @Evan Gabhart - this is the work I want to make available to our customers who are moving to using CCR Tier 1 for their integration instances.  
 

Congratulations everyone on the great set of content created by this community in the past 3 months!  Happy New Year everyone!

thanks all for a great year!  Here's to great things in 2025 :)

very well deserved - congratulations @Alberto Fuentes and thank yoi for everything that you contribute to the Developer Community and to InterSystems!!!

Congratulations to the winners and thank you to everyone who participated! It is great to see such creative solutions being made available in the Open Exchange:-)

this is great, thank you for taking the time to share!

@Subtropical.Bob  - I suggest you reach out the InterSystems Support and they can help you sort this out.