One of the public properties of your CHS_Message object is the ConfigFileName property. When you create your script you can set this property to any type of file you wish (IE txt, xml, dat, json, etc). The idea here is that IF your script needs some additional information at runtime you can simply create a configuration file which contains that information, have your script read it at runtime, and act on the contents.

 

EXAMPLE SCENARIO 1: You have a CORE HL7 C# Script which works on HL7 messages being passed into it (IE either a Type 1 or Type 3 script). What you want is for your script to distribute each message to <xx> different folders. You could create a text file named OutFolders.txt and all it needs to do is have folder names in it like so:

 

C:\HL7\Folder1\

C:\HL7\Folder2\

C:\HL7\Folder3\

C:\HL7\Folder3\Others\

 

When executed your script reads the lines in OutFolders.txt and writes each message as it comes in out to each folder. Voila. Since the file is read on every message you can even edit the file while your Script Engine (or other script hosting application like the CORE HL7 Listener) is running and add or remove folders.

 

 

EXAMPLE SCENARIO 2: You have a Type 2 CORE HL7 C# Script which runs continuously or on a schedule and your script needs to examine certain folders looking for certain files or conditions. You could create the same type of txt file described in EXAMPLE 1.

 

The applications here are only limited by your imagination. These files can contain ANY type of data which your script can effectively read like XML files (use the COREScriptXML object) or JSON files, etc.

 

Best Practices: If your script uses a config file you should make sure that you describe it in the Notes section of your CORE HL7 Script in your Script Library.