This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Tabel definitie

From HL7Wiki
Revision as of 20:44, 9 November 2009 by Adri burggraaff (talk | contribs) (New page: 2.7.6 Table Definition: The table attribute of the data field definition specifies the HL7 identifier for a set of coded val-ues. In the segment attribute tables, the table identifier is ...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

2.7.6 Table Definition: The table attribute of the data field definition specifies the HL7 identifier for a set of coded val-ues. In the segment attribute tables, the table identifier is provided in the column labeled TBL#. An entry in the table number column means that the table name and the element name are equivalent. If this attribute is not valued or blank, there is not a table of values defined for the field. A number of conventions have been applied to this attribute of the data field definition. 1. If more than one table is applicable, the format xxxx/yyyy will be used to so designate multiple tables. Details on multiple tables will be specified in field notes. 2. If the field is of data type ID or IS a table number will be allocated even if, in the case of IS, there may be a notation "No Suggested values" 3. If the field is of data type CE and one or more externally or locally defined tables may be used, the symbolic number 9999 will appear in the column. This is to indicate that table values are used, but no HL7/User Defined table can be allocated. The narrative may constrain which external tables can be used. 4. Tables embedded in field components or subcomponents will not be cited in the attribute column. The exception to this convention are the CE, CNE, CWE and CF data types where the table is dependent on the field context. This also applies to the CM data type if it contains embedded tables. a) Data types having embedded tables are identified in HL7 Table 440 -Data types. These tables are defined in the data type section. They may, however, be constrained in the field note section. The field note definition supercedes the definition in the data type section. b) Tables embedded in fields with a data type of CE, CF CNE, CM or CWE are only defined in the field notes section. HL7 defines table values in 3 ways: HL7 defined, user-defined and externally defined User-defined Tables: A user-defined table is a set of values that are locally or site defined. This accom-modates certain fields, like PV1-3 - Assigned patient location, that will have values that vary from institu-tion to institution. Even though these tables are not defined in the Standard, they are given a user-defined table number to facilitate implementations. HL7 sometimes publishes suggested values that a site may use as a starter set (e.g., table 0001- Sex). The IS data type is often used to encode values for these tables. Note that some of these tables (e.g., table - 0302 Point of care) may reference common master files. There are some user-defined tables that contain values that might be standardized across institutions but for which no applicable official standard exists. For these a set of suggested values may be listed in Appendix A. These suggested values appear in the text in a standard box format (e.g., HL7 Table 0062 - Event reason in Section 3.4.1.4, “Event reason code”). It is recommended that these values be used where applicable within an institution and serve as a basis for extensions as required. These values may, however, be rede-fined locally. The appropriate functional committee within HL7 solicits suggestions for additional values from institutions that are applying the Standard. HL7 Tables: An HL7 table is a set of values defined and published by HL7. They are a part of the HL7 Standard because they affect the interpretation of the messages that contain them. These values may not be redefined locally; however, the table itself may be extended to accommodate locally defined values. This is particularly applicable in the case of HL7 table 0003 – Event Type. The ID data type is most often used to encode values for HL7 tables. The values are listed in Appendix A. These HL7 tables also appear in the text in a standard box format (e.g., HL7 table 0003 Event Type) External Tables: An external table is a set of coded values defined and published by another standards or-ganization. External tables are used to populate fields like FT1-19-Diagnosis Code - FT1. Another exam-ple, the encoding of clinical observations using LOINC codes. The CE data type is used to represent values for these fields. Table numbers 9000 and above are reserved for externally-defined tables published by HL7. Such tables arise from applications where the concepts and possibly the codes are established by external agencies due to regulatory requirements or agreements between HL7 and other Standards Developing Organizations. They are published by HL7 on behalf of other organizations. Their contents are not subject to approval by HL7 ballot. Such tables will be published with HL7 Standards. However, they may be updated more fre-quently than HL7 Standards. HL7 will provide free downloads of the most recent versions of these tables via the Internet without requiring membership in HL7.