Stream: implementers
Topic: Profiling and Bundle - Basic questions
Dominik Klein (Nov 10 2020 at 16:25):
Hello!
I'm new to FHIR and I already tried to find answers to my questions by reading the documentation and searching for other related questions. But still I'm quite confused about some really basic things. So maybe you can help me.
In my scenario I have some data and need to create an export based on HL7 FHIR. As far as I have understood everything correctly, it is first necessary to search for existing profiles and extensions on which I can map my data. The first version of my export will only contain very basic information, so I can map everything to the resources Patient, Observation and Questionnaire/questionnaireResponse and collect them in a (collection) bundle.
My questions would be:
- It would be possible to map all my patient-related data on the patient profile. However, I would only use some elements of the profile, e.g. I would not provide a photo or contact. In this case, would it be best practice to create your own profile based on the patient profile and to restrict it, or would it be better to use only the patient profile "as it is" without using every element?
- If I want to export data in a bundle, can I just create a bundle and export it or is it necessary to first create some kind of definition what data will be included in my bundle?
I would appreciate any help. Thanks
Michele Mottini (Nov 10 2020 at 17:13):
No need to create your own profile, just do not populate the elements you do not have (if they are optional in the specifications)
Lloyd McKenzie (Nov 10 2020 at 17:54):
Be cautious about using Questionnaire/QuestionnaireResponse for export unless the importing system expects to receive the data that way. QuestionnaireResponse can be used to convey any kind of information imaginable, but it doesn't do so in a 'standard' way - so if you're exporting medications, allergies, labs, etc. using QuestionnaireResponse, you won't find systems who know how to import data that way - at least not such that it will show up in the appropriate part of their system. If you just want the data to show up as "questionnaire responses" and not as allergy lists, problem lists, lab results, etc. then using Q/QR is fine.
Dominik Klein (Nov 11 2020 at 09:57):
Thanks for your fast reply!
@Michele Mottini Okay, then I will use the patient profile and only use the elements for which I have data. So in general, if I would only set restrictions for one profile, should I rather not use profiling?
@Lloyd McKenzie Thanks for your remarks. I understand the problems with questionnaires. At the moment there is no actual system which will perform any import. It's a general requirement to perform an export based on FHIR and to describe my own export 'specifictaion', so others could use this export later. The data that I have are predefined questions and the given answers to these questions regarding special circumstances of a disease and other not related things. So for me it seems that Q/QR may be the best way to export the data. What do you think?
Is there a standard way to describe an export that is performed with different FHIR profiles in a bundle?
Lloyd McKenzie (Nov 11 2020 at 14:42):
Normally with an export you'd want to produce Observations, Conditions, etc. because those can be imported by others without further negotiation/understanding. Systems can't import 'QuestionnaireResponse' in the same way. If the data isn't a questionnaire in your system, they shouldn't be a questionnaire when exported.
Lin Zhang (Nov 11 2020 at 16:01):
Naybe we need some kind of artefect(s) for fast staging and further cleaning.
Mitul Adhia (Mar 01 2022 at 08:04):
Hello All ,
Have some basic questions of profiling with extensions ..
Say I have an extension with its canonical property : URL : http://xyz.com/fhir/test-extension Version: 1.0 with data type valueInt .
Set of questions
- When I introduce new version of above extension say 2.0 is it allowed to change data type from "int" to "string" ?
- What are the guidance provided only specific to the extension w.r.t the data type and cardinalities ..
Best Regards,
Mitul
Akiluddin Mohammad (Mar 28 2022 at 13:00):
Hi I am trying to load historical data using bundles, and one of the requirement is to retain the historical versions. Can we update FHIR resource version using a bundle? for example - the bundle could have multiple resources of Patient and with Same Resource ID, but different addresses or telecom information
Vivian Neilley (Mar 28 2022 at 13:04):
This probably depends on what FHIR server you're using, I'd check the conformance statement on the server
Akiluddin Mohammad (Mar 28 2022 at 13:07):
Vivian Neilley said:
This probably depends on what FHIR server you're using, I'd check the conformance statement on the server
Hi Vivian, We are using Google FHIR for our implementation.
John Moehrke (Mar 28 2022 at 13:07):
This would be a "history" Bundle. http://hl7.org/fhir/http.html#history
Akiluddin Mohammad (Mar 28 2022 at 13:07):
John Moehrke said:
This would be a "history" Bundle. http://hl7.org/fhir/http.html#history
Thanks John, I will try this
Akiluddin Mohammad (Mar 28 2022 at 13:25):
Akiluddin Mohammad said:
John Moehrke said:
This would be a "history" Bundle. http://hl7.org/fhir/http.html#history
Thanks John, I will try this
history bundle seems to work only for the GET request Patient/<ID>/_history, we want to create a resource(POST or PUT) with all the historical versions in 1 bundle
John Moehrke (Mar 28 2022 at 13:29):
you want to create historic versions? The Bundle is intended to carry the historic versions.. what you do when consuming is not part of the Bundle. Seems you have a receive operation you want to define.
René Spronk (Mar 28 2022 at 13:29):
You can't POST/PUT a set of historic data, you can only GET a copy of the history.
Lloyd McKenzie (Mar 28 2022 at 15:16):
You can POST/PUT historic data, but only through a custom operation.
Akiluddin Mohammad (Mar 28 2022 at 16:19):
Yes, The only way we can do it is - Create separate resources with meta.versionID and POST them individually in the order we received from Source or in the ascending created DateTimestamp order
I have not seen any Bundle.type handling this type of scenario, I am still trying to research on this rule:
Lloyd McKenzie (Mar 28 2022 at 17:12):
POSTing with a meta.versionId will just result in the versionId being ignored. No system is supposed to accept a versionId on a POST - they assign their own version and set their own 'updated' at the time of creation/update.
Last updated: Apr 12 2022 at 19:14 UTC
