Details
-
Change Request
-
Resolution: Considered for Future Use
-
Medium
-
V2.x Message Specification (V2)
-
V2.9
-
Orders & Observations
-
Observation/Result (OBX)
STRUCTURED NUMERIC (SN) -
Data Types (Chapter 2A)
Observations (Chapter 7) -
2A.3.71.1,7.4.2.5
-
-
Riki Merrick / Peni Moxim: 2- 0 - 0
Description
Our definition of the SN.1 (Comparator) component is somewhat vague and it isn't explicitly clear that it can be used as part of a ratio. For example, an observation for LOINC code 32999-5 (Rickettsia spotted fever group Ab.IgG) with a value of "<1:64" should be reported using an SN value like "<1:^64". I recommend we add another informative example like that in section 2A.3.71.1, or if it isn't appropriate there then consider adding it in section 7.4.2.5.
Attachments
Issue Links
- relates to
-
V2-25403 Deprecate SN.3 (Separator/Suffix) value of "+"
- Resolved - change required
-
V2-25494 Make SN.2 conditional on SN.1
- Applied
-
V2-25190 Tracker ID 25190: Optionality for SN components
- Resolved - change required
-
V2-25369 Specify SN allowed Separator/Suffix values based on other components
- Resolved - change required
-
V2-25401 Deprecate SN.1 (Comparator) value of "="
- Resolved - No Change
- mentioned in
-
Page Loading...