HITSP Send Laboratory Result Message Transaction

Removed footnote regarding informative nature of HITSP/C36 since that construct is complete

Removed references to HITSP/C45 Acknowledgements. This construct is no longer required; the topic is covered in the referenced HL7 Implementation Guide in HITSP/C36 - Lab Result Message

4.2 December 13, 2007

Upon approval by the HITSP Panel on December 13, 2007, this document is now Released for Implementation.

4.3 May 8, 2008

This document has been updated to include the HITSP Security and Privacy constructs and has been updated to reflect the new template.

Removed all references, direct and implied, to HITSP/TP22; this construct is no longer required

4.4 May 16, 2008

Upon approval by the HITSP Panel on May 16, 2008, this document is now Released for Implementation.

4.5 August 20, 2008

This document has been modified to reflect the updated HITSP approach to categorizing standards as Regulatory Guidance, Selected Standards, and Informative References.

Integrating the Healthcare Enterprise (IHE) IT Infrastructure Technical Framework (ITI-TF) Revision 4.0, Volume 2 Transactions, Appendix C

Internet Engineering Task Force (IETF), Transmission Control Protocol (TCP), DARPA Internet Program Protocol Specification (RFC 793)

References to the IHE ITI-TF Revision 4.0 were corrected in the narrative of the construct.

4.6 August 27, 2008

Upon approval by the HITSP Panel on August 27, 2008, this document is now Released for Implementation.

4.7 June 30, 2009

Minor editorial changes were made to this document. Removed boilerplate text for simplification. The term actor was replaced with interface.

4.8 July 8, 2009

Upon approval by the HITSP Panel on July 8, 2009, this document is now Released for Implementation.

[1] HITSP references HL7 2.5.1 messaging for lab results reporting and HL7 2.5 for other messages. Future maintenance work will move toward referencing a single HL7 version across HITSP documents.

[2] The electronic laboratory result may have been transformed, mapped and/or translated into the set of target terminologies and vocabularies prior to transmission. The technology exists to translate between terminologies and some terminologies have been cross-mapped by the National Library of Medicine (NLM). This would allow the laboratory to report using one terminology and the receiver to translate into another. While this technology exists, it is not widely used and the mappings are not yet complete. In the long term, mappings are prone to loss of information and are discouraged.

[3] Optionality = R for Required, R2 for Required if known, O for Optional, or C for Conditional

[4] "These protocols are required in HITSP/TP22 Patient ID Cross-Referencing and HITSP/T23 Patient Demographics Query,where implementers can find additional information."

[5] "These protocols are required in HITSP/TP22 Patient ID Cross Referencing and HITSP/T23 Patient Demographics Query,where implementers can find additional information."

[6] "These protocols are required in HITSP/TP22 Patient ID Cross Referencing and HITSP/T23 Patient Demographics Query,where implementers can find additional information."

4.0 Document Updates

4.1 December 5, 2007