This is the ValueSet that contains all the codes in Vital Signs Units (http://hl7.org/fhir/ValueSet/ucum-vitals-common) and Value Set - Yes No Unknown Vital Records (http://hl7.org/fhir/us/vr-common-library/ValueSet/ValueSet-yes-no-unknown-vr). E.g. what you have to deal with if you get resources containing codes in either of them
Generated Narrative: ValueSet 28e2d74c-b81c-4265-add3-d436511f9f42-8
This value set includes codes based on the following rules:
http://unitsofmeasure.org| Code | Display |
| % | percent |
| cm | centimeter |
| [in_i] | inch (international) |
| kg | kilogram |
| g | gram |
| [lb_av] | pound (US and British) |
| Cel | degree Celsius |
| [degF] | degree Fahrenheit |
| mm[Hg] | millimeter of mercury |
| /min | per minute |
| kg/m2 | kilogram / (meter ^ 2) |
| m2 | square meter |
http://terminology.hl7.org/CodeSystem/v2-0136| Code | Display |
| N | No |
| Y | Yes |
http://terminology.hl7.org/CodeSystem/v3-NullFlavor| Code | Display | Definition |
| UNK | unknown | **Description:**A proper value is applicable, but not known. **Usage Notes**: This means the actual value is not known. If the only thing that is unknown is how to properly express the value in the necessary constraints (value set, datatype, etc.), then the OTH or UNC flavor should be used. No properties should be included for a datatype with this property unless: 1. Those properties themselves directly translate to a semantic of "unknown". (E.g. a local code sent as a translation that conveys 'unknown') 2. Those properties further qualify the nature of what is unknown. (E.g. specifying a use code of "H" and a URL prefix of "tel:" to convey that it is the home phone number that is unknown.) |