Stream: terminology
Topic: terminology defining URL
John Moehrke (Oct 24 2018 at 15:30):
I am noticing that the defining URL for hl7 vocabulary is now at http://terminology.hl7.org, where in STU3 it was at http://hl7.org/fhir
Thus the PurposeOfUse vocab (for example) is now at a different URL
STU3 -- http://hl7.org/fhir/v3/ActReason
Build -- http://terminology.hl7.org/CodeSystem/v3-ActReason
I presume this is known, although it is not clear all examples have been updated (such as the break-glass example)
SO WHAT? The above is not my concern. My concern is that the STU3 url resolves, the Build url gives an unusual human readable text "default terminology error display". If that text is the right thing, then can't it be a bit more useful to a human? Why can't we have the more useful human readable form provided by STU3.... or is this just a temporary bug/fauult?
Robert McClure (Oct 25 2018 at 15:01):
@Grahame Grieve or @Ted Klein Can you explain the planned process for this transition?
Grahame Grieve (Oct 26 2018 at 07:26):
the Build url gives an unusual human readable text "default terminology error display"
where?
Grahame Grieve (Oct 26 2018 at 07:26):
It's certainly a bug
Grahame Grieve (Oct 26 2018 at 07:27):
Can you explain the planned process for this transition
What transition? if you are referring to the url change - then the process is supposed to be complete, but John has evidently found something I overlooked
John Moehrke (Oct 26 2018 at 12:36):
should we be seeing http:/hl7.org/fhir or should we be seeing http://terminology.hl7.org? If we are to be seeing the terminology one, then this is a breaking change for ALL vocabulary. My question on 'transition' is around this very big breaking change.
Grahame Grieve (Oct 26 2018 at 13:00):
the breaking change was so big I couldn't deal with all of it. What we did was move all the code systems where the URL appears in the instances. the canonical URL is changed, but the actual publication location is not -yet - changed. I will remove them from the publication once we publish at http://terminology.hl7.org (and redirect the existing links there)
Grahame Grieve (Oct 26 2018 at 13:00):
so you should be seeing terminology.hl7.org. but the links should actually be to hl7.org/fhir
Grahame Grieve (Oct 26 2018 at 13:01):
well, build.fhir.org right now. You still haevm't identified any broken content?
John Moehrke (Oct 26 2018 at 13:14):
http://build.fhir.org/v3/PurposeOfUse/vs.html
John Moehrke (Oct 26 2018 at 13:15):
http://build.fhir.org/v3/ActReason/cs.html
John Moehrke (Oct 26 2018 at 13:15):
or am I looking at the wrong thing... I am looking at the "Defining URL"
John Moehrke (Oct 26 2018 at 13:17):
which for that build ActReason vocabulary is -- http://terminology.hl7.org/CodeSystem/v3-ActReason
Grahame Grieve (Oct 26 2018 at 13:21):
ok, so what's broken? I guess what you're saying is the defining URL doesn't work as a literal URL. All I can say is that it will ,but vocab still haven't got to the point of publishing at that place yet
John Moehrke (Oct 26 2018 at 13:27):
Okay, that now is clear. So yes we are making this breaking change now.
John Moehrke (Oct 26 2018 at 13:28):
so everywhere we should see these terminology.hl7.org ...
John Moehrke (Oct 26 2018 at 13:29):
which brings me back to the break-glass discusion, where the example is not yet changed -- http://build.fhir.org/security-labels.html#break-the-glass
John Moehrke (Oct 26 2018 at 13:30):
and since that page had some things using terminology and some using the old URL.. I didn't know which direction we were heading
Grahame Grieve (Oct 26 2018 at 13:32):
well, I missed that because it's just plain wrong
Grahame Grieve (Oct 26 2018 at 13:35):
if it is, as it claims, a security label, then the representation should be
Category: http://terminology.hl7.org/CodeSystem/v3-ActReason#BTG; scheme="http://hl7.org/fhir/tag/security"; label="break the glass"
Grahame Grieve (Oct 26 2018 at 13:35):
and I note that http://hl7.org/fhir/tag/security is not defined anywhere, and is not a scheme we use any more. We should define it somewhere
John Moehrke (Oct 26 2018 at 13:55):
Given the IETF draft... do we need the scheme ?
John Moehrke (Oct 26 2018 at 13:55):
it says scheme is optional
Grahame Grieve (Oct 26 2018 at 13:56):
I think we do for future proofing...
John Moehrke (Oct 26 2018 at 13:57):
so you are thinking the scheme is an identifier that -this- category is a PurposeOfUse?
Grahame Grieve (Oct 26 2018 at 13:58):
no, that it's a security label. rather than, say, a tag
John Moehrke (Oct 26 2018 at 14:00):
not sure what else would be used except for PurposeOfUse... and we have a URN we use in IHE-XUA (SAML) and IHE-IUA (OAuth-JWT), that comes from an OASIS spec the healthcare security geeks manage -- urn:oasis:names:tc:xspa:1.0:subject:purposeofuse
John Moehrke (Oct 26 2018 at 14:01):
see IHE-XUA (specific link to volume 2 section on XUA) http://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_TF_Vol2b.pdf#nameddest=3_40_Provide_X_User_Assertion__
John Moehrke (Oct 26 2018 at 14:01):
section 3.40.4.1.2.3
Grahame Grieve (Oct 26 2018 at 14:03):
so you have positive grounds to say that no one else will use that header, and we'll never have any reason to put anything in the category header, then maybe there'd be no reason for us to use scheme
John Moehrke (Oct 26 2018 at 14:04):
well, the IETF spec is a draft spec.. so it could be gone and dead tomorrow... so this is nothing but experimental
John Moehrke (Oct 26 2018 at 14:05):
but, using that purposeOfUse urn as the purposeOfUse does keep us close to what is done today in SAML.. widely deployed such as in the Sequoia and CommonWell environments
Grahame Grieve (Oct 26 2018 at 14:05):
I haven't looked - how does SAML go into HTTP headers?
John Moehrke (Oct 26 2018 at 14:06):
different topic
Grahame Grieve (Oct 26 2018 at 14:06):
I know I'm just askin
John Moehrke (Oct 26 2018 at 14:06):
but, yes there is a way... it is ugly... see the profile "SAML SSO Profile" from WS-I/OASIS
John Moehrke (Oct 26 2018 at 14:06):
it is by reference. much like OAuth token
John Moehrke (Oct 26 2018 at 14:07):
where introspection with the token issuer is done to get the actual XML
John Moehrke (Oct 26 2018 at 14:07):
much like OAuth
John Moehrke (Oct 26 2018 at 14:08):
There is, as with JWT, a way to seralize the XML into the http header... but due to size limitations it is discouraged
Grahame Grieve (Oct 26 2018 at 14:10):
ok thanks
John Moehrke (Oct 26 2018 at 14:12):
just to really mess with reality, there is a way to carry a SAML token in an OAuth token...
Grahame Grieve (Oct 26 2018 at 14:13):
oh? by reference?
John Moehrke (Oct 26 2018 at 14:15):
draft-ietf-oauth-saml2-bearer
Vadim Peretokin (Nov 28 2018 at 09:06):
I'm seeing that strange "default terminology error display" error on https://terminology.hl7.org/CodeSystem/v3-orderableDrugForm now
David Johnson (Nov 28 2018 at 13:37):
Hello Vadim! My name is David Johnson and I am working with Ted Klein on the terminology pages. That default error is displaying for a page not found.
Grahame Grieve (Nov 29 2018 at 01:56):
there's no content at the actual page, and no intent that there will be yet. So I think that Vadim has some other issue
Vadim Peretokin (Dec 05 2018 at 06:02):
I was trying to find the codesystem definition so I can look at other codes in it. Having the same issue with http://terminology.hl7.org/CodeSystem/financialtaskcode
Vadim Peretokin (Dec 05 2018 at 06:25):
It seems to be a made-up code system with only once instance of it being used in an example
Grahame Grieve (Dec 05 2018 at 20:14):
yes that's what it is.
Last updated: Apr 12 2022 at 19:14 UTC
