projectcypress/cypress

An open source tool for testing electronic Clinical Quality Measure calculation

cypress's Issues

unit checking wrong in cms 77 testing

We found this while testing with Cypress 3.0 alpha 6 and found this to be present in Cypress 3.0 Beta 2 as well. The patient ‘HIV_Peds B’ has the lab result for ‘HIV Viral Load’(2.16.840.1.113883.3.464.1003.120.12.1002) expressed in the unit ‘cells/ml’. We believe that the unit should be ‘copies/mL’ which is the standard unit for that test and this is the unit that is mentioned in the HQMF. Can you confirm that this will be updated in the final version of Cypress 3.0 ?

Issue with validator cypress

Hi,
I have been using the below cypress validator for checking QRDA I and III files.
https://validator.projectcypress.org
The website has recently been upgraded and now we are facing some issues in the QRDA I files which were working before.

Please find the attached file
Priority code with negation.txt

These type of errors are coming in all the files which have been tested already

3.0 Beta VM error "You are not authorized to access this page." when trying to create a new vendor.

"Server Error" while trying to create a product

After a vendor was created, while trying to add a product the following error appears:

Beta 1 500 errors

I am having quite a bit of trouble getting beta 1 working. I have spent a number of hours on this but have been unable to successfully create a vendor and a product.

I am using the VM method. Though I have not tried re-downloading the VM in case you may have updated it since beta1 initial release.

Additionally I have tried installing from source but it appears there are some problems with the instructions for this method. I will save this for another post if I feel adventurous.

Here are the steps I followed in attempt to install the VM. I have tried a few times with similar results.

Import virtual machine
edit /etc/network/interfaces
Putty in

sudo su - cypress
cd /opt/cypress
/opt/ruby_build/builds/opt/cypress/bin/bundle exec rake bundle:download_and_install version=2015-beta-20160623 RAILS_ENV=production

Register user
Sign in
Log out

Set user as admin
/opt/ruby_build/builds/opt/cypress/bin/bundle exec rake cypress:add_admin['[email protected]'] RAILS_ENV=production

Sign in
Admin -> Bundles -> Set Default the only bundle (2015 Bundle for the 2016 Reporting Period)

Dashboard
Add Vendor (name Api Tests, id ApiTests), success
Click API Tests vendor
Add Product (name TestProduct, c1-c4, uncheck randomize and duplicate, All eCQMs)
After about a minute 502 Bad Gateway nginx/1.10.0 (Ubuntu)

At this point I can see the VM is writing to hard disk so I am letting it sit until activity stops
Site not responding
Delete cookies and attempt to sign in again, browser reports page isn't working
Landing page works but any attempts to sign in fail

sudo shutdown -r now

Wait for activity to calm down
Sign in successfully
Click on my new vendor
Click on testproduct

"90 of 93 measures ready"
Wait two hours
Refresh page results in 500 error
Entire site no longer seems responsive - results in Server Error trying to access login page
Sometimes it works
"90 of 93 measures ready"
Sometimes 500 error

For CMS171 none of the patients fall under DENEXCEP as per cypress but it expects the same in Cat 3

In Cms 171, none of the patients qualifies for DENEXCEP in any part; whereas cypress excepts the DENEXCEP entry for 0 count measures in cat 3 file. I have checked in the measure xml of cms, exception is mentioned as NONE. Please find the attached screenshot of the Cat 3 error in cypress.
Am using the latest cypress 3.0.0alpha6.

ID root tag is validated in the cypress but its not necessary

It have been observed that ID root and extension are checked in the cypress for uniqueness in each tag for the Cat 1 files.
But the value of ID is not used in any measure calculation or its mentioned anywhere; so ideally this should not be validated in cypress

Counts getting miss match due to consolidated Calculation of Measures from Test Deck of Cypress 3.0 Alpha

