You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is consistent with what I was thinking, but other examples I found seem to always include the value of PQ in addition to the units in 'originalText' (e.g. http://www.cdapro.com/know/24981)
I think that including just the original unit text is 'valid' but it does seem like including the value would help with things like display of the original text. Maybe the sample should include the value as well as the unit if that is whats normally expected?
The text was updated successfully, but these errors were encountered:
When both the value and unit are coded I completely agree -- include both in originalText.
When you receive a 'coded' non-ucum unit from the lab we decided to put that alone in originalText. I am not sure it's the best choice. In another sample we got even more creative...Result with non-numeric physical quantity and unit
I was looking for an example of how to encode a result observation that has no obvious mapping to UCUM and I found the example at https://github.com/HL7/C-CDA-Examples/blob/master/Results/Results%20Unit%20Non-UCUM/Results%20Unit%20Non-UCUM(C-CDA2.1).xml
This is consistent with what I was thinking, but other examples I found seem to always include the value of PQ in addition to the units in 'originalText' (e.g. http://www.cdapro.com/know/24981)
I think that including just the original unit text is 'valid' but it does seem like including the value would help with things like display of the original text. Maybe the sample should include the value as well as the unit if that is whats normally expected?
The text was updated successfully, but these errors were encountered: