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

Difference between revisions of "May 2016 WGM Montreal, Canada: May 8 to May 13"

From HL7Wiki
Jump to navigation Jump to search
Line 149: Line 149:
  
 
Present:
 
Present:
−
 
+
* This session was hosted by O&O. Please refer to their minutes.
  
 
<BR>
 
<BR>
 
Minutes:
 
Minutes:
−
 
+
*A request order does not represent a fulfillment request. To fulfill you need to post the resource with a tag.
−
 
+
*Alternative is to use an operation or message.
−
 
+
**Or use a Task resource.
 +
*Lloyd has displayed a request pattern slide.
 +
*The attribute category represents the different states of a request.
 +
*The request can be nested.
 +
*Also the request have response resource as answer.
 +
*The task resource has been developed.
 +
*Besides that there is also and OrderSet and Protocol resource.
 +
*The name order will be changed to request, such as MedicationRequest.
 +
*How to use transaction reversal in combination with task is not yet done.
 +
*Test in Connectathon where a patient with a Iphone was requested to schedule a lab-test and after confirming the plan set out to make a ask for the lab. In the end the physician was instructed by a task to look at the results.
 +
*Discussion on the word or versus request. Some want to word order back again, but this is discussion that has already been dealt with.
 +
*Need for examples of use cases. These seem to have been worked out for certain use cases.
 +
*Discussion whether dosage instructions should be a datatype.
 +
*The term request would also refer to referrals, procedure and appointment.
  
 
<BR>
 
<BR>

Revision as of 13:58, 10 May 2016


Montreal (Quebec) Canada, WGM - May 2016 Patient Care WG Meeting Approved agenda:




Montreal WGM - May 2016. Patient Care WG Meeting Meeting Minutes

  • Sunday, May 8 - International Council Meeting
- No PCWG meeting


Patient Care WGM, Monday, May 9, 2016


Monday Q1

Chair: Jay Lyle
Scribe: Michelle Miller

Attendees

  • Ayres,Elaine (NIH/Clinical Center)
  • Campbell,Keith (U.S. Department of Veterans Affairs)
  • Duteau,Katherine (DDI)
  • Jones,Emma (Allscripts)
  • Leftwich,Russ (InterSystems)
  • Lyle,Jay (Ockham Information Services LLC)
  • Miller,Michelle (Cerner Corporation)
  • Newman,Shu-Fang (University Of Washington Medical Center)
  • Nguyen,Viet (Lockheed Martin, Health and Life Sciences)
  • Owens,M'Lynda (Cognosante, LLC)
  • Parker,David (Defined IT, Inc.)
  • Popat,Amit (Epic)
  • Pyke,David (Ready Computing)
  • Rehwoldt,Greg (Utah)
  • Spielman,Matthew (InterSystems)
  • Tan,Michael (NICTIZ Nat.ICT.Inst.Healthc.Netherlands)


Minutes

  • Reviewed FHIR announcements
    • Timeline
      • Thurs, May 12 - Q3
      • Wed, June 1
        • All resource and IG proposals for STU3 have been completed, reviewed by WG and submitted
        • Connectathon tracks for Sept have been proposed
        • Feedback on gForge submitted to FMG
      • Sun, July 17 - Substantive content freeze for ballot -- core resources
      • Sun, July 24 - Total content freeze, start of QA
      • Wed, Aug 10 (midnight) - All QA changes applied
      • Fri, Aug 12 - FHIR ballot opens
      • Fri, Sept 12 - FHIR ballot closes
      • Fri, Sept 16 - FHIR triage complete and ballot content loaded to gForge (or alternate)
      • Sept 17-23 - Baltimore WGM
      • Sun, Dec 11
        • Reconciliation complete/substantive changes applied?
        • Just over 10 weeks
        • Will re-evaluate at Baltimore based on volume of ballot comments
      • Dec 31 - Publish
    • FMM level survey
      • One input, but could have other considerations
      • Take into account volume of responses
      • Prioritized resources -- top 20 -- goal is at least level 3
        • Patient
        • Observation
        • Practitioner
        • Medication
        • Condition -- owned by Patient Care WG
        • Allergy -- owned by Patient Care WG
        • Org
        • Encounter
        • MedOrder
        • DiagReport
        • Immunization
        • MedStatement
        • DiagOrder
        • MedAdmin
        • Bundle
        • MedDispense
        • CarePlan -- owned by Patient Care WG
        • Procedure -- owned by Patient Care WG
        • Conformance
        • Person
  • Work group health
    • Mission and Charter updated
      • Motion: Michael/Amit Abstain - 0, Negative - 0, Approve - 10
    • SWOT needs updated
      • Motion: Amit/Katherine Abstain - 0, Negative - 0, Approve - 10
  • FMM Level Goals
    • Resource (current FMM level) Goal
    • AllergyIntolerance (1) 3
    • procedure (1) 3
    • Goal (1) 3
    • Careplan (1) 3
    • Condition (2) 3
    • Careteam (0) 2 or 3
    • FamilyMemberHistory (1) 2 or 3
    • QuestionnaireResponse (2) 2
    • Questionnaire (0) 2
    • ClinicalImpression (0) 1 or 2
    • ReferralRequest (1) 1
    • ProcedureRequest (1) 1
    • Linkage (0) 1
    • Flag (1) 1
    • Communication (1) 1
    • CommunicationRequest (1) 1


