SNOMED CT's release format, RF2, and its content can undoubtedly=
be improved to allow richer/better/easier use through terminology services=
.
This page (and subpages if they are warranted) is designed to capture th=
ese initiatives so they may be documented and communicated to the appropria=
te group in SNOMED International for action. These initiatives may become o=
bvious through review and revision of the Using SNOME=
D CT with FHIR page or other work of the group.
Examples to start with are
- The Using SNOMED CT with FHIR page defin=
es Implicit ValueSets however there is=
no way to GET an implicit ValueSet resource which would be a good way to e=
xpose metadata about a reference set (for example name, title, status, desc=
ription, publisher, purpose, copyright, intensional definition...etc). This=
metadata for reference sets currently has no place in RF2, however is usef=
ul generally and usually gets documented outside the terminology and has be=
en the topic of other discussion (and even others too). This suggestio=
n is to work on defining a set of metadata attributes and their location in=
RF2 so they may be exposed by services like implicit ValueSets and online =
documentation generated from RF2 files rather than maintained separately.=
li>
- Reference sets that represent maps in SNOMED CT can be represented as <=
a href=3D"https://www.hl7.org/fhir/snomedct.html#implicit-cm" class=3D"exte=
rnal-link" rel=3D"nofollow">Implicit ConceptMaps in FHIR. However one m=
issing part of the metadata which accompanies SNOMED CT reference sets oper=
ating as maps is they fail to identify the code system the map is to - it i=
s obvious to a human reading the name of the reference set, but for the pur=
poses of writing software you "just have to know" the target code system an=
d hard code that for the particular reference sets as assumptions. Clearly =
this would be better as machine processable metadata and would help with re=
alising Implicit ConceptMaps in FHIR&=
nbsp;which are quite useful. This may be a specialised case of point 1 abov=
e, however this focusses on machine used metadata as opposed to metadata fo=
r human consumption.
Please indicate if there is interest in working on the above items, and/=
or other suggested items.
------=_Part_12937_1835317252.1710813109856--