ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
Please complete this spreadsheet by 19SEP25
To submit your entry, scroll right and add your votes/comments in the next available column...		Ballot contents:
2
Ballot_2025_01
3
4
Organization-->Philips HealthcareInnoVision Medical TechnologiesRed*Fox ConsultingOR.NETICU MedicalBDPractical Health Interoperability, LLCB. Braun MedicalEpicPaul Schluter Consulting
5
CP-DEV-Descr.Your name-->Bob Gold, Javier EspinaEldon MetzKen FuchsTodd CooperKurt ElliasonMichael WorkmanMonroe PattilloTom KowalczykSilas MorrisPaul Schluter
6
CP-DEV-015-00MEMDMC Minimum Message SetYes/Abstain/NoAbstainYesAbstainAbstainYesYesYesYesYesYes
7
Comments:
(Req'd if No)		Suggest clarification regarding patient assignment informationComment: Content profiles should be developed by specific device groups (e.g. infusion pumps) to enable conformance testing.
8
CP-DEV-016-00OBX-1 and OBX-4 Consistency with TF in DEV-51 and DEV-52Yes/Abstain/NoAbstainYesAbstainAbstainYesYesAbstainYesAbstainYes
9
Comments:
(Req'd if No)		Comment: We should reserve OBX-4 = |0.0.0.0| specifically for "no containment" while allowing the first dotted-digit to be zero (0) to support "pre-pending" a PCH Application Hosting Device (aka "gateway") in front of data reported by one or more individual (104xx PHD) devices. I believe this convention was adopted by Continua and/or PCHA over ten to fifteen years ago.
10
CP-DEV-017-00Filter associations transaction cleanupYes/Abstain/NoAbstainYesAbstainAbstainYesYesAbstainYesAbstainAbstain
11
Comments:
(Req'd if No)
12
CP-DEV-020-00Examples for Pillar/Rack/SlotYes/Abstain/NoYesYesAbstainAbstainYesAbstainAbstainYesAbstainYes
13
Comments:
(Req'd if No)
14
CP-DEV-021-00Update PCD-03 message definition and examples to clarify multistep programmingYes/Abstain/NoAbstainYesAbstainAbstainYesYesAbstainYesAbstainNo
15
Comments:
(Req'd if No)		Comments: (1) There are numerous cut-and-paste errors that preclude successful message validation. (2) How should RXG-32/33 be calculated for an open-ended "continuous" infusion? (3) The TQ1 segment in Example 1 should follow RXG, not RXR, per the HL7 message structure stipulated in Table 3.3.4.2-1. (4) OBX-4 for MDC_DEV_PUMP_INFUS_VMD should be either |0.1.0.0| or |0.1|, not |0.1.1.0| for all three examples. (5) RXG-32/33 should be 600 mL for Example 1, not 1000 mL. (6) Please refer to the file <<CP-DEV-021-Comments-Corrections.PSS.1b.2025-09-18T19.pdf>> for additional comments and findings, sent to Kurt on 2025-09-19.
16
CP-DEV-023-00Update Infusion Event Parameters and ExampleYes/Abstain/NoAbstainYesAbstainAbstainYesYesAbstainYesYesAbstain
17
Comments:
(Req'd if No)		Comment: I'd like to hear more about how this should be used for message validation and how this information should be included in the pump containment tree [before I try to integrate it into my message validator].
18
White paper publication approvalWhite paper : Standardization of Device Identification for Improved InteroperabilityYes/Abstain/NoYesYesYes YesYesYesAbstainYesYesYes
19
Comments:
(Req'd if No)		Have some comments. Keeping them for the PC phase.See my comments and edits in the posted white paperComment added to document.
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100