1. John Garguilo and Sandra Martinez 11-16 September, 2011
HL7/Healthcare Devices WG (San Diego, California) NIST Tooling Activities
John Garguilo and Sandra Martinez
11-16 September, 2011

2. Our Team and Project Web Sites…
Contacts
John Garguilo
Sandra Martinez
Tools and Project Sites
NIST’s IHE-PCD HL7 V2
Static ‘Instance Testing’ Pre-/Connectathon Web site:
Pre-Connectathon Cycle 6 ( )
‘Isolated Testing’ Coming in October…
(URL coming soon…)
MDC Testing Web site:

3. NIST Supported Test Tools Overview/Status Update
HL7 V2 Validation (IHE-PCD)
Instance-type Environment (at message level)
Cycle 6 ( )
Isolated-type Environment
Scenario based
Actor centric
One System Under Test (SUT)
RTMMS – Rosetta Terminology Mapping Management System
No version available to public – yet…
ICSGenerator (ICS = Implementation Conformance Statement)
Next Steps and What’s still needed…
Envelope/Message wrappers (WS, SOAP, SAML?) validation
Web Services

4. HL7 / Healthcare Devices WG (San Diego, California) NIST Tooling: HL7 V2.6 Test Tool For Cycle 6 ( )
13 September, 2011

5. Test Environments Instance Testing
Conformance (e.g., against HL7 V2.x or CDA)
Implementation conforms to Spec. on which it is based
Isolated System Testing
Includes Instance Testing Activities
Protocol Conformance
Functional Behavior Conformance
Features and Operational behavior correspond to Specs.
Peer-to-Peer System Testing
Includes Isolated System Testing Activities
Interoperability Testing
Testing complete application environment
May include interacting w/ Database, using Network Communications, or interacting w/ other hardware, apps, or systems if appropriate
In IHE Model:
Instance and Isolated testing ~ Virtual and Pre-connectathon
Peer-to-Peer System Testing ~ Connectathon
NIST HIT Test Infrastructure

6. Conformance Testing of an HL7 V2 Message
Report
Test Artifacts
Conformance Profile
HL7 Tables
‘Device’ Test Agents
ISO/IEEE 11073/Rosetta Terminology
HL7 V2
Message
Validation
Services
Test Management
HL7 V2 Message
Validation Test Case
Results
Validation Report
Test Harness
(Java Code)
Test Execution
User
Web
Application
Client
Registry/
Repository
Instance System Test Environment

7. IHE-PCD Pre- and -Connectathon Tool

8. Validation Report (Example)

9. Test Environments Instance Testing
Conformance (e.g., against HL7 V2.x or CDA)
Implementation conforms to Spec. on which it is based
Isolated System Testing
Includes Instance Testing Activities
Protocol Conformance
Functional Behavior Conformance
Features and Operational behavior correspond to Specs.
Peer-to-Peer System Testing
Includes Isolated System Testing Activities
Interoperability Testing
Testing complete application environment
May include interacting w/ Database, using Network Communications, or interacting w/ other hardware, apps, or systems if appropriate
In IHE Model:
Instance and Isolated testing ~ Virtual and Pre-connectathon
Peer-to-Peer System Testing ~ Connectathon
NIST HIT Test Infrastructure

10. IHE-PCD Testing using a Web Application Client
Report
IHE-PCD
DOR/DOF
Test Agent
HL7 V2
Message
Generation
DOC
Validation
Services
Test Management
Router/Logger/Proxy
Vendor
IHE PCD
Device
Application
System Under Test
Test Artifacts
Conformance Profiles
HL7 Tables
Validation Context Files
Generation Context Files
IHE-PCD Client
Test Scenario
Results
HL7 V2 Message Validation Reports
Test Harness
(Java Code)
Test Execution
Web
Client
IOR AM
IOC AR
IDCC
IDCR
Isolated System Test Environment

11. Isolated / Scenario Testing
Demonstration of a ‘user’ or System Under Test (SUT) [acting as a device observation reporter – DOR] interacting with the NIST Test System [acting as a device observation consumer – DOC] ‘Test Agent’

12. IHE-PCD HL7 V2 Isolated Test Tool

13. IHE-PCD HL7 V2 Isolated Test Tool Select Version and Actor

14. IHE-PCD HL7 V2 Isolated Test Tool DOR – select test case

15. IHE-PCD HL7 V2 Isolated Test Tool Test Case and Step Descriptions

16. IHE-PCD HL7 V2 Isolated Test Tool Configuration

17. IHE-PCD HL7 V2 Isolated Test Tool Waiting for DOR/SUT…

18. IHE-PCD HL7 V2 Isolated Test Tool Parse ORU^R01; Send ACK^R01

19. IHE-PCD HL7 V2 Isolated Test Tool Transaction Processing, with result

20. IHE-PCD HL7 V2 Isolated Test Tool Test Result Summary

21. IHE-PCD HL7 V2 Isolated Test Tool Validation Report

22. IHE-PCD HL7 V2 Isolated Test Tool Validation Report, Continued

23. IHE-PCD HL7 V2 Isolated Test Tool Submit Report (to Test Management)

