Stream: implementers
Topic: STU3 CodeSystem & VaueSet
Richard Kavanagh (Apr 15 2016 at 23:32):
In the STU3 CodeSystem resource the concept element has a child element of property ( CodeSystem.concept.property )
Does this need to follow through to the STU3 version of ValueSet?
Also the ValueSet resource does not seem to reference CodeSystem, I assume that's not intended..
Grahame Grieve (Apr 15 2016 at 23:58):
I'm not sure what you mean 'follow through'
Grahame Grieve (Apr 16 2016 at 02:41):
btw, I just added a search parameter on CodeSystem.content - I need it
Richard Kavanagh (Apr 16 2016 at 08:22):
Perhaps I am misunderstanding what the "property" element is for.
Richard Kavanagh (Apr 16 2016 at 08:24):
My thoughts were that if a valueset was to select concepts from a codesystem (via import?) then the complete definition of that concept would be available in the valueset (after expansion).
Richard Kavanagh (Apr 16 2016 at 08:24):
also what about the case of a valueset using an in-line defined code system?
Kevin Mayfield (Apr 16 2016 at 12:24):
@Richard Kavanagh are you looking at putting UK SNOMED into HAPI FHIR Server? If you are, I've done some working in this area with other TRUD downloads (consultants, practice, trusts and gp).
Grahame Grieve (Apr 16 2016 at 14:02):
Richard - we haven't discussed this a lot, but HL7 is not familiar with exposing properties through value sets. The value sets select based on them, but do not expose them. what's your use case?
Grahame Grieve (Apr 16 2016 at 14:02):
there is no longer an inline code system in value set
Richard Kavanagh (Apr 16 2016 at 15:04):
I don't have a specific use case. I'm looking at requirements for a tool. I don't think I understand the use case for 'property'. In CodeSystem.concept there isn't any documentation or examples on the CodeSystem page yet.
Richard Kavanagh (Apr 16 2016 at 15:05):
As for valeSets containing in-line codeSystem - the STU3 valueSet page still asserts this is legal.
Grahame Grieve (Apr 16 2016 at 20:37):
changing from inline codesystem to a code system resource was a massive change for me for the build tool. I spent at least 6 weeks working on it , and I'm still working on it now. The things I had to do for going to a frozen version only just made it. One of the consequences of that is that the narrative was not updated, and is deeply out of sync with the rest of the specification
Richard Kavanagh (Apr 16 2016 at 22:03):
Ok fair enough I'll wait until after the pages have been updated. I appreciate its a busy time at the moment.
Richard Kavanagh (Apr 19 2016 at 06:36):
@Kevin Mayfield Currently we have no ambition to do that, though if we ever do I'll be back in touch :-)
Michael Lawley (Apr 19 2016 at 16:17):
@Grahame Grieve It does expose the "display" property, and if this differs from the CodeSystem's value, then things can get complicated
Grahame Grieve (Apr 19 2016 at 20:02):
well, the fact that it can differ is by design
Michael Lawley (Apr 19 2016 at 22:02):
Yes, it's certainly potentially useful for certain interface terminology issues, but when ValueSet A imports ValueSets B and C which have different display text for the same code, which one goes in the expansion?
Grahame Grieve (Apr 19 2016 at 22:39):
My implementation would pick one at random. We should ask on the vocab list what is correct behaviour
Last updated: Apr 12 2022 at 19:14 UTC
