Stream: terminology
Topic: GF#18689
Grahame Grieve (Sep 30 2018 at 00:13):
@Carol Macumber why do you say, for GF#18689 , that
once inactive, it can no longer be used to create new content)
I can't see why you say that
Carol Macumber (Sep 30 2018 at 18:09):
The expirationDate extension definition states:
"The date when the value set version is no longer expected to be used to create new content. This is the first date-time when the value set version becomes Inactive, so this value SHALL present on all Inactive value set versions. "
and comments:
"An Inactive value set version may no longer be used to create new content"
I concede, however, if the status is changed to active, then the vs could be used to create new content.
I don't think i captured the issue accurately in my original text. So...more specifically, in comparing VSDs required Activity Status Date element to the available FHIR extensions (expirationDate) it was noticed that this expirationDate extension only covers one state transition (active to inactive). We either need additional extensions to cover other state transitions OR, this one could be updated to cover all state transitions (active to retired, draft to active, unknown t
As a side note, since valid status values are restricted to draft, active, retired and unknown, we should also update verbiage to say retired instead of inactive to be consistent.
Copying VSD Alignment team
@Ted Klein @Robert McClure @Carmela Couderc @Rob Hausam
Grahame Grieve (Sep 30 2018 at 18:24):
ok so we update the task to match activity status date?
Robert McClure (Sep 30 2018 at 18:33):
I agree, but we need to change the name of the extension because this is no longer just "expiration date" but is when the status changes to any status. Extension: activityStatusDate?
Grahame Grieve (Sep 30 2018 at 19:38):
right that's what I meant - sorry I wasn't clear
Grahame Grieve (Oct 01 2018 at 16:04):
ok updated the task
Last updated: Apr 12 2022 at 19:14 UTC
