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

Difference between revisions of "Conformance Weekly Meeting 2018 07 02"

From HL7Wiki
Jump to navigation Jump to search
 
Line 31: Line 31:
  
 
*FHIR Strategy Discussion
 
*FHIR Strategy Discussion
−
** Grahame suggested a FHIR Connectathon idea, but there is not funding, NIST won't be able to commit
+
** Grahame suggested a FHIR Connectathon idea, but there is not funding, NIST won't be able to commit in September but can in January
 
** FHIR is an API without a single data model, need to focus on conformance testing
 
** FHIR is an API without a single data model, need to focus on conformance testing
 
** IHE is a way we can become more involved because they create profiles
 
** IHE is a way we can become more involved because they create profiles

Latest revision as of 14:06, 9 July 2018

Meeting Information

  • Date: Monday, July 2, 2018
  • Time: 10:00 am, North America Eastern Time (New York, GMT-04:00)
  • Phone Number: +1 515-739-1227
  • Pass Code: 732544
  • Web Meeting: Free Conference Call

Proposed Agenda Topics

  • Vote on Minutes
  • FHIR Strategy

Agenda Topics for Next Week

Topics to discuss:

  • Finalize for Baltimore
  • Ballot reconciliation of the standardized data type flavors library
  • Other running topics:
    • Length Discussion
    • FHIR Strategy

Discussion

  • Vote on Minutes from Cologne
    • Vote to approve Ioana/Frank 3/0/1
  • Action items from Cologne discussions:
    • Not much discussion, except on HL7 v2+
    • Interested in Connectathon track
    • Baltimore meeting with FHIR-I should discuss gaps between V2 conformance constructs and FHIR conformance constructs
    • Need discussion before meeting with FHIR-I, need to agree on gaps
    • IHE concerns about testing, want to bring to attention of the board, setup type with Joyce to discuss concerns, will try for Monday August 20, in this meeting
  • FHIR Strategy Discussion
    • Grahame suggested a FHIR Connectathon idea, but there is not funding, NIST won't be able to commit in September but can in January
    • FHIR is an API without a single data model, need to focus on conformance testing
    • IHE is a way we can become more involved because they create profiles
    • Work with ONC and other regulators
    • US Realm, Quality Measures will make a major impact because of the financial impact
    • Propose to do a gap analysis against FHIR, have this as a regular item, compare and contrast between V2 and FHIR
    • Invite Mathew Rahn to these calls, want to talk about gaps in current testing, need to wait for the rules to be released. ONC Interoperability Forum August 6-8, probably release more information on upcoming rules
    • Rob Snelick has list of conformance constructs used v2 testing need to compare with Structured Definition resource that is used for profiles in FHIR

Attendees

  • Nathan Bunker
  • Craig Newman
  • Ioana Singureanu
  • Didi Davis
  • Frank Oemig

Todo List

Discussion

Retrieved from "https://wiki.hl7.org/w/index.php?title=Conformance_Weekly_Meeting_2018_07_02&oldid=158820"