Stream: committers
Topic: discriminators
Eric Haas (Mar 26 2016 at 15:17):
I had an issue before with trying to slice translations on codeableconcept by system ( e.g. I wanted the first coding to be LOINC then you could optionally have has many other codings as you wanted (more specific loinc, smomed, local etc) could not do it since the slicing discriminator was not specific since I could not prescribe the additional code system? "When a discriminator is provided, the composite of the values of the elements designated in the discriminator is unique and distinct for each possible slice and applications can easily determine which slice an item in a list is." Is there a solution for this now? Or do I have to descriminate at the code level?
Lloyd McKenzie (Mar 26 2016 at 15:21):
First - doing what you're trying to do - saying that specific coding repetitions need to appear in specific positions - is really bad practice. It essentially says "I don't care if you've got the data I need, I need you to specifically put the data in a specific order to talk to me, even though order is meaningless"
Lloyd McKenzie (Mar 26 2016 at 15:22):
That said, all you should need to do is declare the first slice, say that slicing is ordered and the slicing is open.
Eric Haas (Mar 26 2016 at 15:23):
I don't care if it position 1 , 2 or 6 just want it to be there...
Lloyd McKenzie (Mar 26 2016 at 15:24):
In that case, declare the slicing as "unordered". Though it would seem easier to just declare a fixed binding to "all of LOINC"?
Eric Haas (Mar 26 2016 at 15:26):
Iremember we has very long discussion on this for US Lab and that's what we did. but If I have a code now it can be sliced right
Eric Haas (Mar 26 2016 at 15:26):
thanks for clearing the cobwebs
Last updated: Apr 12 2022 at 19:14 UTC
