Stream: implementers
Topic: SDC implementation Guide
Grahame Grieve (Feb 06 2018 at 23:56):
A new round of work is beginning on the SDC implementation guide. The SDC IG community has generally been dominated by the research community looking to gather data to use in secondary data analysis.
Grahame Grieve (Feb 06 2018 at 23:57):
But forms and questionnaires permeate healthcare: intake forms, psychological assessments, surgical checklists, eligibility checks, public health reporting forms, case report forms – the type and variety are nearly limitless. Forms provide for efficient, tightly controlled data capture. They can also be used for information display. In FHIR, they act as a shareable, configurable user-interface for data.
The challenge with forms is getting information into them and out of them. Without standardized logic embedded in the form or customization of the EHR application, there’s no way to automatically fill out the form with information that’s already been captured. The result is that end-users must re-key the same information multiple times, causing issues with efficiency and data quality. Also, once data has been captured by a form, there’s often a need to expose it so that it can be queried as discrete observations, medications, allergies, etc.
SDC phase 2 will establish expectations for rendering of questionnaires and will also define how forms can be populated from existing EHR data and also allow extraction of EHR data into a more queriable and exchangeable form.
Grahame Grieve (Feb 06 2018 at 23:58):
I believe that all health record systems vendors should be interested in the SDC work - it's not purely a research interest. If you're interested in beng involved, please reach out to @Lloyd McKenzie so he can include you in discussions about telecom times, and other participation forum options. thanks
Jeremy Ward (Feb 07 2018 at 20:51):
Currently, we are using custom logic to handle automatically filling data into forms. We've experimented with QuestionnaireResponses and using the linkId as a mapping resource to specific fhir resources. Has the SDC community solved this problem yet?
Grahame Grieve (Feb 07 2018 at 20:51):
have you looked at Questionnaire.item.definition?
Lloyd McKenzie (Feb 07 2018 at 21:03):
linkId is intended to tie the QuestionnairResponse response to the Questionnaire, not to link questions to data sources/targets. item.definition is one mechanism, though we're also looking at more computable mechanisms such as StructureMap or embedded FHIRPath mappings.
Jeremy Ward (Feb 07 2018 at 21:13):
Do you have any examples of a useful Questionnaire.item.definition ?
Lloyd McKenzie (Feb 07 2018 at 22:37):
References to LOINC codes are one option
Lloyd McKenzie (Feb 07 2018 at 22:38):
http://hl7.org/fhir/us/sdc/questionnaire-sdc-profile-example-ussg-fht.xml.html
Brian Postlethwaite (Feb 08 2018 at 01:46):
That example doesn't have item.definition values in it (but does have LOINC)
Lloyd McKenzie (Feb 08 2018 at 03:15):
Umm, I see <definition elements all over the place in it...
Brian Postlethwaite (Feb 09 2018 at 23:10):
Those don't look like valid definition properties, the look like the old DataElement format, not the new ElementDefinition format (http://hl7.org/fhir/stu3/questionnaire.html#2.38.5.4).
e.g. http://hl7.org/fhir/StructureDefinition/Observation#Observation.value[x]
(on re-reading that section it does talk about the implicitly defined LOINC codes part that I missed)
Lloyd McKenzie (Feb 16 2018 at 00:59):
The SDC calls have now been scheduled. They will run at 5pm Eastern on Thursdays. Call information can be found here. Discussion will happen on the new #questionnaire stream. Subscribe to it if you're interested in following the project's progress.
Lloyd McKenzie (Feb 22 2018 at 02:11):
Reminder that the SDC calls will start tomorrow.
Last updated: Apr 12 2022 at 19:14 UTC
