FHIR Chat · VSAC · terminology

Stream: terminology

Topic: VSAC


view this post on Zulip Grahame Grieve (Jul 28 2020 at 01:55):

@Keith Boone:

There's absolutely NO EXCUSE for a system designed to support FHIR to have an easily accessible CSV distribution mechanism for value sets, BUT not to have a FHIR ValueSet distribution mechanism

If you're referring to VSAC - I think you are - then they do have a FHIR API, but I can't make use of it, because it's password protected. I've asked for some arrangements to access the VSAC API so that we can leverage it but nothing has come of it yet

view this post on Zulip Keith Boone (Jul 28 2020 at 04:53):

I'm actually referring to a different system, and the people who know the system know of my complaint. VSAC has other problems, including basically no funding for any sort of infrastructure support to even respond to your feedback (or mine). I've had several interesting e-mail conversations, but basically, it boils down to "no budget".

view this post on Zulip Grahame Grieve (Aug 27 2020 at 21:31):

@Chris Moesel asks

the FHIR API provided by VSAC returns value sets with the following canonicals: http://cts.nlm.nih.gov/fhir/ValueSet/{oid}. Why does the VSAC package redefine the canonical?

view this post on Zulip Grahame Grieve (Aug 27 2020 at 21:31):

in response to my message that:

view this post on Zulip Grahame Grieve (Aug 27 2020 at 21:32):

we have a VSAC package now. To use it, you need something like this in your IG dependencies:
Value set canonical URIs are http://vsac.nlm.nih.gov/fhir/ValueSet/{oid}

view this post on Zulip Grahame Grieve (Aug 27 2020 at 21:33):

The answer is that my records said otherwise, and I could get the API to run. Maybe I shouldn't have been in such a hurry.

view this post on Zulip Grahame Grieve (Aug 27 2020 at 21:34):

so it looks like I should change the canonical to http://cts.nlm.nih.gov/fhir/ValueSet/{oid} but I don't want to change it more than once so I'm checking here to see if anyone knows a reason not to use the what vsac are using on their API (which has some experimental-ness to it)

view this post on Zulip Michael Lawley (Sep 03 2020 at 04:59):

cts.nlm... looks like a system URL and vsac.nlm... looks like an institutional URI, and thus to be preferred; URIs should normally reflect the governing entity.
But it's ultimately that entity's call.

view this post on Zulip Chris Moesel (Sep 03 2020 at 12:03):

I'm not 100% sure, but I think cts.nlm.nih.gov is: Clinical Terminology Services at the National Library of Medicine at the National Institute of Health. I suppose it allows NLM to go beyond the scope of just VSAC in the service. For me, my main concern was that NLM had already established the cts.nlm variant of the canonical, so I would prefer to not have a competing canonical hanging around.

view this post on Zulip Grahame Grieve (Sep 04 2020 at 07:53):

ok I release v0.2.0 of the vsac package with more vsac value sets in it - though not all of them. These have corrected canonical URLs

view this post on Zulip Robert McClure (Sep 09 2020 at 22:02):

@Grahame Grieve VSAC FHIR representations of value sets should all have a canonical of http://cts.nlm.nih.gov/fhir/ValueSet/{oid}. Are you saying you found different, or was it that you guessed different?

view this post on Zulip Grahame Grieve (Sep 09 2020 at 22:18):

poor record keeping on my part, yes


Last updated: Apr 12 2022 at 19:14 UTC