Stream: implementers
Topic: Replacing contained resources with reference.identifier?
Josh Mandel (Nov 05 2020 at 17:29):
@Paul Church do you have an example or two, in the direction of this speculation?
Paul Church (Nov 05 2020 at 17:31):
the medication has no identifying information other than a code => just put the code in an identifier ref
stub patient known only by their MRN => just put the MRN in an identifier ref
Paul Church (Nov 05 2020 at 17:32):
this goes back to the tension between subject.identifier and subject:identifier, the client has to know which convention is being used
Josh Mandel (Nov 05 2020 at 18:48):
Interesting to think about using a Coding->Identifier mapping for this (though it feels like a hack; breaks down when you're starting with a nontrivial CodeableConcept that includes multiple codings, one marked primary, etc)
Jean Duteau (Nov 05 2020 at 18:55):
for Medication, the main use of the contained resource is for specifying compound products. If you have a code, you just specify the code in the CodeableReference. If you have a description of a compound, you contain the Medication resource and specify your ingredients and/or recipe in the contained resource. Almost no implementation that I've seen is storing the compound drug as a separate Medication resource.
Jean Duteau (Nov 05 2020 at 18:57):
CodeableReference was introduced to support the idea of "specify a code or refer to a resource". Having something similar for a "specify an Identifier or refer to a resource" might be something to consider.
Vassil Peytchev (Nov 05 2020 at 18:58):
Having something similar for a "specify an Identifier or refer to a resource" might be something to consider.
You mean like the Reference data type?
Jean Duteau (Nov 05 2020 at 18:59):
True, that already exists. :)
Last updated: Apr 12 2022 at 19:14 UTC
