12.07.2015 Views

IHE Patient Care Device Technical Framework

IHE Patient Care Device Technical Framework

IHE Patient Care Device Technical Framework

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

10<strong>IHE</strong> <strong>Patient</strong> <strong>Care</strong> <strong>Device</strong> <strong>Technical</strong> <strong>Framework</strong>, Vol. 2: Transactions________________________________________________________________________conformant receiving application may ignore the values of that element. Ifthe element is not present, the conformant receiving application shall notraise an error due to the presence or absence of the element.If the predicate is NOT satisfied: The conformant sending application shallnot populate the element. The conformant receiving application may raisean application error if the element is present.X: Not supported. For conformant sending applications, the element will not besent. Conformant receiving applications may ignore the element if it is sent,or may raise an application error.• Cardinality: Within square brackets, minimum and maximum number of occurrencesauthorized for this segment in the context of this Integration Profile.• HL7 chapter: Reference of the HL7 v2.5 chapter that describes this segment.Table 3.2-1: Example: Initial segments of a message descriptionSegment Meaning Usage Card. HL7 chapterMSH Message Header R [1..1] 2[ --- PATIENT begin [1..1]PID <strong>Patient</strong> Identification R [1..1] 3[ --- PATIENT VISIT begin [1..1]PV1 <strong>Patient</strong> Visit RE [0..1] 3F.2 Static definition – Segment level and Data Type level20The Segment table and the Data Type table each contain 8 columns:• SEQ: Position (sequence) of the field within the segment.• LEN: Maximum length of the field• DT: Field Data Type• Usage: Usage of the field within this <strong>IHE</strong> Integration Profile. Same coded values asin the message level: R, RE, C, CE, O, X.• Cardinality: Minimum and maximum number of occurrences for the field in thecontext of this Integration Profile.• TBL#: Table reference (for fields using a set of defined values)• ITEM#: HL7 unique reference for this field• Element Name: Name of the field in a Segment table. / Component Name: Name ofa subfield in a Data Type table.Table 3.2-2: Example: The MSH segment descriptionSEQ LEN DT Usage Card. TBL# ITEM# Element name1 1 ST R [1..1] 00001 Field SeparatorRev. 1.1 TI: 2006-08-1597Copyright © 2005-2006: ACC, ACCE, HIMSS, and RSNA

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!