 |
Return to detail page at www.hitsp.org | HITSP/IS12 |
| 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/IS12 |
| Prev TOC |
The following sections provide the details of updates made to this document.
The changes in this construct address the following comments received during the Public Comment and Inspection Testing period (September 29 October 24, 2008).
5030,5155,5156,5157,5158,5395,5414,5564,5565,5566,5567,5568,5569,5570,5571,5572,5683,5684,5685,5686,5687,5688,5689,5690,5691,5692,5693,5694,5695,5696,5697,5698,5699,5700,5701,5702,5703
The full text of the comments along with the Technical Committees disposition can be reviewed on the HITSP Public Web Site.
Incorporated all of the 37 Public Comment TC dispositions into the document
Acknowledged difficulties in navigating the IS, particularly with mapping requirements into constructs. Suggestions have been passed on to the Project Management team
Updated Section 3.1.2 to reflect a case where access originates from a public computer (assumption), and to ensure that a users computer maintains standard virus protection (pre-condition)
Tables in Section 6.2 have been updated to ensure consistency of IERs and DRs to reflect proper sequencing of events and actions
All references to business actors, technical actors, interoperability exchange requirements (IERs) and data requirements (DRs) have been update to align with a library of objects that have been harmonized across all IS
Left-over references to TP13, TP49 and T29 from earlier versions have been removed
Several glossary-related items have been referred to Project Management to ensure consistency of definitions
All punctuation and formatting inconsistencies have been corrected
Updates have been made to Table 3-1 to clarify Use Case scoping statements, particularly to exclude various forms of live communications, and to clarify the use of read and delivery receipts
Labeling on UML diagrams in Figure 2-1 have been corrected for consistency and accuracy
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.
[1] The IntendedRecipient metadata attributes is associated with the SubmissionSet entry, whereas all of the other metadata attributes are associated with the XDSDocument entry
[2] Inclusion of support for a For Clinician Eyes Only indication on messages containing very sensitive patient information is addressed using the Confidentiality Code.
[3] Optionality = R for Required, O for Optional, or C for Conditional
|
Return to detail page at www.hitsp.org | HITSP/IS12 |
| Prev TOC |