...
- Status of JIRA items for changes in the FHIR core documentation of Device, DeviceDescription, and related resources - are they there yet and in good order?
- The upcoming Working Group Meeting (WGM)
- Agenda items suggested so far
Attendees
Todd Cooper, John Dyer, Martin Hurrell, Stefan Karl, Tom Kowalczyk, Filip Manevski, Koichiro Matsumoto, Joe Quinn, Brian Reinhold, Elliot Siver, Marti Velezis
Meeting Notes
References
Meeting Notes from May WGM Meeting Notes: May 2022 Virtual - IEEE 11073 General Committee / IEEE-PoCD WG / HL7 DEV Devices WG
...
(Full Q) (Martin Hurrell) Intra-procedural Anesthesia FHIR IG Work (proposed Thursday Q1)Device Alerting (John Rhoads)Housekeeping - (proposed Wednesday Q1)Required Documentations (e.g., SWOT, 3 Year Plan, others )items such as PHD publicationReview:See OO joint topics belowReview DEV related Jira ticketsIdentify priority discussion topics for joint OO sessions (communicate to OO)
(FHIR Core Resource Changes) - DEV discussion (prior to joint meeting with OO)PHD Status update/report out (Martin R. + Javier??)Report Out from IHE-DEV proceedings (from Spring F2F WG meetings week of Apr 26-28, 2022)Test and Test Tooling Report out (NIST and others...)RTMMS + "V2+" Ongoing work...(Paul Schluter) Nomenclature - RTM status update
Co-Chair Report Out(John Rhoads) Directions of / from HL7 to be aware of...
- Joint Sessions:
OO (FHIR Core Resource Changes) - joint with OO (Tuesday Q1 + Friday Q1 - )Review:Not schedule Tuesday Q1 unless there is something significant to discuss (noting overlap with IEEE)Thursday Q1 OO has joint meeting time set aside (OO, BRR, DEV)Friday Q1 (OO, DEV, (BRR, CQI, mHealth) FHIR-I)Discussion will include review of Jira tickets + device Word document etc.
- MHealth (Thursday Q2)
- FHIR-I - see above for Q1 Friday w OO (waiting on FHIR-I Agenda to be formulated??)
Friday Q1/2:Gemini Approved Project DiscussionOpen discussion on New architectures within "regulated personal health space"e.g., Digital Therapeutics/Personal Health Navigation Ecosystem - Areas being progressed in ISO/TC-215How should DEV reposition ourselves given SOMD kinds of regulated devices...related to new HL7 Organizational direction...
Test Tooling Landscape (Todd Cooper)
Meeting with the Physical Activity Alliance and the American Heart Association regarding project proposal (Q3 Thursday)- Members/Co-Chairs - Please add new topics here (add your name "( @ ... )" so we know who to ask about the topic):
- (Todd Cooper ) "What is a 'Device'?"
- Review general "heads up" content proposed for the updated Device resource description
- Review the content being added to the SDPi 1.0 TF-1 front matter related to the scope of the IHE DEV TF (this will be the first version of the broadened IHE domain (vs. PCD only)
- Discuss whether and who and where to include and publish the broader question of "What is a 'Device'?" material
- Consider Martin's work around establishing a metamodel w/ attributes, looking for "clusters" and leveraging that to address some common uses of the term: device
- Link in the previous material from Paper: What is a device? confluence page
- Determine the best place to publish this article - for example as an article in the FHIR space similar to workflow and other topics (and linkable from the device-related resources!)
- A previous project proposal (pre PSS) was floated for this topic but never fully advanced .. should it be now?
- All in favor of Dr. Martin Hurrell being the Editor-in-Chief, raise your hand! (you cannot vote, Martin ...)
- Is this a Gemini (joint IHE-HL7 article) and should fly under that flag? Or simply an HL7 internal paper? (it will be used / leveraged in the IHE DEV TF-1 discussion)
- (Todd Cooper ) DeviceAlert project:
- Consider leveraging the "What is a 'Device'?" metamodel mentioned previously to explain what is unique about the alerting devices & DEVAL space but without having to include the whole topic (again, linkable article)
- not computable
- This is a similar concern to the ISO/IEC JWG7 "SES" concern and is tied in with requirements from 60601-1-8, 11073-10702, and similar standards
- Alert management systems (DIS / DAS / cDAS etc.) all include support for configuring in accordance with implementation environment polices, e.g., around escalation BUT ...
- Is there value in making this COMPUTABLE (as is the case with security infrastructure) and if so, how?
- (Todd Cooper ) MDIRA Project Update (esp. relevance to SDPi + EP group discussions)
- Note: DEV can meet w/ OO on Friday Q1 as spillover from Thursday or if additional discussion needed around Device resource
- ...
- DISCUSS: (John Donnelly ) Alert Policy
- Should the DeviceAlert project also include something around a care provider's "alert policy"?
- By analogy, security experts who see "risk management" as 100% a security issue, always talk about managing security policies
- Medical device alerting includes similar policies; however, they are never formalized (via standards) and are definitely not computable
- This is a similar concern to the ISO/IEC JWG7 "SES" concern and is tied in with requirements from 60601-1-8, 11073-10702, and similar standards
- Alert management systems (DIS / DAS / cDAS etc.) all include support for configuring in accordance with implementation environment polices, e.g., around escalation BUT ...
- Is there value in making this COMPUTABLE (as is the case with security infrastructure) and if so, how?
- Consider leveraging the "What is a 'Device'?" metamodel mentioned previously to explain what is unique about the alerting devices & DEVAL space but without having to include the whole topic (again, linkable article)
- (Todd Cooper ) MDIRA Project Update (esp. relevance to SDPi + EP group discussions)
- (Todd Cooper ) "What is a 'Device'?"
- Note: DEV can meet w/ OO on Friday Q1 as spillover from Thursday or if additional discussion needed around Device resource
- ...
...