We have tried querying Observation entries with examples like https://fhir.immport.org/fhir/Observation?code=FEV. We received good records like the one below. However, our question is whether it is possible to link an Observation to a ResearchStudy from which the observation value belongs to.
We also tried the KidsFirst FHIR server and noticed that their Observation entry includes the study in the meta tag( example below). This provides a way to link the Observation to the study it originates from. As we know, the FHIR Observation resource links to Patient, but not to ResearchSubject. Including the study identifier in the meta tag seems like a useful workaround.
In dbGaP, the same individual can be enrolled in completely different studies (not merely parent and sub-studies). Additionally, the same person in different studies can have distinct "observed" values for equivalent phenotypic measures. Therefore, it’s crucial to be able to link an Observation to the specific study it came from. dbGaP uses "study-specific phenotype variable (phv)" as a way to link an Observation to a study ( see example below). However, we are open to exploring the KidsFirst approach of adding the study tag in the meta tag of Observation.
We would appreciate your insights on this matter. We hope this issue helps gather feedback and action items. Thank you!
What were you reviewing?
Thanks for the very nice IG!
We have tried querying Observation entries with examples like https://fhir.immport.org/fhir/Observation?code =FEV. We received good records like the one below. However, our question is whether it is possible to link an Observation to a ResearchStudy from which the observation value belongs to.
We also tried the KidsFirst FHIR server and noticed that their Observation entry includes the study in the meta tag( example below). This provides a way to link the Observation to the study it originates from. As we know, the FHIR Observation resource links to Patient, but not to ResearchSubject. Including the study identifier in the meta tag seems like a useful workaround.
In dbGaP, the same individual can be enrolled in completely different studies (not merely parent and sub-studies). Additionally, the same person in different studies can have distinct "observed" values for equivalent phenotypic measures. Therefore, it’s crucial to be able to link an Observation to the specific study it came from. dbGaP uses "study-specific phenotype variable (phv)" as a way to link an Observation to a study ( see example below). However, we are open to exploring the KidsFirst approach of adding the study tag in the meta tag of Observation.
We would appreciate your insights on this matter. We hope this issue helps gather feedback and action items. Thank you!
ImmPort Observation: https://fhir.immport.org/fhir/Observation?code:text=FEV
KidsFirst bservation: https://kf-api-fhir-service.kidsfirstdrc.org
dbGaP example Observation (synthetic data server): https://dbgap-api.ncbi.nlm.nih.gov/fhir-jpa-pilot/x1/Observation?code:text=FEV&_count=2 note: phv00508498 can be used to find the specific study it is from.
Thank you for looking at this!