FHIR Chat · Group vs List

Stream: implementers

Topic: Group vs List

Brendan Keeler (May 07 2021 at 23:44):

I see some references to this being a point of discussion, but a search doesn't net me that discussion. When should Group be used vs List?

Brendan Keeler (May 07 2021 at 23:46):

Specific use case: I have a list of patients I believe should be attributed by a payer. I receive that payer's attribution list.

I want to have a Group or List (or another mechanism to group) for "patients on my list but not payer's" and another for "patients on payer's list but not mine"

Josh Mandel (May 08 2021 at 00:18):

The best we got to in discussion was:

For use cases where Group is suitable (e.g. for a list of Patients to be viewed on a dashboard), the Group resource should be preferred to the List resource. The underlying rationale is that a collection of patients, practitioners, etc is likely to be of interest as the subject of a measure, observation, communication, etc, which Group is intended to support.

Josh Mandel (May 08 2021 at 00:18):

See FHIR-27083

Eric Haas (May 08 2021 at 01:08):

have you looked at Da Vinci Member Attribution?

Eric Haas (May 08 2021 at 01:08):

(hint ... it uses Group)

Lloyd McKenzie (May 08 2021 at 01:12):

A Group can be the subject of an action (Procedure, Observation, etc.). A List cannot. A Group's membership is generally defined by criteria, a List by manual curation. A Group need not enumerate its members, a List must.