Stream: implementers
Topic: Composition.section.entry and list
Grahame Grieve (Feb 27 2018 at 21:29):
@Rick Geimer @Brett Marquard @Lloyd McKenzie @Sean McIlvenna @Lisa Nelson @Calvin Beebe We collapsed some of the features of List into Section.entry.... now we have a ballot item GF#14875 from @Claude Nanjo that identifies some confusion about that. So this leads to a question for me: when would it be appropriate for you to reference a List from section.entry? I think we should say something about this in the specification. (in particular, I'd be using a list if I wasn't using a composition.... so when do I keep the list, and when do I collapse it?)
Richard Townley-O'Neill (Feb 28 2018 at 00:44):
I'd say that when List.identifier is important it is worth keeping the list.
Brett Marquard (Feb 28 2018 at 13:22):
comment appears to be from @Mark Kramer . Do we know of anyone using the list resource in section.entry?
Eric Haas (Feb 28 2018 at 13:44):
I'd have to agree with Mark, using composition for representing a catalog really highlights how List like Composition is.
John Moehrke (Feb 28 2018 at 14:06):
Or, how more appropriate the catalog could have been addressed with simply a List rather than a Composition...
Eric Haas (Feb 28 2018 at 15:50):
... or how Composition like List is. List was there first :-)
Grahame Grieve (Feb 28 2018 at 15:53):
I don't understand why catalog uses composition.
Lloyd McKenzie (Feb 28 2018 at 16:34):
They want to organize the presentation into sections and sub-sections - as you would find in a real catalogue. Which is fine. Except that the knowledge of the catalogue needs to exist even if there's no Composition.
Eric Haas (Feb 28 2018 at 16:34):
(Brett hates when I say this) but when you strip out all the Document paradigm stuff its a like a book's Table of contents. BTW I did not make that decision, but when I learned about it, it did make me look at Composition as just another prettier way to wrap and relate a bunch of resources and why I totally agree with Mark.
Grahame Grieve (Feb 28 2018 at 16:36):
so it makes total sense to have a ToC in a composition to me. but I agree with Lloyd
Eric Haas (Feb 28 2018 at 16:37):
I don't understand what knowledge bit means. can you dumb it down for me
Eric Haas (Feb 28 2018 at 16:39):
because the catalog entries still exist, but you need to organize them for ease of use.
Lloyd McKenzie (Feb 28 2018 at 16:55):
It means that all of the information you might glean from a catalog - price, relationships, availability, pre-reqs, etc. - need to live outside of Composition. And you need to be able to share and query all of that information without any Composition existing. So, for example, if I want to know what meds are covered by this payor in 2018, the resources need to be populated such that I can find that out without having to retrieve a Composition with the title "2018 covered meds"
Eric Haas (Feb 28 2018 at 16:58):
ty
Last updated: Apr 12 2022 at 19:14 UTC
