Stream: implementers
Topic: Mothers and fathers height
Ludvig Eek Hofmann (Apr 27 2021 at 19:32):
Hi!
We have a requirement to communicate the mothers and fathers height of a patient for a growth chart use case.
We would like to use the code attibute for sending a SNOMED code telling that the observation is a mothers or a fathers height.
Our question is however now if we should use the standard body height observation for this. The problem is that the observation height profile already has a fixed value with the LOINC code for body height.
What is the attended use for these standard profiles. Do they support the use case of sending mothers or fathers height? And if yes, is it possible to use observation.code to send a snomed code for e.g, mothers height aswell as the LOINC code? Or do we need to send a reference for the parent in the observation.focus element?
Thanks in advance!
David Pyke (Apr 27 2021 at 19:44):
Using the Observation with the standard code and Observation.focus referencing the RelatedPerson record of the Parent is the most straightforward. There are other possibilities but that likely will work most smoothly
Craig Newman (Apr 28 2021 at 13:01):
@Sarah Gaunt - where did the Vital Records project end up with the Mother's Height observation? Did it use the newborn or the mother's patient record as Observation.subject?
Ludvig Eek Hofmann (May 04 2021 at 10:02):
Thank you @David Pyke
I am curious what other possibilites there might be. In our context we do not have any reference or knowledge about the mother or father of the patient other than that the observed body height belongs to the patients mother/father.
Is the other possibility to send the code in observation.code? And if it is, should we use the standard profile when deriving our body weight profile?
I am thinking of creating a use case specific observation profile for only comunicating the mother or fathers body height. In that profile have a value set containing codes for fathers height and mothers height binded to the observation.code attribute.
David Pyke (May 04 2021 at 12:49):
Yes, if you don't have the information about the parent, you're going to need to create a custom profile on Observation to handle this case.
Ludvig Eek Hofmann (May 06 2021 at 06:12):
Thanks! @David Pyke Would you say that the custom profile should be derived from the standard body height profile(and therefor inherit the LOINC code for body height)? Or should we derive it from the standard vital sign profile and only support snomed codes for mothers height and fathers height? The only difference in the profile would be if the LOINC code would be present or not.
David Pyke (May 06 2021 at 18:07):
I would suggest that you work with a derived profile adding an extension to mark it as a parental measurement (that has no record in the server)
Lloyd McKenzie (May 06 2021 at 22:55):
You can't mark something as a parental measurement with a regular extension - you'd have to use a modifierExtension (which would mean a lot of systems wouldn't accept/process the instance). Using focus to point to a 'contained' RelatedPerson that just captures the relationship would probably be better.
Last updated: Apr 12 2022 at 19:14 UTC
