Attachment IV ITL Mock Task Order.pdf

Request for Proposal Number SB1341-12-RP-0015

Attachment IV, ITL Mock Task Order

Title: Advanced Testing Tool Development

BACKGROUND

The mission of the National Institute of Standards and Technology (NIST), Software and

Systems Division (SSD) is to develop software testing tools and methods that improve quality, conformance to standards and correctness. The Division also participates with industry in the development of forward-looking standards relative to the healthcare industry. The Division's programs also respond to industry, consortia, and standards groups needs by concentrating on key areas at the forefront of technology and assisting in the transfer of technology and expertise to industry.

The demand for correct, reliable, robust and interoperable software is crucial to our nation’s infrastructures such as healthcare. In particular, online medical information and simplified, standardized methods to access healthcare information and services is crucial in making healthcare safe and available to all. Appropriate standards for healthcare information systems provide the cornerstone to achieving a healthy healthcare infrastructure.

This task order seeks to contribute to the general state of the art for trustworthy software as well as contribute to the healthcare industry specifically, by advancing healthcare information standards that are complete and testable and by providing the necessary conformance tests, tests tools and techniques where appropriate. There is a real need for formal and informal coordination of these efforts to leverage the synergy of the various efforts, to harmonize vocabularies, to enable interoperability, and to promote consistent testing and certification programs across and within organizations.

The NIST SSD requires project leadership and technical staff support from the Contractor in the areas of standards and technology development and adoption, measurement, and development of software testing tools to improve the quality and correctness of software used in our nation’s critical infrastructures such as healthcare, electronic commerce, and homeland security. The task order focuses on NIST’s efforts to build a Health IT

Standards Testing Infrastructure (TI). The Health IT Standards Testing Infrastructure is a collaborative effort to help ensure interoperability among all healthcare providers, hospitals, clinical laboratories, pharmacies, payers, and others.

OBJECTIVES/PURPOSE

The purpose of this task order is to develop software to promote the adoption of appropriate standards and achieve interoperability of systems, e.g., interoperability of healthcare information systems and sharing of electronic health information by deploying

ANSI-accredited Health Level Seven (HL7) messaging standards. NIST SSD and HL7 are working to ensure that HL7 conformance can be defined and measured at appropriate levels, by building tools that will promote consistent definitions and reuse of conformant models and artifacts (e.g., profiles, templates, message types, codes, examples) within HL7 implementations.

GENERAL REQUIREMENTS:

The Contractor shall support NIST SSD in the collaboration with industry, healthcare informatics-related standards organizations, consortia, and government agencies to build tools and prototypes to advance the adoption of IT within healthcare systems.

Specifically:

-Collaborating with Health Level Seven (HL7) members to help ensure that HL7 messaging and EHR systems' conformance can be defined and measured at an appropriate level;

-Providing technical leadership on 'Integrating the Healthcare Enterprise' (IHE) projects, in particular the Information Technology Infrastructure (ITI) profiles and medical device-related profiles;

-Providing technical leadership to build a common web-based tool set that integrates testing tools/activities of various SDOs, consortia and other organizations.

SPECIFIC REQUIREMENTS:

Task 1: Develop a UML Model of the Health Level 7 (HL7) Messaging Standard Version 2.8

Conformance Profile Schema (see attachments for schema.)

The contractor shall create a UML (Unified Modeling Language) model representing HL7’s

Messaging Standard Version 2.8 Conformance Profile Schema to be able to visualize the attributes and relationships required to build a valid HL7 conformance profile. The conformance profile provides a message template in which constraints can be applied. The

UML model will give developers a visual aid of an HL7 V2.8 conformance profile.

Three attachments will be provided with this task order:

1) The HL7 Conformance Profile Schema

2) The Table Library Schema

3) HL7 Version 2.8 Conformance Document- describes the methodology for producing a precise and unambiguous specification of a single interaction called a message profile

The UML model will represent the schema in attachment #1; the Table Library schema in attachment 2 is required in the attachment 1 schema. Attachment 3 is for background information on HL7 messaging and conformance profiles.

The Contractor shall present to the NIST team at a project meeting, the outcome of this task which is the UML Model. The COR will inform the contractor as to the location and times for the meeting when project status can be presented in a simple power point presentation. The UML model will be presented using MagicDraw, A visual UML modeling and

CASE tool NIST uses and will provide, and a brief description of the interactions modeled.

UML Model due no later than 12 months after contract award.

Task 2: Develop a Software Tool to Test that an Electronic Healthcare Record (EHR) System can generate messages that comply with the Electronic Prescribing (ePrescribing) messaging standard.

