XPHR Connectathon Tests

IHE Technical Framework: Year 3
______

Integrating the Healthcare Enterprise

BPPC Connectathon Test Cases

Revision 2007-1

11-January-2007

______

Rev. 2007-1Copyright © 2006: ACC/HIMSS/RSNA
2007.01.11

BPPC Connectathon Test Cases
______

Contents

1Introduction

2Tests

2.1BPPC_Load_Sample

2.2BPPC_Document_Scrutiny

2.3BPPC_Process

1Introduction

This document describes the IHE Connectathon tests for the XPHR Integration Profile.

2Tests

2.1BPPC_Load_Sample

2.1.1Special Instructions

You need to complete this test by Day 2 at 12:00. We would prefer that you complete by Day 1 at 17:00 if possible. If you complete after Day 2 at 12:00, you increase your risk that Content Consumers will ignore your document, and you will be marked incomplete.

2.1.2Description

The Content Creatorr shall create/register one patient in the proper affinity domain: SYSTEM_NAME^BPPCt. Use the RIS Mall to register this patient and obtain a patient identifier.

Create the appropriate document for the BPPC patient.

Create a readme.txt file that lists the Patient ID, Patient Name, company name, your name, and your Kudu system name.
Create a screen capture of a rendering of the BPPC document. We recognize that not all renderings will be the same.
Name the document BPPC_kudu.xml where kudu is your Kudu system name.
Create a zip file named BPPC_kudu.zip that contains the three documents listed above.
Find the Connectathon Wiki page that references BPPC documents. Upload your document according to the instructions on that page. Update the Wiki page to list your document/zip file.
If you support XDS, complete XDS_Doc_Source_Stores_Document or XDS_Embedded_Repository_Registers_Document using the BPPC document.

2.1.3Evaluation

This will be evaluated with the BPPC_Document_Scrutiny and BPPC_Process tests.

2.1.4Actors

Content Creator

2.1.5Steps

Trans 0:Use RIS Mall to register SYSTEM_NAME^BPPC

Trans 0:Create BCCP document for patient BPPC

Trans 0:Upload zip file to Connectathon Wiki for BPPC

Trans 0:Complete XDS store/register test if applicable

2.2BPPC_Document_Scrutiny

2.2.1Description

One assigned Connectathon Monitor will be assigned to scrutinize BPPC documents. The purpose of this test is to have a single person with domain knowledge examine one example of each document. The Connectathon Monitor is looking for proper document structure, proper use of coded values and any other CDA or IHE specific requirements defined in PCC TF 3.

The Content Creator should use the same documents produced and stored in the Connectathon Wiki in the BPPC_Load test.

The Connectathon Monitor will take the files offline and perform evaluation. The monitor will document any deficiencies and ask the Content Creatorto correct during the Connectathon.

This test needs to be completed by Day 2 at 12:00, and is better completed the afternoon of Day 1 if possible. This will give downstream actors better test documents.

2.2.2Evaluation

In the evaluation, the Connectathon Monitor is looking for features that are specified in PCC TF 3: 3.3, the section headings. The monitor is also looking for proper use of coded values.

2.2.3Actors

Content Creator

2.2.4Steps

Trans 0:Complete test BPPC_Load.

Trans 0:Notify the assigned monitor that your documents are ready for scrutiny.

2.3BPPC_Process

2.3.1Special Instructions

2.3.2Description

In this test, the Content Consumer retrieves the BPPC document and somehow processes it. This is most like rendering to examine the consent form.

2.3.3Evaluation

In the evaluation, the Connectathon Monitor is looking for evidence that the Content Consumer can interpret the document produced by the Content Creator. That is a test of both actors. The Connetathon Monitor is then looking for evidence that the Consumer processes at least one of the options as specified in the BPPC Integration Profile.

2.3.4Actors

Content Creator

Content Consumer

2.3.5Steps

Trans 0:Uses the Connectathon Wiki to find the appropriate document produced by the Content Creator.

Trans 0:Extract the BPPC document from the Connectathon Wiki or retrieve the documents using XDS.

Trans 0:Content Consumer exhibits that it can somehow process the consent document. This is likely rendering, but may be some other function.

______