IHE Patient Care Device Technical Framework

More documents

Recommendations

Info

102030IHE Patient Care Device Technical Framework, Vol. 2: Transactions________________________________________________________________________See HL7 V2.5 Section 3.4.2.26 for details. The PCD TF does not further constrainthis field.PID-27: Veterans Military Status (CE), required but may be empty:See HL7 V2.5 Section 3.4.2.27 for details. The PCD TF does not further constrainthis field.PID-28: Nationality (CE), required but may be empty:See HL7 V2.5 Section 3.4.2.28 for details. The PCD TF does not further constrainthis field.PID-29: Patient Death Date and Time (TS), required but may be empty:Definition: This field contains the date and time at which the patient death occurred.See Appendix C.6 TS Data Type for PCD constraints.PID-30: Patient Death Indicator (ID), required but may be empty:See HL7 V2.5 Section 3.4.2.30 for details. The PCD TF does not further constrainthis field.PID-31: Identity Unknown Indicator (ID), required but may be empty:See HL7 V2.5 Section 3.4.2.31 for details. The PCD TF does not further constrainthis field.PID-32: Identity Reliability Code (IS), required but may be empty:See HL7 V2.5 Section 3.4.2.32 for details. The PCD TF does not further constrainthis field.PID-33: Last Update Date/Time (TS), required but may be empty:Definition: This field contains the last update date and time for the patient’s/person’sidentifying and demographic data, as defined in the PID segment. Receiving systemswill use this field to determine how to apply the transaction to their systems. If thereceiving system (such as an enterprise master patient index) already has a record forthe person with a later last update date/time, then the EMPI receiving system coulddecide not to apply the patient’s/person’s demographic and identifying data from thistransaction.See Appendix C.6 TS Data Type for PCD constraints.PID-34: Last Update Facility (HD), required but may be empty:See HL7 V2.5 Section 3.4.2.34 for details. The PCD TF does not further constrainthis field.PID-35: Species Code (CE), required but may be empty:Rev. 1.1 TI: 2006-08-1543Copyright © 2005-2006: ACC, ACCE, HIMSS, and RSNA
10IHE Patient Care Device Technical Framework, Vol. 2: Transactions________________________________________________________________________See HL7 V2.5 Section 3.4.2.35 for details. The PCD TF does not further constrainthis field.PID-36: Breed Code (CE), conditional.See HL7 V2.5 Section 3.4.2.36 for details. The PCD TF does not further constrainthis field.PID-37: Strain (ST), conditional.See HL7 V2.5 Section 3.4.2.37 for details. The PCD TF does not further constrainthis field.PID-38: Production Class Code (CE), required but may be empty:See HL7 V2.5 Section 3.4.2.38 for details. The PCD TF does not further constrainthis field.PID-39: Tribal Citizenship (CWE), required but may be empty:See HL7 V2.5 Section 3.4.2.39 for details. The PCD TF does not further constrainthis field.B.6 PV1 - Patient Visit Segment2030See HL7 V2.5 Section 3.4.3 for details.The PV1 segment is used by Registration/Patient Administration applications tocommunicate information on an account or visit-specific basis. The default is to sendaccount level data. To use this segment for visit level data PV1-51 - Visit Indicator mustbe valued to ‘V’. The value of PV-51 affects the level of data being sent on the PV1,PV2, and any other segments that are part of the associated PV1 hierarchy (e.g. ROL,DG1, or OBX).The facility ID, the optional fourth component of each patient location field, is a HD datatype that is uniquely associated with the healthcare facility containing the location. Agiven institution, or group of intercommunicating institutions, should establish a list offacilities that may be potential assignors of patient locations. The list will be one of theinstitution’s master dictionary lists. Since third parties other than the assignors of patientlocations may send or receive HL7 messages containing patient locations, the facility IDin the patient location may not be the same as that implied by the sending and receivingsystems identified in the MSH. The facility ID must be unique across facilities at a givensite. This field is required for HL7 implementations that have more than a singlehealthcare facility with bed locations, since the same ^ ^ combination may exist at more than one facility.Details of the PV1 segment as used in the IHE PCD Technical Framework are given inError! Reference source not found..Rev. 1.1 TI: 2006-08-1544Copyright © 2005-2006: ACC, ACCE, HIMSS, and RSNA
Page 3 and 4: 10203040IHE Patient Care Device Tec
Page 7 and 8: IHE Patient Care Device Technical F
Page 9 and 10: 1020IHE Patient Care Device Technic
Page 33 and 34: 102030IHE Patient Care Device Techn
Page 35 and 36: 10IHE Patient Care Device Technical
Page 43: 102030IHE Patient Care Device Techn
Page 79 and 80: Attribute Description Term Code Dat
Page 81 and 82: elowChannel AttributesAttribute Des
Page 95 and 96:
102030405060IHE Patient Care Device
Page 97 and 98:
10203040IHE Patient Care Device Tec
Page 99 and 100:
IHE Patient Care Device Technical F
Page 101 and 102:
102030IHE Patient Care Device Techn
Page 103 and 104:
IHE Patient Care Device Technical F
Page 105 and 106:
102030IHE Patient Care Device Techn
show all

IHE Patient Care Device Technical Framework

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?