Stream: australia
Topic: Vital signs
Grahame Grieve (Mar 19 2016 at 21:30):
Active discussion in argonaut project about vital signs, and a move to impose a single profile for vital signs for all FHIR use.
Grahame Grieve (Mar 19 2016 at 21:31):
Does Australia have any standards for the representation or exchange of vital signs?
Grahame Grieve (Mar 20 2016 at 00:07):
Candidate: http://argonautwiki.hl7.org/index.php?title=Vital_Signs
Grahame Grieve (Mar 20 2016 at 00:07):
comments welcome
Brett Esler (Mar 20 2016 at 07:13):
I am mostly really happy to go along with how this is defined in Argonaut
Brett Esler (Mar 20 2016 at 07:15):
However, one query is how to do sitting/lying/standing blood pressure this is a commonly implemented qualifier for the observations
Brett Esler (Mar 20 2016 at 07:24):
I have BP loinc codes for these as:
sitting: 8459-0 / 8453-3
standing 8460-8 / 8454-1
lying 8461-6 / 8455-8
Grahame Grieve (Mar 20 2016 at 10:11):
well, that's why we allow additional codes. You code with the simplest code, always, so it can always be found, but you can also code with more information for applications that need more understanding
Brett Esler (Mar 20 2016 at 11:14):
so could support the argonaut profile non-specifc blood pressure for all of these? i.e. can't tell the difference?
David Hay (Mar 20 2016 at 16:52):
Is observation.method a possibility for the lying/standing question?
Grahame Grieve (Mar 20 2016 at 21:45):
This is the iso-morphism that CIMI is obsessed with. You can use a generic code in Observation.code, and a method code, or you can use a combination code in Observation.code.
Grahame Grieve (Mar 20 2016 at 21:46):
though there's an open discussion about whether things like posture are method things or not - that's effectively a different kind of iso-morphism
Brett Esler (Mar 21 2016 at 00:47):
do we need a profiled preferred way for these? if I want to chart/report blood pressure I would care about the body position so means a profile that uses generic code and method would need to be able to search by code and method;
Brett Esler (Mar 21 2016 at 00:47):
currently no search param for method...
Grahame Grieve (Mar 21 2016 at 00:49):
I don't think you'd want to search by method. I think you'd still need to plot them all, just mark them differently.
Grahame Grieve (Mar 21 2016 at 00:49):
but you could propose a search parameter for method.
Grahame Grieve (Mar 21 2016 at 00:49):
not that we have any chance of nailing down which method codes etc .
Grahame Grieve (Mar 21 2016 at 00:49):
it'll be enough just to get everyone to agree to use the same code at all
Brett Esler (Mar 21 2016 at 00:55):
think i would prefer to have all the Observation codes available (for specific and unspecified body position) then just use the ones the profile needs - think this will come up again in other areas; you care if you care...
Brett Esler (Mar 21 2016 at 00:57):
if I am supporting specific then I would like to have that available via search etc. but would I have the same observation in twice or have specific and non-specific components? e.g. bloodpressure with children systolic, diastolic, systolic-sitting, diastolic-sitting
Grahame Grieve (Mar 21 2016 at 00:57):
what we're trying to do is just to get everyone to use at least the one common code. Additional specific codes can also be provided
Grahame Grieve (Mar 21 2016 at 00:58):
you're going to have one observation, with multiple codes for the value
Brett Esler (Mar 21 2016 at 00:58):
so okay to have a generic and specific code in the Observation.code or Observation.component.code
Grahame Grieve (Mar 21 2016 at 00:59):
yes
Brett Esler (Mar 21 2016 at 00:59):
ah okay cool - very happy with that
Brett Esler (Mar 21 2016 at 01:02):
so if we are keen in the AU space suggest we support the argonaut profile as is and give some guidance on how/which codes to use for specific blood pressure observations
Last updated: Apr 12 2022 at 19:14 UTC