24. IHE-PCD HL7 V2 Isolated Test Tool Test Management – Vendor Summary

25. IHE-PCD HL7 V2 Isolated Test Tool Test Management – Vendor Dashboard

26. IHE-PCD HL7 V2 Isolated Test Tool Validation Report

27. IHE-PCD HL7 V2 Isolated Test Tool Validation Report, Cont

28. Put Sandra RTMMS and ICSGenerator Slides Here…
Extra slides

29. John Garguilo and Sandra Martinez 11-16 September, 2011
HL7/Healthcare Devices WG (San Diego, California) “Rosetta Terminology Mapping Management System” (RTMMS) Activities
John Garguilo and Sandra Martinez
11-16 September, 2011

30. NIST Contacts John J. Garguilo 301-975-4248 john.garguilo@nist.gov
Sandra Martinez
Isabelle Barclay (Guest Researcher) – term ends this month
Nicolas Crouzier (Guest Researcher)
Project Web site:
Semantic Interoperability of Medical Devices

31. RTMMS Overview
RTMMS was developed to support the IHE-PCD Rosetta Terminology Mapping (RTM) :
A web application that allows vendors and reviewers:
access, retrieval, and reporting of Rosetta Tables over the internet in conformance to IHE RTM Profile.
saving the data in the xml format as defined by RTM Profile.
Aids in The harmonization process by:
Identifying missing terms.
Automatic generation of the “Harmonized Rosetta Table”
Viewing and downloading latest hRTM table.
Facilitates the proposal of New Terms to x73 Nomenclature

32. Technologies employed
J2EE / JAVA 6
ExtJS : Cross-browser JavaScript library
Spring Framework
Spring MVC : Full-featured MVC (Model View Controller) implementation
Spring Security : Provides security solutions (authentication, identification)
Hibernate 3 : Java persistence framework
MySQL 5.1
XMLBeans : Technology for accessing XML by binding it to Java types
Apache Tomcat
MySQL Workbench : To design the database
Tested browsers
Mozilla Firefox (from version 3)
IE (from version 7)
Google Chrome (from version 12)

33. Database Models RTM data and relationships Stores RTM data
Rosetta table
Units and Unit Groups
Enumerations and Enumeration Groups
hRTM table
Uses IEEE Nomenclature database
REFIDs
Term codes
Partition numbers

34. RTMMS Users General user Reviewer Vendor
Views Rosetta Tables
Reviewer
Participates in discussions
Vendor
Modifies Vendor Rosetta Table
Suggests new or mapped terms
SDO (Standard Development Organization)
Modifies Units and Enumerations Table
Register new or mapped terms
Admin
Manages User Accounts
Potential IEEE-Member User ??

35. RTMMS Features Access to NIST IEEE 11073 Nomenclature database
Appendix A terms
Appendix B terms
IDCO terms
PHD terms
Access to RTM database
Ability to proposed terms in Rosetta
Download in XML format hRTM, units and enumerations tables
User registration
confirmation, approval…
Filtering based on regular expressions
Rosetta validation against hRTM
Management capabilities for SDO users

36. RTMMS Updates (since May 2011)
Database management capabilities implemented.
Versioning system implemented.
Possibility for the SDO to view previous Rosetta versions.
Logging history capabilities implemented.
To identify occurred changes, time they were made, users who made them…
New menu on top of login screen for the user guide
Differentiation between mapped terms and new terms
Access to Vendor, Groups and Rules tables.
Harmonized Rosetta is now generated in real time from Rosetta table
Import directly Paul’s XML files
Tables are submitted by individual vendors (MyRosetta)
Tables are merged into one file (Rosetta –xml)
The review process begins
The review is performed by vendor, reviewers and the SDO users.
Any correction or addition will be reflected back to the vendor table (MyRosetta) and Rosetta.
Any missing or new MDC RefId is submitted to the SDO.
Once agreement is reached the hRTM table is generated.

37. Ongoing Work RTM database re-structuring to facilitate management.
Implementing synonym terms
Support synonyms in Nomenclature Database
Support synonyms in RTM Database
SNOMED interface.
Resolved bugs identified in functionality testing exercise.
Add unit filtering
Improve registration content
Allow to add units or enumeration, not both at the same time.

38. Next Steps Add aECG into X73 Nomenclature Dbase. hRTM table updates
Support Vendor_VMD, and Vendor Description
Populate X73 Nomenclature dbase systematic name, common term, acronym and term description tables.
Waiting for electronic files, if available.
SDO ability to set Rosetta versions.

39. Issues IEEE copyright issues -Displaying of copyrighted information…
-Maintenance issues…
-Hosting/Server issues…
-Access control issues…
Integration of LOINC Terms
We have no documentation on LOINC.
Mapping must be provided.
Waiting for SNOMED mapped terms.
Clarification of new/private terms adoption process

40. 11073 Term Adoption Process @ May Working Group Meeting
hRTM?
hRTM? 40

41. RTMMS Scenario and DEMO
All users capabilities:
View/Download Rosetta Table
View/Download Units Table
View/Download Enumerations Table
View logging history
Filter Rosetta Table
By Vendor ID (Philips)
Using Regular Expressions (MDCX_.*)
Viewing Discussed Entries
MDCX_.*

