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.

Hi Craig,

ImportFromString returns an HL7 Message, it does not populate an existing instance of EnsLib.HL7.Message.

Moreover, make sure that you are reading the entire message with %request.Content.Read, you'll probably want to wrap that in a loop.

Here is the code I get to work on my instance (2017.1)
 

Hi Dan, Can you please update the following to make this tutorial up-to-date?

• The endpoints in the Google1N and Google2n depend on your server and ssl port. Maybe make a note there that .../csp/google/Web.OAUTH2.... would be /csp/user/Web or /csp/namespaceABC/Web.Oauth2 depending on where you implement the code.
• The issuing endpoints for the tutorial have changed to the following: https://accounts.google.com/.well-known/openid-configuration

You could use a linked database (remote db projected as local tables) and then write an insert query to that linked table before it gets sent to a production.

As far as I know, they should be included in the output. If you want to force it you can add a property parameter on the relationship. https://docs.intersystems.com/irisforhealth20221/csp/docbook/DocBook.UI…

// Relationship to be includeed in JSONExport using JSON adaptor
Relationship Ingredients as Food.Item(%JSONINCLUDE = "inout", %JSONREFERENCE = "object") [ Cardinality = one, Inverse = Recipe ];

6 years ago I designed such a system at Boston College:

• Web Application Demo
• Source Model and Ingestion Code

This python code can easily be adapted for irispython. My suggestion, use a computer with modern graphics cards, and potentially outsource this ML work to one of the many AI companies that offer emotion detection these days.

If you investigate and find you need to do a global get, try using the %Net.DB package.

Here is another community link that should that in action.

https://community.intersystems.com/post/netdbconnection

I think what you'll need is a write stream method below (I haven't had a chance to test this so the code comes with no guarantees). This will work for Non-Shared web-socket connections since I don't have the chance to test with shared pools at the moment.

Method Send(message As%Library.DynamicObject) As%Integer
{
    Set stream = ##class(%Stream.TmpCharacter).%New()
    Do message.Msg.%ToJSON(stream)
    Set sc = ..WriteStream(stream)
    If$$$ISERR(sc) $$$SysLog(2,"WebSocket","[Write] Error WRITE Stream on JSON Command",sc)
    quit1
}

Method WriteStream(data As%Stream.Object) As%Status
{
	Set$ZTrap="WriteError"If i%WSClassProtocolVersion > 1 & i%WSDataFraming = 1 {
		Set head=$ZLChar(data.Size)
		If i%BinaryData = 1 {
			Set head=head_"8"
		} Else {
			Set head=head_"7"
		}
	} Else {
		Set head=""
	}
	#; As there is activity on this session reset the session timeoutSet sc=$$updateTimeout^%SYS.cspServer(i%SessionId) If$$$ISERR(sc) $$$SysLog(2,"WebSocket","[Write] Error updating session timeout",sc)
	#; Only return an error status if there's an issue with the write itself.Set sc=$$$OKIf (i%SharedConnection = 1) {
        // If you want to try and play with the shared pools and large payloads, move the commented code to the loop below

		#; Set sc=$$CSPGWClientRequest^%SYS.cspServer3(i%GWClientAddress,"WSW "_i%WebSocketID_" "_head_data1,-5,.response)
		#; If $$$ISERR(sc) $$$SysLog(2,"WebSocket","[Write] Error sending request",sc)$$$SysLog(2,"WebSocket","[Write] Shared Connections Don't Support Stream Sizes over 3.6MB",sc)
        Quit$$$Error($$$GeneralError, "[Write] Shared Connections Don't Support Stream Sizes over 3.6MB")
	} else {
        SET sc = $$$OK// Write headerWrite head
        // Rewind StreamDo data.Rewind()
        // Loop through stream and write 64kb chunkswhile (data.AtEnd = 0) {
            // Set Buffer to 64KBSet BUFSZ = 65536// Read BufferSET BUFBLOCK = data.Read(.BUFSZ)
            // Convert UTF8 if we aren't using Binary Web SocketsIf i%BinaryData '= 1 {
                Try {
                    Set BUFBLOCK=$zconvert(BUFBLOCK,"O","UTF8")
                } Catch exp {
                    $$$SysLog(2, "WebSocket", "[Write] Exception: "_exp.DisplayString(), data)
                    Set BUFBLOCK=BUFBLOCK
                }
            }
            // Use DEVICE WRITE methodWrite BUFBLOCK
            // Quit when done with streamBREAK:(BUFSZ < 65536)
        }
        // Send a flush command mnowWrite *-3Quit sc
	}
	Quit sc
WriteError	
	#; No interrupts during cleanup or error processingDo event^%SYS.cspServer2("WebSocket Write Error: "_$ZError)
	$$$SetExternalInterrupts(0)
	Set$ZTrap="WriteHalt"Hang5Close0
WriteHalt 
	Halt
    
}

Great release! @Dmitry Maslennikov

For deployed code, does this prevent source (src or module.xml) from being stored on the disk as well?

Currently, product development is working on containerization and kubernetes support for healthshare. It might be worth waiting until it is officially supported.

Will this change the commands from zpm to ipm?

Please ensure that any dark version uses our white logo as the default color is invisible in dark mode.