HL7 provides two ways by which to offer message
representation:
- Sampled object representation
The HL7 message body offers object representation to just the
header. The message body is treated as a blob. One business object,
to represent all message types.
- Native object representation
This level of object representation of HL7 message offers object
representation to both message header and message body. A
corresponding business object represents virtually every HL7 data
element, including every message structure or query.
The following sections describe rules to follow when
constructing business objects to represent HL7 data elements.
When creating, configuring or modifying supported native
messages:
- All message types and queries, except examples, defined by
version 2.4 of HL7 message standard specification
- Industry specific business objects (ISBO) that correspond to
the template used in the standard specification are provided for
reference only. Not all data elements are fully solidified, thus no
support is provided to these business objects.
- Earlier versions of the HL7 standard permited users to create
their own custom made (CM) data type. Since CM data types are not
specified in the standard, they are not included in the published
collection of industry specific business objects (ISBOs). However,
the meta-data model employed in the published ISBOs offers users a
way to create their ASBO representation to these CM data types
Use the following table to map the primitive data type:
Table 25. Mapping the
Primitive data type
HL7 data
elements |
Business object
attribute data type |
SI |
String |
ID |
String |
NM |
Float |
DT |
String |
IS |
String |
ST |
String |
FT |
String |
TX |
String |
