Cross-Posting Issue From cal_engine #4
Comments
|
Hmmm. This is odd behavior indeed. I ran some simple validations via an HTTP Client like the following: These are returning "Code not found" even though they are obviously present in the ValueSet. So, it doesn't look like the JpaTerminologyProvider code is the culprit here. It appears as though the $expand operation may be the issue as it looks like it is returning an empty expansion when the following is run: I will continue investigating and keep you posted. |
|
Resolved... |
|
Still not 100% by my test. Still not finding the Colon cancer in HAPI as Terminology Server Local Terminology Server |
|
Should be reopened. I still have two more issues that I posted on the thread. I need to figure out how to get my test case to you.
Jeff
… On Jul 22, 2017, at 3:02 PM, c-schuler ***@***.***> wrote:
Resolved...
This was a programmer error. Get the latest.
See results of operation here:
http://measure.eval.kanvix.com/cqf-ruler/baseDstu3/Measure/col/$evaluate?patient=Patient-12214&startPeriod=2014-01-01&endPeriod=2014-12-31 <http://measure.eval.kanvix.com/cqf-ruler/baseDstu3/Measure/col/$evaluate?patient=Patient-12214&startPeriod=2014-01-01&endPeriod=2014-12-31>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#4 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIO2lIKfU2gLilY0IJnv-laQMdlP19hUks5sQkdMgaJpZM4Ofogx>.
|
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I use the cqf-ruler as terminology provider and evaluate the col-logic against two encounters I get this result:
When I copy the JpaTerminologyProvider code into a LocalFhirTerminologyProvider that loads the downloaded valueSets into a Map and run the same test, I get:
From this I conclude that there's different behavior in Jpa's
ValueSet vs = valueSetProvider.getDao().read(new IdType(valueSet.getId()));and my local 'ValueSet vs = valueSets.get(valueSet.getId());'The text was updated successfully, but these errors were encountered: