IHE-PCD Pre-Connectathon
HL7 V2 Test Tool
John J. Garguilo
National Institute of Standards and Technology November 11th2009
IHE-PCD Testing – Key Objectives
• Increase test comprehensiveness & quality
• Support both conformance & interoperability testing
• Support for Pre- & Virtual- Connectathons, actual
Connectathon & enable year round testing
• Remain in alignment with IHE-PCD integration profile
development road map
• Establish single framework for PCD covering increasing
complexity and technologies over next 5 years
• Coordinate with IHE ―Gazelle Project‖
• Generate work products that companies can use in their
regulatory submissions
NIST IHE-PCD HL7 V2 Pre-Connectathon Test Tool:
Overview
• IHE-PCD 2009-10 Pre-Connectathon testing (cycle 4)
• Tool
now available
for IHE-PCD domain
• PIX/PDQ and XDS (
IHE-ITI domain
) supported by other ―NISTers‖
• NIST IHE-PCD HL7 V2 tool utility
– Additional tool to the existing Messaging Workbench (MWB)
– Supports IHE‘s evaluation of vendor Pre-Connectathon applications
• Test cases are established by IHE-PCD Test Manager
(Manny )
• In conjunction w/ Integration Profile Working Groups (WGs)
• Integrated into NIST HL7 V2 Test Tool
• Part of the next generation of IHE tools (‗Gazelle‘ project)
• Developed through the NIST Healthcare Testing Infrastructure
initiative supported by ARRA
NIST IHE-PCD HL7 V2 Pre-Connectathon Test Tool:
Overview
• Supports IHE-PCD Pre-Connectathon testing for HL7 V2:
IHE-PCD Integration Profile
Actors Transaction (Message Type)
DEC Device Observation Reporter (DOR) PCD-01 (ORU^R01) DEC SPD (Option) Device Observation Consumer (DOC),
Device Observation Reporter (DOR), Device Observation Filter (DOF)
PCD-02 (QSB^Q16) PCD-01 (ORU^R01) PCD-01 (ORU^R01) PIV Infusion Order Programmer (IOP) PCD-03 (RGV^015) ACM Alarm Reporter (AR) PCD-04 (ORU^R01) IDCO Implantable Device Cardiac Reporter (IDCR) PCD-09 (ORU^R01)
• DEC – Device Enterprise Communication
• DEC – SPD – Subscribe to Patient Data
• PIV – Point-of-care Infusion Verification
• ACM – Alarm Communication Management
NIST IHE-PCD HL7 V2 Pre-Connectathon Test Tool:
Overview
• Static HL7 V2 message validation
• ‗
Instance
‘-type testing
• Implementation conforms to Specification on which it is based
• Validation of IHE-PCD message(s) and corresponding HL7
Profile(s)
•
Syntax and Semantic Content Validation
•Against HL7 V2 message (e.g., PCD-01)
•Message structure
(e.g.,
MSH,PID,PV1,OBR,NTE,
{{OBX},OBX,OBX,OBX,…}
)
•Against HL7 profile
•(Msg_type^Event_type^ e.g., ORU^R01^…)
•Against HL7 and/or user provided tables
•Example of user provided table is RTM for Ref_IDs, Units, etc.
•Against ‗validation context‘, including specific values
NIST IHE-PCD HL7 V2 Pre-Connectathon Test Tool:
Overview
• Resultant ‗
Validation Report
‘
• Provides syntax and semantic results of checks against:
HL7 V2 Structure Validation
IHE-PCD Technical Framework/Supplements
Harmonized Rosetta (hRTM)
• Validation against ‗failure types‘:
– VERSION*: The version in the message and in the profile should match.
– MESSAGE_STRUCTURE_ID*: The message type (MSH.9 element) in the profile and in the message should match.
– MESSAGE_STRUCTURE: The message should have a valid message structure (correct usage, correct cardinality, and correct element name).
– USAGE: R elements should be present; X elements should not be present in the message. – CARDINALITY: Elements should be present at least the minimum times and at most the
maximum times specified in the profile. It should also take into account the usage of the element (X element with a minimum of 4 should not be present in the message).
– LENGTH: The value of the element should have a length equal or less than the value specified in the profile.
– DATATYPE: For the data type NM, DT, DTM, SI and TM, the value of the element should match the regular expression defined in the standard.
– DATA: The value of the element should match a constant specified in the profile, a value set specified in a table, a value or a regular expression specified in the message validation context. – MESSAGE_VALIDATION_CONTEXT*: This is a user input error when the location specified in
the message validation context can't be found in the message.
NIST IHE-PCD HL7 V2 Pre-Connectathon Test Tool:
NIST IHE-PCD HL7 V2 Test Tool:
Access
• Tool Access—
Open for business on November 11
th
, 2009
–
http://xreg2.nist.gov:8080/PCD-HL7Web/
– Web-based application - no downloads and installation necessary
– Available 24/7
• User‘s Guide and Validation Context Files (XML)
available at IHE Patient Care Devices‘ FTP site:
–
ftp://ftp.ihe.net/Patient_Care_Devices/Tools/NIST-Tools/NIST_HL7_V2_Tools/
• Does not require user registration
• Test reports are available and may be saved
– Contact the IHE Project Manager for instructions on
sending/recording report results
NIST IHE-PCD HL7 V2 Test Tool:
Issues/Issue Reporting
• IHE-PCD Supplements are being updated…
– Several HL7 Profiles are still being worked on…
– As Profiles are updated, we will do our best to keep tooling in synch…
• Test Cases are under development…
– As Test cases are updated, we will do our best to keep tooling in synch…
Issue/Bug Reporting
• IHE-PCD Google Groups
– Continue to use established Google Groups to discuss testing issues
• Report tool bugs/issues/suggestions/concerns/comments
directly to John Garguilo (
)
–
Summary
• New IHE-PCD HL7 V2 Pre-Connectathon testing tool
• Trial for the 2009-10 Pre-Connectathon testing cycle
(PCD‘s cycle 4)
• The tool is evolving…
– So stick in there… many areas still a moving target…
– We need your feedback (
mailto:[email protected]?subject=NIST
IHE-PCD HL7 V2 Test Tool Issue
)
• Current to-do list
– Complete Web Site FAQs and other ‗help‘ documentation
– Update and add User Guide to Web Site
– Resolve remaining Beta Tester Issues
• Feedback to IHE-PCD Technical Framework and Supplement Documents
