I would say Yes in the sense that HL7 messages can be constructed entirely from scratch via code.

The main supporting method for this on EnsLib.HL7.Message the method "SetValueAt" can use to add and replace content for an HL7 message.
There are various ImportFrom methods (File, Stream, String) where a vanilla base message can be correlated to an HL7 Message.
The DocType is assigned by method PokeDocType, after which virtual property paths used by "SetValueAt" method will assign content in the right place as expected.
The DTL (Data Transform Language) documents can visually assist converting some other form of structured data into new HL7 messages. They are dynamic in that they can respond not just to a source reference message but leverage Lookup tables to control the content created for output HL7 messages. Then new configuration can be added to lookup tables and this extends the behavior of an existing DTL.

For some code example I have a UnitTest framework class that contains code demonstrating correlation of flat content to an HL7 message, setting the DocType and comparing virtual document paths. https://openexchange.intersystems.com/package/UnitTest-DTL-HL7

I think you hit the utility of the documented approach. To not accidentally delete the databases.

If you forgot to delete databases as part of namespace removal, they can be manually tidied up (System Administration->Configuration->System Configuration->Databases).

Questions I would also be asking when directed by Customer from a Vanilla "ENSEMBLE" name, to a purposeful named Namespace:

• Are IRIS.DAT(s) located in the correct disk volume / Drive name. ie: Sufficient capacity for expected use. (Is it supposed to be on the same volume / location as where services are installed).
• Is there a backup strategy. AND did I retest it yet?
• Are the databases journal enabled.
• Check Users don't still have "ENSEMBLE" as default namespace location
• Check Scheduled Tasks are not expecting "ENSEMBLE" namespace
• Update documented standard build script

One more thought. If you are using Unix / Linux for hosting IRIS, a more recent option is mergeCPF, to update both Namespace, Database and Application settings. Suitable for:

• migration activity as a testable automated script
• configuration and setup from vanilla docker images.

https://docs.intersystems.com/iris20231/csp/docbook/Doc.View.cls?KEY=AC…

This allows applying updates with a simple text file AND it does both traditional CPF settings AND the [csp web] Application settings in one go.

Your question encouraged me to share a little web calculator for CreateApplication settings.

So less time needed to figure out Application setting names and values.

https://openexchange.intersystems.com/package/MergeCPF-Application-Sett…

Am going to make some assumptions that you have been given an IRIS.DAT file and you want to mount that Database file on a new instance for some evaluation activity.

This is likely to not be exactly the situation but can serve as an example to help understand what you need to achieve.

A Namespace is a CODE and DATA context that database processes normally operate in.

To use the Database file it is "mounted" as a Database configuration.

The Database configuration is used by a Namespace, either as the DEFAULT for code and routines OR the data is MAPPED for use by a namespace.

As an example I create a copy of an empty database at: C:\InterSystems\somewhere\db\empty2
  This directory contains the IRIS.DAT.
In System Management Portal I can "Create a Database" (System Administration->Configuration->System Configuration->LocalDatabases)
  Use the path of new IRIS DAT file: "C:\InterSystems\somewhere\db\empty2"
  There will be a warning:  "Database file, IRIS.DAT, already exists in directory."

If you then navigate with System Explorer -> Globals

  And use "Lookin : Database" for the example is "EMPTY2"
  Here I added the Global Test

If the IRIS.DAT has both code (eg: SQL Table definitions) and Data, possibly you might want to create a new namespace and make the mounted database from earlier as the default database for routine and code for that namespace.
  So "Namespaces -> Create New Namespace

Alternatively, you may want to apply the new Data with code in another existing database for example SQL Table definitions. Here you could decide what data you want to map from the new database file to an existing namespace. (See: Explorer for Globals above)
  Navigate to Namespaces (System Administration->Configuration->System Configuration->Namespaces)
  Select "Global Mappings" of the namespace you want to "access data from the new Dat file".

Example to map the whole of global "Test" to existing namespace. Note this is will "hide" any data in "Test" that might exist in the default database of the pre-existing namespace.

Hint: Be sure to have database files unmounted or instance shut down when first learning to copy / swap database files around.

There are advanced ways of doing things. Occasionally you might get an IRIS database file from an operating system with a different Endian composition. The tool cvendian can help translate this to a target operating system endian mode. When moving big DAT files about it can be useful to run an SHA-1 or MD5 checksum hash on the database file before and after copying to ensure there is no corruption.

Hope this gave some ideas and helps progress the direction needed for your specific situation.

