Continuation Messages

[Tony Benitz]

Our transcription system is using the HL7 DSC notation to send really long clinical care notes out of the system.  Our HIS (cerner) will NOT place the continued messages back together again.

In 5.2 we were using the GDBM database to combine the messages within the interface engine and send outbound a single large message.  Now that we are at 5.3, GDBM is causing major problems.  (Strange errors, working in a test env.  Then not working in production.  Crashing in production, then working just fine once the process is cycled).

Support says.. GDBM.. that is 3rd party product.. SOOO.. perhaps now is a good time to change the method in which we deal with continuation messages.

Long story short.

If you are dealing with continuation messages in the interface engine, what is your approach?

Topic

[James Cobane]

Tony,

I would run this one by Support; I think there were some minor issues with the GDBM in 5.3, but I believe they were all resolved.

Jim Cobane

Henry Ford Health

[Bill Bertera]

Tony Benitz wrote:

Long story short.

If you are dealing with continuation messages in the interface engine, what is your approach?

We used to have an interface use them. I think we just wrote the first message(s) to a file, using the msgID as the filename. When the message was complete, we’d continue it on and delete the file. Would probably use “read_file” and “write_file”

[Author]

Replies