 |
Return to detail page at www.hitsp.org | HITSP/T24 |
| Prev TOC |
| HOME | ABOUT | MEMBERSHIP | NEWS & ANNOUNCEMENTS | MEETINGS | FAQ | CONTACT US | | Powered by American National Standards Institute |
|
Return to detail page at www.hitsp.org | HITSP/T24 |
| Prev TOC |
The following sections provide the history of all changes made to this document since the last publication.
This document is now Released for Implementation.
Updated to new template
Added support for provider data pseudonymization
Generalized term patient to person
Updated context to include Quality in addition to Public Health
Updated the standard Use Case as a general person pseudonymization Use Case
Added Quality Extension
Added constraints to the Patient Identity Feed and PIX Query for support of provider pseudonymization
Upon approval by the HITSP Panel on December 13, 2007, this document is now Released for Implementation.
Updated to place standards into 3 categories: Regulatory, Selected, and Informative References
This document has been modified to reflect the updated HITSP approach to categorizing standards as Regulatory Guidance, Selected Standards, and Informative References.
The following standard has been designated as regulatory guidance:
Health Insurance Portability and Accountability Act (HIPAA) -- Administrative Simplification
The following standard has been designated as informative reference:
Health Level Seven (HL7) Version 2.5
The following standard has been added as informative reference:
Integrating the Healthcare Enterprise (IHE) IT Infrastructure Technical Framework (ITI-TF) Revision 4.0, Volume 2 Transactions, Appendix M Using Patient Demographics Query in a Multi-Domain Environment
Upon approval by the HITSP Panel on August 27, 2008, this document is now Released for Implementation.
Minor editorial changes were made to this document. Boilerplate text was removed for simplification. The term actor was replaced with interface.
Upon approval by the HITSP Panel on July 8, 2009, this document is now Released for Implementation.
[1] Future considerations are necessary to generalize the purpose, the types of HL7 Feeds that may be leveraged, and to harmonize with the HITSP Security and Privacy TC ongoing and pending efforts in identity management.
[2] Optionality = R for Required, R2 for Required if known, O for Optional, or C for Conditional. Conditional footnotes are further described below.
[3] 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.
|
Return to detail page at www.hitsp.org | HITSP/T24 |
| Prev TOC |