Monday Q2

  • Plenary Session
- No PCWG meeting



Patient Care Monday Q3

Present:

  • This session was hosted by O&O. Please refer to their minutes.


Minutes:

  • A request order does not represent a fulfillment request. To fulfill you need to post the resource with a tag.
  • Alternative is to use an operation or message.
    • Or use a Task resource.
  • Lloyd has displayed a request pattern slide.
  • The attribute category represents the different states of a request.
  • The request can be nested.
  • Also the request have response resource as answer.
  • The task resource has been developed.
  • Besides that there is also and OrderSet and Protocol resource.
  • The name order will be changed to request, such as MedicationRequest.
  • How to use transaction reversal in combination with task is not yet done.
  • Test in Connectathon where a patient with a Iphone was requested to schedule a lab-test and after confirming the plan set out to make a ask for the lab. In the end the physician was instructed by a task to look at the results.
  • Discussion on the word or versus request. Some want to word order back again, but this is discussion that has already been dealt with.
  • Need for examples of use cases. These seem to have been worked out for certain use cases.
  • Discussion whether dosage instructions should be a datatype.
  • The term request would also refer to referrals, procedure and appointment.


Patient Care Monday Q4

Present:



Minutes:




Patient Care Monday Q5: Placeholder for extra meeting if necessary

Present:



Minutes:




Patient Care WGM, Tuesday, May 10, 2016


Patient Care Tuesday Q1

Chair: Jay Lyle
Scribe: Emma Jones

Attendees

  • Heerman-Langford,Laura (Intermountain)
  • Matney, Susan (Intermountain)
  • Maclean, Andrea (Infoway)
  • Huff, Stan(Intermountain)
  • Lyle, Lyle (Contractor)

On phone

  • Patrick Langford
  • Ken Kawamoto


Minutes: Agenda:

  • PSS - investigative action - looking at a project to take existing patient care concepts and represent it in CIMI
    • PSS thru DESD (response) -
      • need to review dates,
      • choice of data, artifacts (need a list),
      • draft output patterns - some are in CIMI, others may be needed,
      • draft output of the composition - how large will CIMI get? medicalPsychiatric condition will be left out for now. CIMI will need to look at conditions/findings
  • Review of scope (the below are specific to ulcers)
    • Skin assessment model
    • Braden - note made that Braden Q is proprietary and request compensation to be used (ONC is aware)
    • review example ADL



Patient Care Tuesday Q2

Present:


Minutes:



Patient Care Tuesday Q3

Present:



Minutes:




Patient Care Tuesday Q4

Present:



Agenda:

  1. OO: multiple answers to a question in a questionnaire
  2. Negation
    1. PSS: asking MnM for participation; CQI & PA had expressed interest. Also need to articulate how to engage with existing design & guidance -- design constraints based on legacy environment are requirements.
    2. Plan
      1. Collection of use cases
      2. Classification of use cases
        1. Including cases out of scope to clarify boundaries
      3. Identification of principles
      4. Identification of what can be provided to design groups / how feedback can be addressed
    3. Review classification current state; solicit gaps

Minutes:



Patient Care WGM, Wednesday, May 11, 2016


Patient Care Wednesday Q1

Present:


Minutes:



Patient Care Wednesday Q2

Present:


Minutes:



Patient Care Wednesday Q3

Present:



Minutes:




Patient Care Wednesday Q4

Present:



Minutes:




Patient Care WGM, Thursday, May 12, 2016


Patient Care Thursday Q1

Present:


Minutes:



Patient Care Thursday Q2 (PCWG, SDWG, Template Joint meeting)

Present:


Minutes:




Patient Care Thursday Q3

Present:



Minutes:




Patient Care Thursday Q4

Present:



Minutes:




Patient Care WGM, Friday, May 13, 2016


Patient Care Friday Q0: PCWG Co-Chairs meeting

NOTE: co-chairs to determine whether this will be moved to Thursday Q-Lunch

Present:


Minutes:




Patient Care Friday Q1


(1) Template WG meeting

- PCWG representative(s) to attend

(2) Agenda: open

- Possible: Clinical Connectathon



Present:


Minutes:



Patient Care Friday Q2


Agenda: open

Possible: Clinical Connectathon


Present:


Minutes:



Patient Care Friday Q3


Agenda: open

Possible: Clinical Connectathon


Present:



Minutes:




Patient Care Friday Q4


Agenda: open

Possible: Clinical Connectathon


Present:



Minutes:



Retrieved from "https://wiki.hl7.org/w/index.php?title=May_2016_WGM_Montreal,_Canada:_May_8_to_May_13&oldid=119787"