IHE Patient Care Device Technical Framework

IHE Patient Care Device Technical Framework, Vol. 2: Transactions________________________________________________________________________SEQ LEN DT Usage Card. TBL# Component name6 227 HD RE [0..1] Assigning Facility7 8 DT RE [0..1] Effective Date8 8 DT RE [0..1] Expiration Date9 705 CWE RE [0..1] Assigning Jurisdiction10 705 CWE RE [0..1] Assigning Agency or DepartmentThe constraints above particularly apply to the Patient Identifiers carried in the PIDsegment.The data type has been constrained because the PCD Framework regards the AssigningAuthority and the Identifier Type Code as essential components.A common value of the Identifier Type Code for a Patient Identifier assigned by thehealthcare organization (PID-5) is “PI”. Other values are defined in Table 0203 of HL72.5 section 2.A.14.5Example: 12345^^^Saint-John Hospital^PIC.3 EI Data Type1020Table 30 EI: Entity IdentifierSEQ LEN DT Usage Card. TBL# Component name1 16 ST R [1..1] Entity Identifier2 20 IS RE [0..1] 0363 Namespace ID3 199 ST RE [0..1] Universal ID4 6 ID RE [0..1] 0301 Universal ID TypeComponent 1 is required. Either component 2 or both components 3 and 4 are required.Components 2, 3 and 4 may be all present.The EI is appropriate for machine or software generated identifiers. The generatedidentifier goes in the first component. The remaining components, 2 through 4, areknown as the assigning authority; they can also identify the machine/system responsiblefor generating the identifier in component 1.Example 1: AB12345^RiversideHospitalExample 2: AB12345^^1.2.840.45.67^ISOExample 3: AB12345^RiversideHospital^1.2.840.45.67^ISOIHE constrains the length of the first component to 16 characters. National extensions canextend this length up to a maximum of 199.IHE recommends that Component 2, “Namespace ID,” always be populated. Particularlywhen there are several concurrent assigning authorities within the healthcare enterprise,Rev. 1.1 TI: 2006-08-1558Copyright © 2005-2006: ACC, ACCE, HIMSS, and RSNA