Stream: terminology
Topic: GF#16431 - ValueSet.status
Grahame Grieve (Jul 27 2018 at 02:07):
We agree to compare VSD status and ValueSet.status for GF#16431:
- Preliminary: State during which time the Value Set Definition version is being drafted and is not available for use. The element Workflow Status will carry additional information regarding pre-Active state.
- Active: State during which the Value Set Definition version is available for use. The Activity Status Date associated with this status is known as the “Effective Date”.
- Inactive: State indicating that the Value Set Definition version is no longer available for use in creating new content. The Activity Status Date associated with this status is known as the “Expiration Date”.
- Deleted: State intended to be used to remove a Value Set Definition from use and view in a repository and is only possible if the Value Set was never Active (i.e., can only transition from Preliminary).
Existing status (common to all conformance resources):
- draft Draft This resource is still under development and is not yet considered to be ready for normal use. ~draft
- active Active This resource is ready for normal use. ~active
- retired Retired This resource has been withdrawn or superseded and should no longer be used. ~inactive
- unknown Unknown The authoring system does not know which of the status values currently applies for this resource. Note: This concept is not to be used for "other" - one of the listed statuses is presumed to apply, it's just not known which one.
Comments:
- unknown has no equivalent in VSD, but since VSD makes it a required element, VSD might need it
- draft = Preliminary - definitions seem functionally equivalent to me
- active = Active - definitions seem functionally equivalent to me
- retired = inactive - definitions are different in as much as the definition includes 'creating new content'. I think that the VSD is wrong on this, because it relates to assumptions outside the workflow of the individual resource and what it means to replace it or not. FHIR has a take on this which is thoroughly discussed and common across all the conformance resources. So I don't want to change the general FHIR definition
- deleted -> inactive - the definition of this in VSD is related to the assumptions built into the previous one, so same comments.
It's hard to comment about the comments that are part of the definition, because of the common sharing of status elements in FHIR. I reviewed them and there's no consistent mapping between the resources and the elements for several reasons.
So I don't see any solid candidate for change. @Carmela Couderc
Robert McClure (Jul 29 2018 at 18:52):
The problem with "has been withdrawn or superseded and should no longer be used" is that even though the version marked "INACTIVE" is not to be used for new content creation because there is a newer version available, the INACTIVE version can still be used to generate expansions that were in use when it was ACTIVE for comparisons, data retrieval, and legal reasons. So yes, it can be used for those reasons.
I'm not sure what your point is about DELETED. It's valid and not obviously not the same as INACTIVE
Grahame Grieve (Jul 29 2018 at 19:02):
So you can't generate an expansion for comparison purposes etc on a deleted value set?
Robert McClure (Jul 29 2018 at 19:07):
Practically, Active = Published and available for use (hence the definition.) So a deleted version would not have been available for use. The only entities that could do an expansion based on it would be server dependent based on allowed access to never active, pre-publication content. So for some, yes, they could do a compare, but the expectation is that it's not a value set non-authors could find.
Grahame Grieve (Jul 29 2018 at 19:34):
ok so my comment about deleted was wrong; it corresponds to actually being deleted in FHIR, so we don't have a status for that.
Last updated: Apr 12 2022 at 19:14 UTC
