yunwwang
commented
2 years ago My preference is that when server support DAR binding for an element, then server should support searching with DAR code. This is the same as using local coding. Assume a server supports local code "my-category" in additional to code "clinical-note". Server need to support searching with "my-category". Otherwise, client could not get resources with that category. DAR code, technically, falls into the same "extensive" codes beyond what specified in valueset. What if the client "wants" to see resources with DAR code so client can do something, for example fixing those.
As for Inferno testing, Inferno does not query DAR value intentionally. Inferno uses the category code from the first resource to build search query. Here, the first resource happened to have that DAR code.
We could add a logic to say that if the code is DAR then skip this resource and look next one.
bh021790
Thank you for reporting a possible bug in Inferno! Please fill in as much of the template below as you can.
Subject of the issue This may be more of a question: Should data-absent-reason codes be included as supported search parameters for a given element?
Currently we have a test patient with a document that we populate with an 'unknown' DAR code since it is not populated. So when the earlier Inferno tests search by patient, the subsequent test then makes an attempt to search for that patient+category=unknown; DocumentReference?category=unknown&patient=12742542
I'm wondering if this is something we just need to enhance our APIs to support or if Inferno should really be testing these scenarios. Not sure if this was an intended workflow based on the US Core profiles (but can also see the value in us supportingif we need to)
Your environment
Steps to reproduce Tell us how to reproduce this issue.
Include:
The selected test suite ONC Program
The URL of the FHIR server being tested https://fhir-open.cerner.com/r4/ec2458f2-1e24-41c8-b71b-0e701af7583d/
The Test ID, if it's a problem with a specific test. USCDR-05
Any required configuration options (client ID, client secret, etc.) NA
Anything else needed to make the issue occur. Patient ID: 12742542 https://fhir-open.cerner.com/r4/ec2458f2-1e24-41c8-b71b-0e701af7583d/DocumentReference?category=unknown&patient=12742542
Expected behavior This is more of my question: should we be supporting a search by a DAR code? And should Inferno test for this?
Actual behavior We do not support this today but Inferno tests for it.