The InterSystems Kubernetes Operation (IKO) version 3.3 is now available via the WRC download page and the InterSystems Container Registry.
IKO simplifies working with InterSystems IRIS or InterSystems IRIS for Health in Kubernetes by providing an easy-to-use irisCluster resource definition. See the documentation for a full list of features, including easy sharding, mirroring, and configuration of ECP.
IKO 3.3 Highlights:
Support for 2021.2 and 2022.1 editions of InterSystems IRIS & IRIS for Health
Support for Kuberentes 1.21
Deploy common System Alerting and Monitoring (SAM) configurations as part of your irisCluster
InterSystems API Manager (IAM) can now also be deployed and managed as part of the irisCluster
Automatic tagging of mirror pair active side, so a service can always point to the active mirror member.
i'm trying to extend both the MemberEnrollment and the MedicalClaim objects in HS. The CareProvider is perfect for some of my extensions (Operating provider, referring provider, third-party insurer), but the documentation says https://docs.intersystems.com/irisforhealthlatest/csp/docbook/DocBook.UI...
I need something that is just like a CareProvider, and I will be using the CarePRoviderType as a CodeTableDetail.
Why is CareProvider excluded? Does this mean I can't add property HS.Local.SDA3.MemberEnrollment.PHPProvider as HS.SDA3.CodeTableDetail.CareProvider?
What is a better solution? Yes, this is also going to go to HealthInsight, so I'll need an analogous table in HSAA.
Open Exchange
.png)