Blog

Hi all CMAG members,

After completion of the consultation period for discussion about: National content identified by a second country as useful a draft document (link below) has been developed and is now out for review. 

Please provide any feedback on the draft guidelines by Monday 7th October. 

https://docs.google.com/document/d/1iCISTBfepOwDqrIYeKkYLL2alN5nMVoMmRCFoeKtsLQ/edit?usp=sharing

Kind regards,

Cathy Richardson


  • No labels

15 Comments

  1. Hi Cathy,

    Thank you for the possibility to comment on the Promotion of National Content document. I have two questions:

    Ad 1) Do we have a definition of ‘an approved extension’

    Ad 10) Will the imported Concept ID from the original national extension be transfered to the Core? /Regards, Camilla

    1. Hi Camilla Wiberg Danielsen , 10) Will the imported Concept ID from the original national extension be transfered to the Core? Yes, the Technical team will ensure the imported concept includes the full model for the National extension concept retaining all existing identifiers, concept ID, description ID, relationships and language refset members. Best wishes, Maria

      1. Hi Camilla Wiberg Danielsen

        "Do we have a definition of ‘an approved extension" - this has been changed in the document to an 'NRC approved extension', Best wishes, Maria

  2. Hi Cathy,

    It has been a general problem for several terminologies used in Norway that local extension are introduced when perhaps the best thing to do would be to put the content in the "mother" terminology.

    It is of course important to re-use content if possible, so this guideline that you are writing is essential.

    However, it would be even better if the content was introduced into the core in the first place, not as a result of activities happening after the content has been created in an extension. To that effect - would it be possible to have a mechanism were one could see requested content, once it was requested from other NRCs? If that were possible, one could wait for the content to be added to the core. With more frequent releases, it might work even in cases of "urgency".

    With regards to 4:

    In my opinion the NRC responsible for the needed content must be the one submitting the content to the CRS.  Of course, this will require goodwill from country 1, but if there is agreement that the content is needed in the core, this should be possible.

    Country 1 may not want the content to be in the core (there was perhaps a good reason for having it in an extension), in which case country 2 must submit the request.


    With regards to 6:

    I fear that this will create a messy situation. Of course, if the content cannot be introduced into the core, e.g. because of editorial policy, then the "second country" may want to introduce it into their extension (or a shared extension, if that is/will be possible in the future). In case there is urgent need for the content/concept, the Concept ID from Country 1 can be used.


    1. Hi Jostein Ven,

      "would it be possible to have a mechanism where one could see requested content once it was requested from other NRCs?" - new content requests can be reviewed via the CRS.

      With regards to 4: In my opinion the NRC responsible for the needed content must be the one submitting the content to the CRS - the member that wishes to have a national extension concept promoted is responsible for seeking permission from the 'owning' country and also for submitting the CRS request.

      Country 1 may not want the content to be in the core (there was perhaps a good reason for having it in an extension), in which case country 2 must submit the request - in this case the originating member extension must veto the submission to the CRS.

      With regards to 6:I fear that this will create a messy situation. Of course, if the content cannot be introduced into the core, e.g. because of editorial policy, then the "second country" may want to introduce it into their extension (or a shared extension, if that is/will be possible in the future). In case there is urgent need for the content/concept, the Concept ID from Country 1 can be used - the relevant NRC would need to create the content in their own extension to meet their own use case. 

      Best wishes, Maria


  3. Thanks Cathy,

    Looks good. Presumably 10, now includes Axioms too?

    Also, regarding 8: I expect SLA's will probably need clarification/revisiting. Does this mean there's a limit to 100 concepts being promoted each cycle? Concept dependencies. Do such requests prevent additional requests for fixes to existing content?

    1. Hi Matt Cordellthanks for the comments, the SLA was updated in Jan 2019 in order to provide clarification on its content. The SLA does not include a limit to 100 concepts being promoted each cycle, the updated version of the SLA is here 2019 Change to Service Level Agreement for International CRS, Best wishes, Maria

      1. Hi Matt Cordell

        Presumably 10, now includes Axioms too? - anything that is in RF2 will be imported with identifiers including axioms, active stated relationships will not be accepted. We would expect any content in the RF2 submission to be updated to the most recent International release. Best wishes, Maria

  4. Hi Cathy,

    Thank you for the opportunity to provide feedback on this topic.

    Regarding bullets 4,7 and 8:

    First, we think that the member country that needs the content, should reach out to the "owning" country and validate the comprehension of that content. If the meaning matches the expected representation, then the steps for requesting promotion of that content can be undertook. That step should be achived by the member countries together prior to submission so SNOMED International has all relevant information on the use case. A confirmation of the countries discussion and agreement of the use case could be submitted to SI as any other supporting documentation.

    Regarding bullet 6:

    I am not sure I understand… I guess you are aluding to the fact that the request (conceptID) can be modified when promoted. But in most cases we would expect to keep at least the same conceptID. In that case, only module transfer will be required when the concept will be promoted to core. 

    1. Hi Linda Parisien  

      Regarding bullets 4,7 and 8 - this appears to align with the contents of the document, thank you for the clarification.

      Regarding bullet 6: A non-owning requestor may create the concept in their own extension whilst awaiting the release of a concept promoted to the International edition from another extension; however the non-owning extension concept would require future inactivation with its associated impact to implementation. This relates to content that is not promoted or if the requesting country needs the concept sooner, the original concept ID would be kept if promoted to the International release.

      Best wishes, Maria


  5. Thank you everyone for your comments. We are now closing this review. Maria Braithwaite will be reviewing your feedback. Kind regards, Cathy.

  6. Thanks to all for your valuable contributions, the 'Customer Guidance for CRS' document will be updated and published on the website (and via Confluence) shortly, Best wishes, Maria

    1. Maria Braithwaite Thanks everyone for your contribution. Thank you to Maria for pushing this important initiative forward. Monica

  7. Hi,


    I'm wondering if there is already a final version of the draft above? The usecase in our country is that Belgium is interested in national content of the Netherlands, created in function of their Clinical Building Blocks. So maybe it can be useful to promote this content to the international edition. Otherwise Belgium will have to duplicate this content in its own extension...


    Kind regards, Katrien

    1. Hi Katrien, 

      Yes the information is published in 'Customer Guidance For Requesting Changes to SNOMED CT' which is available on the SNOMED International website, please see Section 5.3 https://www.snomed.org/SNOMED/media/SNOMED/documents/Version-9-0-CRS-Customer-Guidance-20200527.pdf

      Best wishes, Maria