SMAT FILE – 6.1.1.0 – Windows Server – Capture single message MetaData

[Varun Sinha]

I found an old link for which I am looking for any tcl script or a quicker way to generate different messages based on message type OR Medical Record Number OR Patient name

Capture single message MetaData

e.g. *.idx file contain offset of where each message starts and its length (as well as all the other metadata) and, say for example, 1000 of messages, of different message types under *.msg file.

Is there any tcl script or a quicker way to generate different messages based on message type OR Medical Record Number OR Patient name? I need to create these messages in bulk for almost 300 interfaces and I can’t take the GUI option.

I do see that it’s mentioned under forum or post that there is Charlie’s hcismat script in your $HCIROOT/contrib directory, but I am unable to find this script.

Can someone please help me either to find the above mentioned script location or to give me a tcl script to start off with.

 

Thanks & Regards,

Varun

 

 

 

 

 

Topic

[Jim Kosloskey]

If you search for hcismat it should be someplace in the Cloverleaf directory set. I have a command line proc which counts up the various Message/Event Type HL/7 messages in a set SMAT files.

That is not exactly what you want but it will show you how I navigated the .idx and .msg files and got the MSH-9 from messages. That might get you started. If you want that proc, email me an I will send it to you.

When I was faced with a similar challenge for something not to be run routinely, I had a Tcl proc which recursively located all of a specified glob pattern of SMAT files from potentially multiple directories and copied them to a single directory. Where there were collisions in the SMAT file names a 5 digit counter and an underscore was prepended to the file name to assure uniqueness.

I then had another Tcl Proc which would merge specified (via glob specification) SMAT file copies in the single directory to a single SMAT file. From there I could use hcismat to create a new-line terminated file of just the messages.

Then I used an HL/7 analysis tool (I think it was HL/7 Explorer but there are others) to extract matching messages based on field level matches.

The above methodology gave me the flexibility to change the scope of my analysis as needed and use whatever other tools I had once the data had been gathered and/or merged.

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Varun Sinha]

Thanks Jim!

I have sent you an email. Please send me the proc, so that I can start off with.

 

Regards,

Varun

[Charlie Bursell]

Let me know if you need hcismat or hcismatdb I can send to you

cbursell@fastem.com

[Rob Abbott]

Feel free to post tcl procs as attachments!

Rob Abbott
Cloverleaf Emeritus

[Charlie Bursell]

hcismat and hcismatdb have been posted a few times already

[Author]

Replies