Stream: implementers
Topic: Description in codesystem
Mounika (Jun 28 2017 at 07:13):
Hi all, When I am trying to retrieve the code using the description from the resource CodeSystem, an error is getting displayed as in the screenshot below. How can I fix it? Is there any way to retrieve the code on the basis of CodeSystem.description in advanced rest client?
Mounika (Jun 28 2017 at 07:13):
Vadim Peretokin (Jun 28 2017 at 07:38):
What is the exact request you're using?
Mounika (Jun 28 2017 at 08:12):
GET http://192.168.128.20:8080/fhir/baseDstu3/CodeSystem/$lookup?system=http://loinc.org&description=Heart failure in last 7 days
Vadim Peretokin (Jun 28 2017 at 08:52):
@Mounika K If you look at http://hl7.org/fhir/codesystem-operations.html#lookup, you'll see that system is a valid In Parameter, but description isn't.
In general, a $lookup is - "given a code, give me all information about it". A description as lookup won't work because more than one code could have the same description and so on.
Mounika (Jun 28 2017 at 09:01):
Okay @Vadim Peretokin But, display parameter which is included in http://hl7.org/fhir/codesystem-operations.html#lookup is also not working
Vadim Peretokin (Jun 28 2017 at 09:05):
It's an Out Parameter - one you get from such a query, not an In Parameter :)
Vadim Peretokin (Jun 28 2017 at 09:06):
The table is a bit hard to see I agree, in/out parameter heads should stand out more
Mounika (Jun 28 2017 at 09:10):
Okay. We want to add some code decription in the URL.Then which paramter we should use?
Vadim Peretokin (Jun 28 2017 at 09:11):
What are you trying to do - find a code given a description?
Mounika (Jun 28 2017 at 09:12):
yes
Vadim Peretokin (Jun 28 2017 at 09:13):
Is this to implement in your own FHIR server?
Mounika (Jun 28 2017 at 09:15):
yes. In our server. Is there any way ?
Vadim Peretokin (Jun 28 2017 at 09:15):
Yeah, actually you could define a custom operation on the CodeSystem that's a description-based lookup
Vadim Peretokin (Jun 28 2017 at 09:16):
You could implement it, document it using OperationDefinition and then advertise that you support it in your CapabilityStatement
Vadim Peretokin (Jun 28 2017 at 09:17):
That said are you sure you want to do this - can you turn the problem around somehow?
Mounika (Jun 28 2017 at 09:19):
Sorry, I didn't get you.Could you please elaborate ?
Vadim Peretokin (Jun 28 2017 at 09:21):
You can't use $lookup, it's designed to return zero or 1 code only. With your description-based lookup, there's a chance you might get more than 1 code with the same description - because FHIR allows that, right?
Vadim Peretokin (Jun 28 2017 at 09:22):
So you can create your own operation, lets say $lookupDescription
Mounika (Jun 28 2017 at 09:23):
Yeah okay. How can I do that
Vadim Peretokin (Jun 28 2017 at 09:25):
3 steps:
1) code it in your FHIR server. Nothing prohibits you from just adding new operations
2) you've coded in your custom operation and it works, but nobody knows how to use it - what parameters it accepts and such. Describe your operation using a OperationDefinition
3) you now describe your operation, but people don't know that you actually support it. You can tell people that you do by sticking them in your CapabilityStatement.rest.operation
Vadim Peretokin (Jun 28 2017 at 09:26):
Does that make more sense?
Mounika (Jun 28 2017 at 09:32):
Okay. Thank you
Peter Jordan (Jun 28 2017 at 20:44):
Searching/filtering on code descriptions is commonly performed by expanding ValueSets, remembering that for large code systems, such as LOINC and SNOMED CT, the FHIR Terminology Services API provides implicit ValueSets that expose the entire Code System.
Anand Mohan Tumuluri (Jun 28 2017 at 21:48):
Yeah, your use case is covered by ValueSet-expand. Something like this: http://tx.fhir.org/r3/ValueSet/$expand?url=http://loinc.org/vs&filter=pulse
Last updated: Apr 12 2022 at 19:14 UTC
