Скачать презентацию Software Diagnostics and Conformance Testing Division ISO IEEE 11073 Скачать презентацию Software Diagnostics and Conformance Testing Division ISO IEEE 11073

7afa1abbfbac85d6d5b42fbf37d2adc2.ppt

  • Количество слайдов: 43

Software Diagnostics and Conformance Testing Division ISO/IEEE 11073, IHE-PCD, PHD and NIST Medical Device Software Diagnostics and Conformance Testing Division ISO/IEEE 11073, IHE-PCD, PHD and NIST Medical Device Communication Test Effort HL 7/IEEE WG Meetings (Phoenix, Arizona) 6 May 2008

Software Diagnostics and Conformance Testing Division Medical Device Test Effort NIST Team Members • Software Diagnostics and Conformance Testing Division Medical Device Test Effort NIST Team Members • John Garguilo (john. [email protected] gov, 301 -975 -5248) • Sandra Martinez (sandra. [email protected] gov, 301 -975 -3579) • Maria Cherkaoui (maria. [email protected] gov Guest Researcher) • Richard Theimer (richard. [email protected] gov CENTECH Group, Inc. , Contractor)

Software Diagnostics and Conformance Testing Division Meeting Topics/Discussion • Testing focus areas of IHE-PCD Software Diagnostics and Conformance Testing Division Meeting Topics/Discussion • Testing focus areas of IHE-PCD – Device to Device (via ISO/IEEE 11073 protocols) – Device to Enterprise (via HL 7 protocols) • Focus areas of IEEE PHD WG – Standards development (X 73 -20601 and 104 xx) – Device to Device (via ISO/IEEE 11073 protocols) • NIST Test Tool Inventory and Update – Patient Care Device focus (mainly IHE-PCD) – Adaptation to Personal Health Device • NIST P 11073 -10202 DIM XSchema (PAR) – PAR Project Plan – X 73 -10202 Documentation Discussion – Feedback to standards • http: //www. nist. gov/medicaldevices

Software Diagnostics and Conformance Testing Division Test Focus Areas • NIST Test Tools Inventory Software Diagnostics and Conformance Testing Division Test Focus Areas • NIST Test Tools Inventory – Device Communication • ISO/IEEE 11073 – ICSGenerator – Validate. PDU – XML Schema (ISO/IEEE P 11073 -10202 TMD 01 a) – Enterprise Communication • IHE-PCD – Data Mapping from device to “enterprise” (via IHE-PCD Vol II/III Framework Doc) • HL 7 (general across all IHE domains) – MWB (VA), Message. Maker (NIST) – MESA / Kudu (IHE, Steve Moore and Erik Poiseau) – Web Services (mainly Validation) (NIST) – Gazelle (next generation building on Kudu [and other tools]) – Cypress Collaborative – just kicked off • Cypress wiki: http: //collaborate. nist. gov/twikicypress/bin/view/Cypress/Web. Home

Software Diagnostics and Conformance Testing Division IHE-PCD Year 3+ Profile Proposal PCD-Real Time Plug-n-Play Software Diagnostics and Conformance Testing Division IHE-PCD Year 3+ Profile Proposal PCD-Real Time Plug-n-Play X 73 APDU • • Validate APDUs against Standard Determine if APDUs meets device profile (defined using ICSGenerator)

Software Diagnostics and Conformance Testing Division What are we doing? Test Tools ICSGenerator What Software Diagnostics and Conformance Testing Division What are we doing? Test Tools ICSGenerator What is it? Implementation Conformance Statement Generator, Profile builder X 73 Message validation: profile and standard • Easy to use interface • Based on standard Promote Interoperability Why? Who’s using it? Validate. PDU Most major medial device manufactures –IHE-PCD participants (pre-connectathon, HIMSS) –PHD participants (smaller devices - Continua effort) A few small manufactures have expressed interest Countries participating: US, Europe, Japan, Korea, Canada How is it being As a requirement to standard (ICSs) used? Early stage interoperability Validate Standard Who are we working with? • IHE-Patient Care Domain • Personal Health Device WG • IEEE 11073 WG IHE-PCD profile validation Message validation Validate Standard

