FHIR Chat · GF#18685 · terminology

Stream: terminology

Topic: GF#18685


view this post on Zulip Grahame Grieve (Sep 29 2018 at 22:42):

@Carol Macumber this is a substantive change. we can't make this one and pass the ballot. Is the invariant worth breaking the ballot over?

view this post on Zulip Grahame Grieve (Oct 01 2018 at 16:02):

ping @Carol Macumber

view this post on Zulip Carol Macumber (Oct 01 2018 at 18:01):

linking to the larger Ballot thread where this one was being discussed. Further, we are discussing this one even more in Vocab M Q3 and/or Tuesday Q3
https://chat.fhir.org/#narrow/stream/48-terminology/subject/Ballot.20Status/near/192162

view this post on Zulip Carol Macumber (Oct 02 2018 at 18:31):

Proposed resolution from Vocab has been drafted on the GF ticket (https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=18685).

Key points of that proposition are summarized here:
1) remove vsd-11 invariant, which is a substantive change
2) update the definition of the valueset status element to indicate
a) the element applies only to the value set definition (ValueSet.compose) and the associated resource metadata
b) the expansion is always considered to be stateless
3) adds similar text to ValueSet.expansion comment around stateless nature of the expansion

The related ticket is also therefore resolved with no changes required
https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=18564

view this post on Zulip Michael Lawley (Nov 08 2018 at 11:10):

@Carol Macumber the original comment in the ticket suggested:
valueset.status in a resource that is only an expansion SHALL be the valueset.status of the valueset resource when the expansion was created
But there are no words to this effect in the changed version.

Is this an oversight?

view this post on Zulip Grahame Grieve (Nov 08 2018 at 12:00):

no there was subsequent text from the committee

view this post on Zulip Carol Macumber (Nov 08 2018 at 14:35):

Correct, we added more detailed text and instead of changing the invariant, we removed it.

view this post on Zulip Michael Lawley (Nov 08 2018 at 21:43):

Thanks. So the current situation is that status is mandatory but does not indicate anything about the expansion, only the definition, and there is no guidance on whether it SHOULD or SHALL be the same value as that of the ValueSet used to generate the expansion.

view this post on Zulip Grahame Grieve (Nov 08 2018 at 22:25):

I think that statement that it's the status of the definition is pretty strong guidance


Last updated: Apr 12 2022 at 19:14 UTC