Stream: IG creation
Topic: Requirements for publishing HL7 independent ig's
Oliver Egger (Sep 04 2020 at 08:31):
If we want to publish an ig outside of hl7 (private organization):
- Are there any best practices/examples available how to refer to the base FHIR licences including copyright terms?
- Are the HTA terminologies under the same license as FHIR or do we need to add another copyright statement if ValueSets/CodeSystems are used from https://terminology.hl7.org/?
Grahame Grieve (Sep 04 2020 at 09:55):
HTA approvals etc at present only apply to HL7 International. It's not clear whether it applies to affiliates. It definitely doesn't apply to private organizations
Grahame Grieve (Sep 04 2020 at 09:55):
best practices - I'm not sure what you're exactly talking about
Oliver Egger (Sep 04 2020 at 14:38):
Grahame Grieve said:
best practices - I'm not sure what you're exactly talking about
we would like in a section to refer to all the licenses and requirements for an implementation guide:
This Implementation Guide is based on FHIR® Release 4. FHIR® is licensed under Creative Commons "No Rights Reserved" (CC0 ).
HL7®, HEALTH LEVEL SEVEN®, FHIR® and the FHIR ® are trademarks owned by Health Level Seven International, registered with the United States Patent and Trademark Office.This Implementation Guide includes content from SNOMED Clinical Terms® (SNOMED CT®) which is copyright of the International Health Terminology Standards Development Organisation (IHTSDO). Implementers of these artefacts must have the appropriate SNOMED CT Affiliate license - for more information contact http://www.snomed.org/snomed-ct/getsnomed-ct or info@snomed.org.
probably we would end up (except the statement to FHIR) like FHIR does it itself under 2.20.3 Third-party artifacts and terminologies, does this make sense for an ig?
Oliver Egger (Sep 04 2020 at 15:01):
Grahame Grieve said:
HTA approvals etc at present only apply to HL7 International. It's not clear whether it applies to affiliates. It definitely doesn't apply to private organizations
Sorry, I think my explanation was not clear. The FHIR datatype Timing has a required binding which refers to the ValueSet http://hl7.org/fhir/ValueSet/event-timing. This includes all the codes from as defined in http://terminology.hl7.org/CodeSystem/v3-TimingEvent.
My question was, what kind of license would be necessary for http://terminology.hl7.org/CodeSystem/v3-TimingEvent. But I have seen now, that this redirects to http://hl7.org/fhir/v3/TimingEvent/cs.html and is covered in that case by the general FHIR license, nice!
Grahame Grieve (Sep 04 2020 at 20:17):
@Ted Klein UTG doesn't specify a license. This is on me, but something we must rectify in the next version
Grahame Grieve (Sep 04 2020 at 20:18):
@Oliver Egger:
But I have seen now, that this redirects to http://hl7.org/fhir/v3/TimingEvent/cs.html
it certainly should not. where do you see a redirect?
Oliver Egger (Sep 07 2020 at 06:41):
@Grahame Grieve : not a http redirect, but in http://hl7.org/fhir/R4/valueset-event-timing.html the link behind the canonical url http://terminology.hl7.org/CodeSystem/v3-TimingEvent is pointing to http://hl7.org/fhir/R4/v3/TimingEvent/cs.html which is within the R4 spec and not to the definition in http://terminology.hl7.org/CodeSystem/v3-TimingEvent.
Grahame Grieve (Sep 07 2020 at 07:15):
ah right. I will ask about this on #terminology thanks
Last updated: Apr 12 2022 at 19:14 UTC