removed finalize function.  This will be handled as part of the measure definition
removing old spreadsheet based patient importer
QME refactored to use mongoid models for the QueryReport PatientCache QuailityMeasure ....
lock file updated with updated version of QME
adding method to get patient level results for a quality report
 adding method to get measure associated with quality report
fixing typo
moving patient matcher query generation into quality report as what is in meausre evaluator is aggrataion based
Updating Gemfile.lock
merging fixed median aggregation function branch
Fixing issue where if a bundle_id was not passed in it was set to null in the query for a measure.  This caused some annoyance issues for applications that may have only a single bundle installed yet did not pass the bundle_id into the calculation creating an issue where the measures would not be found.  This fixes that issue by only applying bundle_id to the measure query if the
'bundle_id' key is in the passed in paramenters.  This will result in a potentially different problem for applications useing the library if they have multiple bundles installed with the same measures in that this will choose the first measure it finds.
merging perf (performance) branch
adding backwards compatibility to query cache model , placing result values at the top level of the q cache and in the results. Will remove in the future
Rolling back perf branch merge seeing how it needs rebuilt measures to work correctly
Fixing the providers filter, was the wrong format previously
Updating to deal with changes required by MongoDB sharding

These changes have come into play with more recent versions of MongoDB
Update to the Travis-CI config for new rubies and branches
Bumping the version for beta2
marking initailzer of QualityReport as a protected method.  Previous versions of QME used QualityReport as a facade around the query cache entries.  This version uses mongoid and treates the reports as first class objects so we need to enusre that they are first searched for and then created as a last resort if they do not exist.  Protecting the initalizer will cause errors in applications attempting to use this updated version of the code with older symantics and alter the users to issues that they will need to address in their own codebase.
adding a comment as to why the initiaizer is protected