AMDS Progress

I have been working with Dan to get the Simple Secure Transfer service working for the Harvard group for the last few days (see SecureSimpleTransfer Odyssey postings). I did manage to upload Jim Tobias' RODS data set into my local Postgresql database yesterday and wade through a significant amount of reading on Globus security which is essential, since the clients we develop need to be able to run without a Globus installation on the client machine in much the same way that vBrowser works. I am getting my head back into where I left off with my code so that I can complete the AMDS Web UI. I still have a little work on the amds-rods-client in terms of resolving library dependencies.

AMDS Sample Structure

So Jeremy and I have been tossing some ideas back about an initial draft for the AMDS data structures. Based on discussions led by Tom Savel on what fields should be included in the AMDS, we're going to start testing development using a basic AMDS that includes:

• Date


• Patient Zip3


• Syndrome


• Syndrome Classifier (i.e. which classifier was used to assess the syndrome)(e.g. BioSense, EARS, RODS, ESSENCE, etc.)


• Count


• Denominator (i.e.total count of all syndromes for that zip3 on that date)

Felicia is starting to think about converting the RODS-HDS service (developed to meet this feature request) to RODS-AMDS to meet the draft xml structures. These xml structures are very lightweight and we will modify them as the AMDS data structure undergoes changes based on scientific comment.

The next step is to add the sample xml and schemas to the wiki so we can start getting comments in. Based on comments, we will start to plan services that provide BioSense VA and DoD sample data using the AMDS structure so that it can be combined with RODS data (and eventually EARS, ESSENCE, other systems).

Architecture Diagrams for AMDSS

As part of the project planning that John Stinn is doing, I'm starting to draft up some architecture diagrams for how the AMDS services (AMDSS) will be built, accessed and deployed. The first in this series is a deployment diagram for CDC facing and Partner facing components. This is all fairly vanilla UML 2.x diagram notation-spec, wikipedia in case anyone is interested.

Please let me know your comments.