PCD - WCM

WaveformWaveformCommunicationCommunication

Management [WCM]Management [WCM]

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 

WCM

Device

Waveform Obs.Reporter (DOR)

Device ObsConsumer (DOC)

Device Obs.Filter (DOF)

PCD-01: CommunicateDevice Data

PCD-02: Subscribe toDevice Data

PCD-01: CommunicateDevice Data

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 streams4. MCW snapshot archive query5. Periodic trend data on request

• It is not expected that all Use Cases will be covered during the first cycle.

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.

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

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…

PCD - Testing

Test Tooling SupportTest Tooling Support

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

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.

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

Test Tool Support – HL7 v2

Actor

Actor

2

Specification Tool (e.g. MWB)

IHE/PCD-01Validation

Criteria(XML)

HL7 Test

Messages

HL7 Test

Messages

MsgMappingProfile

TestReports

HL7 TestMessages

Message Generation(X73 + HL7 Partial Messages)

IHE-PCD MessageSpecifications

(IHE-PCD TF Vol 2)

HL7 V2 Profile(XML)

NIST Data Repository(HL7 Ref. DB,Table Values,

Sample Values,From Profiles,

Default Values,X73 Device Profiles)

(XML)

Device Table Values

[Rosetta Stone Terms]

(Manufacturer Specific)[e.g., B.Braun, Draeger, GE, Philips, Spacelabs,

Welch Allyn, etc.]

NIST HL7 V2.xTesting Tool

(Web Services)

Message Specification

Profiles

1

Device Content

HL7 Msgs

Msg Specifications

Arrow Key: