FHIR Chat · Flagging potential redundancy in Observation · Orders and Observation WG

Stream: Orders and Observation WG

Topic: Flagging potential redundancy in Observation


view this post on Zulip Jay Lyle (Mar 16 2022 at 13:45):

We are implementing a lung cancer screening app, which will collect answers to several questions. Some of these answers might be inferred from or represented in other resources, if and when those resources are available, but we need to send the Observations irrespective of that availability. We don't, however, want to repeat information without clear indication that there is repetition.

So, for instance, the "size of highest risk nodule" observation might also employ the "derivedFrom" relationship to an ImagingStudy.

The problem we face is that some observations represent information in resources not included in the "derivedFrom" scope.

Next scan timeframe: this may be represented in a ServiceRequest
Provider notification: this may be represented in a Communication

Would this be the place to use the relatedArtifact extension? supportingInfo?


Last updated: Apr 12 2022 at 19:14 UTC