Closed

Hi Community,

Click play and immerse yourself in our new video on InterSystems Developers YouTube:

HealthShare Health Connect - Upgrade Automation with Production Validator @ Global Summit 2023

https://www.youtube.com/embed/61Nduu5UyS0
[This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]

3 0
0 65

Hey everyone,

I'm currently running into a very weird issue to where I am trying to connect with a 64 bit version of SQL Server Management Studio (SSMS) to a HealthShare instance. I have created a System DSN using the Drivers (image below) that were downloaded with the Client version of the install and I'm able to successfully connect using my credentials.

0 2
0 53

InterSystems has encountered a defect that causes some upgrades of HealthShare® Health Connect to fail. This only affects instances that are not licensed for the use of FHIR® and that have interoperability-enabled namespaces. Under these conditions, the upgrade fails with an <HSFHIRErr> error.

0 0
0 49

Hi

Some of our integrations use a system DSN to interact with our Data Warehouse (built on Microsoft SQL Server). We've recently migrated from SQL Server 2016 to 2022 and on the day of go-live we changed DNS cname records as a mechanism for redirecting everything to the new server. This worked great for users and reports, but for some reason we found that HealthShare clung onto the old server name even after several days.

1 1
0 46