Stream: implementers
Topic: PDEX Plan Net exact and contains modifiers for token
Yengibar Manasyan (Jun 02 2020 at 16:40):
Hi everyone,
We are implementing PDEX PlanNet and we see these 6 (2 searches for 3 resources) search parameters:
https://build.fhir.org/ig/HL7/davinci-pdex-plan-net/SearchParameter-plannet-available-days.html
https://build.fhir.org/ig/HL7/davinci-pdex-plan-net/SearchParameter-plannet-available-start-time.html
Here we can see exact and contains modifiers for token parameters. In HL7 FHIR search page we can't find these 2 modifiers for token types. Based on the description in the search page, by token parameters must be done close to the exact-match searches. Meanwhile seems I understand your motivation for doing so.
But shouldn't we either use string parameters for these searches with exact and contains modifiers or token parameters without exact and contains modifiers?
@Saul Kravitz
Saul Kravitz (Jun 02 2020 at 17:08):
Thanks for the input.
This is probably an error on my part. I created a jira issue -- https://jira.hl7.org/browse/FHIR-27760
There is strong probability that these search params may not make it into the published version. No decisions yet, but we are trying to prune interface to minimize server burden.
Yengibar Manasyan (Jun 02 2020 at 17:45):
@Saul Kravitz when are you going to publish it, maybe you have an approximate date for the publication?
Saul Kravitz (Jun 02 2020 at 18:02):
I wish it had been published months ago.....
We do not have a date, other than ASAP.... Sorry.
I hope to have the search parameters and capability statement updated in the CI build (not published) within the next 2 weeks.
Yengibar Manasyan (Jun 02 2020 at 18:08):
@Saul Kravitz does it mean that you also are going to check this search parameter?
https://build.fhir.org/ig/HL7/davinci-pdex-plan-net/SearchParameter-plannet-available-end-time.html
It's for 3 different resources combined into 1 search parameter. I hope it will at least be split into 3 search parameters. Meanwhile, I can't judge should it be there at all or it's not necessary.
Saul Kravitz (Jun 02 2020 at 18:14):
Yes.
Curious, why do you prefer three different SPs, instead of 1 associated with 3 profiles?
I thought it would be easier to understand by making the common queries a single SP....so I was well intentioned.
Yengibar Manasyan (Jun 02 2020 at 18:29):
We initially were confused because of the expression. But later on, we understood your intention. Also, we built an application that is taking JSON Definition directory (the unarchived version of JSON Definitions (zip)) and generating reports for us, in my opinion having a unified and simple structure is better, more clear and easy to use for implementers.
Saul Kravitz (Jun 02 2020 at 18:36):
I find the way that most IGs present search parameters very confusing. So I built this page for myself, thinking that others would benefit as well: https://build.fhir.org/ig/HL7/davinci-pdex-plan-net/searchParameters.html. This shows which SPs apply to which Profiles. Obviously, the new/improved capability statement and the SPs themselves show the same thing, but for humans I thought this was helpful.
I'm happy to get feedback from someone who is actually trying to CONSUME the IG as an implementer, rather than just criticizing as a reviewer with a theoretical connection to the actual implementation.
Yengibar Manasyan (Jun 02 2020 at 20:29):
We are actively using that page, it's really helpful, thank you.
Last updated: Apr 12 2022 at 19:14 UTC
