Presentation is loading. Please wait.

Presentation is loading. Please wait.

Software and Systems Division “IHE-PCD F2F Meeting” (NIST Testing Tool Status) National Institute of Standards and Technology (NIST) John Garguilo, Sandra.

Published byMelina Stokes Modified over 9 years ago

Similar presentations

Presentation on theme: "Software and Systems Division “IHE-PCD F2F Meeting” (NIST Testing Tool Status) National Institute of Standards and Technology (NIST) John Garguilo, Sandra."— Presentation transcript:

1 Software and Systems Division “IHE-PCD F2F Meeting” (NIST Testing Tool Status) National Institute of Standards and Technology (NIST) John Garguilo, Sandra Martinez, Isabelle Barclay and Nicolas Crouzier October, 2011

2 Software and Systems Division “2011 Pre-Connectathon Testing” Updates, Issues, Questions for Cycle 6 Profiles and Test Cases National Institute of Standards and Technology (NIST) John Garguilo, Sandra Martinez, Julien Deshayes, Jing Gao 20 October, 2011

3 Software and Systems Division DEC Testing – Cycle 6 Validation Updates Profile syntax and structure validation using DEC profile static definition: OBX-2: The value types in HL7 table 0125 have been constrained NTE.4 (Comment Type): Length is now 705 PV1-44(Admit Date/Time): Usage is now RE and cardinality [0..1] OBR segment: two more components were added (Collection Volume and Collection Identifier) OBX-2: LEN is now 3 OBX-3: LEN is now 705 OBX-6: LEN is now 705 OBX-15: LEN is now 705 OBX-16: LEN is now 3220 OBX-17: LEN is now 705 OBX-18: LEN is now 427 Add the following table references: ORC-1: TBL# 0119, ORC-5: TBL#0038, ORC-6: TBL#0121 ORC-2 usage is “R” and cardinality [1..1] ORC-3 usage is “X” and cardinality [0..0]

4 Software and Systems Division DEC Testing – Cycle 6 Validation Updates Semantic Validation updates: MSH.11.1 (Processing ID) value = HL7 Table 0103 MSH.11.2 (Processing Mode) value = “P or D” MSH-21 (Message Profile Identifier) value = “1.3.6.1.4.1.19376.1.6.1.1.1” PID.5.7 (Patient Name – name type code) = “L or U” OBX-17 (Obeservation Method) = “UNSPEC^mcat-unspec^MDC,AMEAS^auto- measurement^MDC,MMEAS^manual-measurement^MDC, ASET^auto-setting^MDC, MSET^manual-setting^MDC, ACALC^auto-calculation^MDC, MCALC^manual-calculation^MDC – if omitted the default value I AMEAS

5 Software and Systems Division DEC Test Cases

6 Software and Systems Division PIV Testing – Cycle 6 Validation Updates Profile syntax and structure validation using PIV profile static definition, with the following cycle 6 updates: –Component PID-3.1 (in terms of the CX data type, CX-1) "ID number", is required. PID-3.4 (CX-4) "Assigning authority", and PID-3.5 (CX-5) "Identifier Type Code" are required for each identifier if they are known (for example if they are ordinarily included in ADT messages at the institution), but may be empty if they are not known. –RXR-3 usage is now “RE”, cardinality [0..1] and TBL#0164 –RXR-4 usage is “R”, cardinality [1..1] and TBL#0165 –OBX-2: LEN is now 3 –OBX-3: LEN is now 705 –OBX-6: LEN is now 705 –OBX-15: LEN is now 705 –OBX-16: LEN is now 3220 –OBX-17: LEN is now 705 –OBX-18: LEN is now 427 –OBX-2: the value types in HL7 table 0125 have been constrained –ORC-2 should be ‘R’ and ORC-3 should be ‘X’ –RXR-3 usage should be changed to “RE” and cardinality “0..1 –RXR-4 usage should be changed to “R” and cardinality “1..1”

7 Software and Systems Division PIV Testing – Cycle 6 Validation Updates Semantic Validation updates –MSH-21 (Message Profile Identifier) value = “1.3.6.1.4.1.19376.1.6.1.3.1” –RXR-3 (Administration Device) = ^IVP^HL70164, ^SYR^HL70164 or empty –RXR-1 (Route) = ^IV^HL70162 –RXR-4 (Administration Method) = ^IV^HL70165, ^IVPB^HL70165 or empty

8 Software and Systems Division PIV Test Cases

9 Software and Systems Division PIV Test Cases (Cont.)

10 Software and Systems Division IDCO Testing – Cycle 6 Validation Updates MSH-21=“1.3.6.1.4.1.19376.1.6.1.9.1” See “Question/Issues” section.

11 Software and Systems Division IDCO Test Cases

