What's your favorite Transport method and why?
So we've used PHINMS all these years for ELR and CDC Messaging. It's an old technology, and many of the IT staff that set it up and knew how to maintain it well have retired or moved on. We DO plan to upgrade to PHINMS 3.1 before the June 30th deadline to keep the CDC Messages flowing, but we'd like to explore other alternatives. PHINMS doesn't always work and the certificates always seem to be expiring...
I've reached out twice to the EDX mailbox on this question and haven't heard anything back. APHL knew of SFTP and S3.
So I'm reaching out to my Basecamp colleagues: What are some other options for secure transport methods for ELR and CDC (HL7) messages?
Thanks much!
I've reached out twice to the EDX mailbox on this question and haven't heard anything back. APHL knew of SFTP and S3.
So I'm reaching out to my Basecamp colleagues: What are some other options for secure transport methods for ELR and CDC (HL7) messages?
Thanks much!
Comments & Events
Misty Johnson turned on public link sharing for this message
on
Misty, we are allowed no other alternatives by our IT overlords, but for PHINMS we switched from LDAP to public certificates because of problems. But yes, you do have to renew. I'm interested in responses as well. Good luck.
Iowa uses Rhapsody with a PHINMS commpoint which uses the same protocol rather than the PHINMS software itself. You still have to manage the certificates. Also, the PHINMS commpoint doesn't automatically come with Rhapsody, but can be requested from ORION (or Rhapsody, now). We have been using it for years without any problems. It does not currently use LDAP, but we have requested this functionality from Rhapsody. This means that the certificates to have to be manually imported into Rhapsody when they expire.
In Utah, we have implemented S3 using NextGen Connect (formerly Mirth Connect) and it has successfully replaced all our connections with AIMS. We currently have not explored alternatives to replacing the PHINMS CDC RnR Hub or the PHINMS PHLIP Reporting, but we do have plans to start exploring alternatives in the near future. From an end user perspective, it was fairly painless and the AIMS team was very easy to work with, and we now have 4 less PHINMS feeds we have to worry about.
thank you Rachelle!