Software Diagnostics and Conformance Testing Division ICSGenerator Tool and XSchema CEN 13734 and 13735 Software Diagnostics and Conformance Testing Division ICSGenerator Tool and XSchema CEN 13734 and 13735 ISO/IEEE 11073 Nomenclature Part 10101 DIM Parts 10201/ 20601 DIM XSchema Compare Devices ICSGenerator HL 7/OBX Mapping (XML) Device UML Diagram

Software Diagnostics and Conformance Testing Division ICSGenerator Capabilities • Generates Implementation Conformance Statements (ICSs) Software Diagnostics and Conformance Testing Division ICSGenerator Capabilities • Generates Implementation Conformance Statements (ICSs) – Required in conformance section (10) of DIM x 73 document – Ensures common format for ICS generation • Builds Device Profile (XML) – Generates an electronic (XML) version of device data model based strictly on the IEEE x 73 DIM – Includes private or manufacturer-specific extensions • Provides validation against DIM Schema – A device data model generated using this tool can be validated against an updated version of the DIM XSchema • Provides high level semantic interoperability – Ensures correct containment relationship and terminology at the object class and related attribute, notification, and behavior level – Compare Device ICSs • Device ICSs comparison capability aids in identifying potential interoperability issues • Generates HL 7 OBX Segments • Generates Device UML Diagram

Software Diagnostics and Conformance Testing Division ICSGenerator Enhancements What’s new since our last meeting… Software Diagnostics and Conformance Testing Division ICSGenerator Enhancements What’s new since our last meeting… • Added PHD Profile – Agent • ICSGenerator has been enhanced to allow the generation of X 73 -PHD 104 xx XML configuration files in compliance with the IEEE P 11073 20601. – The tool prohibits users from developing non-compliant IEEE P 11073 20601 configuration files. – (e. g. , restricting a user from abstractly defining a “conditional” attribute (which is “mandatory” in the standard). – Currently we have developed configuration files for: • • 10415 Weighing Scale 10404 Pulse Oximeter 10441 Cardiovascular fitness and activity monitor 10442 Strength fitness equipment • ICSGenerator also generates ICS’s tables as required by IEEE P 11073 20601.

Software Diagnostics and Conformance Testing Division Validate. PDU Tool • Validate. PDU: Performs APDU Software Diagnostics and Conformance Testing Division Validate. PDU Tool • Validate. PDU: Performs APDU syntax/structure and semantic validation using a MDER Coder. Device Profile (From ICSGenerator) (xml) ROSEapdu (MDER) Validate. PDU (MDER + XER Coder) Coder Encode/Decode) Validation Report (APDU Syntax and Semantic Validation) APDU (XER)

Software Diagnostics and Conformance Testing Division Validate. PDU Capabilities • • Decodes MDER PDUs Software Diagnostics and Conformance Testing Division Validate. PDU Capabilities • • Decodes MDER PDUs and builds ASN. 1 object instances. Provides an interface to display a parsed message in the following formats – XER (in compliance with the standard XER where applicable). – MDER binary – Enhanced view (JTree representation) • • • Generates Validation Reports. Highlight incorrect fields in enhanced view. Associates report messages with Test Assertions. Note: Validate. PDU functionalities are captured in a Validate. PDU Software Requiremen Specification document. (Reviewed by members of the WG)

Software Diagnostics and Conformance Testing Division Validate. PDU Capabilities (Detailed) • Validates APDU syntax Software Diagnostics and Conformance Testing Division Validate. PDU Capabilities (Detailed) • Validates APDU syntax against X 73 DIM specifications and the X 73 Application Profiles – Base Standard • ASN. 1 data types syntax. • Object hierarchy, cardinality, acceptable behaviors, notifications and attributes in compliance with X 73 Standards. • Relationship between ROSE and CMIP data types. • Validate APDU semantic/content against device profile (object, attribute, behavior, notification and services implementation) – Tool determines if: • a MOC, attribute, behavior and notifications identified in a message is implemented by the device profile. • attributes identified in a message are implemented as part of a MOC in the device profile. • the message contains the attribute as required by the device profile (missing or unrecognized attributes). • the message contains valid MOC information, such as handle and context-id according to the device profile. • the message contains valid attribute information, such as fixed values and value ranges according to the device profile. • a behavior identified in a message is supported by the device profile. • MOC objects hierarchy complies with device profile specifications. • the message contains the MOCs as required by the device profile (missing MOC or unrecognized MOCs)

