‹ Home
Exported

CSTE National ELR Workgroup

Welcome to the CSTE National ELR Workgroup Basecamp! We hope you will utilize the space to share resources with colleagues, start discussion threads, and identify topics for the workgroup to tackle on future calls. All workgroup members will have the opportunity to join. Please note that you may edit your notification preferences to suit your needs (and your email inbox). If you are not already on the ELR distribution list and would like to receive call communications, please enroll using this subscription form (copy and paste in browser): https://app.smartsheet.com/b/form/5a91a4579952496682084796b82112e6
Becky Lampkins, Manager, Surveillance/Informatics Program at CSTEMegan Toe, CSTEScott Troppy, Surveillance Epidemiologist at MA DPHMeredith Lichtenstein, CSTEAmy Drake, NMJohn RobertsNancy Barrett, Epi 4/PH Informatics SpecialistErin Holt, TDHRita Altamore, EpidemiologistDavid DiCesareJason HallWalter Kemper, ELR Coordinator, NC DHHS Div of Public HealthJulie LuepkeCarmen Pugh, Labcorp Manager State Reporting at LabCorpTom Safranek +399 others
Posted by Cody McNeese ·

Rhapsody Users- Upgrade to 7 and AIMS S3 Commpoint

Hello, 

Has anyone upgraded from Rhapsody 6.x to Rhapsody 7? OR is attempting to upgrade from 6.8 to 7 but is running into issues with AIMS S3 commpoint and we are searching for solutions. 

Thank you, 

Cody

Comments & Events

Michael Lopez Michael Lopez
Hello,
We are on 6.7.1.

Thank you,
Michael Lopez
Director, Surveillance Systems
Bureau of Epidemiology and Public Informatics | Kansas Department of health and Environment | 1000 SW Jackson; Suite 200 | Topeka, Kansas 66612-1371
Office Phone: 785-296-7127 | Cell Phone: 785-496-0468 | Email: michael.lopez@ks.gov<mailto:michael.lopez@ks.gov> | Fax: 877-427-7318
Notified 380 people
Jonathan Johnson, Informatics and Data Science Lead (HI - DOH) Jonathan Johnson, Informatics and Data Science Lead (HI - DOH)
Hi Cody,

Unfortunately not as we are still on 6.5. What is the issue you're running into?

Mahalo,
Jonathan
Notified 380 people
Ann Kayser Ann Kayser
Hi Cody -

In Minnesota, we are on 7.0. My IT counterpart did post the following on the Lyniate community forum today as well: We (MN) are on 7.0, but did not use the AIMS provided communication point.  We used the Rhapsody SQS comm point along with the JavaScript REST Client to facilitate our connections to AIMS.  https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html explains how to build the appropriate authentication needed.

Hope that helps!
Ann Kayser
MN Dept of Health
Notified 380 people
Misty Johnson, Informatician, WI DHS Misty Johnson, Informatician, WI DHS
Cody McNeese Cody , in WI we are also upgrading from Rhapsody 6 to Rhapsody 7.  We've also learned that the AIMS S3 comm point for Rhapsody 6 does not appear to work in Rhapsody 7, and AIMS is not expecting their updated version until September.

We've reached out to Rhapsody support for a workaround. In the meantime, we've considered reverting back from S3 to SFTP, or even PHINMS. Unfortunately, we're aware that SFTP does not have the metadata that S3 has.

Ann Kayser Ann , thank you for that solution! We'll look into that!
Notified 380 people
Brooke Beaulieu, APHL Brooke Beaulieu
Thanks Cody McNeese Cody and others for your input.

The AIMS team is aware of this issue and actively testing updates to the commpoint. Besides OR, WI, and MN, have any other jurisdictions already upgraded to Rhapsody v7? AIMS will ensure the updated release is distributed to those states as soon as it is ready to go out.

Thanks,
Brooke  
Notified 380 people
Cody McNeese Cody McNeese
Brooke Beaulieu, APHL Brooke I believe Montana is actively exploring an upgrade to v. 7 Jennifer Floch Jennifer would you be able to provide any details?

Thank you Ann Kayser Ann and Misty Johnson, Informatician, WI DHS Misty  for your input as well! 

Thank you, 

Cody
Notified 380 people
Brooke Beaulieu, APHL Brooke Beaulieu
Thank you! For others that have not already upgraded to v7, the recommendation from AIMS is to postpone upgrading if possible until the compatibility issues are sorted out. 
Notified 380 people
Cody McNeese Cody McNeese
Here are the potential solutions discussed on the CSTE call today: 

AIMS S3 Commpoint – 

Rhapsody v. 6 to Rhapsody v. 7 upgraded their logging service for security reasons. 

Potential Solutions: 

APHL/AIMS- AIMS S3 – swapping out the log files for new log files – into the AIMS S3 commpoint. 

-          Use the Rhapsody Development toolkit to change out the log files

MN Solution – 

Take the S3 commpoint and split into an SQS Commpoint and a Rest API commpoint. 

-          This is a good resolution if you do not have a proxy server 
o   Need dedicated IT from state
o   SQS thread – Needs to be SQS thread safe so that you can stop threads if needed one by one
o   Rhapsody has a ticket to allow proxy server on SQS

OR Potential Solution – 

Working with Rhapsody to build just a rest API to do the same job as an SQS + API 

Will keep everyone updated once we find a resolution that works for OR based on our server set up. 
Notified 386 people
Nancy Barrett, Epi 4/PH Informatics Specialist Nancy Barrett, Epi 4/PH Informatics Specialist
MD and WA state mentioned use of MFT; also Pam Alexander at ARUP was knowledgeable about it
Notified 386 people
Nancy Barrett, Epi 4/PH Informatics Specialist Nancy Barrett, Epi 4/PH Informatics Specialist
is this a new topic?
Notified 386 people
Cody McNeese Cody McNeese
It's separate from sFTP, MFT, and PHINMS. I jumped the gun with information I am about to share. 
Notified 386 people
Nancy Barrett, Epi 4/PH Informatics Specialist Nancy Barrett, Epi 4/PH Informatics Specialist
no worries!

Nancy L. Barrett, MS, MPH
Epidemiologist
Connecticut Department of Public Health
410 Capitol Avenue
Hartford, CT 06134
860-509-7998
nancy.l.barrett@ct.gov<mailto:nancy.l.barrett@ct.gov>

P Before printing, please think GREEN and keep it on the screen.
CONFIDENTIALITY NOTICE: This electronic message may contain information that is confidential and/or legally privileged. It is intended only for the use of the individual(s) and entity named as recipients in the message. If you are not an intended recipient of the message, please notify the sender immediately and delete the material from any computer. Do not deliver, distribute, or copy this message, and do not disclose its contents or take action in reliance on the information it contains. Thank you!
Notified 386 people