Stream: implementers
Topic: patient.multipleBirth
Jose Costa Teixeira (Dec 06 2019 at 09:53):
We are discussing that patient.multipleBirth seems not really administrative but closer to the clinical side. What is the reason for it not to be e.g. an observation?
Cooper Thompson (Dec 06 2019 at 14:18):
Multiple birth indicators are often use in patient matching, so having them on Patient makes matching possible without having to dig into Observation.
Lloyd McKenzie (Dec 06 2019 at 17:48):
It's really about demographic identification. "Baby Smith #2" as opposed to "Baby Smith #3" - because with newborns they don't necessarily have names yet. Now, we could argue that the usecase for this probably falls into the same category as Patient.birthtime. However, it's now normative, so too late for the discussion :)
René Spronk (Dec 07 2019 at 08:19):
It's also useful for adult patients, especially in areas where there are no solid citizen/patient identifiers, it acts as a warning "beware: twins, take care not to mix them up." - as in Huey, Louie and Dewey Duck, born on the same date, living at the same address.
Last updated: Apr 12 2022 at 19:14 UTC
