Stream: uk
Topic: SNOMED Observation
Kevin Mayfield (Oct 07 2017 at 06:05):
I've mocked a smoking history example based on argonaut example: https://gist.github.com/KevinMayfield/618f7f613bd59b6038f5930e7de97257
Kevin Mayfield (Oct 07 2017 at 06:08):
Looking at the codes used, the valueCodeableConcept [Occasional tobacco smoker (finding)] tells me it's a [Finding of tobacco smoking consumption (finding)]
Kevin Mayfield (Oct 07 2017 at 06:12):
So with the acutal implementation (at database) could store the observation like: https://gist.github.com/KevinMayfield/b1dc6e9baf3152500df3eecc09bc95b8
Kevin Mayfield (Oct 07 2017 at 06:18):
My view (based on how some UK GP systems store the data) is both are roughly the same.
Kevin Mayfield (Oct 07 2017 at 06:21):
And search for [Finding of tobacco smoking consumption (finding)] should return both Observations.
Kevin Mayfield (Oct 07 2017 at 06:41):
Actually I think I've got my gists wrong. The code 428041000124106 | Occasional tobacco smoker (finding) | should be in valueCodeableConcept and I believe the code is possibly 229819007 |Tobacco use and exposure (observable entity
Kevin Mayfield (Oct 07 2017 at 06:46):
So corrected Observation is: https://gist.github.com/KevinMayfield/a1921748f91e6245319132989be14909
Kevin Mayfield (Oct 07 2017 at 06:50):
Kevin Mayfield (Oct 07 2017 at 06:50):
For non smoker
Kevin Mayfield (Oct 07 2017 at 06:52):
So for some finding's I can work out the Observation.code from the CodeSystem (which implies I'd need some form of terminology database) :)
Kevin Mayfield (Oct 07 2017 at 06:54):
On my implementation I don't want to store the parent of a valueCodeableConcept as it may create duplication issues when searching.
Kevin Mayfield (Oct 07 2017 at 06:57):
So that leads onto the next question - do I need to store category. Can I use refsets or other to populate category from the recorded SNOMED concept.
Kevin Mayfield (Oct 07 2017 at 06:59):
@Jonny Rylands @Ian McNicoll ?
Kevin Mayfield (Oct 07 2017 at 07:44):
@Victor Harris
Ian McNicoll (Oct 07 2017 at 17:10):
Hi Kevin, Can you give a wee bit more background context as to what you are trying to do? First you need to define your valueset and that very often is a restriction on the SNOMED hierarchy (which often contains irrelevant or orthogonal terms) plus get agreement on what your user community actually means by 'smoking status' - the Argonaut defs. may not apply in the UK. In broad terms I don't think the way you have set this up is incorrect but it might not fit the user need as it seems pretty broad. In general, any time you start using SNOMED CT in anger you are going to need a terminology server to resolve relationships, handle refsets etc., and you should not store the parent - the termserver should work that out if needed. @Hildi Franke - any thoughts from UK GP system experience
Last updated: Apr 12 2022 at 19:14 UTC
