Stream: implementers
Topic: Mapping concepts to structures
Jose Costa Teixeira (Jul 27 2020 at 11:55):
How do we map concepts to structures? For example the following elements have corresponding SCT concepts:
Dosage.site --> 736479009 (dose form intended site)
Event.performer may map to 420158005 (performer of method)
Is this were we'd use ElementDefinition.code?
If so, how do we track complexity of the mapping (provisional mapping, one to several...) ?
Any experience or recommendation?
Jose Costa Teixeira (Jul 28 2020 at 08:34):
@Grahame Grieve any recommendation on mapping FHIR elements to the SNOMED codes that correspond to those concepts? Is that done elsewhere?
Grahame Grieve (Jul 28 2020 at 09:44):
it certainly is - look at either Condition or Observation. There's 2 kinds of SNOMED mappings - a snomed concept that maps to the element definition (~question) and a snomed concept that is the root of possible appropriate values (~answer)
Jose Costa Teixeira (Jul 28 2020 at 11:20):
ok so this is on elementDefinition.mapping.
Jose Costa Teixeira (Jul 30 2020 at 13:05):
For the wish box -
Eventually would be interesting to also have these in our publication / diff:
If the resource says observation.device maps to 424226004 (Using device)
and if one IG profile says that their observation.device maps to 371882005 (Device used), that could be relevant
Grahame Grieve (Jul 30 2020 at 23:47):
it will be published if you define it
Jose Costa Teixeira (Jul 31 2020 at 06:28):
cool
Jose Costa Teixeira (Aug 05 2020 at 11:40):
Further on this: If we want to build our own conceptual model (on the business level, just supporting the concepts and definitions,
Jose Costa Teixeira (Aug 05 2020 at 11:41):
we can use CodeSystem to preserve the Glossary Terms.
For example we'd define a "Medical Device"
Jose Costa Teixeira (Aug 05 2020 at 11:43):
How can we say "this concept/definition maps to SCT code 12345678" ?
Lloyd McKenzie (Aug 05 2020 at 22:40):
ElementDefinition.code for the root element of the logical model
Last updated: Apr 12 2022 at 19:14 UTC
