Stream: terminology
Topic: ValueSet validate-code and date
Jack Bowie (Aug 07 2018 at 21:17):
Does the date parameter in ValueSet $validate-code refer to a date relative to the proposed code's CodeSystem or a date relative to the specified ValueSet? (See the description of date in ValueSet $expand for a possible explanation of my confusion.)
Russ Hamm (Aug 08 2018 at 18:18):
Good question Jack. I interpret it as relative to the value set (i.e., was the code a valid member of the value set on the specified date). Awaiting other responses.
Rob Hausam (Aug 08 2018 at 19:48):
Yes, I agree with Russ. It would be validating against the set of codes that would have been members of this value set (based on the specified value set definition) as of that date. There's also another wrinkle in this which I've just started to think about. In the case where the value set definition itself changed between the date specified in the parameter and the current time (this is assuming that it is the same value set - i.e as identified by the specified canonical url) what should be the validation behavior? Should the server perform the validation using the earlier definition which would have been in effect on that date (if known and available, and if that's not the case return an error)? Or should it use the current definition and validate based on what would have been available in the value set if the current definition had been used with the terminology content that was known to be available on the specified date? Which of those assumptions and behaviors would be the most useful when I'm asking the server this question now?
Grahame Grieve (Aug 08 2018 at 20:07):
actually, the definition it says 'this is the date of the record' (not the date of the value set or the code system). Mainly it's about deprecated codes, ones that you can't use anymore ... but you're doing historical work
Michael Lawley (Aug 10 2018 at 08:29):
These questions are why I dislike this parameter. In the end the only way to clearly ask the question is to specify versions not dates
Grahame Grieve (Aug 10 2018 at 08:46):
right. but sometimes, clarity is not in the real world
Jack Bowie (Aug 10 2018 at 15:46):
FYI, I currently use date as a proxy for version. I find the version that is/was active for the given date and validate (or expand, etc.) based on that. If you specify both a version and a date and they are inconsistent its an error.
Last updated: Apr 12 2022 at 19:14 UTC
