Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should originalText include the value as well as the unit? #10

Open
lmsurpre opened this issue Sep 22, 2017 · 2 comments
Open

Should originalText include the value as well as the unit? #10

lmsurpre opened this issue Sep 22, 2017 · 2 comments

Comments

@lmsurpre
Copy link

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?

@brettmarquard
Copy link
Collaborator

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

@sumaiya1996
Copy link

🕋

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants