Modular+Specs+Directed+Exchange

include component="page" wikiName="siframework" page="ModularSpecTabs" =Phase 2 - Direct Transport Specifications =

Scope
The scope for the project is to extract the specifications currently utilized in DIRECT pilot implementation; and develop implementable, testable specifications along with a conformant test implementation and high quality test cases that verify conformance of reference implementations to the specifications.

The following are DIRECT specifications related reference material that can be used to enhance, clarify and create the deliverables of this project but will not be extracted and specified as part of the specifications.
 * ~ **Reference Material** ||~ **Applicability to Mod Spec Project** ||~ **Link** ||
 * User Stories || The user stories can be used to understand the clinical workflow relevance of the DIRECT specifications || http://wiki.directproject.org/User+Stories ||
 * DIRECT Project Overview || This document provides an overview of DIRECT including the abstract model and some of the terminology used as part of DIRECT. || http://wiki.directproject.org/The+Direct+Project+Overview ||
 * DIRECT Project Security Overview || This document provides an overview of the DIRECT project security model || http://wiki.directproject.org/Direct+Project+Security+Overview ||
 * <span style="display: block; font-family: arial,helvetica,sans-serif; font-size: 12px; text-align: justify;">DIRECT Project Compliance || <span style="display: block; font-family: arial,helvetica,sans-serif; font-size: 12px; text-align: justify;">This provides an overview of the compliance criteria and some examples that help in creating compliant implementations and test cases that test compliance. || <span style="display: block; font-family: arial,helvetica,sans-serif; font-size: 12px; text-align: justify;">http://wiki.directproject.org/Direct+Project+Compliance ||

<span style="display: block; font-family: arial,helvetica,sans-serif; font-size: 12px; text-align: justify;">The technical details of the Mod Spec Project are outlined as Tasks below:

<span style="display: block; font-family: arial,helvetica,sans-serif; font-size: 14px; text-align: justify;">**Task 1: Develop Implementable, testable and certifiable specifications** <span style="display: block; font-family: arial,helvetica,sans-serif; font-size: 12px; text-align: justify;">This task involves analyzing the specifications documented at the links referenced below and creating specifications that are clear, complete, accurate, implementable, and testable.
 * <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">SMTP Secure Health Transport:
 * <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">http://wiki.directproject.org/Applicability+Statement+for+Secure+Health+Transport
 * <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">XDR Simple Health Transport:
 * <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">http://wiki.directproject.org/XDR+and+XDM+for+Direct+Messaging

<span style="display: block; font-family: arial,helvetica,sans-serif; font-size: 12px; text-align: justify;">The SMTP Secure Health Transport specification is the primary DIRECT specification that DIRECT conformant implementations need to implement. The following table summarizes the sections of the SMTP Secure Health Transport specification that is in-scope and out-of scope and the justification for out-of-scope sections.

<span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Section 2.3 should be left out since the S&I Provider Directory Initiative work is overlapping with the requirements in this section. ||
 * ~ <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">**SMTP Secure Health Transport Specification Section #** ||~ <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">**In-Scope or Out-of-Scope** ||~ <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">**Justification** ||
 * <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Section 1 and sub-sections || <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">In-Scope || <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Basic DIRECT concepts that need to be universally applied. ||
 * <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Section 2 and sub-sections except Section 2.3 || <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">In-Scope || <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Basic DIRECT Security which provides the minimum security required for transferring PHI information on the Internet.
 * <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Section 3 and its sub-sections || <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">In-Scope || <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Basic DIRECT Security which provides the minimum security required for transferring PHI information on the Internet. ||
 * <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Section 4 and its sub-sections || <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">In-Scope || <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Basic DIRECT Security which provides the minimum security required for transferring PHI information on the Internet. ||
 * <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Section 5 and its sub-sections || <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Out-of-Scope || <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Section 5 and it’s sub-sections should be left out since the S&I Provider Directory Initiative work is overlapping with the requirements in this section. ||
 * <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Section 6 and its sub-sections || <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Should be included in the specifications as Informative Content for organizations. || <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">This section provides critical operational considerations that will help DIRECT adopters to be successful and hence should be included. ||
 * <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Section 7 and 8 || <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">No content not required. ||  ||
 * <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Section 9 and sub-sections || <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">In-Scope || <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Provides reference links to the base specifications. ||
 * <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Section 10 || <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">In-scope || <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Specifies copy right information. ||

<span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">The XDR Simple Health Transport specification can be used by DIRECT implementations that are using IHE profiles or by implementations that provide mechanisms to convert from SMTP based DIRECT messages to corresponding IHE profiles.

