Example of an unconstrained table
Table 0202 (telecommunications equipment type)
Table as of v2.7.1 (only Satellite Phone is new form 2.5.1)
HL7 Table 0202 - Telecommunication Equipment Type
Value
PH
FX
MD
CP
SAT
BP
Internet
X.400
TDD
TTY
Description
Telephone
Fax
Modem
Cellular or Mobile Phone
Satellite Phone
Beeper
Internet Address
X.400 email address
Telecommunications Device for the Deaf
Teletypewriter
Comment
Conformance statement for NK1-5:
Conformant systems shall support values of PH, CP, and Internet in NK1-5.
Comments:
The table in section 5 would not need to call out all values because we are not trying to exclude support
for any value.
On a side note, I think it’s unfortunate that the next of kin phone number is RE where the patient phone
number is C(RE/O) depending on support for the PH profile. It seems inappropriate to require more
demographics from a next of kin than from the patient.
I’ll also note that I don’t think we can achieve our desire to send the home and business phone numbers
for next of kin in NK1-5 alone (not support NK1-6) because we don’t require that XAD.2
(Telecommunication Use Code) to be supported and that is how we distinguish between a work and
residence phone number.
Example of a constrained table
Table 0065 (specimen action code)
Table in the IG right now:
HL7 Table 0065 – Specimen Action Code (V2.7.1)
TABLE 0-1. HL7 TABLE 0065 SPECIMEN ACTION CODE (V2.7.1)
Value
Document1
Description
Usage Comment
-1-
Last Saved: 2/9/2016 1:51:00 AM
TABLE 0-1. HL7 TABLE 0065 SPECIMEN ACTION CODE (V2.7.1)
Value
Description
Usage Comment
A
Add ordered tests to the existing specimen
C(R/O) Condition Predicate: If MSH-21 contains
‘2.16.840.1.113883.9.PP’
(LOI_AO_Component).
G
Generated order; reflex order
R
L
Lab to obtain specimen from patient
R
O
Specimen obtained by service other than Lab
R
P
Pending specimen; order sent prior to delivery
R
R
Revised order
R
S
Schedule the tests specified below
R
D
Specimen obtained by provider
R
Table as of v2.7.1
Value
A
G
L
O
P
R
S
Description
Add ordered tests to the existing specimen
Generated order; reflex order
Lab to obtain specimen from patient
Specimen obtained by service other than Lab
Pending specimen; Order sent prior to delivery
Revised order
Schedule the tests specified below
Comment
Note that “D – Specimen obtained by provider” is unique to the IG.
Conformance statement for OBR-11:
Conformant systems shall support values of L, O, P and D in OBR-11.
Comments:
Given my comment above about defining acceptable values in the table in the back, I’m not sure what
this table would look like. But, the table contains several values that I feel cannot be required by this
guide. For example, as I understand it, Add Ons are being considered as new orders and so “A” cannot
be a required value to support. As well, the guide does not touch on updating orders, so “R” cannot be a
required value to support. There may be others too.
Example of a user defined table
Table 0045 (courtesy code)
Table in the IG right now:
Document1
-2-
Last Saved: 2/9/2016 1:51:00 AM
HL7 Table 0045 – Courtesy Code
TABLE 0-1. HL7 TABLE 0045 COURTESY CODE
Value
Description
S00
Patient will receive 100% discount
S01
Patient will receive 95% discount
S02
Patient will receive 90% discount
S03
Patient will receive 85% discount
S04
Patient will receive 80% discount
S05
Patient will receive 75% discount
S06
Patient will receive 70% discount
S07
Patient will receive 65% discount
S08
Patient will receive 60% discount
S09
Patient will receive 55% discount
S10
Patient will receive 50% discount
S11
Patient will receive 45% discount
S12
Patient will receive 40% discount
S13
Patient will receive 35% discount
S14
Patient will receive 30% discount
S15
Patient will receive 25% discount
S16
Patient will receive 20% discount
S17
Patient will receive 15% discount
S18
Patient will receive 10% discount
S19
Patient will receive 5% discount
This table is not currently in chapter 02C in 2.7.1. In chapter 3 of 2.5.1, there are no suggested values.
Conformance statement for PV1-22:
<none>
Comments:
Are there really values from this table that we think all EMRs should be required to support? Or is it
enough to say that this field must be supported (it’s current C(RE/O) based on the value in PV1-20)? In
that case, is it enough to list the values in the table in section 5? Do we have to note that the EMR must
support some values but that no individual value is required? Or should all of them be required?
Document1
-3-
Last Saved: 2/9/2016 1:51:00 AM
Example of a non-HL7 table code set
Conformance statement for OBR-4:
Conformant systems shall be capable of sending all LOINC as specified by the laboratory system as part
of the ordering compendium.
Comments:
It is not practical for the IG to list every LOINC code that should be supported by a compliant system.
Not only is LOINC constantly evolving, but any given implementation may only use a subset of the
defined LOINC codes. I think that for data sets like LOINC, SNOMED and ICD (9 or 10), it makes more
sense to require a generic mechanism to support sending and receiving codes and let the individual
implementations define exactly which codes are in scope. Unlike some of these other tables (such as
specimen action code), in my mind specific LOINC, SNOMED and ICD don’t imply particular workflows or
integration scenarios are supported.
Document1
-4-
Last Saved: 2/9/2016 1:51:00 AM