The Demo site for our new HL7 Version 2+ (plus) Standard
visit the hl7 website

Draft Website - For Review Purposes Only

RP - reference pointer

HL7 Component Table - RP - reference pointer
Seq# Description Data Type Usage Vocabulary Length C.LEN Flags
RP
1 Pointer ST O
999
2 Application ID HD O
   
3 Type of Data ID O
0834(S) MIME Types(Suggested)
[4..11]    
4 Subtype ID O
0291(R) Subtype of Referenced Data(Required)
   

Components: <Pointer (ST)> & <Application ID (HD)> & <Type of Data (ID)> & <Subtype (ID)>

Subcomponents for Application ID (HD): <Namespace ID (IS)> ^ <Universal ID (ST)> ^ <Universal ID Type (ID)>

Definition: This data type transmits information about data stored on another system. It contains a reference pointer that uniquely identifies the data on the other system, the identity of the other system, and the type of data.

RP-1: Pointer (ST)

Definition: A key to the referenced data assigned by the system that stores the data. The key, which is an ST data type, is used to identify and access the data, either as an object identifier, or as a hierarchical name or query string.

RP-2: Application ID (HD)

Definition: A unique designator of the system that stores the data. It is an HD data type (See Section 2.A.33, "HD - hierarchic designator"). Application ID’s must be unique across a given HL7 implementation.

Usage Note: The Application ID together with the Pointer may form a Uniform Resource Identifier (URI) in accordance with RFC 2396. In this case the Application ID shall include the Scheme and Authority parts of the URI, and the Path part if that points to an application. The Pointer shall include the Query part of the URI, or the Path part if that points to an object. All delimiters between URI parts (“:”, “/”, “?”) should be included in the components.

Referenced data may be obtained by a mechanism not defined in the HL7 standard. The Scheme part of a URI in the Application ID specifies the access protocol, e.g., HTTP or FTP.

Example 1: A CDA document accessed by FTP:

|/cdasvc/u28864099/s9076500a/e77534/d55378.xml^&ftp://www.saintelsewhere.org&URI^text^x-hl7-cda-level-one|

Example 2: A DICOM image accessed by HTTP and converted to JPEG (using the ISO/DICOM WADO standard);

Note: the ampersands in the Pointer string are escaped to “\T\” to avoid conflict with the sub-component delimiter:

|?requestType=WADO\T\study=1.2.840.113848.5.22.9220847989\T\series=1.2.840.113848.5.22.922084798.4\T\object=1.2.840.113848.5.22.922084798.4.5^&https://www.pacs.poupon.edu/wado.jsp&URI^image^jpeg|


RP-3: Type of Data (ID)

Definition: An ID data type that declares the general type of data. Refer to Imported Table 0834 – MIME Types for valid values. Table 0834 comprises the values of MIME media types established in accordance with RFC 2046 (http://ietf.org/rfc/rfc2046.txt) and registered with the Internet Assigned Numbers Authority (http://www.iana.org/numbers.html).

Note: The MIME media type values are case-insensitive, in accordance with RFC 2045.

Note: HL7 Table 0191- Type of Referenced Data is retained for backward compatibility as of v 2.6.


RP-4: Subtype (ID)

Definition: An ID data type declaring the format for the referenced. Refer to Externally-defined Table 0291 – Subtype of Referenced Data for valid values. Table 0291 comprises the values of MIME media subtypes established in accordance with RFC 2046 (http://ietf.org/rfc/rfc2046.txt) and registered with the Internet Assigned Numbers Authority (http://www.iana.org/numbers.html).

Note: the MIME media subtype values are case-insensitive, in accordance with RFC 2045.


HL7 approved "standard" extensions as defined in table 0291 are allowed.

Additional subtypes may be added to this Standard. All subtypes registered by IANA may be used by implementation agreement between cooperating parties. In addition, private, non-standard subtypes may be defined by agreement between cooperating parties. All private, non-standard subtypes should begin with the character combination “X-” to distinguish them from the standard subtypes, in accordance with RFC 2045.