FHIR Chat · hl7.org/fhir some links are broken · implementers

Stream: implementers

Topic: hl7.org/fhir some links are broken


view this post on Zulip Tim Zallin (Dec 09 2019 at 13:06):

confirmed for http://hl7.org/fhir/sid/us-npi, http://hl7.org/fhir/sid/us-ssn, http://hl7.org/fhir/sid/us-mbi

view this post on Zulip Tim Zallin (Dec 09 2019 at 13:28):

@Grahame Grieve hello, whom do I need to ping about this issue?

view this post on Zulip Lloyd McKenzie (Dec 09 2019 at 13:55):

That's not an error. There's no intention at the moment that they resolve. Agree it would be nice if they did though - presumably to the NamingSystem instances that define the space. Can you submit a change request using the "propose a change" link at the bottom of any page in the spec? (If you haven't registered as a user, you'll need to go to http://jira.hl7.org and do that first.)

view this post on Zulip Tim Zallin (Dec 09 2019 at 14:28):

but spec says identifier.system should resolve to at least some human readable description when it is an URL. Spec also suggests to use default identifier registry which includes examples I attached. It looks like an inconsistency to me :slight_smile:

view this post on Zulip Lloyd McKenzie (Dec 09 2019 at 14:30):

The key term being "should" - you can't count on it doing so. That said, I agree it would be nice if it did. So feel free to submit a formal change request :)

view this post on Zulip Tim Zallin (Dec 09 2019 at 14:33):

sure, will do, thanks for the clarification!

view this post on Zulip Tim Zallin (Dec 09 2019 at 15:57):

do you have guidelines on change request structure? And maybe some description on how spec development works? It would be nice to understand the internals

view this post on Zulip Lloyd McKenzie (Dec 09 2019 at 16:27):

Documentation on the change request process is here: https://confluence.hl7.org/display/HL7/Specification+Feedback
I'm not aware of a page that talks about overall development process. In summary, the responsible work group will review the proposed change, generally on a conference call and make a decision. If you flag the element as "in person", they'll try to make sure they discuss it at a time you're able to attend. If a decision is made to change the spec, someone will eventually make it in the continuous integration environment. Eventually the specification will go out for a formal ballot review (which may drive eventual changes) and finally a new official version will be published. We're currently targeting R5 for Q1 2021.

view this post on Zulip Grahame Grieve (Dec 09 2019 at 19:24):

they used to resolve, and it's an oversight that they don't from when I rebuilt the redirection system a couple of weeks ago

view this post on Zulip Michael Lawley (Dec 10 2019 at 10:46):

I'm guessing that's why things like https://www.hl7.org/fhir/valueset also no longer redirect to https://www.hl7.org/fhir/valueset.html ?

view this post on Zulip Tim Zallin (Dec 10 2019 at 10:53):

yes, this is why I raised the issue in the first place, I recall they resolved some time ago

view this post on Zulip Tim Zallin (Dec 10 2019 at 10:54):

thanks @Lloyd McKenzie , it is clearer right now

view this post on Zulip Grahame Grieve (Dec 10 2019 at 20:31):

things like https://www.hl7.org/fhir/valueset also no longer redirect to https://www.hl7.org/fhir/valueset.html

whoops. I'll fix that - should take about an hour to upload


Last updated: Apr 12 2022 at 19:14 UTC