The requirements for the software tool to be developed are described in the following test procedure documents: (http://healthcare.nist.gov/docs/170.304.b_eRx_v1.1.pdf) EP

Link and (http://healthcare.nist.gov/docs/170.304.b_ePrescribing_Errata.pdf) EP Errata.

The software tool must be able to take input from the EHR either as a text file or directly as a message using SOAP/TLS. Tool must be developed in the JAVA programming language. Electronic prescribing enables a user to electronically generate and transmit prescriptions and prescription-related information in accordance with:

(1) The standard specified in (http://www.hipaasurvivalguide.com/hit-subchapter-d/hit-

170-205.php) §170.205(b)(1) or §170.205(b)(2); and

(2) The standard specified in (http://www.hipaasurvivalguide.com/hit-standards/170-

207.php) 170.207(d).

Minimum Requirements of the tool are as follows:

1. The tool only has to support NCPDP SCRIPT version 10.6;

2. The tool must support RxNorm;

http://healthcare.nist.gov/docs/170.304.b_eRx_v1.1.pdf http://healthcare.nist.gov/docs/170.304.b_eRx_v1.1.pdf http://healthcare.nist.gov/docs/170.304.b_eRx_v1.1.pdf http://healthcare.nist.gov/docs/170.304.b_ePrescribing_Errata.pdf http://healthcare.nist.gov/docs/170.304.b_ePrescribing_Errata.pdf http://www.hipaasurvivalguide.com/hit-subchapter-d/hit-170-205.php http://www.hipaasurvivalguide.com/hit-subchapter-d/hit-170-205.php http://www.hipaasurvivalguide.com/hit-standards/170-207.php http://www.hipaasurvivalguide.com/hit-standards/170-207.php

3. The tool must operate on EDIFACT and XML formats;

4. The tool must manage the test data specified in the test procedure;

5. Develop message validator - syntactic, semantic (vocabulary alignment), coding consistency/business rules;

6. Validation contexts, vocabulary, value sets, and test data shall be provided by

NIST;

7. Generate validation reports.

Not later than one month after award, the Contractor shall develop a project plan on the approach to implement the software tool. The project plan must state the milestones over the 1 year period so the progress of the tool can be tracked. The plan must also state project personnel assignments and software to be used.

The development of the software tool must be completed no later than twelve months after award. An initial Beta version should be ready 2 months prior to allow NIST personnel to test and give feedback on the tool to the contractor. Any bugs found or deficiencies noted by the NIST testing will be corrected by the contractor.

The completed software tool is due no later than 12 months after contract award. The contractor will demonstrate the use f the tool at a project meeting on the NIST site.

Task 3: Develop a Tool to Test SNMP Based Direct Protocol.

The Contractor shall develop a tool to test the SNMP based direct protocol. The tool must support meaningful use stage 2 testing tools, see (http://www.healthit.gov/providers-professionals/meaningful-use-stage-2) for a description of the meaningful use testing.

The contractor must integrate specific validation contexts; vocabulary and value set flexibility, and test data sets into the software components and tools. See

(http://wiki.directproject.org/XDR+and+XDM+for+Direct+Messaging) for the specification.

Not later than one month after award, the Contractor shall develop a project plan on the approach to implement the software tool. The project plan must state the milestones over the 1 year period so the progress of the tool can be tracked. The plan must also state project personnel assignments and software to be used.

Minimum Requirements of the tool are as follows:

1. Tool must be able to accept a message in SNMP format (email format) with an SMIME encrypted attachment.

2. Tool must be developed in the JAVA programming language and delivered to NIST.

3. The attachment must be encrypted using a self-signed certificate.

4. The content of the attachment will be a HITSP/C32 - Summary Document Using HL7

Continuity of Care Document format. See (http://wiki.hitsp.org/docs/C32/C32-1.html) for format.

5. The tool must use the NIST CDA validation tool to verify the syntax of the C32 Document. The NIST CDA validation tool is at http://xreg2.nist.gov/cda-validation/validation.html .

6. The tool must output a validation report (the output of the NIST validator).

The development of the software tool must be completed no later than twelve months after award. An initial Beta version should be ready 2 months prior to allow NIST personnel to test and give feedback on the tool to the contractor. Any bugs found or deficiencies noted by the NIST testing will be corrected by the contractor.

The completed software tool is due no later than 12 months after contract award. The http://www.healthit.gov/providers-professionals/meaningful-use-stage-2 http://www.healthit.gov/providers-professionals/meaningful-use-stage-2 http://wiki.directproject.org/XDR+and+XDM+for+Direct+Messaging http://wiki.hitsp.org/docs/C32/C32-1.html http://xreg2.nist.gov/cda-validation/validation.html http://xreg2.nist.gov/cda-validation/validation.html contractor will demonstrate the use f the tool at a project meeting on the NIST site.

Task 4: Attend monthly project team meetings

1. The Contractor shall present the status of each of the above tasks at a monthly project team meeting.

2. Meetings will be help on-site at NIST.

3. Project Manager will attend project meetings; other contractor personnel are welcome but not required.

4. Project Manager will give a simple PowerPoint presentation outlining the status of the above 3 tasks

5. Project Manager will include in the presentation any current or projected problems that would delay the completion of the tasks.

All work must be completed no later than 12 months from the date of award.

PERIOD OF PERFORMANCE

The period of performance shall be one year from the date of award.

PLACE OF PERFORMANCE

The Contractor’s staff must work on-site at NIST Gaithersburg.

GOVERNMENT FURNISHED PROPERTY

The Government will provide the following Government Furnished Property (GFP) for the

Contractor’s use throughout the period of performance of this task order:

1. Office space to include desk and chair;

2. All computing hardware, software and networking resources;

3. Access to NIST campus during working hours; non-working hour access may be granted on a need basis. Working hours are Monday through Friday between 7:00 AM and 5:00 PM.

DELIVERABLES

Number/

Reference

Description Format Quantity Due Date

Task 1 UML Model MagicDraw File

12 months from award

Task 2 -Project plan for implementation of the tools

-Software tool

PDF Document

Java Source

Code

1 months from award

Task 3 -Project plan for implementation of the tools

-Software tool

PDF Document

Java Source

Code

1 months from award

Task 4

Attend monthly project team meetings

Power Point

Presentation

1 Monthly

ATTACHMENTS

Attachment 1: HL7 Conformance Profile Schema

Attachment 2: Table Library Schema

Attachment 3: HL7 Version 2.8 Conformance Document

INSPECTION/ACCEPTANCE OF DELIVERABLES

As tasks and deliverables are completed, the Contractor shall submit the deliverables for review by the COR. The COR will provide comments on any given deliverable within five business days after the receipt of deliverables. The Contractor shall revise and resubmit the deliverable(s) in accordance with the COR’s comments and resubmit for COR review and further comment/approval. All revisions shall be made at no additional cost to the

Government.

TRAVEL

N/A

INVOICES

The Contracting Officer will negotiate a deliverable based payment schedule with the successful offeror prior to award of the task order.

QUALITY ASSURANCE SURVEILLANCE PLAN

The purpose of this plan is to provide a quality assurance surveillance plan for the work to be conducted under this task order. The plan provides a basis for the NIST COR to evaluate the quality of the Contractor's performance. The oversight outlined in this plan will help to ensure that the topics and assessment are maintained at the required levels through the Period of Performance. Further, this plan provides the NIST COR with a proactive way to avoid unacceptable or deficient performance.

Performance Standards:

1. Quality Level: By monitoring the Contractor, the NIST COR will determine whether the

Performance Standards set forth in the task order have been attained. Performance

Standards for all tasks are specified in the Performance Requirements Summary of the

Performance Work Statement.

2. Frequency: During the performance of this task order, the NIST COR takes periodic measurements (i.e., conduct surveillance), as specified, and will analyze whether the frequency of measurement is appropriate for the work being performed. Adjustments may only be made by a modification to the task order.

3. Management Responsiveness: The NIST COR will determine whether the Contractor has managed the Contract effectively and efficiently with successful completion of the topics and assessment as specified in the Performance Standards set forth in the Performance

Requirements Summary.

PERFORMANCE REQUIREMENTS SUMMARY

Task 1: Develop a UML Model of the Health Level 7 (HL7) Messaging Standard Version 2.8

Conformance Profile Schema (see attachments for schema.)

Desired Output: UML Model. Presentation made to NIST team on the model in MagicDraw, at internal NIST team meeting. Input provided to Project Leader through meetings, email and other discussion opportunities. Meetings attended as required. Phone and email discussions held as needed.

Monitoring Method: Reviewed by COR.

Performance Standard: Presentation material details all the components, interactions in the UML Model.

Task 2: Develop a Software Tool to Test that an Electronic Healthcare Record (EHR) System can generate messages that comply with the Electronic Prescribing (ePrescribing) messaging standard.

Desired Output: Demonstration of the ePrescribing Tool, presentation made to NIST team at internal NIST team meeting. Presentation material developed using Microsoft PowerPoint.

Input provided to Project Leader through meetings, email and other discussion opportunities. Meetings attended as required. Phone and email discussions held as needed.

Performance Standard: The software tool detects non-conformity to the NCPDP ePrescribing

Standard.

Task 3: Develop a Tool to Test SNMP Based Direct Protocol.

Desired Output: The software tool provides the capability to test Direct Based Protocol implementations.

Performance Standard: The software tool detects non-conformity to the Direct Protocol standards.

Task 4: Attend monthly project team meetings

Desired Output: Monthly Power Point Presentation on the status of the above 3 tasks.

Performance Standard: Presentations keep COR informed on progress.