Stream: terminology
Topic: Snapper connected to r4 ontoserver
Manik Chopra (Apr 20 2020 at 00:10):
I am trying to create a conceptmap using Snapper connecting to https://r4.ontoserver.csiro.au/fhir but unable to find amt-mp-codes valueset in there. I am able to find the same in https://stu3.ontoserver.csiro.au/fhir
"name": "MyTestConceptMap",
"sourceUri": "https://itoc.metavision.codesystem.valueset.medications",
"targetUri": "http://hl7.org.au/fhir/ValueSet/amt-mp-codes"
Any idea why r4 does not load with the same valuesets?
Manik Chopra (Apr 20 2020 at 00:10):
@Michael Lawley ?
Jim Steel (Apr 20 2020 at 00:11):
They're different servers. They have different resources in them
Manik Chopra (Apr 20 2020 at 00:12):
shouldnt amt codes valueset be present in r4 as well? does it make a difference if I use STU3?
Jim Steel (Apr 20 2020 at 00:14):
If you're trying to create an R4 ConceptMap, you'll be better off using the R4 server. I can pop a copy of the MP ValueSet in there if it helps (or you can; the server is fully read-write)
Manik Chopra (Apr 20 2020 at 00:16):
that would be great...I am try to create CodeSystems, ValueSets and ConceptMaps for a project where I wanted to utilize the AMT valuesets as "target"in several conceptMaps
I am looking for MP, MPUU, TP, TPUU, Location, routes, doseForm, frequency, Unit of Measure
Jim Steel (Apr 20 2020 at 00:17):
All of those are available as implicit ValueSets, so one alternative is to just use the implicit ValueSets as your source/target
Jim Steel (Apr 20 2020 at 00:18):
For example, the implicit ValueSet for AMT MPs is http://snomed.info/sct?fhir_vs=refset/929360061000036106
Michael Lawley (Apr 20 2020 at 00:18):
http://hl7.org.au/fhir/ValueSet/amt-mp-codes is "just a valueset" -- there is no special reason why it should be in any particular terminology server (FHIR-defined valuesets are a little different). So, if you need it in the server you'll need to put it there.
Michael Lawley (Apr 20 2020 at 00:21):
As @Jim Steel says, the definition of http://hl7.org.au/fhir/ValueSet/amt-mp-codes is just "all members of the 929360061000036106 reference set".
I'm a little uncomfortable that the direct URI http://snomed.info/sct?fhir_vs=refset/929360061000036106 isn't used instead (in which case it would just work), but sometimes indirection is a good thing.
Manik Chopra (Apr 20 2020 at 00:28):
Awesome. The implicit valueset works in r4. I am happy to use the same.
Manik Chopra (Apr 20 2020 at 00:28):
What would be the best way to find out implicit valuesets for the rest?
Jim Steel (Apr 20 2020 at 00:40):
Look up Shrimp for the correct SNOMED id for the appropriate refset, (e.g. search shrimp for trade prod ref set)
Jim Steel (Apr 20 2020 at 00:42):
then put that concept id in place of the 923936... concept in the above url
Jim Steel (Apr 20 2020 at 00:46):
There are also other patterns for implicit SNOMED refsets:
- http://snomed.info/sct?fhir_vs=isa/12345 is the concept 12345 and all of its descendents
- http://snomed.info/sct?fhir_vs=refset (without a concept id after it) is the list of all refsets
- http://snomed.info/sct?fhir_vs=ecl/XXXXXXXX is the set of concepts that satisfy the ECL expression XXXXXXXXX
Manik Chopra (Apr 20 2020 at 01:11):
Perfect. Thanks @Jim Steel
Michael Lawley (Apr 20 2020 at 03:10):
Alternatively, these http://hl7.org.au/fhir/ValueSet/amt-mp-codes are resolvable and so you can inspect the definition
Cora Drenkhahn (May 12 2020 at 12:21):
Hi,
I created a ConceptMap using Snapper:Map for testing purposes of our local Ontoserver. The tool works great until I try to either upload or download the ConceptMap - nothing happens at all, only a message "Generating FHIR ConceptMap and uploading..." is displayed when trying to upload.
With Snapper:Author I can upload similar resources successfully to our server but I'd also like to use the Map tool's functionality.
Any idea what's going on here?
Cora Drenkhahn (May 13 2020 at 07:48):
@Jim Steel ?
Jim Steel (May 13 2020 at 08:01):
Cheers Cora. We're looking into it. We've been doing some work on improving Snapper's R4 conformance recently, so it may be linked to that. Hopefully shouldn't take long to sort out
Cora Drenkhahn (May 13 2020 at 08:55):
That sounds plausible. Great, thank you!
Michael Lawley (May 13 2020 at 09:10):
Hi Cora, it was a bug (two actually) that resulted from the R4 work on Snapper:Author not being completely tracked in Snapper:Map.
I've just deployed a new version so it should be okay after a page reload
Cora Drenkhahn (May 13 2020 at 09:40):
Hi Michael, thanks for looking into the issue so fast.
Unfortunately, there's no change yet...
Michael Lawley (May 13 2020 at 09:47):
Sorry, a slight propagation delay. 2.3.6 should now be visible (you might need to force-reload)
Cora Drenkhahn (May 13 2020 at 09:52):
Now it works! Thank you very much!
Last updated: Apr 12 2022 at 19:14 UTC
