PCD Pre-Connectathon Testing Information
Jump to navigation
Jump to search
PCD_Pre-Connectathon_Testing_Information
This Wiki page is intended to provide a summary and evolve as a reference for future years.
This page provides information on tests using the NIST Tools for testing, on tests not using the NIST Tools, and on Virtual (Internet and workaround) Connectathon tests. Internet testing before attending the Connectathon is strongly recommended: time is short at the Connectathon and PCD has found that testing with partners in advance of the Connectathon can mean the difference between complete success and something significantly less. Workaround refers to conducting these tests when firewalls don't allow direct Internet connection.
IN PREPARATION FOR THE JANUARY 2013 NORTH AMERICAN CONNECTATHON:
IHE Pre-Connectathon Testing:
- The IHE link provided here is a high level index to Connectathon tests, and includes some additional links. It is useful in identifying tests for other IHE domains as well. http://ihewiki.wustl.edu/wiki/index.php/Index_to_Preconnectathon_Test_Software. Note: this will need to be verified.
PCD Pre-Connectathon And Virtual Testing:
- DRAFT PCD Connectathon, Pre-Connectathon (NIST Tools) and Virtual Connectathon tests are provided in Excel Workbooks as we develop and review the tests. ftp://ftp.ihe.net/Patient_Care_Devices/ConnectathonsIncludingProcessAndTesting/Yr7-2013Connectathon-PreConnectathonAndVirtualConnectathonTesting/.
- PCD's Pre-Connectathon tests make use of the NIST test tool. The actual (current) version of the Pre-Connectathon tests are found ONLY on the NIST site to avoid the possibility of version conflicts.
- You will also find the patient demographics tables for PCD profiles (there is a separate table for IDCO) on the ftp site. These tables have no relation to patient data provided by ADT systems. Error table 0533 for PIV is also available here.
- We strongly recomment Virtual / Internet testing, conducting as many of the appropriate Connectathon tests as possible in advance of the Connectathon. These tests are arranged by participants. An Excel document identifying possible test participants by profile, actor and option is provided and includes contacts at the various companies.
- When the messages satisfy you that they are correct, please post the messages to Gazelle as requested in the Connectathon instructions. Include an explanation if necessary in a Word or Text file.
- Some Connectathon tests cannot be translated into reasonable Pre-Connectathon tests with the NIST tool (e.g., multiple sending systems sending data to a single receiving system, interruption of communication). These can be tested in the lab or over the Internet. These may be conducted as Virtual Connectathon tests if desired.
Pre-Connectathon (NIST tool) tests:
- Tests are available at http://hit-testing.nist.gov:13100/PCD-HL7WebPreCon/. Both test steps and test patients are identified. Before conducting these tests, please review the Excel versions described above. These provide some context for the tests and are similar in format, and in most content, to the Connectathon tests.
- Please post the NIST test report to Gazelle and notify the Technical Project Manager when you do. If there are discrepancies that are not relevant to your implementation please upload a Word or text document along with test results. If some tests do not apply to your system, upload a short Word or text document with an explanation. The NIST tool identifies the patient(s) to be used with those tests.
Posting Sample Messages
- Please contact the Technical Project Manager for ftp site log in information.
- For Cycle 7, the current cycle, the subfolders for posting the sample messages that are tested using the NIST tool are at:
- which has the samples in folders identified by company.
Virtual Connectathon Testing:
- These tests are strongly recommended, but not required. You are asked to notify the Technical Project Manager when you successfully complete virtual testing. Please send an email, indicate the Pre-Connectathon test number(s) and identify your partner(s). No data/documentation is required. Feel free to comment on your experience.
Index to the Tests:
- The index is also posted to placeholder ftp://ftp.ihe.net/Patient_Care_Devices/ConnectathonsIncludingProcessAndTesting/Yr7-2013Connectathon-PreConnectathonTesting/PreCTests/. It includes a table of “optionality” to indicate which actors are required or optional for that test. For NIST testing an O should mean that the transaction has been tested in a different test case and therefore need not be tested with the NIST tool again. Since Virtual Connectathon testing is recommended, but optional, this table merely restates that optionality for those tests that do not utilize the NIST tool. One exception: While optional, the ACM AM <- -> AC ACM_AR_AM_AC_Basic test is should be accomplished in the lab if it is not possible to test over the Internet - because this is the fundamental test for these actors and cannot be accomplished otherwise.
- The high level index to Connectathon tests, with some additional links is available at http://ihewiki.wustl.edu/wiki/index.php/Index_to_Preconnectathon_Test_Software, with a section for PCD
- placeholder We will not post the test steps or url within the Gazelle test description. These will instead be available at
- o placeholder the Excel workbook – please read the tests here before proceeding to the NIST tool, and
- o http://xreg2.nist.gov:8080/PCD-HL7WebCon/ where the NIST tool provides the NIST test steps
- placeholder The NIST tools will report test results, labelling the tests with the same number as the Gazelle test
- Some Pre-Connectathon tests cannot be conducted with the NIST tool; instead please provide a document that describes the results (the test may specify the documentation required)
- Patient identity for these tests is provided in the tests and may be different at the Connectathon
- The patient demographics table has been uploaded to the ftp site for your use in conducting Virtual Connectathon (Internet) testing ftp://ftp.ihe.net/Patient_Care_Devices/ConnectathonsIncludingProcessAndTesting/Yr7-2013Connectathon-PreConnectathonAndVirtualConnectathonTesting/
Profile Specific Information:
ACM Profile:
- Jeff suggested that the infusion pump alarm should be a choice of infusion occlusion or door position error. For systems that support infusion pump alarms, test either or both. Our flexibility will be increased if you test both. The other test should be a physiologic parameter, and diastolic blood pressure is a reasonable example. Feel free to test other parameters.
DEC Profile, WCM option:
- At this time there are no "triggering events" to initiate a waveform transmission; i.e., it is a configuration issue. DORs will need to make provision for waveform communications.
- There are many optional characteristics for waveforms. Sending and receiving systems should test as many as possible within the communications, even though not required. The Virtual/Internet testing period provides an opportunity to evaluate this and perhaps determine how best to test at the Connectathon.
Aspects that are unique to IDCO:
- Device Identification and Patient Demographics must be reviewed and adjusted as necessary. Device identification is a required part of the IDCR message. This is relevant to NIST testing, Virtual Connectathon testing as well as Connectathon testing. We may use different patient demographics in the Connectathon.
- We need to have a “minimal set” of data for all test environments. For 2013 this should include 8 to 12 parameters that all systems can support. This may change later.
- PV1 remains optional in this cycle. This may not be the case in the future.
- The Time Client must be tested even if not utilized in the IDCO messages. It will become required in a future cycle.
PIV:
- As noted above (ACM), Jeff suggested that the infusion pump alarm should be a choice of infusion occlusion or door position error. For systems that support infusion pump alarms, test either or both. Our flexibility will be increased if you test both.
Other Tools:
- The MWB is an optional tool, developed by the Veterans’ Administration. It is useful in development and testing. No reports are required. The ftp site has the 2009 version along with recordings of two tutorials on the use of the tool.
Virtual Connectathon Tests
Virtual Test Profile Specific Information:
- Please include parameters that are appropriate for the clinical stories to be demonstrated at the Showcase. At the Connectathon parameters that are thought to be appropriate for the demonstration will be used.
- You can identify test partners using Gazelle. The Technical Project Manager will provide contact information for potential partners as they become available.
- Cycle 4 samples are at ftp://ftp.ihe.net/Patient_Care_Devices/ConnectathonsIncludingProcessAndTesting/YR4-2010Connectathon-PreConnectathonTesting/SampleMessages/ placeholder
- The subfolders for posting sample messages used in Virtual Connectathon testing (Internet or workaround) are at:
- which is also arranged by company. These are in different folders to make retrieval easier and to distinguish them from messages from NIST testing.
PCD CONNECTATHON TESTS
- The latest draft Connectathon tests are available at ftp://ftp.ihe.net/Patient_Care_Devices/ConnectathonsIncludingProcessAndTesting/Yr7-2013Connectathon-PreConnectathonAndVirtualConnectathonTesting/Yr7-2013%20North%20American%20Connectathon%20Testing/.
- Connectathon Tests may resemble Pre-Connectathon Tests, may use different patients, may be optional in one and required in the other.
ADDITIONS, CORRECTIONS AND UPDATES TO THIS WIKI PAGE
- This page is established with notes developed in preparation for the 2011 North American Connectathon, January, 2011 and updated on occasion. It is intended to evolve and support future Connectathons and the testing process leading to them for North American Connectathons.
- Please contribute to this evolution with the benefit of your experience and point of view. Comments, corrections, suggestions for immediate or future application are welcome.