Does anyone use EnsLib.ITK.DTS.Framework.Operation.DTSTransferFile ? and how did you manage the transition to MESH?

Does anyone use EnsLib.ITK.DTS.Framework.Operation.DTSTransferFile ? and how id you manage the transition to MESH?

I just noticed this PR from 2011

https://www.intersystems.com/news-events/news/news-item/itk-2-0-0-compliance-for-intersystems-ensemble-makes-it-easier-and-cheaper-for-nhs-trusts-to-exchange-information/

which led me to this class EnsLib.ITK.DTS.Framework.Operation.DTSTransferFile 

Given this was 2011, and DTS (now called MESH) is widely used by GP practices , I'm hoping someone in the community used this class?

If so - how did you manage the transition to MESH in Jan-2017?

Notes:

https://nhsconnect.github.io/spine-mesh/index.html

https://meshapi.docs.apiary.io/#

Answers

Hi Stephen,

We do have an update package that provides MESH support in place of the old DTS support. As with the old DTS, it uses the MESH client (rather than the MESH API). It provides you with full support for sending and receiving MESH messages. The package is provided as "sample" code, but it works well and is in use by a number of trusts. It comes with full documentation on installing and using the package.

If you could let me have your e-mail address and organisation, I would be happy to send you the package.

Paul Dayan

InterSystems Sales Engineer

Comments

Stephen 

Have you connected to MESH yet? If you have could you please share your experience? Anything to look out for?