Stream: terminology
Topic: Terminology-Supported-Extension: avatar of V3?
Jay Lyle (Jun 23 2020 at 14:36):
We'd like our extensions to be easy to look up and understand. One way to do that would be to use Observations, which we do when the subject is a Patient. But for an Immunization, that seems out of line.
We are considering using the terminology resources defined for V2 (LOINC code for Vaccine Information Statement date, e.g.). This means creating a complex extension with a fixed element for the code. Seems legal.
But once the semantics go in the code, we've kind of reinvented V3 Observation, and we might just leave the code open in the extension, fixing it in specific profiles. Does that prospect cause fear and loathing, or joy?
Lloyd McKenzie (Jun 23 2020 at 15:13):
Vaccine Information Statement date seems like it's the same as Immunization.recorded, so you probably shouldn't be using an extension at all. Extensions are already relatively easy to look up and understand - they're identified by URL which should generally resolve to a definition (and ideally a web page) that provides a full description of the content. It would be completely inappropriate to turn all extensions into complex extensions just so you can convey a code that is redundant with the meaning conveyed by the URL. If you want to specify a code, put it in the definition of the extension, not in the instance. (So definitely loathing :>)
Jay Lyle (Jun 23 2020 at 16:48):
Fair enough. "Put the definition in the extension": i.e., in a mapping? I'd like the equivalence to be computable. (Looks like in this case VIS will be supported by R5 Immunization.education.reference & publicationDate)
Craig Newman (Jun 23 2020 at 17:04):
I don't think Immunization.recorded is redundant with the VIS provided date. You might be able to make an argument that Immunization.occurenceDateTime should be the same as the VIS provided date (you should get educational materials when you get the shot), but they really are different concepts.
Lloyd McKenzie (Jun 23 2020 at 21:19):
StructureDefinition.snapshot.element[0].concept contains the 'code' that represents the overall structure
Lloyd McKenzie (Jun 23 2020 at 21:19):
(If there is one, and if anyone has bothered to declare it.)
Last updated: Apr 12 2022 at 19:14 UTC