Bring up the VSCode command palate.
Choose: ObjectScript: Compile current file with specified flags.

Use flags: ckb

Where:
b=Compile Dependent Classes
c=Compile
k=keep generated source code
u=Skip related upto date classes

Hi Stella,

Thinking could this use the "List Of" syntax to achieve a collection for XML projection.

Service:

Class TEST.SOAPCOL.MyService Extends EnsLib.SOAP.Service
{ 
/// Name of the WebService.
Parameter SERVICENAME = "MyService"; /// TODO: change this to actual SOAP namespace.
/// SOAP Namespace for the WebService
Parameter NAMESPACE = "http://tempuri.org"; Property Target As Ens.DataType.ConfigName; Parameter SETTINGS = "Target:Basic";
Method SendToTarget(pRqst As TEST.SOAPCOL.Request) As TEST.SOAPCOL.Response [ SoapAction = "http://tempuri.org/Sample.MyService.SendToTarget", WebMethod ]
{
    set tResponse=##class(TEST.SOAPCOL.Response).%New()
    Set tSC= ..SendRequestAsync(..Target, pRqst)
    return tResponse
}
}

Request (Note "List Of" )

Class TEST.SOAPCOL.Request Extends Ens.Request
{
  Property MyContainer As list Of TEST.SOAPCOL.ListItem;
} 

Inner Items

Class TEST.SOAPCOL.ListItem Extends (%Persistent, %XML.Adaptor)
{
Property PropertyA As %String;
Property PropertyB As %String; 
}

Response:

Class TEST.SOAPCOL.Response Extends Ens.Response
{
}  

Projection seen in Message Trace:

<?xml version="1.0" ?>
<!-- type: TEST.SOAPCOL.Request  id: 1 -->
<Request>
  <MyContainer>
    <ListItem>
      <PropertyA>AAA
      </PropertyA>
      <PropertyB>BBB
      </PropertyB>
    </ListItem>
  </MyContainer>
</Request>

Trying out client code in terminal:

set o=##class(MyService.MyServiceSoap).%New()
set o.Location="http://localhost:1980/TEST.SOAPCOL.MyService.CLS"
set pRqst=##class(MyService.Request).%New()
set item=##class(MyService.ListItem).%New()
set item.PropertyA="AAA"
set item.PropertyB="BBB"
do pRqst.MyCOntainer.Insert(item)
set response=o.SendToTarget(pRqst)

Hi Pravin,

The following pattern could work for you. Override and add a callback with a single line edit. Then maintaining the custom logic in a supporting callback. Will need to track behavior changes for %JSONImport when upgrading.

Method OnJSONImport(%JSONObject As %Library.DynamicAbstractObject)
{
  set %JSONObject.Version=""_%JSONObject.Version
}

/// %JSONImport imports JSON or dynamic object input into this object.<br>
/// The input argument is either JSON as a string or stream, or a subclass of %DynamicAbstractObject.<br>
/// mappingName is the name of the mapping to use for the import. The base mapping is represented by "" and is the default.
Method %JSONImport(input, %mappingName As %String = "") As %Status [ ServerOnly = 1 ]
{
Try {
  Set sc=$$$OK
  New %JSONObject
  If $isobject(input),input.%IsA("%Library.DynamicAbstractObject") {
    // Already a dynamic object
    Set %JSONObject=input
  } Else {
    // A JSON stream or string
    Set %JSONObject=##class(%Library.DynamicAbstractObject).%FromJSON(input)
  }
   // Add callback
  Do ..OnJSONImport(%JSONObject)
  // Do the import now.
  Set sc=..%JSONImportInternal() } Catch ex {
  Set sc=ex.AsStatus()
  } Quit sc
}

Hi Thembelani,

This site requires access by HTTPS.

I created a TLS configuration in Management Portal with defaults called "Open".

Then the following works for download.

Set httpRequest = ##class(%Net.HttpRequest).%New() Set httpRequest.Server = "msedgedriver.azureedge.net"
set httpRequest.Port=443
Set httpRequest.ContentType = "application/octet-stream"
Set httpRequest.SSLConfiguration="Open"
set httpRequest.Https=1
Do httpRequest.Get("/113.0.1774.0/edgedriver_win64.zip")
Set fileName = "tryedgedriver_win64.zip"
Set fileStream = ##class(%Stream.FileBinary).%New()
Set fileStream.Filename = "C:\tmp\"_fileName
Do fileStream.CopyFrom(httpRequest.HttpResponse.Data)
Do fileStream.%Save()
Do fileStream.%Close()

Kind regards,

Alex