| HOME | ABOUT | MEMBERSHIP | NEWS & ANNOUNCEMENTS | MEETINGS | FAQ | CONTACT US | | Powered by American National Standards Institute |
![]() |
Return to detail page at www.hitsp.org | HITSP/IS03 |
| Prev TOC |
The following sections provide the details of updates made to this document.
This document is now Released for Implementation.
Updated Foreword to account for the CACI Use Case description
Updated Interoperability Roadmap
Rename IS to Consumer Sharing of Health Information via Networks
Updated HITSP/C32 Registration and Medication History Document Content Component to include: list of allergies for the consumer, encounters, identified conditions and problems diagnosed, the current list of immunizations received by the consumer, as well as some key laboratory test results indicative of the patient health status
Updated HITSP/TP13 with provisional selection of XDS.b to support Entity Identity Assertion (SAML) support
Added HITSP/C37 and HITSP/C35 constructs for laboratory reports
Added reference to Security and Privacy constructs: HITSP T15, T16, T17, TP20, TP30, C19, C26
Add in Section 4.0 reference to SNOMED, CLIA, LOINC, UCUM
Add in 3.1 the CACI resolution plan with 2008 work items
Add to overview of the CACI Use Case description
Re-scope Scenario 3.2.2.1
Remove security pre-conditions now explicitly addressed
Extend technical actors with Content Creator (to leave Doc Source and Media Creator for infrastructure interchange) and Content Consumer
Add Security and Privacy technical actors
Add Results Laboratory, Immunizations, Encounters, Vital Signs in HITSP/C32 summary
Add Lab Report Doc description
Re-scope Scenario 3.2.2.2
Re-scope Scenario 3.2.2.3
Extend list of Transaction, Transaction Package and Components
Update list of dependencies
Remove Overview figure
Add for each business actor the extended list of technical actors
Extend the mapping from technical actor to Transaction Requirements
Add CACI to supporting documents
Add Subsetting to the conformance section
The changes in this cycle address the following comments:
2424, 2444, 2445, 2446, 2456, 246, 2424, 2444, 2445, 2446, 2456, 2461
The full text of the comments along with the Technical Committee's disposition can be reviewed on the HITSP Public Web Site.
1. The Consumer Empowerment IS deliverables represent the joint analysis of both of the Consumer Empowerment (CE) Use Cases (Consumer Empowerment and Clinical Access to Clinical Information). The ISs are differentiated solely by the transport by which the consumer has access to and shares clinical information via Networks (IS03) and using Media (IS05). As such, Section 2 for each of these ISs is identical. Section 2 Tables and their associated UMLs have been completely redone to reflect a concatenation, where appropriate, of the events/actions from both of both CE Use Cases. This integration of the events/actions resulted in scenario one being fully merged into a single scenario entitled Consumer creates account to host and Access Registration Summary and Clinical Information. Scenario 2 and 3 of the Consumer Empowerment Use Case were likewise edited to include operationally equivalent events/actions from the Consumer Access Use Case. Scenario 2 and 3 of the Consumer Access Use Case remained intact as originally presented.
2. Section 3 has been revised to reflect the new template (effective 11/29/07) which was the result of a cross-TC and project management assessment of the IS readability and usability for implementation and certification purposes. The following changes were made to the document in this regard:
- Table 3-7 was revised to only list the technical actor names and their descriptions
- The UMLs in Section 3.2.2 were completely redesigned to improve the segmentation of business actor-to- business actor interactions and technical actor-to technical actor transactions
- Table 3-9 was completely redesigned to improve the clarity of the requirements (and optionality) for a business actor in terms of what technical actors need to be supported AND what specific transactions for those technical actors are required, optional, or conditional
- The conformance subsets previously included in Section 5.1.2 were relocated to Section 3.2.3 as paragraphs 3.2.3.x, where x = the subset number. These subsets were also included in Table 3-9 accordingly
- The Conformance Section 5.1 was revised to direct the reader to Section 3.2.3 for the mandatory requirements to claim conformance to this specification
3. Transactions and Content were differentiated in Table 3-9 to clarify how specific technical actors (e.g., Document Source) needed to support both Content Technical Actors (Content Creator and Content Consumer), specified with the detailed subsets of clinical information, and the transaction to transport that information (e.g., TP13).
4. All relevant Security and Privacy constructs, including their applicable transactions, have been included in Section 3.0, with particular specificity regarding their association to business actors requirements highlighted via Table 3-9.
5. The results of TC dispositions of public comments received against this IS have been appropriately reflected in the text, tables, and UML diagrams of the IS. Specifically, comment dispositions for the following comment topic categories have been effectively included:
- PHR Data Entry/Quality/Integrity comments #2424, 2425, 2426, 2427, 2428, 2443, 2450
- Data Content Specifics comments #2444, 2446, 2454, 2455, 2456, 2489
- Data Transport Logistics & Controls comments #2445, 2453, 2461
- CFH Initiative General Comments comment #2495
Upon approval by the HITSP Panel on December 13, 2007, this document is now released for Implementation.
This document has been modified to reflect the updated HITSP approach to categorizing standards as Regulatory Guidance, Selected Standards, and Informative References. Please refer to the underlying constructs for specific changes to standards.
Upon approval by the HITSP Panel on August 27, 2008, this document is now Released for Implementation.
This document has been modified to address two of the requirements previously identified as gaps in Section 4.2. These were specifically identified as work items targeted for the 2008 publication cycle. The two work items addressed with this update are:
1. Advance Directives (AD)
2. Med/Labs Info in Consumer-friendly Manner
The first work item, Advance Directives, was only partially addressed in the 2008 cycle. The full resolution of this requirement is included as a work item for the 2009 work cycle in that the standards to complete this are still in works-in-progress. In this cycle, the standard for the capture of a scanned document which could include any type of advance directive that has been specified, i.e., HITSP/C62 Unstructured Document.
The second work item, Med Labs Info in Consumer-friendly Manner, has been fully resolved by the creation of a new HITSP construct entitled Retrieval of Medical Knowledge (HITSP/T81). This construct has been fully included and is identified as a construct which can facilitate the translation of clinical terms into consumer-friendly text.
Specific tables modified reflecting the inclusion of these two new constructs are:
Table 2-1, Table 1-1
Table 3-2, Table 3-4, Table 3-5, Table 3-6
Table 3-7, Table 3-9, Table 4-2, Table 4-3
Text in Section 3.2.2
In addition to the inclusion of the above work items to address existing gaps, the document has been converted to the latest template for Interoperability Specification documents.
Minor editorial changes were made to this construct.
Upon approval by the HITSP Panel on December 18, 2008, this document is now Released for Implementation.
![]() |
Return to detail page at www.hitsp.org | HITSP/IS03 |
| Prev TOC |