SNOMED CT IP statement

[nriss]

Hi everyone!

Here is a sentence about the SNMED license in the IP statement, hard-coded in the publisher

1/ Is it possible to make it variable in the language pack ?

2/ In France, as a SNOMED CT member, it would be interesting to change the sentence to ask the lector to contact the national contact point to get a license, is it possible ?

Thank you for your help!

Discussion in France with @M-Priour and @legallm

fhir-ig-publisher/org.hl7.fhir.publisher.core/src/main/java/org/hl7/fhir/igtools/renderers/IPStatementsRenderer.java

Line 221 in 4bfb8bf

"for more information contact <a href=\"https://www.snomed.org/get-snomed\">https://www.snomed.org/get-snomed</a> or <a href=\"mailto:[email protected]\">[email protected]</a>.";

""This material contains content that is copyright of SNOMED International. Implementers of these specifications must have the appropriate SNOMED CT Affiliate license - "+
"for more information contact <a href="https://www.snomed.org/get-snomed\">https://www.snomed.org/get-snomed or <a href="mailto:[email protected]">[email protected].";
}"

[costateixeira]

https://chat.fhir.org/#narrow/channel/179252-IG-creation/topic/Which.20IP.20statement.20to.20use.3F

[lmckenzi]

1. There's some trickiness there as this language is formally agreed by the lawyers of the code system in question and, presumably, lawyers would also need to sign off on any translated language. It's certainly possible for us to allow for translations, but the process for managing them would likely need to be different from most translations as we would need not just someone to provide a translation, but would need the code system owner to actually agree to the translated legalese. Step Correct dependencies to not be specific to Grahame's harddrive #1 is to get SNOMED international to agree to an official French translation of their standard language.

2. At the moment, there's an agreement for a single set of wording to be used for all SNOMED licensees. It's possible to say more than the standard wording, but the standard wording must be there word for word. If the desire is to deviate rather than supplement, again there would need to be something in writing from SNOMED International and there would need to be clear technical rules we could follow based on metadata in the instance that would allow determining whether to require the alternate language or the general-purpose language.

Assigning this back to the submitter to work on getting agreement from SNOMED International on what should happen here.

[grahamegrieve]

From the next version of the IG publisher, this will be translatable, but I have to approve the translations, since for technical reasons they’ll be in the software tool translations, not the language pack. But you’ll need to do more French translations that just that one - there’s 1180 phrases to translate. Grahame

…

On 20 Nov 2024 at 9:21:06 AM, Lloyd McKenzie ***@***.***> wrote: 1. There's some trickiness there as this language is formally agreed by the lawyers of the code system in question and, presumably, lawyers would also need to sign off on any translated language. It's certainly possible for us to allow for translations, but the process for managing them would likely need to be different from most translations as we would need not just someone to provide a translation, but would need the code system owner to actually agree to the translated legalese. Step #1 <#1> is to get SNOMED international to agree to an official French translation of their standard language. 2. At the moment, there's an agreement for a single set of wording to be used for all SNOMED licensees. It's possible to say more than the standard wording, but the standard wording must be there word for word. If the desire is to deviate rather than supplement, again there would need to be something in writing from SNOMED International and there would need to be clear technical rules we could follow based on metadata in the instance that would allow determining whether to require the alternate language or the general-purpose language. Assigning this back to the submitter to work on getting agreement from SNOMED International on what should happen here. — Reply to this email directly, view it on GitHub <#989 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABMWKFLANUZCXOQUYABAVQD2BO2VFAVCNFSM6AAAAABSBRUUQOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBWHA3TAMBWGM> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[legallm]

1. There's some trickiness there as this language is formally agreed by the lawyers of the code system in question and, presumably, lawyers would also need to sign off on any translated language. It's certainly possible for us to allow for translations, but the process for managing them would likely need to be different from most translations as we would need not just someone to provide a translation, but would need the code system owner to actually agree to the translated legalese. Step Correct dependencies to not be specific to Grahame's harddrive #1 is to get SNOMED international to agree to an official French translation of their standard language.

   2. At the moment, there's an agreement for a single set of wording to be used for all SNOMED licensees. It's possible to say more than the standard wording, but the standard wording must be there word for word. If the desire is to deviate rather than supplement, again there would need to be something in writing from SNOMED International and there would need to be clear technical rules we could follow based on metadata in the instance that would allow determining whether to require the alternate language or the general-purpose language.

Assigning this back to the submitter to work on getting agreement from SNOMED International on what should happen here.

Thank you all for your feedback!
Regarding the agreed translation, as we are French NRC we are part of the SNOMED Int. and work directly with them. They send us a valid English version of the copyright and our legal team will translate it.

Maël

[nriss]

I will be pleased to contribute to the French Language pack @grahamegrieve :)

But I don't find any documentation about how to do it! Directly create a PR here ?

[grahamegrieve]

Yes, a PR. The relevant files for the trench translations are https://github.com/hapifhir/org.hl7.fhir.core/blob/master/org.hl7.fhir.utilities/src/main/resources/source/validator-messages-fr.po https://github.com/hapifhir/org.hl7.fhir.core/blob/master/org.hl7.fhir.utilities/src/main/resources/source/rendering-phrases-fr.po Grahame

…

On 20 Nov 2024 at 7:40:13 PM, Nicolas Riss ***@***.***> wrote: I will be pleased to contribute to the French Language pack @grahamegrieve <https://github.com/grahamegrieve> :) But I don't find any documentation about how to do it! Directly create a PR here <https://github.com/hapifhir/org.hl7.fhir.core/tree/master/org.hl7.fhir.utilities/src/main/resources/source> ? — Reply to this email directly, view it on GitHub <#989 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABMWKFOXM7DXIEJDDFGJGGT2BRDG3AVCNFSM6AAAAABSBRUUQOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBXHA4TSMBTHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[nriss]

Will work on that during my free time if I find some, thank you :)