The AMDS Service for BioSense is now in beta release. Please view details of how to download,configure, build, deploy and use on the service registry page.
You can also download the raw gar from sourceforge. But I recommend getting the source and building with your own configuration.
This service uses the updated 5/31 AMDS draft.
This service is specifically developed to share BioSense aggregate data over PHGrid, but can actually be used for any JDBC data source that wants to be shared using the AMDS spec.
This release is significantly different than the 4/30 alpha release. Specifically we're using Introduce 1.3 (big improvement over 1.2) for service development and configuration management and iBATIS for easy db access / ORM. This release is smaller than the alpha release in size and lines of code so theoretically it will be easier to use. Please let me know any comments. We'll be following the weekly build schedule with a target of July 8 for code freeze.
Update: Tom asked me to explain that we're using iBATIS rather than Hibernate. Both are decent JDBC/ORM frameworks. I chose iBATIS because it has a lighter footprint and I got it working in about 15 minutes. This doesn't mean we won't use Hibernate in the future, but just that we're using iBATIS for now.
Showing posts with label BioSense. Show all posts
Showing posts with label BioSense. Show all posts
Monday, June 1, 2009
Wednesday, April 8, 2009
AMDS Store for BioSense data
So part of the BioSense program strategic plan is to share national data sources in a federated manner. In order to support this using grid and AMDS, we've started working with the BioSense Data Quality team (they run the analysis on the Data Mart) to generate some sample files that we can use to populate an AMDS data store with all the aggregate counts of BioSense syndromes by zip code and by day.
So far, we've got a sample file for all the zip codes covered by VA, DoD and Real-Time data. Of course all the counts are redacted as we don't deal with real data in the lab. But this will let me start working on an ETL process to get this into the AMDS extract data base that Vaughn is developing against.
So far it's only about 5MB/day of data and that's before I normalize out a lot of the content (we won't actually store syndrome names in the tables, etc. etc.) so this is still a good sign.
Also, it looks like Tom has started calling AMDS the Population Data Object (PDO) some times so we may be relabling soon. This actually makes more sense as we're not talking about a data set so much as we are a specification for sharing population data (as opposed to patient specific data that is NHIN's currency).
So far, we've got a sample file for all the zip codes covered by VA, DoD and Real-Time data. Of course all the counts are redacted as we don't deal with real data in the lab. But this will let me start working on an ETL process to get this into the AMDS extract data base that Vaughn is developing against.
So far it's only about 5MB/day of data and that's before I normalize out a lot of the content (we won't actually store syndrome names in the tables, etc. etc.) so this is still a good sign.
Also, it looks like Tom has started calling AMDS the Population Data Object (PDO) some times so we may be relabling soon. This actually makes more sense as we're not talking about a data set so much as we are a specification for sharing population data (as opposed to patient specific data that is NHIN's currency).
Monday, March 30, 2009
BioSense AMDS Extract
John, Tom and I met with the BioSense data team to discuss the best way to provide aggregate BioSense data for AMDS. Until we can prepare an automation routine to determine aggregate data, the data team will generate a trailing 30 day report for the 11 syndromes (using the Chief Complaint bucket for Real-Time sources and the Outpatient Final Diagnosis bucket for VA and DoD).
This report will be parsed and loaded into the BioSense extract database for querying using the AMDS service for BioSense.
All this is near future (before June) kind of stuff. So we are getting rather close to being able to pilot AMDS-BioSense securely in a proper production/staging environment.
The release of AMDS-BioSense would be the second step in releasing the BioSense Grid Publisher (the first being the planned release of the Grid Publisher node).
This report will be parsed and loaded into the BioSense extract database for querying using the AMDS service for BioSense.
All this is near future (before June) kind of stuff. So we are getting rather close to being able to pilot AMDS-BioSense securely in a proper production/staging environment.
The release of AMDS-BioSense would be the second step in releasing the BioSense Grid Publisher (the first being the planned release of the Grid Publisher node).
Thursday, February 19, 2009
AMDS BioSense Extract
I loaded Dr. Tokar's synthetic BioSense data into the Lab's staging database. This gives us AMDS data for 2008 covering GA, SC, NC and IN for BioSense's 10 syndrome classifications.
I'll put the SQLServer DDL up somewhere as soon as we determine a proper way to share DDL.
Some may ask why we're using SQLServer when everything else we use is open source. The answer is because the CDC maintains a farm of SQLServer databases that are paid for at the enterprise level (i.e. "free" to the program). Everything we write will also be available for use in an OSS RDBMS (such as PostgreSQL or MySQL). So although we use SQLServer, nothing is hard wired to SQLServer.
I'll put the SQLServer DDL up somewhere as soon as we determine a proper way to share DDL.
Some may ask why we're using SQLServer when everything else we use is open source. The answer is because the CDC maintains a farm of SQLServer databases that are paid for at the enterprise level (i.e. "free" to the program). Everything we write will also be available for use in an OSS RDBMS (such as PostgreSQL or MySQL). So although we use SQLServer, nothing is hard wired to SQLServer.
Subscribe to:
Posts (Atom)