Stream: questionnaire
Topic: How to associate a questionnaire to a research protocol?
Robinette Renner (Aug 15 2018 at 09:16):
I need to indicate which protocol a questionnaire is associated with and provide additional details about the protocol such as the lead organization and phase. The researchStudy resource will work to capture the protocol information. Is there a way to associate a questionnaire instance to a researchStudy instance?
Eric Haas (Aug 15 2018 at 13:57):
useContext, but i the USageContextType valueset doesn't really have the correct concept for this use case, I have another chat asking about that - but no response. https://chat.fhir.org/#narrow/stream/4-implementers/topic/UsageContextType
Lloyd McKenzie (Aug 15 2018 at 14:28):
usageContext wouldn't be appropriate - it's essentially just sophisticated keywords, not links. We do have http://build.fhir.org/extension-questionnaire-studyprotocolidentifier.html, which should probably be changed to a Reference(StudyProtocol). Too late for that now, but submit a change request and we can do it post-freeze.
Robinette Renner (Aug 15 2018 at 14:33):
Sounds good. I will submit a change request.
Eric Haas (Aug 15 2018 at 16:42):
Why not useContext? "The content was developed with a focus and intent of supporting the contexts that are listed. These terms may be used to assist with indexing and searching for appropriate questionnaire instances." sound appropriate to me???
Eric Haas (Aug 15 2018 at 16:43):
the context is project-x ... Canadian English is not that different is it :-)
Eric Haas (Aug 15 2018 at 16:44):
If not then I believe useContext needs a clearer definition to differentiate from all those other contexts out there.
Lloyd McKenzie (Aug 15 2018 at 18:38):
useContext doesn't point to resources. It just provides codes. So you can say "this is for payers" or "this is for cats" or "this is for inpatient". You can't say "this is for research study 123".
Eric Haas (Aug 15 2018 at 20:01):
why not make study123 a code or use string?
Eric Haas (Aug 15 2018 at 20:02):
but I see no reason why it could not be extended to support resources
Eric Haas (Aug 15 2018 at 20:02):
The definition makes it sound like it should cover study123. So the definition makes it is sounds like a good fit. ....and. important to be able to fetch and search all Q belonging to study123
Lloyd McKenzie (Aug 15 2018 at 20:34):
useContext is for keywords, not relationships
Lloyd McKenzie (Aug 15 2018 at 20:34):
If that's not clear, then the definition of useContext needs to be further clarified
Robinette Renner (Aug 16 2018 at 12:21):
The problem is that I need to record more information about the study then just the name, such as organization and phase. The researchStudy resource captures the information that I need. Pointing a questionnaire to a researchStudy resource seems to be the most efficient approach.
Lloyd McKenzie (Aug 16 2018 at 14:24):
Absolutely - which is why we should update the extension to be a proper reference.
Eric Haas (Aug 16 2018 at 15:42):
or a code (string) so we need two extensions/or complex extension
Lloyd McKenzie (Aug 16 2018 at 15:45):
Why would you ever reference a research protocol as a code? You could certainly do it as an identifier or as a name - but Reference can handle both of those.
Lloyd McKenzie (Aug 16 2018 at 15:45):
A research study is an instance, not a concept...
Eric Haas (Aug 16 2018 at 18:02):
So I have been asked about whether you want to fetch from a Questionnaire bank all the Qs for project X or program Y? does it have to be a resource?
Lloyd McKenzie (Aug 16 2018 at 18:41):
Those could potentially be codes.
Last updated: Apr 12 2022 at 19:14 UTC
