Stream: terminology
Topic: ValueSet $expand with specific code system
Yunwei Wang (Jul 03 2018 at 14:23):
Assume I have a valueset which has both Snomed and Loinc in its full expansion. How do I get only Snomed codes in $expand operation. I am considering using context=http://snomed.info/sct parameter. Or I can define my own input parameter in CapabilityStatement.
Grahame Grieve (Jul 03 2018 at 20:04):
right now, there's no way to say this
Grahame Grieve (Jul 03 2018 at 20:04):
sounds like an odd use case to me
Michael Lawley (Jul 03 2018 at 21:11):
You could perhaps define a new ValueSet that includes the original ValueSet and has a filter that restricts system to being http://snomed.info/sct
Grahame Grieve (Jul 04 2018 at 17:42):
actually, this is supported in ExpansionProfile
Rob Hausam (Jul 04 2018 at 18:07):
yes, but we're removing ExpansionProfile
Grahame Grieve (Jul 04 2018 at 19:59):
right. and so I just moved that functionality across. I'm hoping to commit a removed ExpansionProfile in the next 2 hours
Yunwei Wang (Jul 04 2018 at 20:05):
@Rob Hausam Will those parameter in ExpansionProfile be added to $expand operation?
Grahame Grieve (Jul 04 2018 at 20:05):
yes
Yunwei Wang (Jul 04 2018 at 20:09):
I think ExpansionProfile.excludeSystem is close to what I need but not exactly. I may need an extra parameter. To declare additional input parameters, I need update my OperationDefinition instance. Is that all. No extension required?
Grahame Grieve (Jul 04 2018 at 20:15):
no
Grahame Grieve (Jul 04 2018 at 20:15):
why doesn't it do what you want?
Yunwei Wang (Jul 04 2018 at 20:17):
if there are only two code systems, excludeSystem is fine. But if there are more, then I have to exclude the rest one by one. That's why I think it is close but not exactly what I need. I wish there were includeSystem parameter. :)
Grahame Grieve (Jul 04 2018 at 20:22):
hmm what is your use case? Maybe Michael's suggestion above is the go?
Yunwei Wang (Jul 04 2018 at 20:38):
I want to create a ValueSet definition which can be used to generated expansions using different code systems. For example, I can define a value set "diabetes", and I want to generate one expansion for SCT codes and another expansion for ICD-10 code. In my opinion, It is the same ValueSet instance with two different $expand operation results. My problem is, as I mentioned, how to specify which expansion I want when invoke $expand operation.
Peter Jordan (Jul 04 2018 at 20:39):
Maybe this is a case of asking a server to implement something that's easier for a client to do?
Grahame Grieve (Jul 04 2018 at 21:00):
Committing now
Michael Lawley (Jul 06 2018 at 01:38):
If the client is choosing, why can't it just choose the appropriate ValueSet definition? I'm not sure I understand the advantage of having a single ValueSet for this use case
Carol Macumber (Jul 16 2018 at 15:57):
I'm with @Michael Lawley . @Yunwei Wang can you tell us a little more about your use case (if this is still something you still think you need and haven't come up with an acceptable solution)?
Last updated: Apr 12 2022 at 19:14 UTC
