AZ BioSense Community of Practice

The mission of the Arizona BioSense Workgroup is to work collaboratively as partners to build capacity and quality of BioSense syndromic surveillance in Arizona. Our vision is to improve population health and emergency response through the use of timely and effective syndromic surveillance. This space is a platform for our members to continue discussions and share cross-role topics and questions from providing the data to using syndromic data (clinician/IT/public health).

📢 Unscheduled Interruption to Production Replication

BioSense Platform Onboarding Replication:
An unexpected outage in production replication occurred on Wednesday, December 13, 2023. Data in ESSENCE are available, but data in DataMart and Data Quality Dashboard (DQDB) are not available.
Our team is investigating the source of the error. We do not have an estimated timeframe for resolution yet. A closeout communication will be sent once the restoration has been completed.
Effect on Services:
  • DataMart
  • DQDB
User-Required Actions:
  • None
We appreciate your patience while resolving this issue.
Sincerely,
NSSP Support Team
http://support.syndromicsurveillance.org

Comments & Events

Rachel Berg, Syndromic Surveillance Program Coordinator at ADHS
Update:
BioSense Platform Production Replication Repair Update:
 
We previously reported an unexpected outage in production replication occurring on Wednesday, December 13, 2023. The team has identified the issue and is in the process of repairing the outage. 
As part of the repairs, DataMart and DQDB will be unavailable starting Monday, December 18. Dataflow will be turned off for Production starting on Friday, December 22 at 8:00 pm et. The repairs will take place over the weekend.
We anticipate Dataflow to return and services to be restored by Tuesday, December 26. A closeout communication will be sent once the restoration has been completed.
 
Effect on Services:
  • DataMart
  • DQDB
  • Dataflow
User-Required Actions:
 
  • None
We appreciate your patience while resolving this issue