Software Diagnostics and Conformance Testing Division Validate. PDU Enhancements What’s new since our last Software Diagnostics and Conformance Testing Division Validate. PDU Enhancements What’s new since our last meeting… • No new enhancements • See coming slides for next steps…

Software Diagnostics and Conformance Testing Division Software Diagnostics and Conformance Testing Division

Software Diagnostics and Conformance Testing Division IEEE P 11073 -10202 TM/D 01 a XML Software Diagnostics and Conformance Testing Division IEEE P 11073 -10202 TM/D 01 a XML Schema Topics of Discussion • • • Purpose Status Strategy for Review Content of Document Next Steps…

Software Diagnostics and Conformance Testing Division IEEE P 11073 -10202 TM/D 01 a XML Software Diagnostics and Conformance Testing Division IEEE P 11073 -10202 TM/D 01 a XML Schema Purpose • What the XSchema is… – To enable conformance to standard (specifically Domain Information Model and Nomenclature) • • Needed for conformance testing Needed by tooling for automation/consistent approach – – • Attempt to document how DIM (ASN. 1) Data Types map to XML What the XSchema is not… – • Otherwise one must do this by hand, which usually leads to errors propagated into standard(s) Not intended to replace ASN. 1 defined in DIM Exercise of formalizing DIM in a normalized way – Verification • • • – Validation • • – What does it mean to verify the XSchema Classic – more definition, resource issue? PHD – less definition, more resources (across more devices) Using tools to express device Expressing the device according to the standard (Schema tie) All of XSchema content (XSD) will go into document

