Stream: social
Topic: ontoserver
Peter Jordan (Jul 02 2016 at 01:49):
@Michael Lawley I ran this... http://ontoserver.csiro.au/stu3/CodeSystem/$lookup?system=http://snomed.info/sct&code=404684003&property=parent&property=child and then this...
http://ontoserver.csiro.au/stu3/CodeSystem/$lookup?system=http://snomed.info/sct&code=404684003&properties=parent,child
Only the second query returned the parent and child codes.
Michael Lawley (Jul 02 2016 at 02:36):
that looks like a bug - in the second case it's ignoring the properties parameter and just performing default behaviour. For the first one, it should be looking at the property parameter
Michael Lawley (Jul 02 2016 at 05:13):
Question - should the property filters apply to the non-property parameters? ie "display", "version", "name", and "designation"?
Grahame Grieve (Jul 02 2016 at 10:40):
ummm, no? but perhaps you should be more specific? which property, which operator, which value?
Grahame Grieve (Jul 02 2016 at 10:40):
and which code system?
Michael Lawley (Jul 02 2016 at 14:18):
"filter" was the wrong word to use - I was referring to the "property" parameter to the $lookup operation.
Kevin Mayfield (Jul 02 2016 at 18:16):
Wow, that's an extensive rewrite. Looking forward to receiving my copy.
Kevin Mayfield (Jul 02 2016 at 18:20):
@James Agnew that's 1.6 HAPI? Does that mean we'd be able to take SNOMED flat files and import them into HAPI.
Grahame Grieve (Jul 02 2016 at 21:26):
ok then the answer is yes - and we could define this - "name" "display", and "version" are implemented on my system, but not designation or property
James Agnew (Jul 04 2016 at 22:22):
Yup. The 1.6 release will have support for loading SNOMED CT and LOINC distribution ZIP files into a HAPI JPA server (or into the CLI server)
Dave Carlson (Jul 05 2016 at 17:46):
@James Agnew are you embedding part of ontoserver implementation libraries into HAPI, to include same funtionality describe by Michael L? This is in the ontoserver topic thread. I thouht that ontoserer was closed source. I would be very happy to see these expanded terminology services in HAPI, and level-setting common behavior between Grahame's server, ontoserver, and HAPI (and others).
James Agnew (Jul 05 2016 at 19:43):
Nope, these are separate code bases. Ontoserver is built using HAPI, but has it's own actual terminology service implementation (which is presumably far more full-featured than HAPI's given that it is purpose built). HAPI does support the basic stuff though and hopefully over time we'll add more.
Dave Carlson (Jul 06 2016 at 15:36):
Thanks James, I'll look forward to testing HAPI terminology services. One aspect I am especially interested in is lookup of SCT parent and/or child properties for a concept. And, ideally, relationshp attributes for a concept.
Michael Lawley (Jul 07 2016 at 22:59):
Yes, Ontoserver includes special-purpose ranking algorithms for $expand + filter, for example, and pretty deep support for SNOMED CT, multiple versions (including cross-jursdiction versions - so called Editions). etc
Last updated: Apr 12 2022 at 19:14 UTC
