FHIR Chat · Logic and Content Duplication

Stream: questionnaire

Topic: Logic and Content Duplication

Brian Kaney (Feb 17 2021 at 16:27):

Wanted to get some thoughts from the community on a few patterns we have been observing with questionnaires for AOE (ask at order entry) use-cases.

With the combination of 1) profiles for request resource (e.g. medication request, service request, etc), 2) definitional artifacts (e.g. Activity Definitions) and 3) AOE surveys - we are finding a fair amount of duplication of logic (constraint and validation between SDC/questionnaires and FHIR profiles for those request resources; valueset and terminology bindings; and $apply rules / dynamicValue).

Also finding we have duplication of questionnaire items (want to use same items/groups in multiple questionnaires).

Anyone having similar experiences? Any ideas on how these sorts of things could be more reusable? Thanks!

Paul Lynch (Feb 17 2021 at 20:03):

Brian Kaney said:

Also finding we have duplication of questionnaire items (want to use same items/groups in multiple questionnaires).

It has been a while, but I handled that situation in the past with server-side-include templates.

Lloyd McKenzie (Feb 17 2021 at 20:54):

You can define your questionnaires by pointing to the profile as the item definition and then 'generate' a more fully-fleshed out Questionnaire that propagates the text, data type, binding, etc. across. I thought we'd agreed to define a standard operation for this in SDC, but don't remember for certain

Ilya Beda (Feb 18 2021 at 18:53):

Hi @Brian Kaney

Here are some useful links for modularized questionnaires.
https://jira.hl7.org/browse/FHIR-27049
https://jira.hl7.org/browse/FHIR-22356
https://confluence.hl7.org/display/FHIRI/Prefix-based+Modularized+Questionnaires

Brian Kaney (Feb 22 2021 at 21:05):

Thanks for the ideas and links folks!

Brian Kaney (Feb 22 2021 at 21:10):

I like that idea of using a profile and generate. I don't see an operation as you describe @Lloyd McKenzie in the current http://build.fhir.org/ig/HL7/sdc/artifacts.html#behavior-operation-definitions - but would be interested if there is one is in the works...

Brian Kaney (Feb 22 2021 at 21:16):

Oh I think I see the proposed $assemble operation assembledFrom extension, reading the confluence notes.

Bryn Rhodes (Feb 23 2021 at 00:55):

If you’re using CQL for the logic you should be able to consolidate with a shared library. There’s also a proposal in the works for a FHIRPath library profile.

Brian Kaney (Feb 25 2021 at 16:55):

Thanks @Bryn Rhodes - I wonder if there is a way to share FHIRPath logic in a similar way -- for instance we have similar logic in our Questionnnaire AOE constraints (that also exist in our profiles for the eventual (service|medication)request).