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

2016-10-06 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
WebEx: https://cerner.webex.com/cerner/j.php?MTID=mfc8969c4f77244480beee61d31385e79

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


Elaine Ayres NIH/Department of Clinical Research Informatics
Stephen Chu
Eric Haas Haas Consulting
Rob Hausam Hausam Consulting LLC
Laura Heermann-Langford Intermountain Healthcare
Emma Jones Allscripts
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
Russell McDonell Telstra Health
Lloyd McKenzie Gevity (HL7 Canada)
Larry McKnight Cerner
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

Agenda Topics

  1. Agenda review
  2. Approve previous meeting minutes
    • Motion: <moved>/<seconded>
  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

Resource
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

Minutes

Prior Action Item Follow-up

gForge Change Requests

Adjourn

Adjourned at <hh:mm am/pm> <timezone>.

Meeting Outcomes

Actions
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.

Agenda

Agenda Topics

  1. Agenda review
  2. Approve previous meeting minutes 2016-09-29_Patient_Care_FHIR_Call
    • Motion: Rob/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

[2] 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

Resource
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

Minutes

Prior Action Item Follow-up

Drafted ClinicalNote_FHIR_Resource_Proposal

http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_id=677&tracker_item_id=8780 resolved as follows:
"If it's unstructured, but of known type (e.g. a text only referral letter or discharge summary or medication list), then the content should go in the narrative of the resource that would be used for the structured data.
If it's unstructured of unknown or potentially mixed, then using either Basic or perhaps Observation might be appropriate. Composition could be ok if the content is considered a document. DocumentReference wouldn't make sense because you're not referencing a document. Binary wouldn't make sense because you can't have narrative and there's no point making the narrative opaque and hard to render."

Recent Zulip chat: https://chat.fhir.org/#narrow/stream/implementers/topic/Physical.20Exam.20.26.20Review.20of.20Systems when Grahame said "the composition could be the entire contents, but then the contents would be just narrative - effectively, a document. The usual pattern would be for the Composition to wrap a resource that actually captures the clinical content"

gForge Change Requests

Block Vote 1

Block Vote 1 was planned for October 6, but attendees hadn't reviewed yet, so the vote is deferred until next week. Please let Michelle Miller know if you would like any items removed for further discussion.

Block Vote 2

Block Vote 2 planned for next week on Thurs, Oct 13. The first 4 were pulled from the Block Vote #1 due to small updates suggested in the resolution.

In Person

In Person Requests:

Discussion

Adjourn

Adjourned at 6:45PM Eastern

Meeting Outcomes

Actions
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.

Retrieved from "https://wiki.hl7.org/w/index.php?title=2016-10-06_Patient_Care_FHIR_Call&oldid=127262"