Stream: implementers
Topic: userSelected - have to be a human user?
Sheridan Cook (May 17 2021 at 16:30):
Is userSelected exclusively meant for communicating a selection from a human being as the end user?
For example - if a human being selected a visit type from a drop-down and that type determined the visit class that was recorded in the system based on the actions of the human user- would that be excluded for userSelected as an inferred value (even though it was entirely driven by a clinician selection)?
I ask because Visit types and classes can be sanitized/re-coded/translated for a variety of reasons both inside and outside the hospital- it would be nice to have a mechanism to communicate that the coding for something like encounter class was in fact the original coding for decided at point of care.
Lloyd McKenzie (May 17 2021 at 17:59):
@Grahame Grieve
Grahame Grieve (May 17 2021 at 19:53):
From the spec:
There is some ambiguity about what exactly 'directly chosen' implies
Michele Mottini (May 17 2021 at 20:26):
Our system mostly aggregate data coming from other systems and we use userSelected to mean 'this is the original code we got' as opposed to codes we added via mappings or other data enrichment functions
Sheridan Cook (May 17 2021 at 20:34):
Michele Mottini said:
Our system mostly aggregate data coming from other systems and we use userSelected to mean 'this is the original code we got' as opposed to codes we added via mappings or other data enrichment functions
Thanks Michele! This is the exact scenario I was curious about. Can I ask what you do if the originating source provides more than one coding for a CodeableConcept (i.e. local code and snomed code for the same concept)... Both userSelected in that case?
From Grahame's message it sounds like there is flexibility in this approach. I'd hate to add an extension if there was an element that could reasonably be used to communicate the concept.
Michele Mottini (May 17 2021 at 21:26):
If we receive multiple codes from the source they are all going to have userSelected=true in our implementation
Last updated: Apr 12 2022 at 19:14 UTC
