Stream: BRR - Pharmacy model
Topic: OtherCharacteristics should be a name/value pair
Jean Duteau (Sep 06 2019 at 17:27):
Right now, wherever we have OtherCharacteristics, we just have a CodeableConcept. We need to have the ability to indicate the type of characteristic and the value of that characteristic. It's not good enough for me to just say "Red", I need to say "Wrapper Colour" / "Red" (to use a contrived example).
Jean Duteau (Sep 06 2019 at 17:27):
I am making gForge tracker items for these, but I thought I'd raise them here as well.
Rik Smithies (Sep 06 2019 at 19:24):
I have also thought that. I assumed it was meant to have only pre-coordinated "permutations" of codes. But you can't do that for all colours.
Rik Smithies (Sep 06 2019 at 20:00):
There is also Physical Characteristics, if you literally want colours. But all of that could be collapsed into a single repeating pair of Code and Value[x]=code, string, quantity (and boolean)
Jean Duteau (Sep 06 2019 at 20:01):
yeah, colour was just an example. I actually had to express whether or not the product was a combination drug. So i had a valueBoolean and needed to say what the true/false represented.
Rik Smithies (Sep 06 2019 at 20:05):
Well in the contrived one, in fact your wrapper could be a packageItem component, and that could have physical characteristic of red. So it's not so contrived, it's in scope.
Rik Smithies (Sep 06 2019 at 20:06):
And there may be a use case for CombinationDrug as an attribute in its own right. That has come up before. It can be inferred but not easily (especially if you don't have all the levels). It was "Co-packaged Indicator".
Last updated: Apr 12 2022 at 19:14 UTC
