This wiki has undergone a migration to Confluence found Here

2016-10-27 Patient Care FHIR Call

From HL7Wiki
Jump to navigation Jump to search

Meeting Information

Patient Care FHIR Resources Conference Call

Location: Conference Call
Phone Number: +1 770-657-9270
Participant Passcode: 943377

Date: 2016-10-27
Time: 5-6:30pm ET
Facilitator Michelle M Miller Note taker(s) Michelle M Miller
Attendee Name Affiliation

X Elaine Ayres NIH/Department of Clinical Research Informatics
X Stephen Chu Australian Digital Health Agency
X Tracey Coleman Allscripts
Eric Haas Haas Consulting
Rob Hausam Hausam Consulting LLC
Laura Heermann-Langford Intermountain Healthcare
X Emma Jones Allscripts
X Russ Leftwich InterSystems
Tony Little Optum 360
Jay Lyle Ockham Information Services LLC, VA
Sarah Maulden VA
Hank Mayers ReliaTech Consulting
Jim McClay Univ of Nebraska Medical Center
X Rob McClure MD Partners
Russell McDonell Telstra Health
Lloyd McKenzie Gevity (HL7 Canada)
Larry McKnight Cerner
X Michelle M Miller Cerner
Lisa Nelson Life Over Time Solutions
Viet Nguyen Lockheed Martin, Systems Made Simple
M'Lynda Owens Cognosante
Craig Parker Intermountain Healthcare
Scott Robertson Kaiser Permanente
Simon Sum Academy of Nutrition and Dietetics
Iona Thraen Dept of Veterans Affairs
Quorum Requirements Met: yes


Agenda Topics

  1. Agenda review
  2. Approve previous meeting minutes 2016-10-20_Patient_Care_FHIR_Call
    • Motion: Stephen/Russ
  3. Prior Action Item Follow-up
  4. gForge change request

Supporting Information

STU 3 Timeline

From FHIR_Ballot_Prep

  • Sun Oct. 9
    • Last date for change requests (subsequent change requests are auto-punted to release 4)
  • Sun Oct. 30
    • NIBs due for any IGs balloting in the Jan. cycle
  • Sun Nov. 20
    • All ballot reconciliation complete
  • Sun Nov. 27
    • All substantive changes applied to Core
  • Sun Dec. 4
    • Content freeze for ballot & connectathon & publication QA review
  • Sun Dec. 24
    • QA review complete, Qa changes begin being applied
  • Dec 29 - Jan 3ish
    • Publish

FHIR Maturity Levels

[1] Level 3 requires the artifact has been verified by the work group as meeting the DSTU_2_QA_guidelines and has been subject to a round of formal balloting; has at least 10 implementer comments recorded in the tracker drawn from at least 3 organizations resulting in at least one substantive change

Current FMM Level Goal FMM Level QA Status QA Reviewer Implementation Comments
AllergyIntolerance 1 3 Michelle Argonaut
Condition 2 3 Michelle Argonaut
Procedure 1 3 Michelle Argonaut
CarePlan 1 3 Michelle Argonaut
Goal 1 3 Michelle
QuestionnaireResponse 2 2 Lloyd Lloyd will QA to get to level 3
Questionnaire 0 2 Lloyd Lloyd will QA to get to level 3
CareTeam 0 2 NA Michelle Aggressive goal (e.g. whether we'll get the implementations needed)
FamilyMemberHistory 1 2 NA NA Aggressive goal (e.g. whether we'll get the implementations needed)
ClinicalImpression 0 1 NA NA
ReferralRequest 1 1 NA NA
ProcedureRequest 1 1 NA NA
Linkage 0 1 NA NA
Flag 1 1 NA NA
Communication 1 1 NA NA
CommunicationRequest 1 1 NA NA

Note: Bold denotes top 20 resource based on survey
Note: Contraindication and Risk Assessment are owned by CDS, not Patient Care


Prior Action Item Follow-up

gForge Change Requests

FHIR Publication / Backlog Status

  • 119 unresolved tracker items (99 ballot + 19 high maturity resource non-ballot comments + 1 quick win) to resolve by Nov 20
    • 29 scheduled in Block Vote 2
    • 37 scheduled in Block Vote 3
    • 18 requested input from vocab (value set related ballot comments)
    • 13 waiting for input
    • 5 waiting to be scheduled (joint with OO or in person requests)
    • 17 ready for discussion during our weekly conference call

Vote on Block Vote 2

Scheduled for Oct 27. Vote: Russ/Elaine: 4-0-2

Block Vote 3 Preview

Schedule for Nov 3

In Person (Pending Schedule)

In Person Requests -- in the process of being scheduled

Joint with OO -- in the process of being scheduled



Backlog - Ready to Discuss Next Week

Resources with higher maturity - target FMM Level 3


CarePlan / Goal

  • Better define the careplan.activity.outcome field - discussion occurred during the CarePlan (Wed, Oct 26) conference call. PCWG agreed that outcome is needed on both the activity and goal. For example, a goal of losing 20 pounds might include activities to 1) reduce caloric intake via diet and 2)exercise 30 minutes per day. The outcome associated with the weight loss goal might be an observation with the updated body weight whereas the outcome on the activity side might be the number of calories burned via exercise or calories consumed via diet. Next steps:
    • expand/clarify the outcome definitions on both the activity and goal.
    • harmonize the outcome structure to allow the activity to reference an observation (like the goal outcome allows)
    • bind the outcome codeableconcepts to value sets



Questionnaire / QuestionnaireResponse

Care Team


Adjourned at 6:35pm Eastern

Meeting Outcomes

Next Meeting/Preliminary Agenda Items
  1. Agenda review
  2. Approve previous meeting minutes
    • Motion: <moved>/<seconded> Abstain - <#>, Negative - <#>, Approve - <#>
  3. gForge change request

© 2012 Health Level Seven® International. All rights reserved.