Problems following posts? You can easily follow our Community Forum posts by using Google Reader.
The BioSense Platform features a tool giving site administrators control over how their data are shared. Thanks to a workgroup the BioSense Governance Group convened last year, CDC now has a good idea of what data-sharing capabilities users want in this new tool. Michael Coletta and other members of the team will outline the steps being taken to build the BioSense Platform Admin Tool. They also will present sketches of the requirement artifacts (e.g., context diagram, business process flows, and requirement wireframes).
The National Syndromic Surveillance Program has launched the NSSP Service Desk for its users: support.syndromicsurveillance.org
This Service Desk will enable users the following:
We ask that you do not submit technical assistance requests to the BioSense inbox. To view the informational NSSP Service Desk Webinar, click here.
We are upgrading the BioSense database servers from MySQL version 5.5.38 to version 5.5.40. This is a bug-fix release, so we expect this to be a transparent upgrade. You should not observe any differences when running routine SQL queries via phpMyAdmin or RStudio. If you do have issues with SQL code following the update, please contact the BioSense technical support team at firstname.lastname@example.org.
Because of security issues with the Secure Socket Layer version 3 (SSLv3) protocol (see https://www.us-cert.gov/ncas/alerts/TA14-290A for details), we will soon require that PHINMS senders use the newer and more-secure Transport Layer Security (TLS) protocol to secure their data. This should be a transparent upgrade, since most HTTPS connections support both security protocols and automatically select the best-available security. However, there may be a number of users whose systems are currently configured for SSL connections and these users will need to update their systems to be TLS compliant.
Moving forward, we plan on permanently upgrading to TLS only because the vulnerability is a fundamental weakness in the design of SSL. According to the National Institutes of Standards and Technology (NIST), this is a medium-risk vulnerability that could allow an attacker to intercept PHINMS data that is being sent to BioSense from a SSL-only sender. See the NIST vulnerability summary at http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-3566 for further information and resources.
Please ensure that your PHINMS sender will support TLS by November 28th so that the transition goes smoothly.
The BioSense User Community Site can be found here: https://sites.google.com/site/biosenseusercommunity/home
Dear BioSense Onboarding Participants,
We are resuming more normal operations for jurisdictions that are onboarding with BioSense. While there are still minor delays related to a work backlog from interrupted service over the last two weeks, we are working hard to get back on track.
If you have any questions or comments related to this, please contact Michael Coletta, BioSense Program Manager at MColetta@cdc.gov.
Title: BioSense v2.0 Data Flow
Time/Date: Tuesday, October 7, 2014 from 3:00 – 4:00pm EDT
Mike Alletto, BioSense Redesign Team
Nabarun Dasgupta, BioSense Redesign Team
Presenters Mike Alletto and Nabarun Dasgupta will describe the process of how data are received, processed and brought forward to the front-end application in BioSense v2.0. Their presentation will include a technical overview of all of the steps that a set of data goes through from the receipt of raw data, deduplication, the binning process, and arrival in the application itself.
At the conclusion of this Webinar, attendees will be able to:
Please register for this Webinar via this link: https://www2.gotomeeting.com/register/157307170
Dear BioSense Onboarding Participants,
We are expecting delays on activities related to your transition into the BioSense application. We regret the delay and are working hard to get back on track, but onboarding actions will be temporarily suspended while we redirect resources to manage this temporary situation. We do not expect this matter to continue beyond 14 days.
As stated, this is a temporary situation and we are grateful for your patience as we work through this unexpected challenge. We will continue to provide you with updates on this matter because it is very important that we resume your onboarding activities as soon as possible.
As a first option to check the status on this matter, please check here on the Collaboration Site.
If you still have questions, please contact Michael Coletta, BioSense Program Manager at MColetta@cdc.gov.
Late last week, the BioSense Team implemented an update to the database schema to incorporate additional HL7 fields (see attached spreadsheet), based on expressed interest in such fields from users. While this update was not expected to have any effect on users and there have been no known effects on the front-end application, it has affected some custom back-end table views that were created for certain jurisdictions. If you have noticed that a back-end table you were previously able to view or access is no longer available, please contact us at BioSenseProgram@cdc.gov and we will gladly repair the table access for you.
Additionally, the new schema has changed the names of some existing fields. This may require back-end users to alter previously-saved queries that used these fields. The most likely examples are listed below:
If you have any problems creating queries or running existing queries, please let us know and will help to create the proper query for your intended use.