 |
Return to detail page at www.hitsp.org | HITSP/TP30 |
| 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/TP30 |
| Prev TOC |
The following sections provide the history of all changes made to this document since the last publication.
The changes in this cycle address the following comments received during the Public Comment and Inspection Testing period (July 23, 2006 - August 17, 2007):
272, 627, 631, 633, 635, 637, 638, 641, 644, 652, 716, 859, 861, 864, 866, 868, 871, 873, 878, 882, 883, 885, 888, 889, 893, 895, 905, 908, 909, 912, 914, 915, 917, 918, 919, 922, 923, 924, 925, 926, 927, 928, 929, 930, 931, 932, 933, 934, 935, 936, 937, 938, 939, 940, 941, 942, 943, 944, 945, 946, 947, 948, 949, 950, 951, 952, 953, 954, 955, 956, 957, 958, 959, 960, 961, 962, 963, 964, 965, 966, 967, 968, 969, 970, 971, 972, 973, 974, 975, 976, 977, 978, 984, 1197, 1198, 1199, 1200, 1201, 1229, 1231, 1232, 1233, 1244, 1245, 1246, 1247, 1250, 1251
Upon approval by the HITSP Panel on October 15, 2007, this document has been moved to Version 1.1. This document is now Released for Implementation.
Updated to place standards into 3 categories: Regulatory, Selected, and Informative References.
Also clarified text surrounding transactions within the construct, as well as the examples provided to illustrate the transactions.
Updated associated UML diagrams to align with transaction flow
Added clarification on how standards listed in tables of standards are used within the construct.
Added names of standards that were being referenced within specification, however, were mistakenly not being listed in the table of standards.
Updated names/descriptions of HL7 v3 RBAC and Privacy Consent related specifications
This document has been modified to reflect the updated HITSP approach to categorizing standards as Regulatory Guidance, Selected Standards, and Informative References.
The following standards have been added asSelected:
Integrating the Healthcare Enterprise (IHE) IT Infrastructure Technical Framework (ITI-TF) Revision 4.0, Section 10 Cross-Enterprise Document Sharing (XDS.a)
Integrating the Healthcare Enterprise (IHE) IT Infrastructure Technical Framework (ITI-TF) Volume 2 Supplement 2007 2008 Cross-Enterprise Document Sharing-B (XDS.b)
Integrating the Healthcare Enterprise (IHE) IT Infrastructure Technical Framework (ITI-TF) Revision 4.0 - Registry Stored Query Transaction for XDS Profile Supplement [ITI-18]
Integrating the Healthcare Enterprise (IHE) IT Infrastructure Technical Framework (ITI-TF) Revision 4.0 XCA Supplement
Health Level Seven (HL7) Version 3.0 Privacy Consent related specifications RCMR_RM010001 - Data Consent
The following standards have been designated as Informative Reference:
Health Level Seven (HL7) Consent related vocabulary including Confidentiality Codes
The following standard was designated as Informative Reference and updated from:
Health Level Seven (HL7) Healthcare Permissions Catalogue
to:
Health Level Seven (HL7) V3 RBAC, R1-2008, HL7 Version 3 Standard: Role Based Access Control (RBAC) Healthcare Permissions Catalog, Release 1, February 2008
Upon approval by the HITSP Panel on August 27, 2008, this document is now Released for Implementation.
Editorial and technical revisions made, including:
The Consenter (i.e., the consumer of healthcare services, patient, patient representative) is NOT an interface; the IIHI Requester is NOT an interface
Interface Consenter was renamed to Content Creator for Consents and further clarification provided about who this interface is, how it interacts with others
Interface Consent Originator was renamed to Consent Directive Management System and further clarification was provided about who this interface is, how it interacts with others
Interface Consent Directive Requester was renamed to Content Consumer for Consents and further clarification was provided about who this interface is, how it interacts with others
Clarify interaction between Consumer and Content Creator for Consents
Clarify interaction between IIHI Requester and Consent Directive Requester
Clarify the interactions between interfaces under each of the two transactions: Capture Consent Directive and Request Consent Directive
Incorporated support for and use of HITP/TP31 and HITSP/TP33
Updated UMLs, as appropriate
Minor editorial changes were made to this construct. Removed boilerplate text 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] Integrating the Healthcare Enterprise (IHE) IT Infrastructure Technical Framework (ITI-TF), Volume 1, Revision 4.0, Section 10.
[2] Integrating the Healthcare Enterprise (IHE) IT Infrastructure Technical Framework (ITI-TF) Supplement 2007-2008 XDS.b.
[3] Optionality = R for Required, R2 for Required if Known or O for Optional, or C for Conditional
[5] Structured Data are coded, semantically interoperable data that are based on a reference information model. The Consent Directive may be captured as a scanned image, which is not semantically interoperable and would preclude the ability of the Consent Repository to analyze it for conflicts with previously persisted Consent Directives.
[6] IIHI includes Consent Directives, so there may be Consent Directives specifying users and uses of Consent Directives associated with IIHI.
|
Return to detail page at www.hitsp.org | HITSP/TP30 |
| Prev TOC |