We have started testing the Pre-Release Cypress3.0 Alpha. We are facing an issue because the consolidate list of patients are measure wise, whereas our process will run once and calculate status for all patient or visit at once. While generating QRDA III, we are facing issue because few of the patient\visit are getting calculated for other measures due to which Cypress provided count and our count are not matching. Our count is always greater than what cypress has provided due to patients getting qualified across multiple Measures. Please let us know, is this logic the final in Cypress 3.0 or is there supposed to be changed.

Intermittent QRDA upload error in Chrome

This appears to be an issue specific to the Chrome browser, but I wanted to document it here to see if anyone else has experienced it.

In Chrome, when I click the "Upload Results" button and select a QRDA Cat I zip file or Cat III XML file, Cypress will intermittently respond with this error:

Started POST "/test_executions" for 127.0.0.1 at 2013-07-22 11:33:10 -0400
Processing by TestExecutionsController#create as HTML
WARNING: Can't verify CSRF token authenticity
  MOPED: 127.0.0.1:27017 QUERY        database=cypress_development collection=users selector={"$query"=>{"_id"=>"51b9d1176fb30d0285000002"}, "$orderby"=>{:_id=>1}} flags=[:slave_ok] limit=-1 skip=0 batch_size=nil fields=nil (0.4799ms)
  MOPED: 127.0.0.1:27017 INSERT       database=cypress_development collection=logs documents=[{"_id"=>"51ed50b66fb30d6647000002", "username"=>"[email protected]", "event"=>"logout", "updated_at"=>2013-07-22 15:33:10 UTC, "created_at"=>2013-07-22 15:33:10 UTC}] flags=[] (0.1509ms)
Completed 500 Internal Server Error in 91ms

