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

Difference between revisions of "MnM Minutes WGM 201205 Vancouver"

From HL7Wiki
Jump to navigation Jump to search
Line 88: Line 88:
 
= Tuesday May 15 Q1 =
 
= Tuesday May 15 Q1 =
 
== Attendees ==
 
== Attendees ==
Woody Beeler, David Hay, Tanya Achilles, Dale Nelson, Mark Tucker, Ann Wrightson, Lloyd  McKenzie, Brian Pech, Grahame Grieve, Andy Stechishin, Charlie McCay, Steve Fine,  Jay Lyle
+
Woody Beeler, David Hay, Tanya Achilles, Dale Nelson, Mark Tucker, Ann Wrightson, Lloyd  McKenzie, Brian Pech, Grahame Grieve, Andy Stechishin, Charlie McCay, Steve Fine,  Jay Lyle, Rik Smithies, Grahame Greive, Ewout Kramer, Abdul-Malik Shakir, Charlie Mead, Peter Hendler
  
 
== Agenda ==
 
== Agenda ==
 
===FHIR Methodology - Profiles and Extensions===
 
===FHIR Methodology - Profiles and Extensions===
 +
Q: Are profiles necessary for the definition/use of extensions?
 +
A: Yes extensions are defined by profiles. Some Profiles will only be 'grab bags' of extensions
 +
 +
Q: Are profiles part of the core specification?
 +
A: Profiles are expected to be balloted separately from the core specification (much like implementation guides), the specification of profiles and extension is part of the core specification.
 +
 +
Q: What are drvinign design principles behind FHIR's extension mechanism
 +
A: Static wire format. 'Z' segment problem - I have received blob of data or collisions of content/naming. Leveraged experience of OBX segment.
 +
 +
Full principle: in order to deliver a specification for all user you need to deliver a specification that meets all users needs - must have an extension mechanism
  
 
= Tuesday May 15 Q2 =
 
= Tuesday May 15 Q2 =

Revision as of 16:18, 15 May 2012

Return to MnM Minutes for 2012

Sunday Jan. 15 Q3

Attendees

Woody Beeler, Jean Duteau, Austin Kreisler, Lloyd McKenzie, Rik Smithies, Andy Stechishin, Mead Walker, Grahame Grieve, Dale Nelson, Adel Ghemallah, Amnon Shabo, Lee Coller, Ann Wrightson, Adam Chee

Agenda

Establish Agenda for WGM from Hot Topics and FHIR

Steps:

  • Reviewed the existing Hot Topics
  • Reviewed when FHIR was going to be discussed in other committees
  • Updated the Agenda with the proper quarters noted.

Monday May 14 Q1

Attendees

Woody Beeler, Abdul-Malik Shakir, Lloyd McKenzie, Ann Wrightson, Ewout Kramer

Agenda

SAIF Artifact Definition & Implementation Guide

Started discussing the list of SAIF Artifacts to be defined from the SAIF Artifact List page. Re-categorized this based on current views of requirements, including the anticipated inclusion of FHIR in the forthcoming cycles. Lloyd McKenzie collected and edited a Word Document of the result of this discussion. It was agreed to by those present and will be attached to these minutes and used to update the SAIF Artifact List page by gwb.

Abdul-Malik Shakir agreed to take on Project Lead for this project and Woody Beeler agreed to be the facilitator for the project. We will schedule a call to re-invigorate this definition activity.

Monday May 14 Q2

Attendees

McKenzie, Beeler - Failed to reach quorum

Agenda

Ballot Reconciliation for Core Principles R2

Discussed the issues raised on documentation of "isDocumentCharacteristic". Agreed to a strategy to correct, and that would issue second ballot on this item only.

Ballot Reconciliation for RIM R5

Considered how to respond to votes. Most related to "isDocumentCharacteristic" (above). Will treat as non-significant change, and not re-ballot.


All these decisions will be revisited on a Reconciliation Conference Call.

Monday May 14 Q3

Attendees

Woody Beeler, Lee Coller, David Hay, Linda Bird, Henry Wijaya, Ewout Kramer, Rik Smithies, Tanya Achilles, Dale Nelson, Paul Knapp, Mark Tucker, Piers Hollott, Ann Wrightson, Bo Dagnell, Lloyd McKenzie, Brian Pech, Grahame Grieve, Rajan Rai

Agenda

FHIR Data Types and Extant Data Types R3 Requests

Questions :

  • Do we do an R3?
  • If so when? and
  • What is the content difference?

ISSUES from FHIR:

  • Will need to consider, with respect to FHIR, how to handle choices (selection of data type at instance time.)
  • Grieve: "Lack of a typed identifier is a serious omission in V3" (most noticeable in CDA)

FHIR Changes in re R2:

  • Structure of PQ with originalText
  • Relaxing constraints on: TEL, CD, II
  • Text content exists everywhere
  • Additional nullFlavors - "process error", and "as text"
  • Simpler version of GTS that might be of use in other settings

From R3 Page

The Data Types R3 Wiki page will be re-written to reflect these decisions. The following list is intended to summarize what is in scope for R3:

  • Update IETF RFC number under Language data type (BASIC) from RFC 3066 to RFC 5646 (or the latest RFC number) (Wendy Huang)
  • Address the issues raised by turn "II.scope into a mandatory attribute"
  • Add note to integrity Check about it's utility with digital signatures
  • Add ability to flag lists as unsorted.
  • PIVL is unable to express that an interval starts at a time relative to another event.
  • Make it explicitly obvious that relative URLs are allowed in CDA documents for URL types.
  • Add a property to the CD datatype as "valueSetDefinition" with a data type of ED intended to contain the CTS 2 (or possibly other) definition of the value set.

Whence DT R3?

Should follow the first cycle of FHIR deployment to gain experience before trying to tie down the R3 changes upon which FHIR is dependent.

Ergo: Initiate Data Type 3 project proposal discussion in January WGM 2013.

Moved: Grieve/Beeler Unanimous

Tuesday May 15 Q1

Attendees

Woody Beeler, David Hay, Tanya Achilles, Dale Nelson, Mark Tucker, Ann Wrightson, Lloyd McKenzie, Brian Pech, Grahame Grieve, Andy Stechishin, Charlie McCay, Steve Fine, Jay Lyle, Rik Smithies, Grahame Greive, Ewout Kramer, Abdul-Malik Shakir, Charlie Mead, Peter Hendler

Agenda

FHIR Methodology - Profiles and Extensions

Q: Are profiles necessary for the definition/use of extensions? A: Yes extensions are defined by profiles. Some Profiles will only be 'grab bags' of extensions

Q: Are profiles part of the core specification? A: Profiles are expected to be balloted separately from the core specification (much like implementation guides), the specification of profiles and extension is part of the core specification.

Q: What are drvinign design principles behind FHIR's extension mechanism A: Static wire format. 'Z' segment problem - I have received blob of data or collisions of content/naming. Leveraged experience of OBX segment.

Full principle: in order to deliver a specification for all user you need to deliver a specification that meets all users needs - must have an extension mechanism

Tuesday May 15 Q2

Attendees

Agenda

FHIR - Governance and Ballot Plans

Tuesday May 15 Q4

Attendees

Agenda

Condition/CNOD from March Harmonization

Wednesday May 16 Q1

Attendees

Agenda

FHIR Vocabulary

Wednesday May 16 Q3

Attendees

Agenda

ActRelationshipType Clean Up and Organizers

Thursday May 17 Evening

Attendees

Agenda

Schedule 2012 Harmonization

Facilitators' Reports

Friday May 18 Q1

Attendees

Agenda

MnM Business and Planning Mtg