FHIR Chat · Vital signs Body Height standing · implementers

Stream: implementers

Topic: Vital signs Body Height standing


view this post on Zulip Ardon Toonstra (Sep 06 2017 at 14:11):

There are two loinc codes in use for Body height in the vital signs profile, namely: 8302-2 - body height and 8306-3 - body height --lying. Suppose I want to explicitly convey body height standing, what do I do? Do I use the profile with loinc code 8302-2 with a supporting observation for "standing"? Or do I use Loinc code 8308-9 - body height --standing?

view this post on Zulip Eric Haas (Sep 06 2017 at 16:09):

...or assume is standing unless otherwise specified... or add a translation for the standing code

view this post on Zulip Alexander Henket (Sep 06 2017 at 18:31):

I'd agree that Body height - standing is the usual way for anyone >1yr or so, but inferring semantics like that does not seem right to me.

What do you mean by adding a "translation"? Is that adding a second code 8306-9 next to 8302-2? If that is a valid solution than we might as well be consistent and do the same for 8302-2 + 8306-3 Body height - lying and skip that separate profile altogether. That sounds doable to me.

view this post on Zulip Rob Hausam (Sep 06 2017 at 19:08):

I agree, Alexander. I think they are analogous, and it's probably not necessary or helpful to call out body length separately - it could all be 8302-2 (Body height), since it can cover both standing and lying, with the more specific translation codes in addition if they are felt to be needed. I don't recall the details of our previous discussions on this (I'm sure that @Eric Haas probably does) and why it ended up this way, but it seems like this change would make sense.

view this post on Zulip Michelle (Moseman) Miller (Sep 06 2017 at 19:25):

+1 - I believe that is what is conveyed in the profile when it says:

If a more specific code or another code system is recorded or required, implementers must support both the values (LOINC) listed below and the translated code - e.g. method specific LOINC codes, SNOMED CT concepts, system specific (local) codes

Thus, it would manifest as two Observation.code.codings in our implementation.

view this post on Zulip Alexander Henket (Sep 08 2017 at 08:45):

+1 We can work with that. @Ardon Toonstra can you open a tracker for this, so the international Vital Sign for Body height - lying could be deprecated, and wording on Vital Sign for Body height could be extended to make clear that "translations" are the way to go for lying/standing?

view this post on Zulip Ardon Toonstra (Sep 08 2017 at 09:57):

Created GF#13801

view this post on Zulip Eric Haas (Sep 09 2017 at 00:13):

wording on Vital Sign for Body height could be extended to make clear that "translations" are the way to go for lying/standing?

As the primary editor of this artifact That suggestion is a slippery slope - We already state this generally... and provide several example that demonstrate it. One could state something similar for every other profile in vitals.

view this post on Zulip Alexander Henket (Sep 11 2017 at 04:35):

Maybe, but then you also created a separate profile for Body height lying in the Vital Signs panel that does not work like that, and thus created confusion about that mechanism. If the translations thing really works that way naturally for everyone, then the Body height - lying thing would not have existed.

So now that this separate profile exists you can:
1. Obsolete that separate profile and add wording to the general profile Body height to say that translations are the way to go for lying/standing

2. Create a new Body height profile for standing and leave the initial two as-is

If translations are the right direction generally, and that sounds right to me, then 1. is the only right solution. If translations are only sometimes the right solution, then 2. is an option, but it invites people around the world to profile similarly thus creating a zillion profiles based on more specific versions of existing profiles.

view this post on Zulip Eric Haas (Sep 11 2017 at 22:03):

I believe a tracker is already in the docket. Will run by OO and US Realm (for US Core profiles)


Last updated: Apr 12 2022 at 19:14 UTC