FHIR Chat · Refining Composition summary elements · implementers

Stream: implementers

Topic: Refining Composition summary elements


view this post on Zulip Grahame Grieve (Feb 19 2018 at 00:09):

GF#13855 proposes to refine the list of summary elements on Composition. The list in task means that the following elements won't be summary elements that aren't now, and for which I think that's wrong:

  • Composition.class
  • Composition.encounter
  • Composition.date
  • Composition.title
  • Composition.relatesTo / .relatesTo.code
  • Composition.event.period

but actually, reviewing the disposition leaves me confused, since it doesn't say which resource it's about but it talks about DocumentReference elements even though the task says it's about Composition elements.

@Sean McIlvenna @Lisa Nelson @Rick Geimer

view this post on Zulip John Moehrke (Feb 19 2018 at 13:40):

This one points at the fact that GF#12949 was disposed. But seems the rational for Composition should be very different than the rational for DocumentReference. I would agree that this disposition seems to be the one from DocumentReference. Should this would be in th approved state, or that which needs discussion leading to a vote?

view this post on Zulip Grahame Grieve (Feb 19 2018 at 19:45):

it says disposed. Have to hear from the SD guys

view this post on Zulip Grahame Grieve (Mar 14 2018 at 00:20):

@Sean McIlvenna @Lisa Nelson @Rick Geimer ping on this

view this post on Zulip Sean McIlvenna (Mar 14 2018 at 15:47):

Not sure what @John Moehrke means by "disposed"... Feb 1st feels like forever ago. my memory tells me we were focused on changing Composition's summary fields. But, reading the resolution and details makes me question that. I'll bring this ticket up on tomorrow's SD call (which I believe @Lisa Nelson is planning to attend) and see if I can get some better notes about it.


Last updated: Apr 12 2022 at 19:14 UTC