<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Segoe UI";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:394789928;
mso-list-type:hybrid;
mso-list-template-ids:-279405908 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Hello Web3D Medical Working Group, Drs Hammond and Kopper:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The following RFI from the NITRD and NSF came across my radar yesterday.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">https://www.nitrd.gov/news/RFI-action-on-interoperability-of-medical-devices-data-and-platforms.aspx<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Overnight, it occurred to me that Web3D could have some ‘skin’ in this activity, particularly in light of efforts to harmonize with HL7. Whereas the notice mostly seems to seek input from more traditional healthcare providers and groups
working in more traditional healthcare venues, there are groups whose focus are mobile devices and sensors that I know are keen to respond and gain involvement in the conference cited by this announcement. Additionally, the verbiage of the RFI recognizes
that coordination of care delivery occurs across many venues outside these traditional settings and thus coordinating and normalizing the data generated from devices and sensors agnostic to the setting of use is the aim of the whole. Because X3D addresses
many nascent applications and thus benefits to health promotion and care delivery, this may be an excellent opportunity to create awareness for the utility of these as-of-yet unrealized benefits and promote inclusionary language in future funding opportunities.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In review of the announcement, the following is where I see an opportunity for Web3D to respond:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="mso-list:Ignore">1)<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>The overview section refers to the need for interoperability to support “closed loop, autonomous and semi-autonomous” systems in order to “decrease medical errors and reduce provider burden… across healthcare facilities” An important
component of the HL7 FHIR integration will be to enable current (GIS, 3D print, VR) technologies to be integrated in interoperable data exchange, and future (H-Anim, advanced visualization, AR/MR) care delivery and research applications.<o:p></o:p></p>
<p class="MsoListParagraph"><o:p> </o:p></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="mso-list:Ignore">2)<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>The bulk of the future vision section in the RFI addresses a need for medical devices to emulate “industrial controls and autonomous systems in the automotive, aviation and energy sectors” Whereas I am personally naïve of what these
systems are in cited industries and how they work, I have the impression that the Web3D constituency, both within and outside of the Medical Working Group have a deep understanding of not only what those systems are, but how X3D supports data conformity and
persistence and other attributes within these systems or at a minimum the handshakes between components that support these processes.
<o:p></o:p></p>
<p class="MsoListParagraph"><o:p> </o:p></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="mso-list:Ignore">3)<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>The RFI cites “provider burden” and “burnout” as confounders to the issue it aims to address. It is my impression that one of the great benefits of the 3D rendering modalities supported by X3D is a reduction of cognitive load to clinicians
and researchers (possibly patients or caregivers?) who have tasks requiring the use of “big data.” A good example of this kind of (yet unrealized) thinking is in the big annual NSF program now underway aimed at supporting the workforce of the future. They
have funded one or more medical use cases so far in each year of the program. This additionally could be an opportunity to enlighten individuals in the broader Agency to the benefits of a future application from this group.<o:p></o:p></p>
<p class="MsoListParagraph"><o:p> </o:p></p>
<p class="MsoNormal">Given there is a focused, perhaps niche set of benefits X3D can offer, I am wondering if there might be a short response developed which could result in an invitation to the conference cited and more inclusive language in future funding
announcements. Could you please share with me you thoughts?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Many thanks for your time and attention, and please let me know of you have any questions.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#002060">Best,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#002060"> </span><o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-family:"Arial",sans-serif;color:#002060">Davera Gabriel, RN</span></b><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#002060">Research Informaticist</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-family:"Arial",sans-serif;color:#002060">Clinical Research Informatics<br>
Duke Clinical Research Institute<br>
From Thought Leadership to Clinical Practice</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#002060">300 W. Morgan St.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#002060">Durham, NC 27701<br>
office: 530-723-8356 <br>
<u><a href="mailto:davera.gabriel@duke.edu"><span style="color:#002060">davera.gabriel@duke.edu</span></a></u><br>
<a href="http://www.dcri.org/"><span style="color:#002060">www.dcri.org</span></a></span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#4472C4"> </span><o:p></o:p></p>
<p class="MsoNormal"><b><i><span style="color:#44546A">“</span></i></b><b><i><span style="font-size:10.0pt;font-family:"Segoe UI",sans-serif;color:#44546A">Few are those that see with their own eyes and feel with their own hearts.” – Albert Einstein</span></i></b><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>