 |
Return to detail page at www.hitsp.org | HITSP/IS04 |
| 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/IS04 |
| Prev TOC |
The following sections provide the details of updates made to this document.
The changes in this cycle address the following comments:
528, 531, 532, 537, 538, 549, 574, 629, 632, 669, 763, 764, 770, 786, 795, 799, 800, 802, 803, 804, 808, 809, 811, 812, 813, 820, 828, 830, 831, 884, 1171, 1178, 1179, 1182, 1186, 1190, 1191, 1192
The full text of the comments along with the Technical Committee's disposition can be reviewed on the HITSP Public Web Site.
Incorporated all of the 287 Public Comment TC dispositions into the document
Added detail to the description of the pre-hospital scenario to provide clarity regarding Interoperability requirements and differentiation among and between the Use Case elements.
- Introduced the global concept of an Emergency Communications System for Emergency Communications Center to connect the current approach with the more advanced capabilities that are envisioned by the Use Case and underway in the EMS industry
- Updated the UML diagrams for completeness, accuracy and improved understanding
Reflected the additional analysis and Section 3.0 Design necessary to identify the appropriate HITSP constructs to support the Use Case
- Figure 2-2 On-Site Care Component Data Flow Diagram
- Table 3-7 Detailed Design
- Made a number of standards selections to support the constructs
Identified and documented 4.0 Gaps and Overlaps in required standards and created supporting technical actors for the Gaps.
- Created and documented a Road Map to address the Gaps and Overlaps identified including a planning effort, the identification of a number of interrelated projects and potential resources that will be involved in the resolution
- Identified a number of Candidate Standards that will require review and analysis as part of the Road Map effort
Reformatted the document content to adhere to the new HITSP document templates
- Added diagrams and tables based on the new HITSP document templates
Upon approval by the HITSP Panel on December 13, 2007, this document is now Released for Implementation.
This document has been modified to incorporate gaps and overlaps, which have been resolved in 2008.
The changes in this construct address the following comments received during the Public Comment and Inspection Testing period (September 29 October 24, 2008).
5128, 5131, 5134, 5137, 5180, 5444, 5582, 5593
The full text of the comments along with the Technical Committee's disposition can be reviewed on the HITSP Public Web Site.
Minor editorial changes were made to this construct.
The changes in this cycle address the following comments received during the October 2008 public comment and inspection testing period:
Incorporated all of the 13 Public Comment TC dispositions into the document
Updated the gap Table 4-4 as per public comments and changed status of standards since last publication
Updated UML diagrams
- Updated document map
- Updated construct names where needed
- Updated business actor names for clarity
- Updated component diagrams to match IER and DR harmonized numbering
- Updated diagrams for clarity
Added missing standards and corresponding copyrights and amended standards descriptions
Made editorial changes as suggested by public comments
- Updated construct names and descriptions
- Updated business actors and stakeholders as per harmonized spreadsheet
- Corrected use of IERs and DRs as per public comments
- Corrected discussion language for clarity
Moved the following tables and figures to the appendix to allow easier access to the Design Section of the Interoperability Specification:
- Table 6-4 All the tables that provided the Mapping of Use Case Actions to Information Exchange Requirements
- Figures in Section 2.4.2 All the High Level UML Sequence Diagrams
- Table 6-4 Mapping of HITSP constructs to Requirements
The following changes were applied throughout the document for clarification and consistency.
Document reformatted to adhere to the new HITSP document templates
Updated Table 3-7 to correct references to HITSP TP20 Access Control and HITSP C19 Lab Report Document
Added IS business actor in order to consolidate use of SPI constructs
- Removed Locator Service, Data repository, Patient identification service and registries from UML diagrams, business actor tables and Table 3-7 and replaced them with Infrastructure Services business actor
Renumbered IERs and DRs as part of HITSP IER and DR harmonization
- Updated component diagrams in Section 2.4.2
This section contains an extraction of business actors, required interactions and conditions/scenarios from the Use Case into a matrix/table.
- Table 6-3, and Table 6-4
Upon approval by the HITSP Panel on December 18, 2008, this document is now Released for Implementation.
[1] Core Services may implement a collection of standardized, shared services that help ensure security during the sharing of patient information and enable accurate data routing. These include but are not limited to: access control/identity management, data rights management, and location and other information about emergency agencies needed for routing data.
|
Return to detail page at www.hitsp.org | HITSP/IS04 |
| Prev TOC |