12 Software and Systems Division IDCO Questions/Issues MSH-15, MSH-16 and MSH-21 are not listed in the IDCO constrained message structure given in Table 3.9.4.1.2.1-1 for the MSH Segment. Currently these fields are optional in the IDCO NIST Validation Context Files. Is there are an updated list of Model/serial numbers? Which version of the nomenclature should we be using for pre- Connectathon testing? –Currently the tool is using the “2010 Connectathon Term set”

13 Software and Systems Division ACM Testing – Cycle 6 Validation Updates MSH-21= “1.3.6.1.4.1.19376.1.6.1.4.1“ Are there any other updates?

14 Software and Systems Division ACM Test Cases

15 Software and Systems Division DEC-SPD Testing – Cycle 6 Validation Updates MSH-21 = “1.3.6.1.4.1.19376.1.6.1.2.1” No DOF TA available for testing in the isolated environment.

16 Software and Systems Division DEC-SPD Test Cases

17 Software and Systems Division DEC-SPD Test Cases

18 Software and Systems Division DEC-SPD Test Cases

19 Software and Systems Division IPEC Assertions Profile syntax and structure validation using DEC profile static definition, with the following changes: MSH-9=“ORU^Rxx^ORU_R01” ----- waiting for CP. MSH-21.3 = “1.3.6.1.4.1.19376.1.6.1.10.1” Any parameter listed in the OBX-3.2 (Observation Identifier) segment of a PCD-10 message must be in the IPEC event parameter table. If OBX-3.2= “MDCX_ATTR_EVT_COND” then OBX-5.2 = “MDCX_PUMP_DELIVERY_START” or “MDCX_PUMP_DELIVERY_STOP” or “MDCX_PUMP_DELIVERY_COMP” or all the optional events included in the table.

20 Software and Systems Division IPEC Assertions If a PCD-10 message is sent for a “delivery start” event then following parameters are required: –MDCX_ATTR_EVT_COND (Pump Event) –MDC_DRUG_NAME_TYPE (Drug Name) –MDC_PUMP_MODE (Pump Mode) –MDC_PUMP_STAT (Pump Status) –MDC_RATE_DOSE (Rate) –MDC_VOL_FLUID_TBI_REMAIN (Volume Remaining) If a PCD-10 message is sent for a “Delivery Stop” or “Delivery Complete” event then the following parameters are required: –MDCX_ATTR_EVT_COND (Pump Event) –MDC_DRUG_NAME_TYPE (Drug Name) –MDC_PUMP_MODE (Pump Mode) –MDC_PUMP_STAT (Pump Status) –MDC_RATE_DOSE (Rate) –MDC_VOL_FLUID_TBI_REMAIN (Volume Remaining) –MDC_VOL_FLUID_DELIV (Volume Delivered)

21 Software and Systems Division IPEC Assertions The following parameters “MDC_PUMP_STAT”, “MDC_PUMP_MODE” and “MDC_FLOW_FLUID_PUMP” must be under a delivery channel containment level. The following parameters MDC_DRUG_NAME_TYPE” and “MDC_VOL_FLUID_TBI_REMAIN” must be under a source channel containment level.

22 Software and Systems Division IPEC Assertions Valid MDC_PUMP_MODE values (OBX-5) : pump-mode-nominal pump-mode-drug-dosing pump-mode-ramp-taper pump-mode-multi-step pump-mode-multi-dosing pump-mode-bolus pump-mode-loading-dose pump-mode-multi-channel pump-mode-pca pump-mode-continuous pump-mode-pca-and-continuous pump-mode-piggyback pump-mode-concurrent Valid MDC_PUMP_STAT values (OBX-5): pump-status-ready pump-status-infusing” pump-status-paused” pump-status-kvo” pump-status-delayed” pump-status-standby” pump-status-vtbi-complete” pump-status-off” pump-status-priming

23 Software and Systems Division Test Cases

24 Software and Systems Division WCM Assertions 1.Profile syntax and structure assertions using ACM or DEC profile static definition. 2.ACM or DEC supplement assertions are used in addition to the following WCM supplement requirements: WCM supplement assertions for the OBX segment: OBX-1 Set ID - OBX (SI), required: As specified in the IHE PCD Technical Framework, Volume 2. OBX-2 Value Type (ID), conditional: This section will specify specific IDs per attribute. In the case of group IDs this field is empty. OBX-3 Observation Identifier (CE), required: As specified in the IHE PCD Technical Framework, Volume 2. OBX-4 Observation Sub-ID (ST), required: Further guidance is provided per attribute. –The Waveform Data will always be contained in the Channel at dot level 4. OBX-5 Observation Value (varies), conditional. Further guidance is provided per attribute. OBX-6 Units (CE), conditional. Further guidance is provided per attribute OBX-7 References Range (ST), required if available. As specified in the IHE PCD Technical Framework, Volume 2. OBX-8 Abnormal Flags (IS) required but may be empty: As specified in the IHE PCD Technical Framework, Volume 2. OBX-11 Observation Result Status (ID), required if available: Required for Group IDs, optional in other cases.

