Conformance Testing Pilot Project

Project Page Template - This template is for voluntary use, but provides guidance for consistent representation of wiki pages reporting project information

Return to Main Page - include link to return to Work Group main page or wiki page who sponsored the project

• list project co-sponsors and link to their WG wiki page or Work Group web pages

This template was developed using examples from other project pagess: Annotated ECG, BRIDG as DAM, Canonical Pedigree, DCM for Dev, EHR Interop, EHR RM-ES, Oncology EHR, RPS, Templates registry, SPL, VMR

Frequently Asked Questions (FAQ) During the RFP

Who will "demonstrate the profile at the HIMSS conference"?

• A presentation describing the testing definitions and implementation of the profile will be shown in the HL7 booth multiple times each day. Live demonstrations of this profile as implemented in the Developer Integration Lab (DIL) will also be available in the AEGIS.net booth. It is not a requirement that the Contractor(s) that build the profile be present at the HIMSS conference.

Does HL7 see this as primarily an analytical project (develop test cases and some rudimentary tools to evaluate them) or as a software project (develop some test cases and some robust tools to evaluate them), or both?

• A: This project is a pilot of both the analytical process (development of test case definitions and related artifacts) and of the implementation of those test cases in the DIL, a robust testing system which is already developed. HL7 is asking RFP respondents to focus on the analytical process in collaboration with the AEGIS team implementing the test cases and HL7 program staff (“HL7 Implementation Team”) to ensure that the definition work and the implementation work are cohesive. A key point here is that both teams will be assessed by HL7 as part of this initial pilot process to determine whether the pilot will be extended to included additional profile definitions and implementations.

Can you confirm whether generic test cases related to transport-level issues will be in scope of this work or not?

In section 3.2.1, the RFP states: The POC will utilize the SOAP Web Services transport recommended by the EHR-IIS Interoperability Expert Panel Project. • The scope of the POC does not include testing specific to this transport. However, almost immediately after, it then states: Analyze selected transport(s) and develop test cases specific to those transport(s) and to the SOAP Web Services transport

• A: Defining test cases for the transport are in scope for the RFP. As noted in section 3.1, the RFP “pilot” scope covers test case definition work which is a superset of the test cases which can be implemented for HIMSS (“POC” work). This language is saying that although transport testing will not be implemented for the POC, these test cases still need to be defined as a deliverable of this RFP (for implementation subsequent to HIMSS).

Do the test tool and test harness already exist? Or will they be developed in parallel with the effort in producing the test case and test artifacts?

In section 3.2.2, the RFP makes the following statement about the test architecture: The test architecture consists of the System Under Test (“SUT”) acting as the Sending System actor, a Test Tool acting as the Responding System actor, and a Test Harness that captures and evaluates the message traffic in both directions. The Test Harness will also make the captured messages available to human evaluators for those verifications that cannot be fully automated.

• A: The test tool/SUT/test harness do exist as the Developers Integration Lab (DIL); implementation of the test cases defined as an outcome of this RFP award will occur as a result of that definition effort.

Link to Project Insight Searchable Database Entry, which contains:

• Brief description of project
• Name the project facilitators, (add contact info if desired)
• Link to project scope statement
• Name the project listserv if a special one exists

Meeting Information

• link to or list project meeting schedule
• link to minutes web page or wiki minutes page, or list project meeting agendas and minutes

Status

• If balloting, list ballot name/cycle/link
• If in DSTU, link to DSTU comments page
• If in development, link to in progress
• Some projects explicitly list objectives from scope statement and status for each

Issues/Hot Topics

• List issues or link to issues tracking repository (wiki pages or GForge)

Project Documents

• Link to working documents/wiki pages
• Link to project GForge
• Link to reference documentation on GForge, HL7 Web site WG Documents/Presentations page, or external web pages

Categorization

To include your Project Page in a category listing, just include a statement like [[Category:Active_Projects]]