1 / 44

“ IHE-PCD F2F Meeting” (NIST Testing Tool Status)

“ 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. “2011 Pre- Connectathon Testing ” Updates, Issues, Questions for Cycle 6 Profiles and Test Cases.

leala
Download Presentation

“ IHE-PCD F2F Meeting” (NIST Testing Tool Status)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. “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. “2011 Pre-Connectathon Testing”Updates, Issues, Questions for Cycle 6Profiles and Test Cases National Institute of Standards and Technology (NIST) John Garguilo, Sandra Martinez, Julien Deshayes, Jing Gao 20 October, 2011

  3. 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. 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. DEC Test Cases

  6. 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

  7. PIV Test Cases

  8. PIV Test Cases (Cont.)

  9. IDCO Testing – Cycle 6 Validation Updates • MSH-21=“1.3.6.1.4.1.19376.1.6.1.9.1” • See “Question/Issues” section.

  10. IDCO Test Cases

  11. 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”

  12. 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?

  13. ACM Test Cases

  14. 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.

  15. DEC-SPD Test Cases

  16. DEC-SPD Test Cases

  17. DEC-SPD Test Cases

  18. 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.

  19. 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)

  20. 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.

  21. 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

  22. Test Cases

  23. WCM Assertions • Profile syntax and structure assertions using ACM or DEC profile static definition. • 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.

  24. 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

  25. WCM Assertions WCM assertions for the OBR segment.

  26. WCM AssertionsOBX for Waveform Data (Required) Is there a list available?

  27. WCM AssertionsOBX for Waveform Data Attribute – Technical Condition Mapping (Optional)

  28. WCM Assertions OBX for Waveform Data – Sample Rate (Required) Not in the nomenclature

  29. WCM Assertions OBX for Waveform Data - Encoding Scheme (Optional) Not in the nomenclature

  30. WCM Assertions OBX for Waveform Data – Resolution (Optional) Is this table correct? What is Table 10 for?

  31. WCM Assertions OBX for Waveform - Data Range (optional)

  32. WCM Assertions Waveform Filter Description - Filter Description(type) (Required)

  33. WCM Assertions Waveform Filter Description - Filter Order (Optional)

  34. WCM Assertions Waveform Filter Description - Filter Frequency (Optional)

  35. WCM Assertions Waveform Display – Sweep Speed (Optional)

  36. WCM Assertions Waveform Display - Grid Lines (Optional)

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

  38. WCM Assertions Waveform Display - Scale Range (Optional)

  39. WCM Assertions Waveform Display - Physiological Range (Optional)

  40. WCM Assertions Waveform Markers - Instantaneous Waveform Events (Optional)

  41. WCM Sample message Waveform data (provides specific waveform source ID) Technical condition Not in the nomenclature Waveform information

  42. Questions • WCM: • Waveform Sample Count (X.Y.3.5) is not in the data model. Why? Is it optional or required?

  43. WCM Test Cases

  44. WCM Data Model

More Related