Stream: IG creation
Topic: Adding IG to registry
Jose Costa Teixeira (Aug 10 2021 at 16:52):
I presume that any institution can publish their IGs to the registry, not only affiliate or global SDOs like IHE. Is this correct ? Anything else we should know before adding a PR to the ig registry?
Lloyd McKenzie (Aug 10 2021 at 17:30):
@Joshua Procious
Joshua Procious (Aug 10 2021 at 18:22):
@Jose Costa Teixeira before you add a PR to any HL7 managed repo please check out chapter 9 of the GOM (http://www.hl7.org/documentcenter/public/membership/HL7_Governance_and_Operations_Manual.pdf) specifically the section regarding the inclusion of any IP information.
Jose Costa Teixeira (Aug 10 2021 at 18:24):
This is an IG that is to be added to the registry.
Jose Costa Teixeira (Aug 10 2021 at 18:38):
I don't see how to handle IP for this or similar requests - but it's an interesting question, so I engage:
- In general, the PR itself definition(?) does not contain any protected IP. (One could post the coca-cola formula in the comments, or the solution to Fermat's last theorem, but that is not expectable)
- The PR would add a link to the IG, and I'd think the IG falls out of the reasonable control of HL7 - it is owned by someone else.
- However, it can be interpreted (02.02in the GOM) that adding an IG to the Registry adds the IG to the HL7 Protocol specifications -- is this a fair statement? If so, there are quite some implications.
- for example, if I push some protected IP into an IHE IG, and this IG is in the registry , I'm violating IHE rules, not HL7, I guess?
Jose Costa Teixeira (Aug 10 2021 at 18:38):
@Joshua Procious
Lloyd McKenzie (Aug 10 2021 at 18:40):
The question is - is the registry only for HL7-defined stuff or not?
Jose Costa Teixeira (Aug 10 2021 at 18:47):
right
John Moehrke (Aug 10 2021 at 19:02):
There are a bunch of others publishing into the registry. Not just IHE.
John Moehrke (Aug 10 2021 at 19:03):
I was putting stuff in from IHE with direct pull-requests. But now have to do a forked pull-request. Not a problem, but there is clearly some other mechanism involved. This forked pull-request is documented steps of the IG publication process.
John Moehrke (Aug 10 2021 at 19:04):
So, I figure.. @Jose Costa Teixeira ... that you just submit your pull-request and see what the gods think of it.
John Moehrke (Aug 10 2021 at 19:06):
there is now the new registry (https://registry.fhir.org/), to get into that you need to get your organizations RSS feed recognized in the hl7 registry. Once that is done, then the new registry will pull in your new publications whenever you update your RSS feed. Again, it is not clear the steps to get your RSS feed recognized, or what you are allowed to put into your RSS feed.
John Moehrke (Aug 10 2021 at 19:08):
to get your RSS feed recognized is the same forked pull-request to the classic registry.. Here is my git commit when adding IHE rss feed https://github.com/FHIR/ig-registry/commit/bbf402b0f8271ef5211a65731e625249242ff33f
Jose Costa Teixeira (Aug 10 2021 at 19:21):
thanks John
Jose Costa Teixeira (Aug 10 2021 at 19:22):
I think there may be some value in looking at the IP implications of such process, but I'll see if Joshua wants to comment on that. I'll check the technical part
John Moehrke (Aug 10 2021 at 19:33):
yup, also a need for some published governance. I think the technical part is clean, and able to be governed.
Grahame Grieve (Aug 17 2021 at 04:57):
this thread is deeply confused. There's no reason to talk to Joshua Procious. There's two registries:
- registry.fhir.org. There's multiple ways for any FHIR author to get content in there, and anyone is allowed to (and encouraged to) publish there.
- a higher level summary of IGs at http://www.fhir.org/guides/registry/. You make a PR against https://github.com/FHIR/ig-registry to get in there.
In neither case is there any requirements around IP from HL7 to do that
Last updated: Apr 12 2022 at 19:14 UTC
