Nice, the support of ZPM in the json config file is a major improvement.

Now we can use this module as a total replacement of the manifest installer !

Great work !

I tried your module as a replacement for the Manifest installer, see this example:

https://github.com/grongierisc/intersystems-iris-dev-template

However, I'm stuck for the part with ZPM.
The problem is, with your module, I can create a database, its rights, etc., but how to tell ZPM to load the classes in the freshly installed NameSpace?

What are the possible solutions?

• Add an option to your module to load code ?
• Add an option to ZPM to take into account your configurations ?
• What to do with the CPF module?
  • https://docs.intersystems.com/irisforhealthlatest/csp/docbook/DocBook.U…

We have today many options to load configuration IRIS, are they in competition?

How to federate these modules who are all complementary?

What a nice feature.

If I understand correctly, this module can be considered as a replacement for the Manifest installer?

If so, then this module has the benefit of exposing the configuration as JSON and API rather than a compiled class.

Hi Yeung,

First how-to auto increment an integer, you can use this property :

• %Library.AutoIncrement
•  Doc : https://docs.intersystems.com/irisforhealthlatest/csp/docbook/Doc.View…

Then, why you have ID1 in your table, because by default any persistent class have an column called ID who is an auto increment and indexed as a primary key.
You can overload this primary key by your own with this index :

• Index name On property_expression_list [ PrimaryKey ];
• Doc : https://docs.intersystems.com/irisforhealthlatest/csp/docbook/Doc.View…

If you have license key for heathshare (no community version of healthshare is available), the installers and familiar with docker, check this git :

https://github.com/grongierisc/healthshare-docker

It's an unofficial version of HealthShare on docker, very useful to do test and build edge on the fly.

Great app, I'll will definitely take a look, this can be very useful.

Thanks, and good luck for the contest.

Hi Mike, To retrive multi-part from %resquest you have do to this in the %CSP.REST class :

    // Get properties
    set body = %request.Get("body")
    if '$d(body) {
      $$$ThrowOnError($$$ERROR(9200,"no parameters"))
    }
    set dynaBody = {}.%FromJSON(body)

    // Get stream
    set stream = %request.GetMimeData("file")
    if ('$IsObject(stream) {
      $$$ThrowOnError($$$ERROR(9200,"no file"))
    }

To get property you have to use Get and for stream GetMimeData In my example my body is a json.

Hi Yuri, Have a look at this : https://github.com/grongierisc/iris-csvgen-ui/blob/master/src/CSVGEN/API/Dispatch.cls Here you will find and example of a multi-part upload on a %CSP.REST class.

To get the stream from the multi part you have to do this ligne 39 to 43 :

    // Get stream
    set stream = %request.GetMimeData("id")
    if ('$IsObject(stream) {
      $$$ThrowOnError($$$ERROR(9200,"no file"))
    }

Where id is the name of you multi-part

To send the stream to a business service :

        $$$ThrowOnError(##class(Ens.Director).CreateBusinessService(BsName,.tService))
        
        $$$ThrowOnError(tService.ProcessInput(stream,.output))

Where BsName is the name of your business service in the active production of your namespace. And stream you stream.

What a great idea :)

Here is my contribution :

{
	"Request Class": {
		"prefix": "ClassRequest",
		"body": [
			"Class ${0:ClassName} Extends Ens.Request",
			"{",
			"\t$1",
			"}"
		],
		"description": "Message helper"
	},

	"Response Class": {
		"prefix": "ClassResponse",
		"body": [
			"Class ${0:ClassName} Extends Ens.Response",
			"{",
			"\t$1",
			"}"
		],
		"description": "Message helper"
	},

	"Operation Class": {
		"prefix": "ClassOperation",
		"body": [
			"Class ${0:ClassName}  Extends Ens.BusinessOperation",
			"{",
			"\tParameter ADAPTER = \"${1:Adapter}\";",
			"\tProperty Adapter As ${1:Adapter};",
			"\tParameter INVOCATION = \"Queue\";",
			"\n",
			"Method ${2:Methode}(pRequest As ${3:Request}, Output pResponse As ${4:Response}) As %Status",
			"{",
			"\tset tStatus = $$$$OK",
			"\tset pResponse = ##class(${4:Response}).%New()",
			"",
			"\ttry{",
			"\t\t\n",
			"\t}",
			"\tcatch exp",
			"\t{",
			"\t\tset tStatus = exp.AsStatus()",
			"\t}",
			"\tQuit tStatus",
			"}",
			"XData MessageMap",
			"{",
			"<MapItems>",
			"\t<MapItem MessageType=\"${3:Request}\">",
			"\t\t<Method>${2:Methode}</Method>",
			"\t</MapItem>",
			"</MapItems>",
			"}",
			"}",
		],
		"description": "Operation helper"
	},

	"Service Class": {
		"prefix": "ClassService",
		"body": [
			"Class ${0:ClassName} Extends Ens.BusinessService",
			"{",
			"Parameter ADAPTER = \"${1:Adapter}\";",
			"Property TargetConfigNames As %String(MAXLEN = 1000) [ InitialExpression = \"${2:BusinessProcess}\" ];",
			"Parameter SETTINGS = \"TargetConfigNames:Basic:selector?multiSelect=1&context={Ens.ContextSearch/ProductionItems?targets=1&productionName=@productionId}\";",
			"Method OnProcessInput(pDocIn As %RegisteredObject, Output pDocOut As %RegisteredObject) As %Status",
			"{",
			"\tset status = $$$$OK",
			"",
			"\ttry {",
			"",
			"\t\tfor iTarget=1:1:$L(..TargetConfigNames, \",\") {",
			"\t\t\tset tOneTarget=$ZStrip($P(..TargetConfigNames,\",\",iTarget),\"<>W\")  Continue:\"\"=tOneTarget",
			"\t\t\t$$$$ThrowOnError(..SendRequestSync(tOneTarget,pDocIn,.pDocOut))",
			"\t\t}",
			"\t} catch ex {",
			"\t\tset status = ex.AsStatus()",
			"\t}",
			"",
			"\tQuit status",
			"}",
			"",
			"}",
		],
		"description": "Operation helper"
	},
}

Are you looking for thoses classes :

HS.Hub.Standalone.HL7.DTL.SubTransform.PD1ToSDA3

HS.Hub.Standalone.HL7.DTL.SubTransform.PIDToSDA3

and co ?

And you can have a look at this code to convert any HL7 and all his segment into SDA :

https://github.com/grongierisc/FHIR-HL7v2-SQL-Demo/blob/master/src/FHIR…

I agree with you in most cases.

The most important announcement for me would be Embedded Python.
This will bring to the community the power of python libraries, it's a giant step forward.