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

Difference between revisions of "AID 201709 Meeting in San Diego"

From HL7Wiki
Jump to navigation Jump to search
Line 18: Line 18:
 
##FHIR tools for implementers (Grahame Grieve + Lloyd Mckenzie)
 
##FHIR tools for implementers (Grahame Grieve + Lloyd Mckenzie)
 
##* A discussion of plans for the tooling eco-system for FHIR - what tools are available, what are planned, what is needed? + introduction to the tooling system documentation (work supported by the ONC)
 
##* A discussion of plans for the tooling eco-system for FHIR - what tools are available, what are planned, what is needed? + introduction to the tooling system documentation (work supported by the ONC)
##Presentation 4
+
##Bo Dagnall - Digital Health Platform
 
##Presentation 5
 
##Presentation 5
 
##Presentation 6
 
##Presentation 6

Revision as of 00:48, 10 September 2017

Return to: WGM Minutes > 2017 > September San Diego

This is the agenda of the AID WG for the WGM in San Diego, US, September 2017.

Sunday Q3/Q4

  • The Sunday PM session is a series of 20 minute talks (by default; sometimes a little longer) that focus on the 'implementation experiences'.
  • For presenters: the audience consists of fellow FHIR implementers, and as such the presentation should NOT be seen as a product showcase - the aim is to have max 5 minutes to introduce the product and its functionality, followed by a deep dive in things like the architectural approach, tools used, good/bad experiences with FHIR. The aim is for other implementers (even if they're not using the same architecture nor development platform as yours) to learn from your mistakes / development approach.

Agenda

  1. Administrative
  2. FHIR related presentations (please contact a co-chair to get a slot on the agenda)
    1. Mapping v2 to FHIR and vice versa (Corey Spears, Infor, US)
      • Detailed description to follow
    2. Vital needs for FHIR's continued success (Debi Willis, PatientLink, US)
      • Debi plans to speak about having a FHIR Endpoint Directory and an easier workflow for patients to authenticate (instead of having to log into each EHR every time they need their data). It is meant to be a session to present what they found during implementing FHIR in production settings, and to continue with an open discussion of ideas concerning how we might solve the problems.
    3. FHIR tools for implementers (Grahame Grieve + Lloyd Mckenzie)
      • A discussion of plans for the tooling eco-system for FHIR - what tools are available, what are planned, what is needed? + introduction to the tooling system documentation (work supported by the ONC)
    4. Bo Dagnall - Digital Health Platform
    5. Presentation 5
    6. Presentation 6
    7. Presentation 7
  3. Wrapping up
    • MOTION to disband the AID WG, and to continue its Sunday PM WGM activities in some other form (e.g. as part of FHIR Foundation, or as an Interest Group).
      • James: The wider mission of the AID WG (formerly known as: RIMBAA, or before that the Java SIG) has been to make sure the 'implementer community' (as opposed to the standards development community) is represented at HL7 WGMs. AID has acted as the voice of the (HL7 v3) implementers to suggest changes to the standards (when certain aspects of v3 were found to be impractical), and for years has mainly acted as a platform to exchange implementation best practices.
      • James: With the increasing focus of HL7 on FHIR (which itself does have a very active focus on the implementer community) we, as the co-chairs, have a sense of "mission accomplished". HL7 is finally listening to its implementer community, and has set up all sorts of channels to support that community and exchange ideas with that community (well, mainly FHIR, it could cater somewhat better to the HL7v2 and CDA implementer communities). AID doesn't wish to be a WG just for the sake of hanging around in a zombie like fashion - we've done what we wanted to do. Mission accomplished; case closed.
    • MOTION to close PSSs #550, and to request that (a) the TSC takes on the task to wrap up the project (with #1178) around 'Implementation Packages', and (b) that the CDA Product Management group takes on the task of managing the Software Implementation of CDA whitepaper - these efforts will be out of scope for our future activities.
  4. Adjournment