25 Software and Systems Division WCM Assertions WCM supplement assertions for the OBX segment (cont.) –OBX-14 Date/Time of the Observation (TS) required but may be empty: Further guidance is provided per attribute. –OBX-16 Responsible Observer (XCN) required but may be empty: As specified in the IHE PCD Technical Framework, Volume 2. –OBX-17 Observation Method (CE), conditional: As specified in the IHE PCD Technical Framework, Volume 2. –OBX-18 Equipment Instance Identifier (EI), required but may be empty: As specified in the IHE PCD Technical Framework, Volume 2. –OBX-19 Date/Time of the Analysis (TS), conditional may be empty: As specified in the IHE PCD Technical Framework, Volume 2. –OBX-20 Observation Site (CWE), required may be empty: As specified in the IHE PCD Technical Framework, Volume 2. –If a Waveform is included in a transaction OBR-7 and OBR-8 fields are required. OBR-7 refers to the start time and OBR-8 the end time of the end of the last sample interval of all waveforms

26 Software and Systems Division WCM Assertions WCM assertions for the OBR segment.

27 Software and Systems Division WCM Assertions OBX for Waveform Data (Required) Is there a list available?

28 Software and Systems Division WCM Assertions OBX for Waveform Data Attribute – Technical Condition Mapping (Optional)

29 Software and Systems Division WCM Assertions OBX for Waveform Data – Sample Rate (Required) Not in the nomenclature

30 Software and Systems Division WCM Assertions OBX for Waveform Data - Encoding Scheme (Optional) Not in the nomenclature

31 Software and Systems Division WCM Assertions OBX for Waveform Data – Resolution (Optional) Is this table correct? What is Table 10 for?

32 Software and Systems Division WCM Assertions OBX for Waveform - Data Range (optional)

33 Software and Systems Division WCM Assertions Waveform Filter Description - Filter Description (type) (Required)

34 Software and Systems Division WCM Assertions Waveform Filter Description - Filter Order (Optional)

35 Software and Systems Division WCM Assertions Waveform Filter Description - Filter Frequency (Optional)

36 Software and Systems Division WCM Assertions Waveform Display – Sweep Speed (Optional)

37 Software and Systems Division WCM Assertions Waveform Display - Grid Lines (Optional)

38 Software and Systems Division WCM Assertions Waveform Display - Color (Optional) Additional Assertion: Each of R,G and B has a range from 0 to 255.

39 Software and Systems Division WCM Assertions Waveform Display - Scale Range (Optional)

40 Software and Systems Division WCM Assertions Waveform Display - Physiological Range (Optional)

41 Software and Systems Division WCM Assertions Waveform Markers - Instantaneous Waveform Events (Optional)

42 Software and Systems Division WCM Sample message Not in the nomenclature Technical condition Waveform data (provides specific waveform source ID) Waveform information

43 Software and Systems Division Questions WCM: – Waveform Sample Count (X.Y.3.5) is not in the data model. Why? Is it optional or required?

44 Software and Systems Division WCM Test Cases

45 Software and Systems Division WCM Data Model

Download ppt "Software and Systems Division “IHE-PCD F2F Meeting” (NIST Testing Tool Status) National Institute of Standards and Technology (NIST) John Garguilo, Sandra."

Similar presentations

National Institute of Standards and Technology Technology Administration U.S. Department of Commerce 1 Patient Care Medical Devices Test Effort Integrating.

National Institute of Standards and Technology Technology Administration U.S. Department of Commerce 1 Patient Care Medical Devices Test Effort Integrating.
Integrating the Healthcare Enterprise (IHE) Patient Care Devices Domain (PCD) Alarm Communication Management (ACM) IHE PCD 2011 Fall Face-to-Face Kansas.

Integrating the Healthcare Enterprise (IHE) Patient Care Devices Domain (PCD) Alarm Communication Management (ACM) IHE PCD 2011 Fall Face-to-Face Kansas.
March 7, 2011 COMPARATIVE ANALYSIS HL7 V2.5.1 Implementation Guide: Orders and Observations; Interoperable Laboratory Result Reporting to EHR (US REALM)

March 7, 2011 COMPARATIVE ANALYSIS HL7 V2.5.1 Implementation Guide: Orders and Observations; Interoperable Laboratory Result Reporting to EHR (US REALM)
HL7 V2 Conformance Testing Robert Snelick NIST January 20 th, 2004

