1. PCD - WCM Waveform Communication Management [WCM]

2. WCM Waveform Communication Management will extend the [DEC] profile to provide a method for passing near real-time waveform data using HL7 v2 observation messages between a Reporter and a Consumer. –A filter will be an optional element

3. WCM Device Waveform Obs. Reporter (DOR) Device Obs Consumer (DOC) Device Obs. Filter (DOF) PCD-01: Communicate Device Data PCD-02: Subscribe to Device Data PCD-01: Communicate Device Data

4. WCM WCM will cover the following prioritized Use Cases: 1.Current Multi-Channel Waveform (MCW) snapshot as defined by the source is created/pushed by alarm source based on event occurrence 2.Current MCW snapshot as defined by source on request to source 3.Continuous MCW streams 4.MCW snapshot archive query 5.Periodic trend data on request It is not expected that all Use Cases will be covered during the first cycle.

5. WCM A number of existing standards will be evaluated as references: –MFER (ISO 11973-92001) –FEF (ISO 14271) –FDA HL7 v3 Annotated ECG Guideline –DICOM Supplement 30 – Waveform Interchange –Previous HL7 v2 waveform spec (deprecated) Our scope is to create a profile which leverages existing IHE PCD Profiles and “principles” of using HL7 v2.x and IEEE 11073 nomenclature.

6. WCM Key requirements: –Leverage existing IHE PCD Profiles and “principles” of using HL7 v2.x and IEEE 11073 nomenclature. –Provide raw data and not bit-maps or pdf files Supports rendering at end client Supports further analysis at end client –Support “snapshots”, data “streams” and retrospective “trend” data types –Minimize optionality Focus on simplicity and avoid complexity

7. WCM In addition to defining the waveform representation scheme, attributes will need to be defined, including: –Sampling Rate –Range and Offset –Filtering –Display Attributes –Annotations (time points and time intervals) Beat identification Breath identification Optional parametric data (e.g. HR, IBP, …) Etc. –Status Out-of-range Leads Off Zero Artifact, Noise Etc. –Etc…

8. PCD - Testing Test Tooling Support

9. Profile Conformance Testing NIST has the following mission in regards to Health IT Interoperability Standards: –Ensure health IT standards are complete and robust and –Establish a health IT standards testing infrastructure that supports effective industry consensus standards development processes and provides the U.S. healthcare IT industry and federal activities with robust conformance and interoperability testing capabilities

10. Profile Conformance Testing IHE and NIST are collaborating to test vendor implementations as defined across the IHE-PCD profiles. –This cycle year includes IHE-PCD V2 message validation, both syntactically and semantically. –Terminology is constrained to “Harmonized Rosetta” terminology from the ISO/IEEE 11073 standard.

11. Profile Conformance Testing Tooling is being developed to: –Increase test comprehensiveness and quality –Support both conformance and interoperability testing –Establish a framework for IHE-PCD covering increasing complexity and technologies over the next five years –Support for virtual connectathons, actual connectathons and to enable year round testing –Remain in alignment with the IHE-PCD road- map

12. Test Tool Support – HL7 v2