There is incorrect behavior for test 2.1.03 - The server is using FHIR R4. It appears this test can be passed with any URL because the issue lies in the fhir_client.
Here is an example of the report: Inferno QA Report.
I used google.com as a server to check, and please look at the result for test 2.1.03. As you can see, this test passed.
This test uses the method fhir_client.detect_version:
|
server_version = fhir_client.detect_version.to_s.upcase |
But let's examine how this method is implemented:
https://github.com/fhir-crucible/fhir_client/blob/b1fff3131ed293eaec1b92885c23645963d9d0a9/lib/fhir_client/client.rb#L94
It seems this method will return R4 when the CapabilityStatement resource is exactly R4 and also when the CapabilityStatement does not exist.
For this particular test, I suggest adding the following extra actions:
- Request the capability statement.
- Check the response code.
- Verify that it is definitely of the CapabilityStatement type.
There is incorrect behavior for test 2.1.03 - The server is using FHIR R4. It appears this test can be passed with any URL because the issue lies in the
fhir_client.Here is an example of the report: Inferno QA Report.
I used google.com as a server to check, and please look at the result for test 2.1.03. As you can see, this test passed.
This test uses the method fhir_client.detect_version:
us-core-test-kit/lib/us_core_test_kit/custom_groups/capability_statement/fhir_version_test.rb
Line 11 in 7441d56
But let's examine how this method is implemented:
https://github.com/fhir-crucible/fhir_client/blob/b1fff3131ed293eaec1b92885c23645963d9d0a9/lib/fhir_client/client.rb#L94
It seems this method will return R4 when the CapabilityStatement resource is exactly R4 and also when the CapabilityStatement does not exist.
For this particular test, I suggest adding the following extra actions: