Notifications
Clear all
Topic starter
We are changing our transcription vendor and creating a new Noteslink interface. Our vendor is having issues creating Rich Text Format (RTF) hl7 files that will successfully go into Centricity.
I sent them the documentation of the words macro, NLinkHL7.dot and Noteslink.ini - but it was not any help to them using their existing interface engine.
Has anyone had any luck recently with creating this interface successfully with RTF?
Thanks in advance!
Posted : January 17, 2017 6:42 am
IIRC, the inbound document interface (MDM) follows fairly limited RTF standard control codes. Microsoft Word is known to mangle RTF. Unfortunately I don't have any interfaces where I am manipulating RTF.
The nlinkhl7.dot MS Word template appears to be intended for transcription activities. It won't do much good unless they are using MS Word to create documents and HL7 files. That isn't very likely. They might be able to learn how to implement RTF for CPS from the MS Word template however.
noteslink.ini appears to be CPS configuration file that allows you to define certain values for the HL7 MDM message generated with the nlinkhl7.dot MS Word template. That also doesn't look all that helpful.
I don't believe it would be all that difficult to manipulate the RTF to be Centricity-compliant by other means. Determining what RTF controls are acceptable could be somewhat time consuming, but I'll bet someone has already done it.
What exactly is the nature of the problem? Are you receiving RTF control codes that CPS can't interpret?
Posted : January 17, 2017 7:27 am