42. Rosetta Table

43. Units Table

44. Enumeration Table

45. Download Table in XML

46. Logging history

47. Filter Rosetta table
Filter Vendor_ID

48. Filter Rosetta table
Filter Vendor_Discussion

49. RTMMS Scenario and DEMO
All users capabilities:
Account management
User Guide

50. Account Management

51. User Guide

52. RTMMS Scenario ‘Reviewer’ Type User Capabilities
Contribute to Discussions
Adding Comments

53. Comment Dialog

54. RTMMS Scenario ‘Vendor’ Type User Capabilities Add a new Rosetta entry
REFIDs lookup from x73 Nomenclature
Group lookup from RTM tables
Units/Unit Groups and Enumerations/Enumeration Groups lookup from RTM tables
Term codes completion from x73 Nomenclature
Suggesting new terms to the standard
Validating Required fields
Edit a Rosetta entry
Deprecate a Rosetta entry

55. Rosetta : Philips vendor

56. Edit Entry

57. RTMMS Scenario ‘SDO’ Type User Capabilities Register a Proposed Term
Assigning term code
Automatically updating Vendor tables

58. Register new terms

59. RTMMS Scenario ‘Admin’ Type User Capabilities
Save/Load/Delete selected database
User management
Import XML files provided by Paul Schluter

60. Database Management

61. User Management

62. Import Rosetta XML files

63. John Garguilo and Sandra Martinez 11-16 September, 2011
HL7/Healthcare Devices WG (San Diego, California) “ICSGenerator” Tool Activities
John Garguilo and Sandra Martinez
11-16 September, 2011

64. John J. Garguilo 301-975-4248 john.garguilo@nist.gov
NIST Contacts
John J. Garguilo
Sandra Martinez
Jing Gao (Guess Researcher)
Project Web site:
Semantic Interoperability of Medical Devices 64

65. ICSGenerator Overview
ICSGenerator was developed to:
Support IEEE Conformance Testing.
Generate Implementation Conformance Statements (ICSs)
Build Device Profile (XML)
Provide validation against DIM Schema
Provide high level semantic interoperability
Ensures correct containment relationship and terminology at the object class and related attribute, notification, and behavior level
Provides access to Rosetta Dbase and X73 dbase
User can produce a device profile, and subsequently load the profile for validation (and to identify if the profile is still in compliance) as the standard advances. 65

66. ICSGenerator Enhancements
Access to latest hRTM version (3q T10)
Access to the latest X73 Nomenclature dbase version (containing IDC, PHD and Appendix B.)
Private Terms support
Capability to enter private objects using a “blank” object template.
Capability to import private terms using a Rosetta-based xml file.
"File" menu  “import private terms”
Capability to access MDC-<vid> private terms from hRTM, if available.
Capability to enter private attributes to a private object or to already defined objects. (This is based on the x73 DIM allowance of extension (section 6.1.4) to the model that states: “In other cases, it may be necessary to define completely new objects or to add new attributes, new methods, or new events to already defined objects. These extensions are considered private or manufacturer-specific extensions”.)
Note: In the May HL7 WG meeting was decided that; the private terms in the process of x73 adoption, could be managed in RTMMS using MDC-<vid> refids with term codes from the x73 nomenclature private space. ICSGenerator should be able to access these terms from hRTM and should also allow the vendor to import vendor private terms that are not in the process of adoption (non MDC-<vid>). 66

67. ICSGenerator Updates
Capability to enter private objects using a “blank” object template 67

68. ICSGenerator Updates
Capability to enter private objects using a “blank” object template 68

69. ICSGenerator Updates
Capability to import private terms using a Rosetta-based xml file 69

70. ICSGenerator Updates
Capability to access private terms from hRTM. 70

71. ICSGenerator Updates
Capability to enter private attributes to a private object or to already defined objects. 71

72. ICSGenerator Enhancements (Cont.)
User Interface improvements:
"Profile Overview" display
By clicking “DIM” on tree root, profile information is displayed on the right side panel.
Dim Object changeable
By clicking on the DIM Object Name an object can be changed to a different object. 72

73. ICSGenerator Future Enhancements
Support PHD standards
Update specializations with published versions
Access to MCD-<vid> private terms via hRTM, when available. 73

74. ICSGenerator Tool and XSchema
CEN and 13735
ISO/IEEE 11073
DIM
Part 10201
Nomenclature
Part 10101
DIM XSchema
Compare Devices
ICSGenerator
This diagram shows the capabilities of the ICSGenerator.
As you can see the ICSGenerator:
Generates Implementation Conformance Statements (ICSs)
Builds Device Profile (XML)
Provides device profile validation against DIM Schema
Allows comparison of device ICSs
Device ICSs comparison capability aids in identifying potential interoperability issues
Generates (via transformations) HL7 OBX Segments (1-7)
Generates Device UML Diagram
13734/5 Standard provided information model for baseline and polling application profiles
HL7/OBX Mapping (XML)
Device UML Diagram 74

75. Thank You!
Questions
Discussion