<span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">(References section) || <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">In-Scope || <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Provides reference links to the base specifications. ||
 * ~ <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">**XDR and XDM for DIRECT Messaging** ||~ <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">**In-Scope or Out-of-Scope** ||~ <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">**Justification** ||
 * <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Section 1,2,3 and sub-sections || <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">In-Scope || <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Informative content that provides the overall context for the XDR and XDM for DIRECT Messaging specification. ||
 * <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Section 4,5,6 and sub-sections || <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">In-Scope || <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">XDR and XDM specification requirements for DIRECT. ||
 * <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Section 7 and its sub-sections || <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Should be included in the specifications as Informative Content for organizations. || <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">This section provides critical operational considerations that will help DIRECT adopters to be successful and hence should be included. ||
 * <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Section 8 and sub-sections || <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">In-scope || <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Provides useful examples to implementers and is very valuable for implementers. ||
 * <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Authors Section || <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Out-of-Scope || <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Not required for the modular spec project. ||
 * <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Section 9 and sub-sections
 * <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Section 10 (Copyright section) || <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">In-scope || <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Specifies copy right information. ||

<span style="font-family: Arial,Helvetica,sans-serif; font-size: 14px;">**Task 2: Create conformant Test Implementation**
<span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">This task involves creation of a conformant test implementation based on the specifications produced by the Mod Spec Project. <span style="color: #000000; font-family: 'arial','sans-serif'; font-size: 12px;">This test implementation is not production-ready software, but rather a simple and intuitive codebase with the sole purpose to validate test cases and specifications generated by the Mod Spec Project. <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">In order to meet the timelines we strongly recommend the following:
 * <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Adopt and re-use the Production Implementation created by DIRECT community
 * <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Identify gaps and enhance the Production Implementation to conform to the enhanced DIRECT specifications

<span style="font-family: Arial,Helvetica,sans-serif; font-size: 14px;">**Task 3: Create High Quality Test Cases**
<span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">This task involves creation of high quality test cases that can test an implementation’s conformance to the specifications produced by the Mod Spec Project.
 * <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">The test cases should be able to fully test any independent implementation for conformance to the specification
 * <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">The test cases should use the existing NwHIN SOA Transport Specification Test case templates which are in pilot phase
 * <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">The test cases should be provided to NIST and allow NIST to execute the test cases using their tools.
 * <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">The test cases should be executed against the test implementation and grade the test implementation’s conformance to the specifications.

<span style="font-family: Arial,Helvetica,sans-serif; font-size: 16px;">**Success Metrics**
<span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">The success of the project will be focused on two main fronts: Quality and Timeliness.

<span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Specification quality will be evaluated based on __implementablity__ of the specification. <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">The quality of test cases will be evaluated based on the clarity and breadth of the test cases to test independent implementations. <span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">The quality of implementations will be evaluated based on the level of conformance to the specification and passing the independent test cases.
 * ====<span style="font-family: Arial,Helvetica,sans-serif; font-size: 14px;">**__Quality__** ====

<span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">For a successful delivery, **all** required artifacts for each module (Specification, Test cases and test implementation) need to be delivered to ONC by Nov 30, 2011.
 * ====<span style="font-family: Arial,Helvetica,sans-serif; font-size: 14px;">**__Timeliness__** ====

<span style="font-family: Arial,Helvetica,sans-serif; font-size: 16px;">**Timeline**
<span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">At the present time all of the required elements for the selected specifications (Specification, Test conditions, Test Implementation) will need to be finalized by Nov. 30, 2011.

<span style="font-family: Arial,Helvetica,sans-serif; font-size: 16px;">**Mailing List**
<span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">To receive email notifications from the Modular Spec Team, please join the [|modularspec Google Group]

<span style="font-family: Arial,Helvetica,sans-serif; font-size: 16px;">**How to Submit Comments**
<span style="font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Please provide feedback via the<span style="color: #ff0000; font-family: Arial,Helvetica,sans-serif; font-size: 12px;"> Phase 2 Discussion page. Please indicate in the subject line the Team that the comment is directed to (Spec, Test Implementation, Testing, ONC or All) and a short description of the comment. Provide any further comments in the message area of the posting. All comments posted by COB Monday will be number, cataloged and responded to by the responsible team by the end of the week. If there are any questions regarding this process please email Matt Rahn or Farrah Darbouze.

<span style="color: #ff0000; font-family: Arial,Helvetica,sans-serif; font-size: 16px;">**Public Call Schedule**

 * The final public call for Phase 2 of the Modular Specification project is scheduled for Wednesday, January 18th, 2012 from 11:00am to 12:00pm EST **