Software Diagnostics and Conformance Testing Division IEEE P 11073 -10202 TM/D 01 a XML Software Diagnostics and Conformance Testing Division IEEE P 11073 -10202 TM/D 01 a XML Schema Status • To date we have been presenting our work and test tools based on the “classic” DIM – ICSGenerator • • – Validate. PDU • • Generates ICSs Device specializations (abstract representation compliant to DIM) Validates syntax of APDU Validates low level semantics of APDU against profile (from ICSGenerator DIM XML Schema Java Class libraries – ASN. 1 data types in Java (including MDER)

Software Diagnostics and Conformance Testing Division IEEE P 11073 -10202 TM/D 01 a XML Software Diagnostics and Conformance Testing Division IEEE P 11073 -10202 TM/D 01 a XML Schema Strategy for Review • Strategy for review/discussion of x 73 -10202 Document – First Exposure • Description of how documentation maps to the problem – E. g. , Object Definition and relationships – Second Exposure • Eye-ball each section (text, example, MOC Attributes) – Third (Detailed) Exposure • Editorial – go through line by line for emissions, redundancy, etc. leading to a ‘design review’ • Some level of traceability to do conformance testing

Software Diagnostics and Conformance Testing Division • • IEEE P 11073 -10202 TM/D 01 Software Diagnostics and Conformance Testing Division • • IEEE P 11073 -10202 TM/D 01 a XML Schema Document Content Overview, Normative References, Definitions, Abbreviations and Acronyms, Guiding principles XSchema Design Approach XSchema Architecture XSchema Object Definitions – Data Types • • – Object Definitions • • – – • Common Data Types Attribute Data Types Containment relationships Object Inheritance Attribute Definition Behaviour Definition Notification Definition Private Extensions Annexes – – – DIM Traceability (Normative) – how to trace back to DIM Automated Conformance Toolkit Architecture (Informative) Bibliography (Informative)

Software Diagnostics and Conformance Testing Division • • • IEEE P 11073 -10202 TM/D Software Diagnostics and Conformance Testing Division • • • IEEE P 11073 -10202 TM/D 01 a XML Schema Document Content - Design Based on Object-oriented approach from DIM The DIM is an object-oriented model that consists of objects, the object attributes, and methods which are abstractions of real-world entities in the domain of medical devices. UML Diagram (packages in the form of object diagrams)

Software Diagnostics and Conformance Testing Division IEEE P 11073 -10202 TM/D 01 a XML Software Diagnostics and Conformance Testing Division IEEE P 11073 -10202 TM/D 01 a XML Schema Document Content – Design (Cont. ) The following UML components are addressed: • Containment Relationship • Inheritance • Encapsulation • Multiplicity The following textual elements of the IEEE 11073 DIM are also addressed: • Managed Object Classes (MOC) Definitions • Attribute Definition • Attribute Groups • Behavior Definition • Notification Definition • Attribute groups • Private extensions • Common Data Type • Terminology • Service Model • ICS tables

Software Diagnostics and Conformance Testing Division IEEE P 11073 -10202 TM/D 01 a XML Software Diagnostics and Conformance Testing Division IEEE P 11073 -10202 TM/D 01 a XML Schema Document Content - Architecture • DIM XML Schema DIM. xsd General. ICS. xsd service. ICS. xsd Polling. Mode. xsd MOC_Defs. xsd Baseline-Manager. xsd MOC_Attr_Behav_Notif. xsd DIM_Values. xsd Rose. xsd DIM_Data_Types. xsd (http: //www. nist. gov/x 73 DIM) Transport. xsd DIM XSchema Document Structure osxdlib. xsd (http: //www. obj. sys. com/v 1. 0/XMLSchema) include import

Software Diagnostics and Conformance Testing Division IEEE P 11073 -10202 TM/D 01 a XML Software Diagnostics and Conformance Testing Division IEEE P 11073 -10202 TM/D 01 a XML Schema Document Content - Architecture • DIM XML Schema Diagram

Software Diagnostics and Conformance Testing Division IEEE P 11073 -10202 TM/D 01 a XML Software Diagnostics and Conformance Testing Division IEEE P 11073 -10202 TM/D 01 a XML Schema Document Content – Object Definitions Example • Common Data Type Example – 8 -bit unsigned integer INT-U 8 ASN. 1 type mapped into XSD INT-U 8: : =INTEGER(0. . 255) XSD Representation using ASN 2 XSD tool:

Software Diagnostics and Conformance Testing Division IEEE P 11073 -10202 TM/D 01 a XML Software Diagnostics and Conformance Testing Division IEEE P 11073 -10202 TM/D 01 a XML Schema XSchema: DIM Traceability (Normative) XSchema Component DIM Clause(s) Comments DIM_Data_Types. xsd 7. 1. 2, 7. 3. 2. 1, 7. 3. 3. 1, 7. 3. 4. 1, 7. 3. 5. 1, 7. 3. 6. 1, 7. 3. 8. 1, 7. 3. 9. 1, 7. 3. 10. 1, 7. 3. 11. 1, 7. 3. 12. 1, 7. 3. 13. 2, 7. 4. 1. 1, 7. 4. 2. 1, 7. 4. 3. 1, 7. 5. 1. 1, 7. 5. 2. 2, 7. 5. 2. 3, 7. 5. 7. 2, 7. 5. 8. 1, 7. 5. 8. 2, 7. 5. 9. 1, 7. 5. 10. 2, 7. 5. 10. 3, 7. 6. 1. 1, 7. 6. 1. 2, 7. 6. 1. 3, 7. 6. 2. 1, 7. 6. 3. 1, 7. 6. 4. 1, 7. 6. 5. 1, 7. 6. 6. 1, 7. 6. 8. 1, 7. 6. 9. 1, 7. 7. 1. 2, 7. 7. 1. 3, 7. 7. 2. 1, 7. 7. 4. 1, 7. 7. 5. 3, 7. 7. 7. 1, 7. 7. 7. 3, 7. 7. 9. 3, 7. 8. 1. 2, 7. 8. 1. 3, 7. 8. 6. 1, 7. 8. 7. 1, 7. 9. 2. 1, 7. 9. 4. 1, 7. 10. 1. 2, Represents common data types and all type definitions in the DIM_Values. xsd 7. 2, 7. 3, 7. 4, 7. 5, 7. 6, 7. 7, 7. 8, 7. 9, 7. 10 Associates general information such as reference clause, qualifier; object, attribute, behavior and notification term codes; object , attribute, behavior and notification name; attribute_Id, behaviour_Id, notification_Id; behavior action parameter type, behavior action result type and notification event parameter type MOC_Attr_Bahav_Notif. xsd 7. 2, 7. 3, Associate values defined in DIM_values. xsd to specific attributes, behavior or notification.

Software Diagnostics and Conformance Testing Division • • IEEE P 11073 -10202 TM/D 01 Software Diagnostics and Conformance Testing Division • • IEEE P 11073 -10202 TM/D 01 a XML Schema Document Content Overview, Normative References, Definitions, Abbreviations and Acronyms, Guiding principles XSchema Design Approach XSchema Architecture XSchema Object Definitions – Data Types • • – Object Definitions • • – – • Common Data Types Attribute Data Types Containment relationships Object Inheritance Attribute Definition Behaviour Definition Notification Definition Private Extensions Annexes – – – DIM Traceability (Normative) – how to trace back to DIM Automated Conformance Toolkit Architecture (Informative) Bibliography (Informative)

Software Diagnostics and Conformance Testing Division IEEE P 11073 -10202 TM/D 01 a XML Software Diagnostics and Conformance Testing Division IEEE P 11073 -10202 TM/D 01 a XML Schema Next Steps (near term goals) • Take a detailed pass to see if the document is on target. • Determine, through use: Can the XSchema/Tooling be used to express manufacturer’s devices? • Help calibrate what’s in conformance tools… …and tie tools back into the standard • Feedback into the standard (through issues) • Lead to another document for PHD DIM XSchema (20601) • Driven by Users: – What will users do with this document? – Will tooling be enough (for the validation part) – Feedback from use of tools should drive document (and standard)

Software Diagnostics and Conformance Testing Division IEEE P 11073 -10202 TM/D 01 a XML Software Diagnostics and Conformance Testing Division IEEE P 11073 -10202 TM/D 01 a XML Schema • Questions and Further Discussion… • Actions/Take-aways • Thanks for your input and attention

Software Diagnostics and Conformance Testing Division Begin Sandra’s PHD Slides • Sandra’s slides Software Diagnostics and Conformance Testing Division Begin Sandra’s PHD Slides • Sandra’s slides

Software Diagnostics and Conformance Testing Division PHD Project IEEE P 11073 -20601 • IEEE Software Diagnostics and Conformance Testing Division PHD Project IEEE P 11073 -20601 • IEEE P 11073 -20601 makes use of information objects that are defined in ISO/IEEE Std 11073 -10201, adapting these information objects to the domain of Personal Health Device communication. The information objects are specialized and therefore modified in the following ways: – The definition of attributes that are mandatory, optional, or conditional may be different * – Additional Object Services may be defined – Additional Attributes may be defined – Some features of the original model might not be used • • If there is a discrepancy between standards, the IEEE P 11073 -20601 standard takes priority. IEEE P 11073 -20601 replicates relevant portions of ISO/IEEE Std 11073 -10101 and incorporates new nomenclature codes.

Software Diagnostics and Conformance Testing Division Leveraging NIST Tools to PHD X 73 DIM Software Diagnostics and Conformance Testing Division Leveraging NIST Tools to PHD X 73 DIM (IEEE 11073 -10201) DIM XSchema DIM XML config. PHD-DIM (IEEE-11073 -20601) (IEEE-11073 -104 xx) PHD XSchema. X 73 -104 xx XMl config. XML config. PHD XML X 73 -104 xx XSchematron. config. ICSGenerator Validate. PDU Device Specializations ICS’s

Software Diagnostics and Conformance Testing Division ICSGenerator, DIM XSchema and PHD-DIM PHD XSchema • Software Diagnostics and Conformance Testing Division ICSGenerator, DIM XSchema and PHD-DIM PHD XSchema • A PHD-DIM XSchema has been developed to represent the IEEE P 11073 20601 standard. • The PHD XSchema adopts the DIM XSchema architecture and reuses some of it components, when applicable. – DIM_Data_Type. xsd containing classic x 73 ASN. 1 definition will be included and redefined, when appropriate.

Software Diagnostics and Conformance Testing Division “Classic” X 73 DIM XSchema DIM. xsd General. Software Diagnostics and Conformance Testing Division “Classic” X 73 DIM XSchema DIM. xsd General. ICS. xsd service. ICS. xsd Polling. Mode. xsd MOC_Defs. xsd Baseline-Manager. xsd MOC_Attr_Behav_Notif. xsd DIM_Values. xsd Rose. xsd DIM_Data_Types. xsd (http: //www. nist. gov/x 73 DIM) Transport. xsd DIM XSchema Document Structure osxdlib. xsd (http: //www. obj. sys. com/v 1. 0/XMLSchema) include import

Software Diagnostics and Conformance Testing Division PHD_DIM XSchema PHD_DIM. xsd PHD_MOC_Defs. xsd PHD_MOC_Attr_Behav_Notif. xsd Software Diagnostics and Conformance Testing Division PHD_DIM XSchema PHD_DIM. xsd PHD_MOC_Defs. xsd PHD_MOC_Attr_Behav_Notif. xsd Qual_Bases. xsd PHD_Data_Types. xsd PHD_Import. xsd DIM_Data_Types. xsd (http: //www. nist. gov/x 73 DIM) Enumerations_Bases. xsd asn 1. xsd (http: //www. obj. sys. com/v 1. 0/XMLSchema) redefine include import

Software Diagnostics and Conformance Testing Division ICSGenerator, DIM XSchema and PHD-DIM ICSGenerator • ICSGenerator Software Diagnostics and Conformance Testing Division ICSGenerator, DIM XSchema and PHD-DIM ICSGenerator • ICSGenerator generates X 73 “Classic” device specializations using IEEE X 73 baseline and polling application profiles. – • For PHD, ICSGenerator will use an XML IEEE P 11073 -104 XXX device specialization configuration file to define implementation of a device specialization. ICSGenerator has been enhanced to allow the generation of X 73 -PHD 104 xx XML configuration files in compliance with the IEEE P 11073 20601. – The tool will not allow to develop a configuration file that is not in compliance to IEEE P 11073 20601. (ex. Trying to support an attribute as “conditional” or “optional” when the IEEE P 11073 20601 states that it must be “mandatory”. – Currently we have developed configuration files for: • • 10415 Weighing Scale 10404 Pulse Oximeter 10441 Cardiovascular fitness and activity monitor 10442 Strength fitness equipment • ICSGenerator also generates ICS’s tables as required by IEEE P 11073 20601. • The tool must be enhanced to generate X 73 -PHD 104 xx device specializations – XSchematron rules must be applied to achieve compliance to the IEEE P 11073 -104 XXX specification.

Software Diagnostics and Conformance Testing Division ICSGenerator, DIM XSchema and PHD-DIM X 73 -10441 Software Diagnostics and Conformance Testing Division ICSGenerator, DIM XSchema and PHD-DIM X 73 -10441 (Cardiovascular fitness and activity monitor)

Software Diagnostics and Conformance Testing Division ICSGenerator, DIM XSchema and PHD-DIM X 73 -10441 Software Diagnostics and Conformance Testing Division ICSGenerator, DIM XSchema and PHD-DIM X 73 -10441 (Cardiovascular fitness and activity monitor)

Software Diagnostics and Conformance Testing Division ICSGenerator, DIM XSchema and PHD-DIM X 73 -10441 Software Diagnostics and Conformance Testing Division ICSGenerator, DIM XSchema and PHD-DIM X 73 -10441 (Cardiovascular fitness and activity monitor)

Software Diagnostics and Conformance Testing Division ICSGenerator, DIM XSchema and PHD-DIM X 73 -10441 Software Diagnostics and Conformance Testing Division ICSGenerator, DIM XSchema and PHD-DIM X 73 -10441 (Cardiovascular fitness and activity monitor)

Software Diagnostics and Conformance Testing Division ICSGenerator, DIM XSchema and PHD-DIM X 73 -10404 Software Diagnostics and Conformance Testing Division ICSGenerator, DIM XSchema and PHD-DIM X 73 -10404 (Pulse Oximeter)

Software Diagnostics and Conformance Testing Division ICSGenerator, DIM XSchema and PHD-DIM X 73 -10415 Software Diagnostics and Conformance Testing Division ICSGenerator, DIM XSchema and PHD-DIM X 73 -10415 (Weighing Scale)

Software Diagnostics and Conformance Testing Division Validate. PDU 2. 0 and PHD-DIM • Current Software Diagnostics and Conformance Testing Division Validate. PDU 2. 0 and PHD-DIM • Current version of Validate. PDU validates APDU syntax against X 73 DIM specifications and the X 73 Application Profiles – Base Standard and validates APDU semantic/content against device profile. • Validate. PDU must be enhanced to support IEEE P 11073 -20601 specification: – Incorporate new and modified PHD data types. – Extract assertions from the PHD specifications. – Develop code to properly validate and parse PHD messages.

Software Diagnostics and Conformance Testing Division Next Steps • Enhance ICSGenerator to add the Software Diagnostics and Conformance Testing Division Next Steps • Enhance ICSGenerator to add the capability to generate implementations of IEEE-11073 PHD 104 xx device specializations in XML including the ICS tables. – Incorporate XSchematron validation • Enhance Validate. PDU to validate PHD type messages.