Loading...

XML

Word

Printable

JSON

Specification:

FHIR Core (FHIR)
Raised in Version:

STU3
Work Group:

FHIR Infrastructure
Outstanding Negatives:
STU
Related Artifact(s):

Group
Resolution Description:

Hide

Add to the description of Group that if both are present, then the members are the individuals who were found who met the characteristic. It's possible that there might be other candidate members who meet the characteristic and aren't (yet) in the list. But you can't have members who don't meet the listed characteristics.

Show
Add to the description of Group that if both are present, then the members are the individuals who were found who met the characteristic. It's possible that there might be other candidate members who meet the characteristic and aren't (yet) in the list. But you can't have members who don't meet the listed characteristics.
Resolution Vote:
Lloyd McKenzie/Grahame Grieve: 6-0-0
Change Category:
Enhancement
Change Impact:
Non-substantive
Applied for Version:

STU3

No invariant prevents the use of Group.characteristic alongside Group.member. If both are supplied, what does it mean? Some possibilities:

1. Here is a list of members (explicitly, by .member), and the things they have in common (explicitly, by .characteristic)

2. Here is a list of rules (.characteristic) and the members that currently match the rules (by .member)

3. Here is a list of members (implicitly, by .characteristic) and some more members (explicitly, by .member)

Which if these is correct? Should we stipulate? Is there a single "best" answer?

(Mixing rules and data is hard!)

is voted on by

BALLOT-6415 Negative - Josh Mandel : 2018-Sep-FHIR R4