Stream: genomics/committers
Topic: Figure 3: performer/requester
Jamie Jones (Jul 29 2019 at 16:46):
Looking at cleaning up figure 3:
pasted image
I fixed some issues on cardinalities, but the question remains around performer/requester
Jamie Jones (Jul 29 2019 at 16:48):
based off discussion with eMerge (https://chat.fhir.org/#narrow/stream/189875-genomics-.2F.20eMerge.20Pilot/topic/performer), wondering if we still mean to restrict any of the potential references in the rightmost box. Proposed solution:
pasted image
Jamie Jones (Jul 29 2019 at 16:54):
It's actually pretty messy up top-right too: for our Task (and also Specimen) profiles we are restricting for/subject to only Patient, but DiagnosticReport, ServiceRequest, and Observations we can refer to Groups or Locations instead.
Jamie Jones (Jul 29 2019 at 16:57):
It is also unclear as to why any of the genetic observations are broken up: they all now refer to specimen in the same cardinality and clutter the diagram.
Jamie Jones (Jul 29 2019 at 17:15):
Might suggest this:
pasted image
Jamie Jones (Jul 29 2019 at 17:24):
Although adding the "requester" reference from the servicereq to org may be confusing as it likely won't be the same org/etc as in the other references (though already the lab performing the Observations may not be the same org as the recommended actioners...
Bret H (Aug 21 2019 at 03:37):
pardon, so the goal is to show how requester and performer fit into our IG? hmm, those are basic functions of the Observation Resource. can you help me understand the need to show them int he figure? (again, pardon for coming in late)
Jamie Jones (Aug 21 2019 at 14:02):
We are constraining the allowed reference types and I wondered if it's an oversight
Last updated: Apr 12 2022 at 19:14 UTC
