1. IEEE 11073-10103IDC NomenclatureOctober 2012 Implantable Cardiac Devices -Nomenclature for device communication Intermediate survey results -New parameters for version 2 of the standard

2. MAX MIN MEDIAN Importance ratingfor new parameters after 11 reviews HIGH …Importance LOW Recent device programming date/time and/or program counter Mean ventricular heart rate at atrial burden Lead/Device recall information Multisite Left Ventricular Pacing parameters Counters for shocks started/successful and ATPs successful Number and energy of shocks applied per episode (machine readable) Number of ATPs applied per episode (machine readable) Message triggers / alert summary (urgency) RV pacing avoidance algorithm name and status Message trigger categories MRI parameters Patient Pacemaker Dependant? (YES/NO) Message triggers / alert summary (compact) Shock waveform parameters PVARP Patient activity Message triggers / alert summary (long) RA/RV/LV sensing configuration More vendor specific entries in lists of episode types, brady modes. Thoracic impedance Mean A/V heart rate at rest/night AF Suppression algorithm info (ON/OFF) PVARP after PVC/PAC PVAB / Far-field protection window after Pace PVAB / Far-field protection window after Sense Patient comments if stored in device / system (medication, indication,…) Date of the next scheduled in clinic / remote follow-up(s) Rate adaptation settings (for brady pacing) LVPP / TWPP (ON/OFF) Post shock pacing settings (brady mode, basic rate, ...) RVB LVB RARP (ARP) RABP RVRP (VRP) LVRP Rate adaptation sensor type (coded and machine readable) IVRP LVPP / TWPP Respiratory Rate Heart Rate Variability (HRV)

3. Feedback to more detailed questionswas low but if present mostly consistent • Rate adaptation settings shall be provided vianew parameters codes vs. just text = 3 / 1 • It shall be added, what kind of statistics has been used for the HRV value (1)*. • Votes for the patient activity unit:percent per 24h vs. hours per day = 2 / 1 • Details of the TI measurement vector:machine readable vs. as text = 2 / 1 • Message triggers shall be provided as a color code. The name of the detail parameter should be ‘notifications’ (2). • Only the next scheduled (remote) follow-up date if available shall be provided (3), but separate for remote and in-clinic (1). * number of votes

4. Issues under discussion between vendors due to implementation/liability concerns • Providing recall information will be difficult as there are regulated and established workflows in place to be followed. • Message triggers / notifications are seen problematic by some vendors as EMRs are seen as not prepared/designed for that and due to liability issues. • Providing coded rate adaptation settings (as requested) will be burdensome or impossible as systems are very different. • Comments in the device are typically not up to date (missing maintenance process). Should we do new patient comments "since last follow-up“? Should comments have a creation date?