Skip to end of metadata
Go to start of metadata

Date: 16-19 September 2019

Quarters: Q3 Monday - Q4 Thursday

Minutes Approved as Presented 

This is to approve minutes via general consent. "You have received the minutes. Are there any corrections to the minutes? (pause) Hearing none, if there are no objections, the minutes are approved as printed."


Set goals, objectives or some context for this meeting.

Discussion items


Monday, Q3

Welcome, Introductions, Rules

  • IEEE Patent Policy
  • Review of Previous Meeting Minutes and Action Items 

Officers (John Rhoads - IEEE PoCD Chair)

Tom Tompson (IEEE-SA Liaison)
John Garguilo (IEEE PoCD Secretary)

Motion to approve Montreal (May 2019) meeting minutes.  Motion by Todd Cooper, Second by Brian Reinhold 17-0-0
Monday, Q4
  • 11073 PHD Status / PAR Report
  • 11073 PoCD Status / PAR Report
  • 11073 SC and PoCD P&Ps
  • 2020 Feb Sydney Planning:  Meeting?

Tom Tompson / Ken Fuchs / Daidi Zhong

Ken Fuchs / Tom Thompson

Tuesday, Q2

Welcome, Introductions, Rules

  • 11073 SDC:
    • General Update
    • SDC related PARs
    • IHE SDPi WP - Overview / Roadmap
    • OR.NET
    • SDC Connectathon - Update / Planning

Rhoads, IEEE Staff

Schlichting / Andersen / Gregorczyk

Note: Q1 joint w/ O&O (refer to O&O Meeting Mins):  O&O stated the group will enter multiple Tracker items in Gforge and HCD will get notified when action needed.

11073 SDC

  • 11073 SDC Update and presentation (Stefan Schlichting) provided and overview, update, and on-going work regarding 11073-SDC standards (see presentation).
  • 11073-10701, content complete, 80 Requirements, D0 was created in 07/2019
  • 11073-10107, Content collection running, approximately 15 Actions, request for more Actions/Operations (please provide to Stefan); Open Questions: 1) Which code Partition or reuse ACT block of Part 1? 2) MDC_ACT_Prefix?

Stefan suggested starting ballot directly after Feb '20 HL7 meetings.

Stefan would like to start balloting in April 2020.  Also proposed having a Webinar to walk through details prior to having folks receive package...  Todd Cooper suggested perhaps doing a call when folks are together in Cleveland for IHE-NA Connectathon.


Bjorn Anderson

  • Bjorn presented the block diagram of a device specialization for an 'Insufflator' 
  • Bjorn estimated and projected to have "feature complete" for April 2020

  • Focus on modeling at this point.
  • Bjorn showed for IEEE 11073-10207 IG on SIMPLIFIER.NET
  • Bjorn suggested forming a task force on PoC IG integration.

