To use FHIR in HealthConnect you will probably want to start with the installer kits. Each of these will add some bits and pieces of functionality to your current working production:
For example, to install a foundation namespace and add FHIR STU3 support to it:
SET nNamespace = "FHIR"
// Switch to the HSLIB so we can call our installer methods
ZN "HSLIB"
// Make the new namespace
SET sc = ##class(HS.HC.Util.Installer).InstallFoundation(nNamespace)
THROW:$$$ISERR(sc) ##class(%Exception.StatusException).CreateFromStatus(sc)
// Add in all of the FHIR components and create a web app
SET sc = ##class(HS.HC.Util.Installer.Kit.FHIR.HealthConnect).Add( , nNamespace, "STU3", "/csp/healthshare/" _ nNamespace _ "/fhir/stu3", "/csp/healthshare/" _ nNamespace _ "/fhir-oidc/stu3")
THROW:$$$ISERR(sc) ##class(%Exception.StatusException).CreateFromStatus(sc)Once you have this installed, you can use a custom business process to coordinate all of the downstream calls to the external systems. For example, your production might request downstream resources and construct a FHIR response bundle from them.
- Log in to post comments