MDM fun

This topic has 1 reply, 2 voices, and was last updated 18 years, 9 months ago by Roger Moss.

Creator

Topic
April 19, 2006 at 8:13 pm #48480
Danny Mack
Participant
running v5.4 on AIX v5.2

I’m trying to translate an MDM with RTF in OBX;5. Problem is that there is no encoding on that text. Dictaphone says the transcriptionists work in word and it’s simply converted and sent either ASCII or RTF.

Anyone know of a way to get that text formatted so it runs through the translate without the unknown segment stuff? I’m getting a boatload of those, and of course the output is all fubar’d.

[0:TEST] [mid:0x30000050] unknown segment ‘

{‘ — ignored.

[0:TEST] [mid:0x30000050] unknown segment ‘

{‘ — ignored.
Creator

Topic

Viewing 0 reply threads

Author

Replies
- April 21, 2006 at 1:26 pm #58744
  Roger Moss
  Participant
  I did this same interface last year and remember a few of the odd things about it:
  
  – Dictaphone does not send an EVN segment on the transaction and it is required by HL7, so I had to make it optional on a variant.
  
  – The rtf content in OBX 5 can and will exceed the default size, so I increased the size on my variant to 100,000 and had Dictaphone set a limit on their size to below that, which they can do. Also the field can repeat which is no big deal except that my receiving system could not handle that so in my translate I just keep appending it to a tmp variable with a CONCAT statement and then copy it after I fall out of the interation.
  
  – And the last thing is that the Dictaphone side has a MAX message size that it can send on a message, so very large documents will get split across messages and I had to put a tcl proc on the TPS Inbound of the thread to write them out to disk and then put it all back together on a single message to the engine when the last one arrived.
  
  Roger 8)
Author

Replies

Viewing 0 reply threads

The forum ‘Cloverleaf’ is closed to new topics and replies.