(Bjorn) A "hack-athon" is scheduled in Lubeck with real devices to get more into the application - Middle of October.  Also, there will be device simulators to do the conversion of SDC –> FHIR respective resources ("SDC-FHIR Conversion"...  This is on the scheduled for Thursday afternoon and Friday if necessary.  

There will be more details in other details later this week.


Todd Cooper - White Paper under IHE-PCD called "Service-oriented Device Point-of-Care Interoperability (SDPi)" a device-to-device connectivity in high-acuity healthcare environments using Web Services Technology.

  • Out for Public Comment - due VERY soon (9/20/19)
  • Idea of the White Paper is for a broad audience - Intent was to get enough high level knowledge in one place for many perspectives.
  • Todd walked through the sections of the white paper.
  • Todd also mentioned to please take a close look at the Road Map (3-year); in terms of public feedback, Todd is looking for response to "Additional Roadmap Considerations...."  (line 3000 of document).

Tuesday, Q3
  • PoCD Cybersecurity:
    •   11073 PHD Cybersecurity
    •   AAMI TIR57, SW96, TIR97,
    •   UL2900
    •   Security topics from JWG7

  • "Quiet Hospital" Use Case Discussion



Cooper / Schlichting 

General status updates provided by Todd Cooper & Stephan Schlichting,

Links provided by Uwe related to Cybersecurity discussion for attendees:,FSP_LANG_ID:22678,25

Quiet Hospital: Todd Cooper provided a general overview.  Stefan provide a presentation from a previous presentation...

Slides presented on SDC Alarming/reporting etc.

No Action items

Tuesday, Q4
  • U.S. Government MDIRA Project

  • X73 PoCD/PHD "Scoping" Discussion

  • Review and Adjourn IEEE Portion of Meeting

Steve Griffiths

Ken Fuchs

Todd Cooper


Steve Griffiths


Overview (Gov't funding project, in addition to military, FDA, NIH)

Adapters (see diagram above green/pink boxes) given lack of interoperability...

IHE SDPi Use Cases:

Wednesday, Q1
  • Welcome and Introductions
  • Intellectual Property Policy

  • DEV WG Agenda Review
  • Report out from DESD & HL7 Co-chair mtgs.

  • NIST Tooling



Faughn / Garguilo (NIST)

NIST Tool Discussion (Michael Faughn/ John Garguilo)

  • Please refer to Michael's submitted presentation in Confluence "Documents" posted presentations here entitled "Atlanta_11073_NIST-Promethseus_September_2019"
Wednesday, Q2

FHIR  Projects Update

  • Issue relating to 10101R to submit XML files of all the tables

Devices on FHIR :

  • Alerting (incl. DeviceAlert resource proposal)
  • PHD IG Ballot Comment Resolution
  • PoCD IG: 
    • Status Update
    • Content Proposals (see HERE)


Malcolm Clarke

Stefan Schlichting

Reinhold / Rosner
Rhoads / Karl

Issue relating to 10101R submission of XML files of all the tables (Malcolm Clarke)

  • Issues ties to near term deadline (Friday, September 20, 2019) for IEEE document process and submission.
  • Motion to "strike footnote from IEEE submission document which indicates submission of XML files of all the 10101R tables"
    • Motion made by Michael Faughn, second by Todd Cooper
    • Motion passed 11-0-0 by IEEE voting members

Devices on FHIR Discussion: Alerting

  • [John R. ] noted: Agenda item is to give a viewing and awareness to this group, further discussion would occur on DoF weekly call.... Todd 
  • Todd Cooper: Action Item for Todd Cooper to follow up w/ DiVinci folks that device alert is a different 'alert' than the to date understanding by DiVinci group Action items
  • Note: no formal document/presentation submitted to HCD WG, code example shown and discussed at meeting
  • Discussion to call "device" item "AlertSource" from "2019-06-17AlertResourceDiscussionNotes.docx" (John Rhoads to post to documents page of Confluence

  • John Rhoads asked if anyone had anything further to discuss on Alerting?
    • Paul Schluter noted regarding Event Phase ("start" and "End" and "Continue" captured in effective time...  Stefan Schlichling noted that when one changes the 'status of the resource'... perhaps change to "Alert Phase"

PHD IG Ballot Comment Resolution

  • Brian Reinhold noted that a discussion occurred with Clem (who has some outstanding negative items, and that Brian has responded and is waiting on Clem's review.  Clem indicated he agreed to review outstanding issues (persuasive) to be resolved (i.e., accepted by Clem).
  • Stauts update provided by Martin Rosner:
    • Comments and status changes to be made in GForge (and indicated updates will be added in the very near term
    • Assuming Clem's responses (are favorable), wrap up of IG items should be resolved over the next few DoF weekly calls (Wednesday, 9 am EST calls).


  • From John Rhoads: Some administrative items to be addressed by John R., as moving towards another revision... Reference Punch list  (see HERE
  • Fill in 
Wednesday, Q3
  • 10101 to LOINC mapping updates
  • 10101 / LOINC review panel plan

  • IEEE P11073-10101b
    • parameters (NMT, TPTD-CCO, infusion?
    • event and alert nomenclature
    • additional body and measurement sites
  • IEEE -10103 IDCO
  • Harmonized Rosetta (hRTM2a) updates

Abhyankar / McDonald
John Rhoads

Paul Schluter

LOINC mapping updates and Review Panel Plan

  • Dr. Abhyankar indicated that few new terms were added since the last WG meetings  into the LOINC dBase and due to staffing issues, she will dedicate more of her time to the dBase end and thus for the short term not have the resources to dedicate attention to more mappings.
  • John Rhoads noted HCD will attempt to establish volunteer effort (perhaps through IHE) to help with the terminology review and mappings.

Terminology (Schluter)

  • Please see posted presentations here entitled "IEEE_11073_2019-09-18.Atlanta.5d.2019-09-18T10" and
  • Please see the Implantable Device report out here "IDCO HRS Interoperability Reportout Sep 2019"
Wednesday, Q4
  • Joint with Mobile Health
  • Terminology (continuation of Q3 if needed)
  • FHIR Tooling Discussion

Matt Graham / Gora Datta

Mobile Health Joint Session

  • Keith Boone presented Mobile Health PSS-lite project 
    • Keith asked for a "show of hands" of who in HCD are interested in participating as subject matter experts (Brian, John Rhoads and Martin responded favorably).
  • Status Update (Matthew Graham)
    • Please see posted presentations here entitled "2019 Sept Mobile Health Projects Update"
    • New work from last WG report out: "School Healthcare Information Framework utilizing Technology (SHIFT)" (refer to provided slide set)

Terminology report/summary (cont' from Q3)

  •  Hoping for provisional terms for events and reports by end of Oct 2109

FHIR Tooling Discussion (in preparation for Q1 Thursday joint meeting)

  • John R. will build a slide from some items in past weekend's "Connectathon"...related to alerts
  • Other topics
    • Alerting
    • Performance challenges at server side (e.g., can output 200 per second per device w/o or including waveforms)
    • Localization
    • Large Data issues - Experience from FHIR Connectathon like event - 
      • SDC Patient monitor - 50 - 60 devices for example (which is not realistically much from a hospital setting) - would have to write ~7K observations per second. 
      • Writing into the repository was buffered and couldn't handle them...
      • So next the observations were bundled (which optimized) - led to 160-180 observations per second...
      • Then optimized the server and memory... 
      • Next write only every 10 or so seconds (i.e., 10 second blocking)... which worked better - achieved nearly 7K observations per second...  also don't get timestamps.  Note to display on a mobile phone would likely need to do every ~2 seconds.
      • Bottleneck was really at FHIR server... throughput of the network was not the problem...
      • So from Stephan S' perspective this will really not scale up.
      • Brian R. mentioned the large amount processing that has to occur at the FHIR server side, lots of overhead as well to set up.
    • Save two-dimensional data that is not over time
      • real time sample is able to display
      • Distributuion rate not able
    • DoF Road map - process for the next iteration of the IG + release 5

Todd also mentioned to WG about planning for Australia WG meetings and suggested thinking about perhaps having some introductory sessions throughout the week to help the newer folks in Australia to get more engaged with the HCD group.

  • Motion made to close the IEEE portion of WG meetings
    • Motion made by John Garguilo, second by Todd Cooper 
    • Motion approved 11-0-0
Thursday, Q1

Welcome and Introductions

  • Joint with FHIR @ HCD
    • “Devices on FHIR” IG Roadmaps, R5, Resource Maturity, ...
    • DoF:  Alerting Strategies (incl. DeviceAlert)
    • DoF:  Server Performance re. Scaling for Patient Monitored data (e.g., SDC)
    • FHIR "Localization"
    • FHIR support for non-time-based sample arrays
    • Device Static vs. Dynamic Data in FHIR
    • HCD / FHIR Planning

Co-Chairs / Rick Geimer

Rhoads, Karl

Stefan Karl

Stefan Karl


Joint with FHIR @ HCD (FHIRi Rep: Rick Geimer, room M103)

“Devices on FHIR” IG Roadmaps, R5, Resource Maturity, ...

  • Resource Maturity Level (ML): Rick noted when developing and working on IGs for trial use, FMG will be requiring attending/testing at a FHIR Connectathon Event or similar type of event.
    • Noted that IG of this group areML STU
    • The requirement above (attending FHIR Connectathon/Test Event) applies to ML 0 or 1
  • O&O status for device
    • Device status is conflated depending on if device is implanted (vs. if for example if a device is implanted with a dead battery)
    • Looking at status of device and status of record of device...
  • Any resources planned on bringing normative (Level 4 or 5).  
    • HCD would likely bring forward DeviceMetric forward
    • Presently at maturity level 1, next is to fill out spreadsheet, do a testing event at FHIR Connectathon (or similar event if not at HL7 WG meetings)
  • Timing of R5 will likley be May 2021, and still targeting end of year 2021 (this may require an out of cycle ballot

ACTION ITEM : Device Metric needs to have spreadsheet completed (John Rhoads)

DoF:  Alerting Strategies (incl. DeviceAlert)

  • Todd Cooper provided a back drop for Alert
  • Rick noted that other folks are doing work on Alert resource (more FHIR Server)
    • Rick mentioned his mention is tied to subscription approach (e.g., DiVinici)
    • Todd noted alerting from/to devices are different and HCD intends to make this very clear (and in a way that is consistent and synergistic) 
    • Rick noted previously Subscription resource now split into 'Subscription' + 'Topic'
      • This was done so those using subscription would publish topic
  • DeviceAlert resource definition Review (John Rhoads)
    • John showed spreadsheet providing Path, Type, Binding, Multiplicity, Definition, Comment, etc... providing informational and current state representation of alert.
    • Noted that IEEE has many alerts - embedded in the nomenclature
    • IEEE is a recognized, have an OID, and a FHIR page - tooling can expand 
    • John Garguilo mentioned to Rick about the RTMMS and nomenclature source
    • Todd mentioned the IG has two parts in which getting the solid "stuff" concrete and further cook
    • Topic is a new resource spun off from Subscription resource providing the topics allowed to subscribe to... (various channels to establish) EHR will predefine topic in which one can choose topic to "listen for"...
    • Rick mentioned and encourage folks in HCD to create a Device Alert Topic and test out in next FHIR Connectathon track...

DoF:  Server Performance re. Scaling for Patient Monitored data (e.g., SDC)

  • (Stefan Schlichting) provided background for Rick
    • High volume of data from many devices...
    • When testing with FHIR Server, the date was written but buffer was overloaded... 
  • Rick mentioned maybe trying bulk data, but no easy answer at this point...
    • May need some other folks from FHIR team who are on server side to hear about...
    • Todd asked if this could be a good topic at DevDays - and that we should give notification in the IGs
    • Rick mentioned some discussion in FIREi how to "page" the reading... also mentioned "Patch" feature
    • Rick suggested running this issue by and contacting James Agnew lead developer on HAPI 
  • ACTION ITEM: Rick suggested doing a write up and creating a GForge tracker item so the item would get a time to talk about it with FHIR team...  assign it FIREi team.  Stefan Schlichting Stefan Schlichling agreed to do the write-up against the HTTP.html page (description of FHIR use of REST)

FHIR "Localization" (issue brought forth by Paul Schluter)

  • Todd Cooper introduced topic for Rick
  • Localization: a display provides the overall 
    • How does one do the Localization in FHIR
    • There is a "text field" which could be used, but if you need to note a localization such as what language is used (e.g., Japanese, German, etc)... Rick was thinking this may have to be a unique resource for each language...
    • This might fall into an extension...
    • As a general construct, localization would include things like language, geographical info - but doesn't appear to be a place to do this...
  • Rick mentioned this seems like a common issue, but not aware of answer - so he will look into it and get back to HCD (will bring it up in Q2 today)

FHIR support for non-time-based sample arrays

  • Bjorn Andesen provided background...
  • Rick suggested getting a tracker issue in before R5 - to relax cardinality and propose the additional fields needed such as "basic science"

Done. Ticket can be found at #25034

Device Static vs. Dynamic Data in FHIR

  • This does appear to be a good use case for PATCH - perhaps HCD could participate in a Connectathon ; HAPI and ZONK both support PATCH but might not support the item 
  • ACTION ITEM: To do in parallel with Performance item above. (Stefan Karl)

HCD / FHIR Planning

  • End of Oct moving to JIRA (system will be down on a Friday and come back up on a Sunday) Lloyd will notifiy when NOT to file a new tracker...
Thursday, Q2
  • IHE PCD Update
    • PCD "Reorganization" Proposals Update
    • Alerting:  ACM CPs for timing diag. and fatigue
    • SDPi Public Comment
    • DEC FHIR Option
    • Boston Agenda Review

  • NIST V2 Tool Update & Infrastructure

  • Review of Projects, Status

  • HL7 DEV General Roadmap and Planning

  • Carry-over DEV topics 
  • Adjourn 





Action items