software and systems division “ihe-pcd f2f meeting” (nist testing tool status) national...

Soft

ware

an

d S

yste

ms D

ivis

ion

“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

Soft

ware

an

d S

yste

ms D

ivis

ion

“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

Soft

ware

an

d S

yste

ms D

ivis

ion

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]

Soft

ware

an

d S

yste

ms D

ivis

ion

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âuto-

measurement^MDC,MMEAS^manual-measurement^MDC, ASETâuto-setting^MDC, MSET^manual-setting^MDC, ACALCâuto-calculation^MDC, MCALC^manual-calculation^MDC – if omitted the default value I AMEAS

Soft

ware

an

d S

yste

ms D

ivis

ion

DEC Test Cases

Soft

ware

an

d S

yste

ms D

ivis

ion

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) = ÎVP^HL70164, ^SYR^HL70164

or empty– RXR-1 (Route) = ÎV^HL70162– RXR-4 (Administration Method) = ÎV^HL70165, ÎVPB^HL70165

or empty

Soft

ware

an

d S

yste

ms D

ivis

ion

PIV Test Cases

Soft

ware

an

d S

yste

ms D

ivis

ion

PIV Test Cases (Cont.)

Soft

ware

an

d S

yste

ms D

ivis

ion

IDCO Testing – Cycle 6 Validation Updates

• MSH-21=“1.3.6.1.4.1.19376.1.6.1.9.1”• See “Question/Issues” section.

Soft

ware

an

d S

yste

ms D

ivis

ion

IDCO Test Cases

Soft

ware

an

d S

yste

ms D

ivis

ion

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”

Soft

ware

an

d S

yste

ms D

ivis

ion

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?

Soft

ware

an

d S

yste

ms D

ivis

ion

ACM Test Cases

Soft

ware

an

d S

yste

ms D

ivis

ion

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.

Soft

ware

an

d S

yste

ms D

ivis

ion

DEC-SPD Test Cases

Soft

ware

an

d S

yste

ms D

ivis

ion

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.

Soft

ware

an

d S

yste

ms D

ivis

ion

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)

Soft

ware

an

d S

yste

ms D

ivis

ion

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.

Soft

ware

an

d S

yste

ms D

ivis

ion

IPEC Assertions • Valid MDC_PUMP_MODE values (OBX-5) :

pump-mode-nominalpump-mode-drug-dosingpump-mode-ramp-taperpump-mode-multi-steppump-mode-multi-dosingpump-mode-boluspump-mode-loading-dosepump-mode-multi-channelpump-mode-pcapump-mode-continuouspump-mode-pca-and-continuouspump-mode-piggybackpump-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

Soft

ware

an

d S

yste

ms D

ivis

ion

Test Cases

Soft

ware

an

d S

yste

ms D

ivis

ion

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.

Soft

ware

an

d S

yste

ms D

ivis

ion

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

Soft

ware

an

d S

yste

ms D

ivis

ion

WCM Assertions

WCM assertions for the OBR segment.

Soft

ware

an

d S

yste

ms D

ivis

ion

WCM AssertionsOBX for Waveform Data (Required)

Is there a list available?

Soft

ware

an

d S

yste

ms D

ivis

ion

WCM AssertionsOBX for Waveform Data Attribute – Technical Condition

Mapping (Optional)

Soft

ware

an

d S

yste

ms D

ivis

ion

WCM Assertions OBX for Waveform Data – Sample Rate (Required)

Not in the nomenclature

Soft

ware

an

d S

yste

ms D

ivis

ion

WCM Assertions OBX for Waveform Data - Encoding Scheme (Optional)


Soft

ware

an

d S

yste

ms D

ivis

ion

WCM Assertions OBX for Waveform Data – Resolution (Optional)

Is this table correct?What is Table 10 for?

Soft

ware

an

d S

yste

ms D

ivis

ion

WCM Assertions OBX for Waveform - Data Range (optional)

Soft

ware

an

d S

yste

ms D

ivis

ion

WCM Assertions Waveform Filter Description - Filter Description (type)

(Required)

Soft

ware

an

d S

yste

ms D

ivis

ion

WCM Assertions Waveform Filter Description - Filter Order (Optional)

Soft

ware

an

d S

yste

ms D

ivis

ion

WCM Assertions Waveform Filter Description - Filter Frequency (Optional)

Soft

ware

an

d S

yste

ms D

ivis

ion

WCM Assertions Waveform Display – Sweep Speed (Optional)

Soft

ware

an

d S

yste

ms D

ivis

ion

WCM Assertions Waveform Display - Grid Lines (Optional)

Soft

ware

an

d S

yste

ms D

ivis

ion

WCM Assertions Waveform Display - Color (Optional)

Additional Assertion: Each of R,G and B has a range from 0 to 255.

Soft

ware

an

d S

yste

ms D

ivis

ion

WCM Assertions Waveform Display - Scale Range (Optional)

Soft

ware

an

d S

yste

ms D

ivis

ion

WCM Assertions Waveform Display - Physiological Range (Optional)

Soft

ware

an

d S

yste

ms D

ivis

ion

WCM Assertions Waveform Markers - Instantaneous Waveform Events

(Optional)

Soft

ware

an

d S

yste

ms D

ivis

ion

WCM Sample message


Technical condition

Waveform data (provides specific waveform source ID)

Waveform information

Soft

ware

an

d S

yste

ms D

ivis

ion

Questions• WCM:

– Waveform Sample Count (X.Y.3.5) is not in the data model. Why? Is it optional or required?

Soft

ware

an

d S

yste

ms D

ivis

ion

WCM Test Cases

Soft

ware

an

d S

yste

ms D

ivis

ion

WCM Data Model

software and systems division “ihe-pcd f2f meeting” (nist testing tool status) national...

Documents