This coming Monday, the first code should post on OSEHRA's about-to-be-created VOLDEMORT ("longest acronym ever") GIT repository. The focus for the first pass is FileMan schema comparison, in particular how does a particular VistA's schema differ from that of a GOLD VistA. What is "GOLD"? For now, it's FOIA until the VA stamps a set of files and code as the VOLDEMORT GOLD master. In addition to identifying files and fields unique to a VistA, this first pass also calls out when VistAs use the same fields for different purposes. This outlier came up at the VistA Expertise meeting in Seattle: for example, the VA reused some IHS fields for other purposes and the RPMS comparison report shows this. In anticipation of code posting, here are reports it produces for four "VistAs": OpenVistA, WorldVistA (2010), a test VA VistA ("LULU") and RPMS. The reports cry out generated by 0.1 of VOLDEMORT's Schema Comparison module. This module has not been fully tested and will change regularly until VOLDEMORT is released and they will improve and be joined by Build, Routine and other reports. The intention is to release code at least weekly as we build up to a VOLDEMORT version 1 release in mid December. Finally, while the key people from the VA and the VA's orchestration are central to this project's success, I think it's important that VOLDEMORT is tried and kicked on VistAs (and RPMS) outside the VA. As the offering grows and if anyone with a VistA handy has a few cycles, it would be great if they could push it around. Every critique will help, particularly when it comes to whether the reports being produced show what people need to see as they are merging code bases, using data from multiple sources and loading builds. For VOLDEMORT, data access isn't a problem (well, not a technical problem): the work is in making meaningful reports that tell you what you need to know, no more, no less.