STU 3.0.1 Appointment test uses invalid resource and problem with conditional interactions about crucible HOT 4 OPEN

For the X010, you are correct. I have a PR open for a fix here: fhir-crucible/plan_executor#142

For the conditional interactions getting filtered out -- we cache the conformance statement. There is a refresh button in the Capability Statement tab, clicking it appears to have updated our cached copy. Could you verify that it is now not filtered out?

Thanks for the report!

from crucible.

Thanks for your quick response.

I refreshed the Capability statement, and it's the same.
Maybe i interpreted incorrectly, what i mean is that in server's Capability Statement, it shows everything correctly, Conditional Update : true and so on. However, when supported only filter is added, all the test cases related conditional create/update X012, X013, X014, X032, X033 and X034 are filtered out.

from crucible.

You are correct, thanks. It doesn't appear that we are properly filtering conditionalUpdate, conditionalRead, conditionalDelete here:

https://github.com/fhir-crucible/crucible/blob/master/app/models/server.rb#L198

We handle operations and interactions, but not the conditionals, which are represented differently in the Capability Statement.

from crucible.

Base Resources/Resource Test Appointment/Appointment: Create New

In request payload, we have "reason" field which has object value - "coding". Isn't "coding" should be into an array?

from crucible.