Mongoid::Errors::InvalidFind (
Problem:
  Calling Document.find with nil is invalid.
Summary:
  Document.find expects the parameters to be 1 or more ids, and will return a single document if 1 id is provided, otherwise an array of documents if multiple ids are provided.
Resolution:
  Most likely this is caused by passing parameters directly through to the find, and the parameter either is not present or the key from which it is accessed is incorrect.):
  app/controllers/test_executions_controller.rb:15:in `create'


  Rendered /Users/pelargir/.rvm/gems/ruby-2.0.0-p247/gems/actionpack-3.2.11/lib/action_dispatch/middleware/templates/rescues/_trace.erb (0.9ms)
  Rendered /Users/pelargir/.rvm/gems/ruby-2.0.0-p247/gems/actionpack-3.2.11/lib/action_dispatch/middleware/templates/rescues/_request_and_response.erb (0.7ms)
  Rendered /Users/pelargir/.rvm/gems/ruby-2.0.0-p247/gems/actionpack-3.2.11/lib/action_dispatch/middleware/templates/rescues/diagnostics.erb within rescues/layout (6.8ms)

Apparently, the form attributes aren't getting sent in the POST to /test_executions (which is why the CSRF warning also gets displayed). This happens roughly 75% of the time. The remaining 25% of the time, the form attributes are sent with the POST and the upload completes successfully.

This doesn't happen in Safari or Firefox. In these browsers, the form attributes are sent 100% of the time.

There is a known bug in Chrome where form attributes aren't sent, but I'll have to do some additional research before recommending a possible workaround.

Error while parsing files on Validator

PFA the QRDA I file
Enc Active1.txt

and the error image

QRDA Import Issues

Hey all, great job on Cypress!

We are having a few issues at the moment, I will try to explain them to the best of my abilities.

When importing the QRDA Category 1 files we are missing patient medical data such as meds, labs, allergies, encounters, problems, etc. We have no issue seeing this info in the HTML version. I have also confirmed that we have imported QRDA files from other sources with no issue.

I appreciate any help or input!

Cypress Validator Site Crashing

This is regarding https://validator.projectcypress.org/ . I don't know whether this is the right place to post it or not.

updated patient.txt
valuetag_CD.txt

Switching to tag v2.1.0: failed to switch versions error on clean install

I keep getting an error trying to do a clean install of Cypress 2.1 using the install script.

Install MongoDB:
Add 10gen apt repository: already added
Import 10gen package signing key: already in keyring
Update package lists: skipped - no change
Install mongodb-10gen: already installed (2.2.3) - acceptable
Start mongodb daemon: already running
Wait for mongo network socket (may take a while): ready

Install libxml2 verison 2.8: already installed

Install nokogiri gem: already installed (1.5.6)

Install Cypress application:
Create cypress user: already exists
cypress user in sudo group: yes
Retrieve Cypress application: updated
Switching to tag v2.1.0: failed to switch versions
Can't continue.
root@cypress2:/home/glilly# exit

QRDA 1 Test Exection Remains In Progress

QRDA 1 Test Exection Remains In Progress all the time. Cypress 3.0Alpha4

Please install a 2016 Cypress bundle in order to use the Cypress Validation Utility

I have installed the bundles for 2016 and yet every time I click on the "Validation Utility" tab I get this error:
!Please install a 2016 Cypress bundle in order to use the Cypress Validation Utility
If you continue to receive this message, please email the Cypress Validation Utility team. Include the text of the message above, the upload settings you were using when you encountered the error, and a copy of the file you uploaded.

Upload a different file

---

It may be complaining that I did not first upload a file but I don't see any place where can upload file, except the screen where I upload a file for a particular test. When I upload there, it immediately evaluates against the requirements for that test.

On a related note: is there any user documentation for this release available? All I have seen is how to download and install it.
Thx

Unit mismatch "weeks"

At least the following patients use the unit "weeks" while measures use the unit "wk".

1 N Newborn
2 N Newborn
4 N Newborn
1 N OB
2 N OB
NEWBORN A
NEWBORN B
OB A
OB B

QRDA III file not validated in Cypress it give given errors as 24.

1. 40280381-3D61-56A7-013E-6649110743CE Could not find entry for measure 40280381-3D61-56A7-013E-
   6649110743CE with the following population ids {"IPP"=>"ED07A793-9C2B-47C0-B9EB-6AD4A8026A5D",
   "DENOM"=>"47260199-F952-48FE-A822-71AFAEACEF9D", "NUMER"=>"17E39E36-56BB-4AE1-81C4-
   ADC1475ACC08", "DENEX"=>"850A5C2F-3191-4342-BD49-58F392A42172", "stratification"=>"B5B2DE78-4545-447C-
   9699-F8D8C26E7729"}

How to resolve this issue, Please give the solution ASAP.

Error loading vm image

I receive this error when attempting to load the vm image into either Oracle VirtualBox or VMWare Player.
Failed to open virtual machine: SHA1 digest of file Cypress v2 Public.ovf does not match manifest

For CMS73v4, IPP count is expected as 2.0 instead of 1.0 error in Cat 1 file

A patient "5 N VTE" gets denominator inclusion failed for 2 visits as shown below

The CAT 1 generated has details for both the visits and the error should not persist.
Please find the screenshot of the error for cat1 and the output file attached of the patient

5_N VTE.txt

you must wait for the test preparations to be completed

"you must wait for the teset preparations to be completed. this usually takes no more than a couple of minutes.

Generating patient record"

The above is what I get when going into a test regardless of how many measures it is put against.

I looked at the cypress / app / views / product_tests / _status.html.erb and commented out is a section checking for a problem with the test and alerting the user if there is one.

I dont know if I messed things up by making a very large test from the beginning (all core measures) or if there is a larger coding problem with the test or project.

for the test with all core measures I have left it up on screen for 20 minutes. I've also attempted to reload it over an hour after its creation.

It is unclear whether you are suppose to wait on that page for data to be loaded or return again at a later time. Either way, I cannot use any test created.

" Error: Please install a 2016 Cypress bundle in order to use the Cypress Validation Utility"

I downloaded the bundle for 2016-beta-20160623 first.
I created a company, and a product. Set the product to certify for c1, c2 and c3.
I selected measures. I looked at how to download QRDA I files for patients and could not find any way. Decided it must be the "Validation Utility" that does that.
Clicked on the tab for it and after a long time, got this error:

It looks like it thinks I am trying to upload files?
Anyway I thought maybe it wanted me to download the other bundle first so I went back and downloaded the 2015-beta-20160707 bundle as well, and tried again with the validation tab. Same result.

What does it take to get QRDA I files for import?

3.0 Beta 2 VM - error "rake aborted! SocketError: gettaddrinfo: Name or service not known

This happened with Beta 1 as well, and I can't get past it. When I enter the command to download the bundles, I get the error shown below.

I am running this on VMWare. I notice that it says I will have to ssh into the server, but I simply logged into the VM via the VMWare window. Is that the problem?

Taking latest visit if admited again within 24 hours of discharge for Measure Calc

Hi,

For CMS55, a patient named"3 N SCIP" has encounter 1 as


and another encounter 2 as

So, the second encounter is only considered for measure calculation wherein Cypress says all visits should fall under measure calculation (atleast IPP)
PFA the patients file
31_3_N SCIP.txt

For some measure there is no templated id in the device order ACT for patients

For measure id CMS108,CMS114,CMS190, some of the patients have device order tag which do not have any templateid in the cypress data; due to this the QRDA files are not consumed in our environment.
Please find attached the patients files
2_8 N_N VTE.txt
3_11 N_N VTE.txt

Downloading cypress VM issue

After downloading and creating a VM from
https://github.com/projectcypress/cypress/wiki/Cypress-v2.0-Installation-Guide
in VMware, we are not able to login using the given credential
Username: ubuntu
Password: CypressPwd

Please let us know, what needs to be done

Error when tests have no measures

If you create a test without any measures, it gives some errors and the test is unavailable for use.

Suggestion: block being able to click "done" until the user has selected at least one quality measure.

500 error when trying to view Master patient list/Add Product on VirtualBox

I'm running Cypress 3 beta1 on VirtualBox. I'm able to add a log in but I get a 500 error when trying to view the master patient list or add a new product. Attached is the log file.

production.txt

HTML patient extract missing closing DL tags

Minor thing I noticed since my browser is apparently ridiculously sensitive. The HTML exports of patient data from Cypress don't appear to be generating closing DL tags. Instead, they're opening new DL tags

EX: 2_CAP_ADULT_A.html

<dl>
<dt><b>Ordinality</b>: code_system: SNOMED-CT code: 63161005 title: Hospital Measures - Principal</dt>
<dl>

Note the final DL should be </dl>

CMS185 has IPP configured as 2013 spec and Cypress data is per 2015 spec

Hi,
The below ticket says that for CMS 185, the IPP is considered as of 2013 version
https://oncprojectracking.healthit.gov/support/browse/CQM-1142

But the data now Cypress gives is as per 2015 IPP version.
So in this case, the patients are not qualifying IPP as of current cypress data

Beta_2 install error: OpenURI: 404 not found

The error has been mentioned before - I get it after issuing the following command as part as install on a VMWare player. I am using Beta2.

/opt/ruby_build/builds/opt/cypress/bin/bundle exec rake bundle:download_and_install version=2015-beta-20160707 RAILS_ENV=production

Issue with cypress validator

Element '{urn:hl7-org:v3}id', attribute 'root': '604F3C60-99FC-4C4BB224-6A22D74E84E7' is not a valid value of the union type '{urn:hl7-org:v3}uid'.

I am getting the above validation error. The node looks like and the root UDID is correct for 2016.
So what is the issue?

nodeUDID.txt

Cypress getting crashed while uploading QRDA III

It is giving following error.
Server Error
Something went wrong with this request. This is likely a problem with Cypress rather than a mistake on your part. Please find attached xml file just rename it to .xml.

File is a QRDA III xml for CMS111

QRDA3 (1).txt

For CMS188 Route Code missing for Patient Data

For CMS188, as per the measure spec it says Medication, Administered: IV, IM, PO Antimicrobial Medications (route: Substance or Medication Administration Route IV, oral or IM)" satisfies any.
Whereas cypress provided data doesn't have any route code. Please find attachment. Am using the latest cypress 3.0.0alpha6.
Just rename txt to xml.
1_2_N CAP.txt

HTML patient output - invalid style attribute

Super minor

In the "Codes" column, 2nd span tag there's an invalid style attribute:

      paddint-left           (t)

should be:

      padding-left          (g)

Test Patients not getting generated in New version 6alpha

Test Patients not getting generated in New version 6alpha. Check production.log, something is gone in Infinite loop. I tried for CMS100.

Uploading a QRDA Category III File

Hello,

We have an active installation of Cypress where we try importing/ exporting category I and III files. The issue we face is that we cannot get Cypress to accept any Category III file. We have so far tried 3 various formats of Category III. One that follows April 2012's Quality Reporting Document Architecture, August 2012 and November 2012 (the most recent). None of them gets accepted even though they are identified as valid QRDA Category III documents. Can you please point us out to which months specification is being used in Cypress. I will also try looking around the code, but since I hardly have any experience w/ RoR, I doubt I will be able to find what I am looking for. Do let me know if any part of my question is not clear or if more information is needed.

Thanks,
Karthik

Cypress 3.0.0beta1 Corrupt VM File

The new link provided is giving corrupted VM files.
https://s3.amazonaws.com/cypress_public/Cypress_v3.0.0beta1_Public_VM.ovf.tar.gz

Also installation only talks about 2015 Bundles, Can we install Both Bundles at the same time??

Return conditional data based an XHR's request details

Often a server will respond conditionally to a request based on information in the POST data. Would be helpful to be able to do this using cy.route() - currently if a function is passed in it is called immediately, not at the point of requesting.

Unit issue "cells/mm3"

Cypress patients 1_N HIV Peds, 3_N HIV Peds, HIV_Peds_A, HIV_Peds_B have "cells/mm3"

While measure CMS52v5 uses "/mm3"

CMS188v5 also uses "/mm3" but I don't know that any cypress patients have issues there.

Bundle Install fails with 1.9.3-p327

It looks like the most recent 1.9.3 patch has broken some debugger parts. The following commands, done prior to the bundle install, correct the 2 issues and allows the install to succeed.

gem install debugger-linecache -v '1.1.2' -- --with-ruby-include=$rvm_path/src/ruby-1.9.3-p327/
gem install debugger -v '1.1.4' -- --with-ruby-include=$rvm_path/src/ruby-1.9.3-p327/

Jeff

3.0 Beta 2 VM - error "rake aborted! openURI :: HTTPError: 404 Not Found

3.0 Beta 2 VM - error "rake aborted! openURI :: HTTPError: 404 Not Found

For CMS172 the patient should be denominator exclusion but its meeting performance

For CMS172(a)
2_1_N SCIP.txt
the patient should be denominator exclusion as per cypress, but as per data its not meeting any exclusion criteria and hence meeting performance. According to us the patient should pass the below condition for exclusion
OR: "Procedure, Performed: General or Neuraxial Anesthesia" satisfies any ◾<= 4 day(s) ends before start of "Occurrence A of Procedure, Performed: General or Neuraxial Anesthesia"
◾<= 4 day(s) starts after end of "Occurrence A of Procedure, Performed: General or Neuraxial Anesthesia
We found out the difference between the above 2 proc is 6 days; whereas measure says it should be 4 days
Please find attached the patients file
2_1_N SCIP.txt

Installation Issue - Please help

We are 'starting from scratch' so we are trying to install the latest version of Cypress, which of course directs me to 2.4.0 installation instructions, unfortunately I can't get past importing the .ovf file. I can download the file, unzip it and beGIN importing it, but each time I receive the same message at the 99% mark:

HELP!! How may I resolve this so I may continue the installation and upgrade????

Non-GUI install tips

Here are some key elements I had to figure out to install the Cypress VM on a non-GUI CentOS install. The general instructions don't cover any of this.

1. Download and install Oracle_VM_VirtualBox_Extension_Pack-4.2.12-84980.vbox-extpack

vboxmanage extpack install Oracle_VM_VirtualBox_Extension_Pack-4.2.12-84980.vbox-extpack

1. Import VMware image into VirtualBox (will be call "vm" unless specified otherwise)

VBoxManage import "Cypress v2 Public.ovf"

1. I needed to be able to access the Cypress VM from the network and the host server was using ports 80 and 22, so the default install was far from ideal. Changing to bridge mode seems to be the easiest way. My Ethernet interface on the host was eth1, yours may be eth0.

VBoxManage modifyvm "vm" --nic1 bridged --bridgeadapter1 eth1

1. Then I had to connect to connect to the vm to find out what IP address it was given by my DHCP server.

VBoxHeadless -s vm --vrde on

Not sure if this is the right place to post this but I can't find a better place.

offtopic: CCRs and lab results

sorry for the noise (but i can't find email addresses for either of you!)

would it be possible to get a pointer to how one encodes lab results via CCR? neither LabCorp nor Quest Diagnostics have a download "CCR" (or "CCD") button, but only a "PDF" button.

fine, i can run http://tabula.technology/ as well as anyone else and clean up the output. and i can write a transformation program ... if i know what the format/dictionary is... would you be able to help?

many thanks!

/mtr

Accessing Master Patient list produces NoMethodError in PatientsController#index

Full Trace (HTTP stuff follows)

/home/cypress/cypress/app/controllers/patients_controller.rb:31:in `index'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/actionpack-3.2.14/lib/action_controller/metal/implicit_render.rb:4:in `send_action'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/actionpack-3.2.14/lib/abstract_controller/base.rb:167:in `process_action'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/actionpack-3.2.14/lib/action_controller/metal/rendering.rb:10:in `process_action'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/actionpack-3.2.14/lib/abstract_controller/callbacks.rb:18:in `block in process_action'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/activesupport-3.2.14/lib/active_support/callbacks.rb:437:in `block in _run__1524433360865525282__process_action__770927688006593343__callbacks'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/activesupport-3.2.14/lib/active_support/callbacks.rb:215:in `block in _conditional_callback_around_459'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/actionpack-3.2.14/lib/action_controller/caching/actions.rb:147:in `filter'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/activesupport-3.2.14/lib/active_support/callbacks.rb:321:in `around'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/activesupport-3.2.14/lib/active_support/callbacks.rb:310:in `_callback_around_289'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/activesupport-3.2.14/lib/active_support/callbacks.rb:214:in `_conditional_callback_around_459'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/activesupport-3.2.14/lib/active_support/callbacks.rb:414:in `_run__1524433360865525282__process_action__770927688006593343__callbacks'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/activesupport-3.2.14/lib/active_support/callbacks.rb:405:in `__run_callback'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/activesupport-3.2.14/lib/active_support/callbacks.rb:385:in `_run_process_action_callbacks'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/activesupport-3.2.14/lib/active_support/callbacks.rb:81:in `run_callbacks'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/actionpack-3.2.14/lib/abstract_controller/callbacks.rb:17:in `process_action'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/actionpack-3.2.14/lib/action_controller/metal/rescue.rb:29:in `process_action'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/actionpack-3.2.14/lib/action_controller/metal/instrumentation.rb:30:in `block in process_action'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/activesupport-3.2.14/lib/active_support/notifications.rb:123:in `block in instrument'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/activesupport-3.2.14/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/activesupport-3.2.14/lib/active_support/notifications.rb:123:in `instrument'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/actionpack-3.2.14/lib/action_controller/metal/instrumentation.rb:29:in `process_action'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/actionpack-3.2.14/lib/action_controller/metal/params_wrapper.rb:207:in `process_action'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/actionpack-3.2.14/lib/abstract_controller/base.rb:121:in `process'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/actionpack-3.2.14/lib/abstract_controller/rendering.rb:45:in `process'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/actionpack-3.2.14/lib/action_controller/metal.rb:203:in `dispatch'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/actionpack-3.2.14/lib/action_controller/metal/rack_delegation.rb:14:in `dispatch'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/actionpack-3.2.14/lib/action_controller/metal.rb:246:in `block in action'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/actionpack-3.2.14/lib/action_dispatch/routing/route_set.rb:73:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/actionpack-3.2.14/lib/action_dispatch/routing/route_set.rb:73:in `dispatch'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/actionpack-3.2.14/lib/action_dispatch/routing/route_set.rb:36:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/journey-1.0.4/lib/journey/router.rb:68:in `block in call'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/journey-1.0.4/lib/journey/router.rb:56:in `each'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/journey-1.0.4/lib/journey/router.rb:56:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/actionpack-3.2.14/lib/action_dispatch/routing/route_set.rb:608:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/mongoid-3.1.4/lib/rack/mongoid/middleware/identity_map.rb:34:in `block in call'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/mongoid-3.1.4/lib/mongoid/unit_of_work.rb:39:in `unit_of_work'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/mongoid-3.1.4/lib/rack/mongoid/middleware/identity_map.rb:34:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/warden-1.2.3/lib/warden/manager.rb:35:in `block in call'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/warden-1.2.3/lib/warden/manager.rb:34:in `catch'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/warden-1.2.3/lib/warden/manager.rb:34:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/actionpack-3.2.14/lib/action_dispatch/middleware/best_standards_support.rb:17:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/rack-1.4.5/lib/rack/etag.rb:23:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/rack-1.4.5/lib/rack/conditionalget.rb:25:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/actionpack-3.2.14/lib/action_dispatch/middleware/head.rb:14:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/actionpack-3.2.14/lib/action_dispatch/middleware/params_parser.rb:21:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/actionpack-3.2.14/lib/action_dispatch/middleware/flash.rb:242:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/rack-1.4.5/lib/rack/session/abstract/id.rb:210:in `context'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/rack-1.4.5/lib/rack/session/abstract/id.rb:205:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/actionpack-3.2.14/lib/action_dispatch/middleware/cookies.rb:341:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/actionpack-3.2.14/lib/action_dispatch/middleware/callbacks.rb:28:in `block in call'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/activesupport-3.2.14/lib/active_support/callbacks.rb:405:in `_run__2783087504741527961__call__4489379184007931726__callbacks'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/activesupport-3.2.14/lib/active_support/callbacks.rb:405:in `__run_callback'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/activesupport-3.2.14/lib/active_support/callbacks.rb:385:in `_run_call_callbacks'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/activesupport-3.2.14/lib/active_support/callbacks.rb:81:in `run_callbacks'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/actionpack-3.2.14/lib/action_dispatch/middleware/callbacks.rb:27:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/actionpack-3.2.14/lib/action_dispatch/middleware/remote_ip.rb:31:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/actionpack-3.2.14/lib/action_dispatch/middleware/debug_exceptions.rb:16:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/actionpack-3.2.14/lib/action_dispatch/middleware/show_exceptions.rb:56:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/railties-3.2.14/lib/rails/rack/logger.rb:32:in `call_app'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/railties-3.2.14/lib/rails/rack/logger.rb:16:in `block in call'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/activesupport-3.2.14/lib/active_support/tagged_logging.rb:22:in `tagged'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/railties-3.2.14/lib/rails/rack/logger.rb:16:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/actionpack-3.2.14/lib/action_dispatch/middleware/request_id.rb:22:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/rack-1.4.5/lib/rack/methodoverride.rb:21:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/rack-1.4.5/lib/rack/runtime.rb:17:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/activesupport-3.2.14/lib/active_support/cache/strategy/local_cache.rb:72:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/rack-1.4.5/lib/rack/lock.rb:15:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/rack-cache-1.2/lib/rack/cache/context.rb:136:in `forward'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/rack-cache-1.2/lib/rack/cache/context.rb:245:in `fetch'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/rack-cache-1.2/lib/rack/cache/context.rb:185:in `lookup'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/rack-cache-1.2/lib/rack/cache/context.rb:66:in `call!'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/rack-cache-1.2/lib/rack/cache/context.rb:51:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/railties-3.2.14/lib/rails/engine.rb:484:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/railties-3.2.14/lib/rails/application.rb:231:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/railties-3.2.14/lib/rails/railtie/configurable.rb:30:in `method_missing'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/passenger-3.0.18/lib/phusion_passenger/rack/request_handler.rb:96:in `process_request'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/passenger-3.0.18/lib/phusion_passenger/abstract_request_handler.rb:516:in `accept_and_process_next_request'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/passenger-3.0.18/lib/phusion_passenger/abstract_request_handler.rb:274:in `main_loop'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/passenger-3.0.18/lib/phusion_passenger/rack/application_spawner.rb:206:in `start_request_handler'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/passenger-3.0.18/lib/phusion_passenger/rack/application_spawner.rb:171:in `block in handle_spawn_application'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/passenger-3.0.18/lib/phusion_passenger/utils.rb:470:in `safe_fork'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/passenger-3.0.18/lib/phusion_passenger/rack/application_spawner.rb:166:in `handle_spawn_application'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/passenger-3.0.18/lib/phusion_passenger/abstract_server.rb:357:in `server_main_loop'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/passenger-3.0.18/lib/phusion_passenger/abstract_server.rb:206:in `start_synchronously'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/passenger-3.0.18/lib/phusion_passenger/abstract_server.rb:180:in `start'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/passenger-3.0.18/lib/phusion_passenger/rack/application_spawner.rb:129:in `start'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/passenger-3.0.18/lib/phusion_passenger/spawn_manager.rb:253:in `block (2 levels) in spawn_rack_application'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/passenger-3.0.18/lib/phusion_passenger/abstract_server_collection.rb:132:in `lookup_or_add'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/passenger-3.0.18/lib/phusion_passenger/spawn_manager.rb:246:in `block in spawn_rack_application'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/passenger-3.0.18/lib/phusion_passenger/abstract_server_collection.rb:82:in `block in synchronize'
<internal:prelude>:10:in `synchronize'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/passenger-3.0.18/lib/phusion_passenger/abstract_server_collection.rb:79:in `synchronize'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/passenger-3.0.18/lib/phusion_passenger/spawn_manager.rb:244:in `spawn_rack_application'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/passenger-3.0.18/lib/phusion_passenger/spawn_manager.rb:137:in `spawn_application'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/passenger-3.0.18/lib/phusion_passenger/spawn_manager.rb:275:in `handle_spawn_application'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/passenger-3.0.18/lib/phusion_passenger/abstract_server.rb:357:in `server_main_loop'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/passenger-3.0.18/lib/phusion_passenger/abstract_server.rb:206:in `start_synchronously'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/passenger-3.0.18/helper-scripts/passenger-spawn-server:99:in `<main>'

Cypress Password

We are trying to install the latest version (2.2) and are being prompted for the Cypress password ... unfortunately everything we have tried has failed!

Beta 2 (vm image) cannot be imported with the following error:

Failed to import appliance

C:...\Downloads\Cypress_CVU.v3.0.0beta2_Public_VM.ova.

Could not open the medium storage unit 'D:\QRDA_2016\temp_cypresscvuv300beta2-disk1.vmdk.gz'.

VD: error VERR_SHARING_VIOLATION opening image file 'D:\QRDA_2016\temp_cypresscvuv300beta2-disk1.vmdk.gz' (VERR_SHARING_VIOLATION).

Result Code: VBOX_E_FILE_ERROR (0x80BB0004)
Component: ApplianceWrap
Interface: IAppliance {8398f026-4add-4474-5bc3-2f9f2140b23e}

Beta 1 was imported without any problems.

Virtual box version: 5.0.24

Unit percent in string type

Cypress patients N Heart 1 and N Heart 2 have
<value xsi:type="ST" >12%</value>
in entry for "Risk Category Assessment: Framingham coronary heart disease 10 year risk"
These are the only two patients I could find like this but there may exist others.

I believe this should be coded as:
<value xsi:type="PQ" value="12" unit="%"/>

Reopening issue 516

Please find attached screenshot, wherein it says patient to be qualified for Denominator & Denominator Exclusion for CMS 188.
1_2_N CAP.txt