How to handle a XML without Schema in a Business Rule?

Question

Question

Nicky Zhu · Nov 8

#InterSystems IRIS #InterSystems IRIS for Health

Hi guys,

Is it possible to apply business rule on a XML without Schema?

Say, I'm trying to make some business rules on FHIR XML payload. I transferred the XML stream as an EnsLib.EDI.XML.Document in a BPL and passed it to a General Business Rule.

 Set context.xmlDocument = ##Class(EnsLib.EDI.XML.Document).ImportFromLibraryStream(##class(HS.SDA3.QuickStream).%OpenId(request.QuickStreamId))

I'm handling following XML document

With this rule

Then I got stuck at visiting the elements in the XML.

I.e How may I evaluate the profile value？

Thanks。

Product version: IRIS 2024.1

Discussion (6)1

Log in or sign up to continue

score 0 · Answer 1 · 2024-11-08T04:19:57-05:00

It can be down by adding a custom function

Class MDMDemo.Utils.XMLDocumentUtils Extends Ens.Rule.FunctionSet

{

/// GetAt implementation for rulesets

ClassMethod ElementGetAt(ByRef pDocument As EnsLib.EDI.XML.Document, pPath As %String) As %String [ CodeMode = expression, Final ]

{

pDocument.GetValueAt(pPath)

}

But is there anyway to directly visit the elements in the rule?

score 0 · Answer 2 · 2024-11-08T06:46:36-05:00

Convert xml to FHIR object:

Set payload=##class(HS.FHIR.DTL.vR4.Model.Resource.Organization).FromXML(FHIRxmlStream)

score 0 · Answer 3 · 2024-11-08T08:42:19-05:00

Thanks Eduard.

It works in this case indeed. While there are still cases for some of our partners to work on XMLs without schema. Is there someway to do it?

score 0 · Answer 4 · 2024-11-08T09:37:08-05:00

Eduard Lebedyuk · Nov 8

Use VDocs!

0 0

score 0 · Answer 5 · 2024-11-10T03:09:51-05:00

Yes I'm using virtual document thus the xml was loaded as an EnsLib.EDI.XML.Document and saved into BPL context.

While the path about seems not working.

score 0 · Answer 6 · 2024-11-10T09:59:26-05:00

EnsLib.EDI.XML.Document implements Ens.VDoc.Interface, and exposes GetValueAt(propertyPath) method.

This method accepts XPath-like property paths such as "/foo/bar" or "/foo/bar/@attr".

This also means you can use the curly brace syntax in business rules (classes extending Ens.Rule.Definition).

For example, if the context class has a "xmlDocument" property, this expression

xmlDocument.{/foo/bar}

will be compiled into

xmlDocument.GetValueAt("/foo/bar")