HL7 V2 Conformance Testing Robert Snelick NIST January 20 th, 2004
Software and Systems Division Medical Device Communication Test Effort IHE-PCD, HL7 Dev WG, ISO/IEEE 11073, and NIST Medical Device Communication Test.

Software and Systems Division Medical Device Communication Test Effort IHE-PCD, HL7 Dev WG, ISO/IEEE 11073, and NIST Medical Device Communication Test.
John Garguilo and Sandra Martinez September, 2011

John Garguilo and Sandra Martinez September, 2011
Software and Systems Division IHE/PCD Face-to-face meeting April 2012 Semantic Interoperability of Medical Devices Pervasive Computing Program Medical.

Software and Systems Division IHE/PCD Face-to-face meeting April 2012 Semantic Interoperability of Medical Devices Pervasive Computing Program Medical.
IHE PCD MEM-DMC CMMS & RTLS Vendor Perspective

IHE PCD MEM-DMC CMMS & RTLS Vendor Perspective
Device and EMR interoperability (IDCO). Implantable Cardiac Device Information is Collected At Implant … During In Clinic Follow-ups … And in the Home.

Device and EMR interoperability (IDCO). Implantable Cardiac Device Information is Collected At Implant … During In Clinic Follow-ups … And in the Home.
IHE PCD Interoperability Mini-Showcase at AAMI 2013 Long Beach, CA CMMS New Directions Demonstrations Monroe Pattillo Practical Health Interoperability,

IHE PCD Interoperability Mini-Showcase at AAMI 2013 Long Beach, CA CMMS New Directions Demonstrations Monroe Pattillo Practical Health Interoperability,
1 IHE PCD F2F 2014-04-01 IHE PCD Quick Updates IHE PCD Face-to-Face, Cleveland, Ohio Tuesday Q1 and Q2, April 1, 2014 Paul Schluter, GE Healthcare Q1:

1 IHE PCD F2F IHE PCD Quick Updates IHE PCD Face-to-Face, Cleveland, Ohio Tuesday Q1 and Q2, April 1, 2014 Paul Schluter, GE Healthcare Q1:
Result Status Relationships

Result Status Relationships
1 Cardinality Specification and Testing Recommendations LOI and LRI MU Certification September 9 th, 2013 Draft 1.2 1.

1 Cardinality Specification and Testing Recommendations LOI and LRI MU Certification September 9 th, 2013 Draft
1 HL7 DEV SIG and IEEE 11073 GC 2014-09-18 IEEE P11073-10101a Update HL7 DEV SIG and IEEE 11073 GC Meetings, Chicago, IL Thursday Q4, September 18, 2014.

1 HL7 DEV SIG and IEEE GC IEEE P a Update HL7 DEV SIG and IEEE GC Meetings, Chicago, IL Thursday Q4, September 18, 2014.
Sponsored by. Wouldn’t it be great if all your equipment, software and devices worked together, right out of the box? thinks so, too.

Sponsored by. Wouldn’t it be great if all your equipment, software and devices worked together, right out of the box? thinks so, too.
LRI Validation Suite Meeting November 1st, 2011. Agenda Review of LIS Test Plan Template CLIA Testing EHR testing (Juror Document)—Inspection Testing.

LRI Validation Suite Meeting November 1st, Agenda Review of LIS Test Plan Template CLIA Testing EHR testing (Juror Document)—Inspection Testing.
2013 PCD Domain Update Monroe Pattillo Practical Health Interoperability, LLC IHE PCD Planning Committee Co-Chair.

2013 PCD Domain Update Monroe Pattillo Practical Health Interoperability, LLC IHE PCD Planning Committee Co-Chair.
IHE-PCD , HL7 HC Dev WG, ISO/IEEE 11073, and NIST Medical Device Communication and IHE-PCD Cycle 4 Test Strategy IHE-PCD, HL7, ISO/IEEE Joint WG Meetings.

IHE-PCD , HL7 HC Dev WG, ISO/IEEE 11073, and NIST Medical Device Communication and IHE-PCD Cycle 4 Test Strategy IHE-PCD, HL7, ISO/IEEE Joint WG Meetings.
Guide to Using Message Maker Robert Snelick National Institute of Standards & Technology (NIST) December 2005

Guide to Using Message Maker Robert Snelick National Institute of Standards & Technology (NIST) December 2005
February 7-10, 2005IHE Interoperability Workshop 1 Established Profile for connectathon 2005: Laboratory Scheduled WorkFlow Francois Macary GWI Medica.

February 7-10, 2005IHE Interoperability Workshop 1 Established Profile for connectathon 2005: Laboratory Scheduled WorkFlow Francois Macary GWI Medica.

Similar presentations

Ads by Google