This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "2017-09-29 Learning Health Systems Call"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "{| <!-- ******** CHANGE chair and scribe ON NEXT LINES *******************--> | width="10%" colspan="1" align="right"|'''Facilitator''' | width="35%" colspan="1" align="left...")
 
Line 90: Line 90:
 
*Scribe: Emma Jones
 
*Scribe: Emma Jones
  
−
*Motion to approve previous call minutes, <insert link>: <mover>/<seconder>
+
*Motion to approve previous call minutes, [http://wiki.hl7.org/index.php?title=2017-09-22_Learning_Health_Systems_Call] : Stephen moved/Emma second
 +
'''ISA Feedback from LHS'''
 +
*Include DCTM in ISA as an emerging standard. Emma will write up and present to the group to vote on next meeting. Include:
 +
**Section and Interoperability Need
 +
***Including the link to the ISA Interoperability Need page would be ideal.
 +
**Suggestion
 +
***Can include corrections, changes to adoption level, maturity, etc.
 +
**Rationale
 +
***Be realistic, practical, don’t oversell
 +
***Be as positive as possible though
 +
*Suggestion to include as an emerging standard
 +
*Evelyn will send how to write it up
 +
'''Michelle review of FHIR elements '''
 +
*Michelle present current FHIR Care Team, Practitioners, Related persons attributes
 +
**Practitioner.qualification
 +
***how is the qualification valueset different from the roleCode
 +
***binding to valueset is specific to particular implementation guide
 +
***Suggestion to include NUCC as example - binding to NUCC is a US approach
 +
***We've agreed to use NUCC in the role element. Agreement there is a lot of overlap.
 +
***If following the individual regardless of care team or patient
 +
***Do the person still carry the qualification when it's irrelevant? E.g. ortho surgeon who specializes in knee replacement but have to do a hip replacement because that's what is needed.
 +
**relatedPerson responsibility
 +
***observation.code and observation focal-subject.reference (extension)
 +
**All family medicine docs are not of the same specialty
 +
***practitionerRole.specialty - can be a grouping of "services offered" Can be 0..*
 +
**Who's the parent, child, POA, etc Currently 0..1 which means single relationship. Can use patient.contact for additional attributes.
 +
**relatedPerson and Patient contact are not at the careTeam level
 +
**CareTeam.participant.role is specific to each care team
 +
**CarePlan and assign performer to specific activity - Care team is in the middle
 +
*Suggestions
 +
**Related person should be 0..* - can use relationship to be parent and use patient.contact.relationship
 +
*Function and role are synonymous or two different things
 +
*Function and responsibility are different
 +
2 spots use role - practitionerRole where specialty goes
 +
participant.role
 +
participant. [later dropped]
 +
participant.responsibility [later changed to function]
 +
careTeam.participant.role - became careTeam.function
 +
practitionerRole.code is a poorly defined valueset (PA to fix)
 +
practitionRole.specialty have the NUCC like grouping
 +
practitioner.role is independent of the patient
 +
Michelle will send the spreadsheet
 +
Next week - Emma will discuss DCP
 +
Care manager qualification certification roles
 +
Evelyn: my ask is to consider use case where the care team may be using a non clinical IT system (no EHR). Are they using a care management platform

Revision as of 22:03, 29 September 2017

Facilitator Russell Leftwich Note taker(s) Emma Jones
Attendee Name Affiliation


X Russell Leftwich InterSystems
John Roberts Tennessee Department of Health
X Stephen Chu Individual
X Evelyn Gallego ONC
Kathy Walsh LabCorp
Asim Muhammad Philips Research Europe
X Laura Heermann-Langford Intermountain Healthcare
X Emma Jones Allscripts
Jeff Brown Cancerlinq
X Lisa Nelson Individual
Dave Carlson VA
Chris Melo Phillips Healthcare
X Michelle Miller Cerner
Benjamin Kummer Columbia University
Matt Rhan
X Michael Padula
X Joseph Quinn
X Thomson Kuhn
X Rob Hausum
Serafina Versaggi VA

Minutes

  • Chair: Russell Leftwich
  • Scribe: Emma Jones
  • Motion to approve previous call minutes, [1] : Stephen moved/Emma second

ISA Feedback from LHS

  • Include DCTM in ISA as an emerging standard. Emma will write up and present to the group to vote on next meeting. Include:
    • Section and Interoperability Need
      • Including the link to the ISA Interoperability Need page would be ideal.
    • Suggestion
      • Can include corrections, changes to adoption level, maturity, etc.
    • Rationale
      • Be realistic, practical, don’t oversell
      • Be as positive as possible though
  • Suggestion to include as an emerging standard
  • Evelyn will send how to write it up

Michelle review of FHIR elements

  • Michelle present current FHIR Care Team, Practitioners, Related persons attributes
    • Practitioner.qualification
      • how is the qualification valueset different from the roleCode
      • binding to valueset is specific to particular implementation guide
      • Suggestion to include NUCC as example - binding to NUCC is a US approach
      • We've agreed to use NUCC in the role element. Agreement there is a lot of overlap.
      • If following the individual regardless of care team or patient
      • Do the person still carry the qualification when it's irrelevant? E.g. ortho surgeon who specializes in knee replacement but have to do a hip replacement because that's what is needed.
    • relatedPerson responsibility
      • observation.code and observation focal-subject.reference (extension)
    • All family medicine docs are not of the same specialty
      • practitionerRole.specialty - can be a grouping of "services offered" Can be 0..*
    • Who's the parent, child, POA, etc Currently 0..1 which means single relationship. Can use patient.contact for additional attributes.
    • relatedPerson and Patient contact are not at the careTeam level
    • CareTeam.participant.role is specific to each care team
    • CarePlan and assign performer to specific activity - Care team is in the middle
  • Suggestions
    • Related person should be 0..* - can use relationship to be parent and use patient.contact.relationship
  • Function and role are synonymous or two different things
  • Function and responsibility are different

2 spots use role - practitionerRole where specialty goes participant.role participant. [later dropped] participant.responsibility [later changed to function] careTeam.participant.role - became careTeam.function practitionerRole.code is a poorly defined valueset (PA to fix) practitionRole.specialty have the NUCC like grouping practitioner.role is independent of the patient Michelle will send the spreadsheet Next week - Emma will discuss DCP Care manager qualification certification roles Evelyn: my ask is to consider use case where the care team may be using a non clinical IT system (no EHR). Are they using a care management platform

Retrieved from "https://wiki.hl7.org/w/index.php?title=2017-09-29_Learning_Health_Systems_Call&oldid=146892"