P1752 Working Group Meeting
Transcript of P1752 Working Group Meeting
Sponsored by IEEE Engineering in Medicine & Biology (EMB) Standards Committee
P1752 Working Group Meeting
26 June 2018
Teleconference
Attendance
Thisdocumentshowsattendancefrompreviouscallshttps://tinyurl.com/yc3oxg6q(linkinthechatwindowofjoin.me).Ifyouattendedthecall,pleaseverifythatyournameislisted– Ifnot,[email protected]
Putyournameandaffiliationinthechatwindowforattendancetoday.– Ifyournameisnotlisted,orifyouarejoiningonlyviaphone,pleaseemail
[email protected]“P1752WGcall”assubject
Attendanceisimportantfordeterminingvotingrights,sopleaserememberto“checkin”
VotingrightsaregrantedaccordingtotheP&PafterattendingtwoconsecutivecallsandbyexplicitrequesttotheSecretary
IEEEPatentPolicy
ParticipantshaveadutytoinformtheIEEE • ParticipantsshallinformtheIEEE(orcausetheIEEEtobeinformed)oftheidentity
ofeachholderofanypotentialEssentialPatentClaimsofwhichtheyarepersonallyawareiftheclaimsareownedorcontrolledbytheparticipantortheentitytheparticipantisfrom,employedby,orotherwiserepresents
• ParticipantsshouldinformtheIEEE(orcausetheIEEEtobeinformed)oftheidentityofanyotherholdersofpotentialEssentialPatentClaims
EarlyidentificationofholdersofpotentialEssentialPatentClaimsisencouraged
Slide#1
WaystoinformIEEE • CauseanLOAtobesubmittedtotheIEEE-SA([email protected]);or
• Providethechairofthisgroupwiththeidentityoftheholder(s)ofanyandallsuchclaimsassoonaspossible;or
• SpeakupnowandrespondtothisCallforPotentiallyEssentialPatentsIfanyoneinthismeetingispersonallyawareoftheholderofanypatentclaimsthatarepotentiallyessentialtoimplementationoftheproposedstandard(s)underconsiderationbythisgroupandthatarenotalreadythesubjectofanAcceptedLetterofAssurance,pleaserespondatthistimebyprovidingrelevantinformationtotheWGChair
Slide#2
OtherguidelinesforIEEEWGmeetings • AllIEEE-SAstandardsmeetingsshallbeconductedincompliancewithallapplicable
laws,includingantitrustandcompetitionlaws.• Don’tdiscusstheinterpretation,validity,oressentialityofpatents/patentclaims.
• Don’tdiscussspecificlicenserates,terms,orconditions.
• Relativecostsofdifferenttechnicalapproachesthatincluderelativecostsofpatentlicensingtermsmaybediscussedinstandardsdevelopmentmeetings.
• Technicalconsiderationsremaintheprimaryfocus
• Don’tdiscussorengageinthefixingofproductprices,allocationofcustomers,ordivisionofsalesmarkets.
• Don’tdiscussthestatusorsubstanceofongoingorthreatenedlitigation.
• Don’tbesilentifinappropriatetopicsarediscussed…doformallyobject.---------------------------------------------------------------
Formoredetails,seeIEEE-SAStandardsBoardOperationsManual,clause5.3.10andAntitrustandCompetitionPolicy:WhatYouNeedtoKnowathttp://standards.ieee.org/develop/policies/antitrust.pdf
Slide#3
Patent-relatedinformation
Thepatentpolicyandtheproceduresusedtoexecutethatpolicyaredocumentedinthe:
• IEEE-SAStandardsBoardBylaws(http://standards.ieee.org/develop/policies/bylaws/sect6-7.html#6)
• IEEE-SAStandardsBoardOperationsManual(http://standards.ieee.org/develop/policies/opman/sect6.html#6.3)
Materialaboutthepatentpolicyisavailableat
http://standards.ieee.org/about/sasb/patcom/materials.html
Ifyouhavequestions,contacttheIEEE-SAStandards
Slide#4
DeterminationofQuorumhttps://tinyurl.com/yc3oxg6q
ApprovalofAgenda 1. Attendance
2. CallforPatents3. Approvalofagendaandpriorminutes(ifquorumpresent)4. Updatesfromsubgroups5. Discussion:Clinicalsignificance,relationshiptoEHR,
OpenmHealthonFHIRwork6. Otherbusiness
ApprovalofPriorMinutes(May22,June5)
Update:PhysicalActivityandMobility(PA&M)SchemaSubgroup
Physical Activity & Mobility Sub-group
1. Attendance (7 members) 2. Got to know more members 3. Reviewed general plan (timelines) 4. Two tasks
• Task 1: A list of basic measures that apply to or maybe common to physical activities based on physiological changes, types of sensor measures about human movement that quantify PAM and correlate with an outcome measure. (Thanks to Norm, Pradeep, Simona, Agusti)
• Task 2: Important PAM attributes (clinical and non-clinical) • Clinically important (sleep attributes document reviewed)
5. Proposed approaches • Work in two teams (2 tasks)
6. Next Meeting: Thursday June 28, 2018 (11am to 11:30am Eastern Time) ! Ifyouwouldliketojoinoursubgroup,[email protected]@temple.edu
Physical Activity & Mobility Sub-group
Update:SleepSchemaSubgroup
Sleep Schema Subgroup Update (pg.1) ! SleepsubgroupmeetingheldonJune12,2018(1) Taskgroupleadshavereviewed/sharedtheirgroup’swork,theirexperience
andchallenges;(2) Taskgroupleadsaregettingreadytoleadthetransitionfromexploration
phasetodocument/reportpreparationphase(deliverablesofstage1);ThankstoAntoni,JoshandRay(3)Adjustedourstage1timeline(targetdate:July14,2018)(4)Discussedthestage2workpreparation
Sleep Schema Subgroup Update (pg.2) ! Executionaccordingtotheplan(1) Alltaskgroupsaremakingprogress(continueexploration)(2) Taskleadshavedrafted/sharedorwilldraft/sharethedocumentsiniMeet
! Actionitems(1)Eachtaskgroupwillprovideoverview/summaryoftheirdocumentinthenextsubgroupmeeting(July10,2018)(2)Review/Commentonthedraftdocumentsandtrytocompleteasscheduled(3)Leadsupcomingsyncup(July6,2018)viaemail(4)Formstage2taskgroupsandsearchleads
Sleep Schema Subgroup Update (pg.3) ! SleepSchemaMeetingSlides/Minutes:http://sites.ieee.org/sagroups-1752/sleep-subgroup-meeting-materials/! NextSubgroupMeeting:July10,201811:30amto12:30pm(EDT)! p1752.slack.comiscreatedforcollaboration.Ifinterested,[email protected]
! Reminder:liketojoinoursubgroup,[email protected]@philips.com
Discussion:Clinicalsignficance,relationshiptoEHR,OpenmHealthonFHIRwork
Open mHealth work outside of P1752 WG • We’reinYear1of3ofanNIHR24granttodevelopanddisseminatesemanticstandardsformobilehealth.Fundingisfor
• P1752work,secureIEEEapproval• DevelopOpenmHealthonFHIRtorelateOpenmHealthtothedominantEHRdataexchange
standard• Defineprocessofcommunitygovernanceoverpreferred/officialOpenmHealthschemasandOmH
onFHIRprofiles–willbedoneinconjunctionwithP1752
• mProvprovenancework
Using mHealth Data in Frontline Care • EHRistheworkflowtoolforfrontlineclinicians.FormHealthdatatobeusedinclinicalcare,ithastoget“into”theEHR.
• HL7FHIRistheemergingstandardAPIintoandoutoftheEHR.ForOpenmHealthtobeusedatthepointofcare,wemusthaveaFHIRequivalent
• OpenmHealthonFHIRworkisdrivenbyabasicusecase• Stepcountforpreventionofcardiovasculardisease• Cangeneralizetoco-managingotherphysicalactivity,sleep,mobility,etcdisorders
OpenmHealthonFHIRforClinicalmHealthUse
FHIR API endpoint
SMART-on-FHIR environment
mDATA-clin app
“R24 Server”
Sensors and data clouds
Data Store
* e.g., sum, avg, max, min
FHIR API endpoint (OmH instances in binary)
Shimmer
sensor data
sensor data
EHR data
SMART on
FHIR and FHIR server
basic computation
authenticate and map to OmH schemas
digital biomarkers
EHR System
OmH non-standard
mDATA-pt app
Shimmer
OmH schemas
mFHIR resources
HL7 FHIR • FastHealthcareInteroperabilityResources
• theycallschemas“resources”.ThereisagenericObservationresourcethatisconstrainedandextendedusingFHIRProfiles.
• FHIRImplementationGuidestelltheFHIRcommunityhowtouseresourcesandprofilesforspecificusecases
• FHIRhasitsownAPI(HAPI)
• TheOmHonFHIRImplementationGuide(underdevelopment)willguidemappingsofOpenmHealthschemastoFHIRObservationresources
• foreachOpenmHealthschema,therewillbeacorrespondingFHIRObservationProfile(akaOmHonFHIRProfile)
Looking forward at other topics • Importanttopics,likemetadataandprovenance• Theplanistocreateadditionalsubgroups:wehavealimitedamountofresources,sowillproceedwiththoseastimepermits
• Anyadditionalthoughtsfromthegroupaboutthetopicscoveredinthelastcoupleofcalls,namelyoverallschemadevelopmentandAPI
FutureWork
SummaryofActionItems
FutureMeetings
Upcoming Meetings • MainWG(pleasenotechangesfrompreviousannouncements)
• July17:8AMPacific[CANCELED]• August28:8AMPacific[NEWDATE]
• Sleepsubgroup• July10,20188:30amto9:30am(Pacific)
• PA&Msubgroup• June28,201811to11:30am(Eastern)• July12,201811to11:30am(Eastern)
Adjournment