FHIR Chat · US Core QA Issue #3- nasty profiling error · IG creation

Stream: IG creation

Topic: US Core QA Issue #3- nasty profiling error


view this post on Zulip Eric Haas (Jul 03 2020 at 00:40):

have a nasty QA issue that did not get caught last time. The FHIR Core vitals profile has a required binding for UCUM on the component value(x) that the pulse OX profile violates in the flow component --- no l/min :-(

Unfortunately we missed that one last summer. I don't see a clean technical solution. ( I would have thought had a tracker for the core vitals profile already ... but I just made one J#27911 )

view this post on Zulip Eric Haas (Jul 03 2020 at 00:43):

here is the error for this instance: https://build.fhir.org/ig/HL7/US-Core-R4/Observation-satO2-fiO2.html

The Coding provided is not in the value set http://hl7.org/fhir/ValueSet/ucum-vitals-common|4.0.1(which actually refers to http://hl7.org/fhir/ValueSet/ucum-vitals-common), and a code is required from this value set. (error message = The code provided (http://unitsofmeasure.org#l/min) is not valid in the value set VitalSignsUnits)

view this post on Zulip Grahame Grieve (Jul 03 2020 at 00:45):

should be L/min?

view this post on Zulip Eric Haas (Jul 03 2020 at 01:02):

thanks for catching that and I will correct that but Its the parent profile that is the problem.

image.png

view this post on Zulip Grahame Grieve (Jul 03 2020 at 01:17):

well, make a task to fix the parent profile then

view this post on Zulip Eric Haas (Jul 03 2020 at 01:18):

J#27911

view this post on Zulip Paul Bastide (Aug 31 2020 at 17:49):

Thanks Eric and Graham, this conversation was very helpful to resolve our issue with the profile.


Last updated: Apr 12 2022 at 19:14 UTC