HL7 H.S.I Working Group

Minutes October 08, 2015

Atlanta WGM

Agenda:

  • Approve Minutes:
  • IHE SDC profile and FHIR DSTU Collaboration
  • FHIR: Freeze Document Manifest? – it will be added to the frozen list.
  • IHE mACM coordination with the IHE PCD FHIR Project (and Device Alert prototying)
  • Next WGM Planning
  • January WGM
  • Weekly/Bi-Weekly Calls
  • IHE RFD Use in HL7
  • Tracker Spreadsheet – strategy for WG engagement
  • Long term plan for tracking /coordination
  • Review content for …
  • Integrity/updating
  • WG engagement
  • HSI WG Health (Laura)

Thursday Q3

Attendees:

Virginia Barnes,

Keith Boone,

Todd Cooper,

Angelique Cortez,

Farrah Darbouze,

Didi Davis (Sequia project- staff support for eHealth exchange, Carequality),

Richard Ettema,

Laura Heermann,

Emma Jones,

Eric Larsen,

Virginia Lorenzi

Lloyd McKenzie,

Chris Melo

Riki Merrick,

John Moehrke,

Amit Propat,

David Pyke,

Scott Robertson,

Agenda review:

  1. Review and approve minutes from last call ( Motion to approve minutes as documented – David, Keith Boone, no further discussion, against: 0, abstain: 14, in favor: 2
  2. Freezing the documentManifest – SD agreed to make this request – because IHE has used these resource HIS endorse freezing of that resource
  3. Frozen resources will NOT change until the next major release, UNLESS implementer community and FMG approve it
  4. HST WG Health – we got gold stars 
  5. SDC discussion – Slides from Angelique
  6. Pre-population of the form – there is emerging work in CDS area that is applicable to CQI – would be good to have neutral convener (FHIR-I / FMG / HSI) host all WGs interested in “fetch / pre-population” to harmonize the definition and the methods of what we are assigning (data element vs. specific query language for example)
  7. FHIR resources used in SDC: Questionaire (PC), QuestionaireResponse (PC), DataElement (OO), ValueSet (Vocab); reference patient, but don’t profile, acknowledge need for provenance and ??, but not profiled
  8. HL7 mechanism for a WG of WGs when profiling using resources owned by different WGs – raise up to FMG as governance question / structure issue – this ties into the tracker spreadsheet maturity
  9. Bigger question is not the HL7 cross WG coordination for SDC, but how do align or share the same artifacts with IHE – requesting assistance with how to move forward in keeping materials between HL7 and IHE artifacts in sync
  10. HSI should help convene and make WGs aware of overlapping project to avoid having 2 solutions to the same problem
  11. SDC FHIR solution (published Sept 2015) was informed by IHE SDC profile (published Sept 2014) and merged with FHIR methodology – also more limited use case of Questionaire and QuestionaireResponse, not the re-direct
  12. HSI to communicate the collaboration success of SDC to the larger HL7 and IHE community
  13. FHIR documentation now clearly identifies the owners of the resources – but how would owners find out that these resources are used in profiles – we do have a profile registry and they have space to identify the resources that are used – that is on the profile creator
  14. When your WG reference a resource you should keep an eye on changes
  15. Is there a way to see changes between versions?
  16. history page for major deltas from prior versions
  17. gForge tracker release association for ALL changes
  18. source commits into the FHIR build, if desired
  1. General discussion of how HSI can achieve coordination
  2. HL7 does not have a good mechanism of a work group of work groups.
  3. Having issues with folks like QI Core referencing their work as CORE.
  4. The question is how is the coordination done and how does HSI assist?
  5. Challenge is not so much the coordination between the workgroups as much as the coordination of the work that is happening within the IHE space and the work happening in parallel within HL7. How do we align and start to share some of the same artifacts
  6. The issue has to do with how to manage the change requests within IHE and HL7.
  7. We need to convene a session to bring teams together to look at and discuss overlaps.
  8. Changes in FHIR – to fundamental resource is by the owning workgroup, in this case there are 3 working groups owning the four resources used.
  9. SDC started out with single solution through IHE.
  10. How can HSI help promulgate-communicate this success representing it to the TSC and others.
  11. Through the ballot process….
  12. Markings on the FHIR resource page?
  13. Meeting times
  14. call schedule for the regular call – proposals for the doodle poll – not Tuesday / Wednesday – Thursday at 2-3 PM / Friday mornings after 9 AM EDT / Monday anytime
  15. Jan 2016 WGM – move to earlier in the week in order to allow to connect with other workgroups – Tuesday Q4 and Thursday Q4, if needed
  16. Note: January Monday Q3-4 Order response meeting
  17. Regroup in January for May
  18. Look at setting up joint meetings with projects in flight. – such as CDS with ballot reconciliation.
  19. Request joint with CDS wed Q2 for joint GAO ballot reconciliation.
  20. PCC CMAT profile – may want to run through

END OF Q3

  1. Revise the Device PSS – looked at IHE mACM
  2. Bringing our IHE experience with RDF – cross reference to questionnaire / also should think about how SDC and DAF into that – tell Anna to
  3. Tracker spreadsheet
  4. Long term planning
  5. Content review

Thursday Q4

Attendees:

Todd Cooper,

Laura Heermann,

Scott Robertson,

Virginia Lorenzi

Keith Boone,

Didi Davis (Sequia project- staff support for eHealth exchange, Carequality),

Emma Jones,

Keith recounted the FHIR Resources leveraged in IHE profiles:

TBD – Need to create actual list

From proposed frozen list …

AllergyIntolerance

Bundle

ConceptMap … in use in PCC (CMAP)

Condition [PC asked to have taken off the list]

Conformance

DataElement

DiagnosticReport

[DocumentManifest requested by SD to be added to the list]

DocumentReference

Encounter

List

Medication

MedicationStatement

NamingSystem

Observation

OperationDefinition

OperationOutcome

Organization

Parameters

Patient

Practitioner

Procedure

RelatedPerson

SearchParameter

StructureDefinition

ValueSet

NOTE: Order NOT being on the list is good; additional work needed + workflow …

(Keith) IHE GAO – Guideline Accountable Ordering

• Keith presented the draft GAO PSS

• Proposal is that HSI is a co-sponsor of the

◦ Keith Moved … Emma seconded

◦ Discussion:

▪ (Scott) Why is HSI a co-sponsor? What is different between this and ticking the box in the PSS for “IHE” (for example) and being a co-sponsor?

▪ HSI is NOT a governing domain

▪ But because the project was initiated out of HSI; want to be attached to the project as a driver

▪ (Scott) HSI should get some credit for the project and that it exists.

▪ (Emma) For inpatient too? Or only outpatient?

▪ GAO is independent of out or in patient

▪ @ US legislation, it only applies to ambulatory

▪

◦ Motion carried unanimously

(Todd Cooper) IHE mACM coordination with IHE PCD FHIR Project (and DeviceAlert prototyping)

Todd reported out work being done in HL7 DEV WG around FHIR alert communication

IHE RFD Use in HL7

(Keith) HSI needs to create a roadmap

vs. a list of projects to look up in a worksheet)

@ 3 year plan

Ballots

Joint Projects

@ SD … they have Word document that is reviewed the first quarter of each WGM

Mission … Charter … Coordination

Review content for …

Integrity / updating

WG engagement

HSI WG Health (Laura): GOLD STAR!!!

JANUARY MEETING

1 PCC CMAP Profile … should go through vocab in HL7

2 MHD is being updated to DSTU2 … via SD?

3 Send representatives to coordinate with these groups in January

4 Joint with CDS with ballot to reconcile (they will host)

(Keith) Why can’t HSI sponsor projects?

Rationale? Need to explain the principle

Ask TSC? (e.g., Austin and others have asked for the rationale)

For example, HSI for adoption ballot for IHE MHD (+ DocumentReference and DocumentManifest)

For example, CDS … “why are you coming here with GAO?”

ACTION: Push through T3SD Co-Chairs (Freida & Andy)