We should not understand the namespace "snomed-ct" in this way; instead it should resolve to whatever SNOMED there is in the local termology service, which might be some Norway national thing, or Spanish regional server etc. So the expected national extensions and translations would be present for archetypes containing codes that refer to concepts in those extensions.
One might argue that archetypes should carry a localisation code, not just for languages, but for terminology, of the same form as language tags, e.g. "fr-ca" would mean that French translation was expected, and that Canadian SCT national extension was assumed. Currently we don't have a way of marking archetypes like this, but possibly we should.
- thomas On 25/04/2017 08:50, Diego Boscá wrote:
I think having this in a hardcoded terminology list is probably far from ideal (e.g. how do you put "snomed ct+norway national extension"? do we need an exhaustive listing of all possible extensions/versions?)
_______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
