Not an AIMS Issue!
Hello,
It seems my post caused some concern at APHL so I wanted to update it.
The problem as it turned out, was that a SQL server hosted by our IT shop had the logs fill up so the PHINMS feed stopped processing. Once that was identified as the problem it could be cleared up and messages flowing again.
To be fair, my tech person - who does not manage or have access to these servers at DPH - did reach out to CDC PHINMS and was told it was an AIMS issue. When we did not hear back from his first posts to the AIMS help desk yesterday, we did not know how else to get a response to help us. When we did hear back this morning, the AIMS team quickly worked with us to identify the issue. I have escalated that issue up internally because we had a similar issue with central IT SQL DB which stopped file imports into our surveillance system. You can not imagine the ongoing frustration we have with IT here with a lack of monitoring, being able to expand capacity to meet high demand on systems, etc.
This escalation was in no way intended to denigrate the AIMS team, who we respect very much. It is a reflection of the need to have a better protocol/checklist in place so we check certain areas when an issue message comes in. And we have had continuing frustration with messaging, as I'm sure others have, over the past year. We plan on a follow up call with AIMS-APHL next week to be on the same page and also with some questions about S3 that we seem to not be communicating well by email.
We are heading into month 15 for this pandemic as our surveillance work started January 2020. Over the past year of lab reporting, we have not had one single break or been able to add any additional full time staff. I try to be a glass half full person, but I'm starting to feel like my glass is broken.
So APHL-AIMS, not your fault. Thanks for assisting us. We will carry on as best as we can.
Nancy
Hi all, CT messages from AIMS seem to have suffered a total fail since Feb 16. Has any other state noticed issues? We are in the process of moving away from PHINMS to S3 but with one - yes you got that - one technical person supporting our system it is moving forward steadily but not done yet.
We are waiting to hear back from AIMS on issues but wondering if others have had something similar occur recently.
Thanks!
It seems my post caused some concern at APHL so I wanted to update it.
The problem as it turned out, was that a SQL server hosted by our IT shop had the logs fill up so the PHINMS feed stopped processing. Once that was identified as the problem it could be cleared up and messages flowing again.
To be fair, my tech person - who does not manage or have access to these servers at DPH - did reach out to CDC PHINMS and was told it was an AIMS issue. When we did not hear back from his first posts to the AIMS help desk yesterday, we did not know how else to get a response to help us. When we did hear back this morning, the AIMS team quickly worked with us to identify the issue. I have escalated that issue up internally because we had a similar issue with central IT SQL DB which stopped file imports into our surveillance system. You can not imagine the ongoing frustration we have with IT here with a lack of monitoring, being able to expand capacity to meet high demand on systems, etc.
This escalation was in no way intended to denigrate the AIMS team, who we respect very much. It is a reflection of the need to have a better protocol/checklist in place so we check certain areas when an issue message comes in. And we have had continuing frustration with messaging, as I'm sure others have, over the past year. We plan on a follow up call with AIMS-APHL next week to be on the same page and also with some questions about S3 that we seem to not be communicating well by email.
We are heading into month 15 for this pandemic as our surveillance work started January 2020. Over the past year of lab reporting, we have not had one single break or been able to add any additional full time staff. I try to be a glass half full person, but I'm starting to feel like my glass is broken.
So APHL-AIMS, not your fault. Thanks for assisting us. We will carry on as best as we can.
Nancy
Hi all, CT messages from AIMS seem to have suffered a total fail since Feb 16. Has any other state noticed issues? We are in the process of moving away from PHINMS to S3 but with one - yes you got that - one technical person supporting our system it is moving forward steadily but not done yet.
We are waiting to hear back from AIMS on issues but wondering if others have had something similar occur recently.
Thanks!
-Kate
Yes it is on AIMS side. We got the spooled message also, but that is not the problem. We've been working it since yesterday. But we had no response from AIMS to emails yesterday which was a concern. We have since heard from them this morning. We are in transition to SFTP but not finished yet. It seems like everything is built for Rhapsody and we don't use that - and we won't ever switch to that. We've been using our engine since 2012 per state mandate. It's frustrating. If our Gov office didn't insist on these M-F reports (they used to be 7 days a week until July), it would make it easier to catch up on problems. Thanks for listening to my Ted talk.
Thanks for your clarification on yesterday's issue with CT's disk space. Alissa McShane (leading the PHINMS to S3 migration project) and I will reach out to you to see how we can help with any questions you may have related to S3.
Have a great day and thank you for all you do!
Eddie