Add "ResearchStudy" and "ResearchSubject" as an extension/search criteria for all request and event resources

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • FHIR Infrastructure
    • Event Pattern
      Request Pattern
    • Hide

      Will add a standard extension of event-researchstudy that allows pointing to a research study and will deprecate the existing extension on QuestionnaireResponse. Will also define a standard search parameter that allows searching on this extension

      ResearchSubject can be queried through its existing link to Patient, so we don't feel an extension is needed for that now.

      e.g. Observation?patient._has:ResearchSubject:identifier=123

      Show
      Will add a standard extension of event-researchstudy that allows pointing to a research study and will deprecate the existing extension on QuestionnaireResponse. Will also define a standard search parameter that allows searching on this extension ResearchSubject can be queried through its existing link to Patient, so we don't feel an extension is needed for that now. e.g. Observation?patient._has:ResearchSubject:identifier=123
    • John Hatem/Vassil Peytchev: 6-0-0
    • Enhancement
    • Non-substantive
    • STU3

      The ability to filter resources based on "ResearchStudy" and "ResearchSubject" is valuable to academic centers and sponsors involved in the clinical research space.

      Example GET calls utilizing the above might look like this:

      [http://[domain]/fhir/Observations?researchstudy=123|/fhir/Observations?researchstudy=123]

      or

      [http://[domain]/fhir/Observations?researchstudy=123&researchsubject=001|/fhir/Observations?researchstudy=123&researchsubject=001]

      I am not sure if this qualifies as a standard search criteria enhancement or an extension.

            Assignee:
            Unassigned
            Reporter:
            kochm
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: